collector which is 32 bit and while doing some operation on 64 system so getting crash

Hello CHOWDHURY, EKBAL (GE Digital),

Thank you for posting in Q&A forum.

It sounds like you're dealing with a compatibility or runtime issue in a 32-bit application (ihServerToServerCollector.exe) running on a 64-bit system.

Here are some general steps to diagnose and potentially resolve this issue:

Steps to Diagnose the Issue:

1.Check for Dependencies: Ensure that all the required 32-bit libraries and dependencies that your application relies on are available on the 64-bit system.

2.Examine the Stack Trace:

Look at the stack trace provided in the crash dump to identify where exactly the crash is occurring. Tools like WinDbg can be helpful for this purpose.

3.Verify Configuration Settings:

Verify that the environment settings (like PATH variables, registry settings, and environment variables) on the problematic customer’s machine match those on systems where the application is working correctly.

4.Check Permissions: Ensure that the application has all necessary permissions to execute operations, particularly in directories or resources it needs to access.

5.Review Recent Changes:

Look into any recent changes made to the customer’s system that might have affected the application, such as OS updates or the installation of new software.

Steps to Potentially Resolve the Issue

1.Recompile for 64-bit: If possible, recompile your application as a 64-bit binary. This can help eliminate compatibility issues associated with running 32-bit applications on a 64-bit OS.

2.Install 32-bit Libraries: Install any missing 32-bit libraries that your application might depend on. On Windows, make sure that the 32-bit versions of the required Visual C++ Redistributables are installed.

3.Use Compatibility Mode: Try running the application in compatibility mode for a 32-bit version of Windows. Right-click on the executable, go to Properties, select the Compatibility tab, and choose an appropriate Windows version.

4.Update or Patch the Application: Ensure the application is up to date with the latest patches or updates from the vendor or development team.

5.Consult Event Logs: Check the Windows Event Viewer for any additional error messages or logs related to the crash. This can provide more context about the failure.

6.Contact Support: If the issue persists, consider contacting the software vendor's support team with detailed crash logs and environment details for more tailored assistance.

I hope the information above is helpful.

If you have any questions or concerns, please feel free to let us know.

Best Regards,

Daisy Zhou

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.