{"id":369822,"date":"2024-06-04T16:06:17","date_gmt":"2024-06-04T16:06:17","guid":{"rendered":"\/forum\/forums\/reply\/369822\/"},"modified":"2024-06-04T16:06:17","modified_gmt":"2024-06-04T16:06:17","slug":"369822","status":"publish","type":"reply","link":"https:\/\/innovationspace.ansys.com\/forum\/forums\/reply\/369822\/","title":{"rendered":"Reply To: ANSYS Mechanical won&#8217;t open and stays on Blank Gray Screen (Path environment va)"},"content":{"rendered":"<p>&lt;p&gt;Hello again Gary,&lt;\/p&gt;&lt;p&gt;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.&nbsp;&lt;\/p&gt;&lt;p&gt;<img loading=\"lazy\" decoding=\"async\" src=\"\/forum\/wp-content\/uploads\/sites\/2\/2024\/06\/04-06-2024-1717514799-mceclip0.png\" width=\"457\" height=\"303\" \/>&lt;\/p&gt;&lt;p&gt;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.&lt;\/p&gt;&lt;p&gt;<img loading=\"lazy\" decoding=\"async\" src=\"\/forum\/wp-content\/uploads\/sites\/2\/2024\/06\/04-06-2024-1717514817-mceclip1.png\" width=\"978\" height=\"525\" \/>&lt;\/p&gt;&lt;p&gt;I followed the directory shown in the pop-up&nbsp; (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&#8217;t find any AnsysWBDumpFile. Instead I found 2 Ansys files, one just named &#8220;Ansys&#8221; the other ANSYS with my desktop username.241. Nothing notable in the first file, though the second has this:&lt;\/p&gt;&lt;p&gt;&nbsp;&lt;\/p&gt;&lt;p class=&#8221;MsoNormal&#8221;&gt;<img loading=\"lazy\" decoding=\"async\" src=\"\/forum\/wp-content\/uploads\/sites\/2\/2024\/06\/04-06-2024-1717516845-mceclip2.png\" width=\"497\" height=\"265\" \/>&lt;\/p&gt;&lt;p class=&#8221;MsoNormal&#8221;&gt;Within each of the most recent three of them, there were 2 files in each. One &#8220;asserts.dbg&#8221; and another &#8220;errors.dbg&#8221;. I have no idea how to harness the files in order to get that so called diagnostic and know how to operate from there.&nbsp;&lt;\/p&gt;&lt;p class=&#8221;MsoNormal&#8221;&gt;The only maneuver that I found apropos of this error is to add a file directory in Mechanical: File&gt; Options&#8230; &gt; Analysis Settings and Solutions &gt; Analysis data management &gt; Scratch solver. I didn&#8217;t have indeed any files path and I created a scratch folder on my desktop and assigned it there to receive any associated files. That said, the problem persists.&lt;\/p&gt;&lt;p class=&#8221;MsoNormal&#8221;&gt;-The error displayed on WB is &#8220;Unable to display parameters property in Mechanical. Either the application crashed or Workbench lost communication with it&#8221;&lt;\/p&gt;&lt;p class=&#8221;MsoNormal&#8221;&gt;-When importing the geomtry directly on Mechanical, in the message pane, &#8220;Mechanical Locked when attaching Geometry&#8221; is shown.&nbsp;&lt;\/p&gt;&lt;p class=&#8221;MsoNormal&#8221;&gt;&nbsp;&lt;\/p&gt;&lt;p class=&#8221;MsoNormal&#8221;&gt;I tried to see if it was a Discovery bug by transferring the file to SpaceClaim, in vain. I found on Reddit that saving the geometry as a STP file on newer versions might solve it, but I didn&#8217;t find a way to do so on both software. Another user suggested that leaving the 2D sketch active on Discovery may occasion the problem. Wasn&#8217;t the case for this dummy file and yet again, the same pop-up on Mechanical occurs.&lt;\/p&gt;&lt;p class=&#8221;MsoNormal&#8221;&gt;&nbsp;&lt;\/p&gt;&lt;p class=&#8221;MsoNormal&#8221;&gt;Given the upcoming 11 days long maintenance, this message is pretty time sensitive. Your swift response would be very much appreciated.&lt;\/p&gt;&lt;p class=&#8221;MsoNormal&#8221;&gt;Best Regards,&lt;\/p&gt;&lt;p class=&#8221;MsoNormal&#8221;&gt;PS: My driver is updated to the latest version, and my GPU is decently powerful (GeForce RTX 2080Ti)&nbsp;&lt;\/p&gt;<\/p>\n","protected":false},"template":"","class_list":["post-369822","reply","type-reply","status-publish","hentry"],"aioseo_notices":[],"acf":[],"_links":{"self":[{"href":"https:\/\/innovationspace.ansys.com\/forum\/wp-json\/wp\/v2\/replies\/369822","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/innovationspace.ansys.com\/forum\/wp-json\/wp\/v2\/replies"}],"about":[{"href":"https:\/\/innovationspace.ansys.com\/forum\/wp-json\/wp\/v2\/types\/reply"}],"version-history":[{"count":0,"href":"https:\/\/innovationspace.ansys.com\/forum\/wp-json\/wp\/v2\/replies\/369822\/revisions"}],"wp:attachment":[{"href":"https:\/\/innovationspace.ansys.com\/forum\/wp-json\/wp\/v2\/media?parent=369822"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}