AnsweredAssumed Answered

oleaut32.dll Crash

Question asked by Bill Stadler on Aug 9, 2016

I am guessing this will be chalked up to a fluke but I thought I would toss it out here just in case.

A designer had SolidWorks open with no files open.  He went to the intranet on his second monitor and while he was reading SolidWorks crashed on the other monitor.  The event log showed that oleaut32.dll  (Object Link Embedding???) was the failing dll.  He said he had things opened earlier but not for quite some time.

 

We have seen this a handful of times over the years where a user is in IE or Outlook and SolidWorks decides to crash.  If any one has any nuggets or things to check it would be great but I think this is one of those instances where you just shrug your shoulders and chalk it up to gremlins...

 

SolidWorks 2014 SP5 and EPDM SP2

Going to 16 SP4 August 19th...

Outcomes