Ansys Workbench Not Opening
Athina Dollison
I have faced the same issue in my laptop with windows 10 OS that time I thought that it may be the system fault that is why I consulted with windows error code 0x8024a105 but there I got to know that system is absolutely fine. It may be the software issue. Suggest me the solution.
It may be a hardware issue: ie your graphics can't load the software. If you find ANSYS in the start menu can you try and launch Fluent as that may give us something more diagnostic. Supported hardware is listed here: -by-role/it-professionals/platform-support
I am facing a certain issue while opening Workbench 19.2. I am attaching a picture along with this description. I can see 'Initializing Licensing' under the main symbol before the software shuts down. I had received a notice that my license was going to expire in roughly 22 days the same day, it was not yet expired. However since the issue has started I have tried opening the software after renewing the student license (/forum/forums/topic/how-can-i-renew-ansys-student-version-license/) I followed all the instructions here. It is still not opening.
I have created a new thread, with the title 'Workbench 19.2 Software not opening, Closes without displaying any error' and will message on that thread from now. I am just posting my message here too, if it could solve the potential problem.
Good morning
I have a similar problem but it is not a student version, I use the university license and i didn't change anything and it works with others. The problem is that when i try to run workbench it loads and within seconds it closes without errors.
can you help me for that?
Good day folks!
I am here to learn how to use ansys. I will be opening multiple discussions in the upcoming days, as I have been assigned a test assignment to see if I can find a job within a company as for in my graduation assignment. (I study Aeronautical Engineering, a bachelor degree, but never worked with ansys before)...
SO my first question... I have downloaded and installed ansys (student version) on my persona desktop, but now... the million dollar question:
How do I open or launch Ansys for the first time?
There were a few previous inquiry posts about this specific problem for older ANSYS versions. I have the Student version of ANSYS 2024 R1, and when conducting a simple Static Analysis on Workbench, Discovery would work but Mechanical would encounter that classic "Error while waiting for Mechanical initialization to complete. Either the application crashed or Workbench lost communication with it." error. On a side note, I've tried to open software like Fluent, CFX, Optislang, and so forth and they all worked without exception when on their own. Though when meshing from workbench, thus requiring Mechanical as I understand, same problem descrined previously would occur.
I had the same problem a few months ago on ANSYS 2023 R1 (on the same machine, which could be a helpful detail), and it was just Mechanical (which ironically is the one I need the most) that didn't open. I gave up and preferred to go for other FEA alternatives. But I will be needing ANSYS for a course next semester so it's now all different.
In it, ANSYS employee "tsiriaks" shows a maneuver that seemed to help OP solve the issue. It was presumed that the issue was related to the Path environment variable. I have reinstalled ANSYS 2024 R1 many times without solving the issue. Update my driver to the latest version, problem persists.
It was first asked whether there were "any .err file under E:Installed softwareAnsysANSYS IncANSYS Student ?". I couldn't find a way to access that directory as I don't have an E: driver, nor did I find a part in the thread that insinuated that OP had an E: drive. Tried to look for the files mentioned in the directory but didn't find them.I'm probably stuck in a very trivial cul-de-sac, so I beg your indulgence if it happens to be the case.
Here again, it's essentially the same problem, I don't have an E: drive. Now, knowing all of this, what should I do instead in my case? I will leave attached screenshots of "ping %computername% -4" command, DirectX Diagnostic window, and Device Manager (expanding Display Adapter) as it was the sole data shared by the user (I doubt they'll be helpful though).
3rd, 4th and 5th one encountered an error. It essentially the same message for all of them, with the subtle difference that the error code is "0x80070005" for the 3rd one (I'll attach this one for reference), and "0x80004005" for both 4th and 5th one. I've googled both errors to see what I can do but all the resources that I found presented somewhat equivocal explanation for a tech-layman like me. I hope this at least narrows down the leeway of action to help better identify the source of the problem- if you can provide me with further hints on next steps to carry on from here, it will be much appreciated. Thanks again!
Despite initially thinking I successfully executed those commands as an administrator, it so happened that the problem was that trivial (with far-fetched cirucmstances, genuinely sorry for that). What happened subsequently is that all DLLs were registered successfully. After trying to open Mechanical from Workbench, I had a colossal amount of script error pop-ups.
I did circumvent this problem but renaming some Ansys AppData file to itself+ _old which kind of refreshed those files. From a static structural analysis on Wb, I used a dummy geometry from Discovery, then double clicked model, and Mechanical finally opened up showing its interface for the first time. That said, my joy was short-lived as after trying to load the Geometry, I had this pop-up.
I followed the directory shown in the pop-up (though the file names where partly Caps and mostly lower cases, I made sure there were just these ones that could potentially correspond to it) and I didn't find any AnsysWBDumpFile. Instead I found 2 Ansys files, one just named "Ansys" the other ANSYS with my desktop username.241. Nothing notable in the first file, though the second has this:
Further information.
The error 80004005 or 0x80004005 relates to lack of permissions.
It appears that AnsysWBU.exe (Ansys Mechanical) is atempting to execute a Windows script object (Jscript or Cscript) and is being blocked.
As I mentioned before, this occurs for two reasons:
- Windows scripting libraries are not registered.
- A Protection program / endpoint program is preventing AnsysWBU.exe from executing scripts.
I think there was a little miscomprehension. Those very errors were no more pertinent as Mechanical is I can open it with no problem on its own. That said, crash occurs whenever I try to import a geometry with the pop-up present in second attached image in my last message. I registered all DLLs, Uninstalled all of my Antiviruses, Spent a few hours making sure no Windows Firewall or else were interfering with the program. It's really that it's likely another additionnal element is causing this issue and I really doubt it could be a script problem at this point (though it initially was). Mechanical is unable to attach geometry. I wanted to check out what the AnsysWBDumpFile had, but it was nowhere to be found. I precised a few things earlier to rule out as many things as possible, as I tried both Discovery and SpaceClaim, imported an IGS CAD file, and so far the problem persists.
In Windows, run System Information (msinfo32.exe)
In System Information > Software Environment > Windows Error Reporting
In the list, Search for AnsysWBU.exe"
Look for a few of the recent timestamps when you had the crash.
Copy/paste a few of most recent the messages in your reply.
I also want to share this Windows Error Reporting message that occured several time in the inbox along with that AnsysWBU one, which lets me think it may not be unrelated to Mechanical's crashes. Hopefully it could be another resource to look for the solution (as I skim through, it is rather WB-related):
Also, though very probably trivial, I'd like to remention that I had no file path in this Mechanical Directory "File> Options... > Analysis Settings and Solutions > Analysis data management > Scratch solver" which seemed to cause the problem for some. I created a purely arbitrary null folder on my desktop and assigned as path. I really doubt it's the cause of the problem, but better safe I guess.
I'd also mention that the geometries I tried to import were, an IGS file (SW), scdoc, and dsco. I have to select "All files" as type of files rather than "Mechanical Files" where they do not appear. If loading them from WB then opening Mechanical, I will have that pop-up beofre Mechanical crashing. If importing them from Mechanical, they won't be attached but the app doesn't crash and have a pop-up until I manually close it. Trivial details in sum, but I'm trying to optimize my chances of solving this problem before tomorrow.
And with the resetting .old maneuver after the "DISM /Online /Cleanup-Image /RestoreHealth" command, the problem persists. I'm gonna have to suppose reinstalling it is my only option as of now, and I'll try to check out the ISO files technique. Though I'm not exactly sure to what site you're referring to in the PS:.
I'm out of home right now and installing all of 2024 R1 is going to take a gigantic amount of resources, so I might not be able to provide updates before the maintenance. If the problem remains unsolved, while ruling out everything we mentioned earlier, what should I deduce to be a plausible profound cause to this?
In which case, are there any resources that do recommend good laptops that are likely to not have any root problem with ANSYS (while having a decent to powerful performance)? Any additional ones for the specific installation of ANSYS as described? Thanks again, and Best Regards
Before you reinstall, you may want to try uninstalling the Prerequisites from Windows Add/Remove programs, then reinstalling them via the ProductConfig.exe
So,
Run ProductConfig.exe
Check Required Prerequisties. It will list the currently installed ones, and that none are needed. Make a note of these.
In Windows Add/Remove programs, find each of the Prerequisites, and uninstall them.
Reboot.
Run ProductConfig.exe again.
Check Required Prerequisties...It should now list several that are needed.
Reinstall prerequisites.