Learning Forum

[tim.dukes]

​ 🛈​ This post originally contained file attachments which have been removed in compliance with the updated Ansys Learning Forum Terms & Conditions​

​

Hi Support 

 

Do you know what may cause the error in the images above?

 

Fatal Error - ANSYS

 

The application has terminated unexpectedly due to an unhandled exception.

The full details of the exception follow:

System.Runtime.InteropServices.COMException (0x50004005):

Error HRESULT e_FAIL has been returned from a call to COM component.

 

Edit - Have attached the temp files if of use.

[Brian Bueno]

Tim Dukes

Is this happening when AIM is launched or during a simulation?

[tim.dukes]

Hi Brian

 

Thanks for the reply. Customer reply below.

 

I get this message every time when I try to start AIM within the Space Claim/ Workbench and when I start it  as a stand alone application as well.

In a short, I am not able to start AIM at all. At the same time Space Claim and Live seems to be alright.

[tim.dukes]

Brian Bueno

 

Hi Brian

Do you know if the log files point to anything or is there anything that we can try here. Standard things already tried - Un-install / Re-install. remove temp files.

[Brian Bueno]

Tim Dukes 

It seems like HRESULT E_FAIL is not necessarily specific to AIM.  Do you know if the user installed using Run as Administrator, or has full administrator privileges on the PC?

It looks like AIM is checking out the license and then checking it back in almost immediately, usually within about 30 seconds.

I'm waiting on some feedback about this.

[Brian Bueno]

Tim Dukes

I would suggest getting a copy of their msinfo32 output.

Open the command line and run 'msinfo32' without quotes, then save and send the .NFO file.

[tim.dukes]

Brian Bueno

 

Thanks for looking into this see customers replies below and also the msinfo.nfo file attached.

 

A: I have full admin rights on this machine. (although some policies as Windows update are managed by company’s rules). I have installed Discovery as admin.

 

I have reinstalled Discovery, but AIM does not work again – the same error as before. All other programs appears to be fine , including Space Claim and Live.

AIM crashes have started after BIOS update. DELL release at least on BIOS update per month and under their warranty policy it must be applied. It has happened  a few times that ANSYS DISCOVERY  crashes after BIOUS updates.

🛈 This post originally contained file attachments which have been removed in compliance with the updated Ansys Learning Forum Terms & Conditions

[tim.dukes]

Brian Bueno

 

Hi Brian

 

Customer has asked if there has been anything found from the above. They have also contacted DELL who recommend reverting back to the old BIOS but this hasn't helped and are still getting the same error. 

[Brian Bueno]

Tim Dukes 

I'm still waiting on some feedback from the AIM experts who may have seen this in the past.  If the user has time they may want to try the following:

Reinstall the new BIOS, run the web based update checker from Dell (Chrome works best) or install command update and run all the windows updates.  Then reinstall AIM if the problem continues to appear.

[Brian Bueno]

Tim Dukes

Have the user try the following steps in this order:

1. In an Administrator console:

• • Run ...ANSYS Incv{version}FrameworkbinWin64Ans.DriverSetup.exe --force --unregister
  • Run ...ANSYS Incv{version}FrameworkbinWin64Ans.DriverSetup.exe --force --register
  • Try running AIM

       2. Update Intel + Nvidia and/or AMD graphics drivers. (if this is a laptop please ensure the Intel ones are updated as well)

• • Ensure you get new drivers directly from NV, Intel and AMD and not from Dell.
  • Run step (1)
  • Try running AIM

       3. Finally - we have seen issues with some machines getting corrupted but have not managed to determine why in these cases repairing the install of the Redistributable runtimes from Microsoft has resolved the issues:

[tim.dukes]

Brian Bueno

Hi Brian customer has tried all three steps in order and the error still persists?

 

Anything else we can try is it worth arranging a web session?

[Brian Bueno]

Tim Dukes

What version of AIM are they using?

If they have not already tried it I would suggest deleting : %APPDATA%/Ansys there are occasions when we have seen some files corrupted which cause a number of issues.

[tim.dukes]

Hi Brian

Deleting the appdata files worked!

Many thanks for your help with this.

Tim