What is a Script Error with about 22 windows when trying to launch Mechanical within Workbench?
jonespa87
Member Posts: 50
A number of student are receiving a script error this semester when trying to launch Mechanical from within Workbench. I do not know what is causing it. To eliminate the error, we use the Microsoft Task Manager to stop the launching of Mechanical and delete their roaming ANSYS profile folder.
It seems to happen when the students are using an application here at Penn State Erie called Weblabs. It is a web based application that is used to log into a university computer remotely.
Thank you,
Phil
Answers
Hello Phil,
Could you please post the pic of the error as we are not permitted to open files.
What version is being used also?
Thanks You.
Geo
Sure. Geo.
Oops. We are using ANSYS 2020R2.
Phil
Hi Geo,
I was just checking in to see if you were able to see my screen shot of the script error.
Thanks,
Phil
Hi Geo,
The error occurred again today in Ms. Jill Johnson's class. This is the message I received from Ms. Johnson. They were not using the Weblabs application. It happened while in the computer lab.
Hi Phil!
I had this happen to one of my students for the first time today!
We messed around with a few things, like going to different PCs and checking the storage on his V and X drives and we didn't get anywhere. I had him put in a help request to IT to have them reset the ANSYS files in his profile, but I suspect you've already tried this and have had no luck. He was working on the Allen Wrench lab when it happened, which is the first non-linear lab we do in my FEA course.
For now, I have him working with another student, but if you get any help back from ANSYS, let me know what you find.
Jill
Hi Geo,
I am just following up the script error we are receiving in Mechanical. It continues to plague us here at Penn State University, Erie.
Thanks,
Phil
Hello,
I apologize for the delay.
Can you try the following:
As the user seeing the issue, close all ANSYS Programs.
browse to the following:
%APPDATA%\Ansys
Rename the v202 directory to: v202.old
Now, try again.
Best Regards,
Geo
If that does not work, please check the following thread:
https://forum.ansys.com/discussion/11845/getting-a-script-error-code-80004005-line-45377