MicroFocus / ADM-FT-ToolsLauncher

Other
12 stars 8 forks source link

Unhandled Exception when invoking FTToolsLauncher #99

Closed S-278 closed 1 week ago

S-278 commented 3 weeks ago

Tool FTToolsLauncher

Describe the bug When I simply invoke the FTToolsLauncher.exe from the command prompt, I get an Unhandled Exception (see screenshot).

To Reproduce Steps to reproduce the behavior:

  1. Download FTToolsLauncher_net48.exe from the latest release on this repo
  2. Invoke FTToolsLauncher_net48.exe from Windows administrator command prompt (the same behavior occurs when I supply a paramfile)

Expected behavior The app launches and shows a "help" or "usage" text.

Screenshots Screenshot 2024-06-14 141336

OS and testing tools (please complete the following information):

Additional context I have verified that .NET 4.8 is installed (C:\Windows\Microsoft.NET\Framework\v4.0.30319 exists)

I have also verified that the exe file hash matches the hash given in the release.

dorin7bogdan commented 3 weeks ago

Hello,

The specific System.AccessViolationException indicates an attempt to read or write to protected memory, which suggests a memory corruption issue.

Here are some potential causes and solutions:

1. Corrupted .NET Framework Installation: Even though .NET 4.8 is installed, the installation might be corrupted. Solution: Repair the .NET Framework installation. You can do this via the Control Panel by finding .NET Framework and selecting the repair option, or you can use the .NET Framework Repair Tool from Microsoft.

2. Third-Party Interference: Certain third-party software, especially those that interact with system memory or provide security features, can cause memory access issues. Solution: Temporarily disable any third-party antivirus or security software and see if the problem persists. If it does, try running your application in a clean boot state to see if any background services or applications are causing the issue.

3. Faulty Hardware: Memory corruption can sometimes be due to faulty hardware, particularly RAM. Solution: Run memory diagnostic tools like the Windows Memory Diagnostic to check for any issues with your RAM.


Here are steps to repair .NET Framework installation:

You can also run the Windows Memory Diagnostic by following these steps:

S-278 commented 1 week ago

Hello,

Thank you very much for your reply! I tested some of this and eventually found out the issue was due to corrupted folder permissions in Windows. After moving the executable to a different folder, it runs normally.