I'm seeing an OS LoaderLock exception while initializing the ProjectWise CONNECT DI API when calling aaApi_Initialize (regardless of the argument passed). I've never seen this before, but in the last 2 weeks, it happens every time it's called. The exception is catchable, but happens multiple times before it eventually clears. I'm concerned because it's the kind of exception that can result in a deadlock. Anyone else seeing this or know how I can keep it from occuring?
/resized-image/__size/320x240/__key/communityserver-discussions-components-files/342995/3823.Screenshot-2021_2D00_11_2D00_16-083424-ProjectWise-API-inialization-LoaderLock.png
Hi Adrian Abshere,
A colleague (Dan Williams) a couple months back was working with development on a similar issue that appears to occur in ProjectWise 10.3 series releases and should be corrected once ProjectWise 10.4 client/SDKs are available. Can you try to see if performing the following work-around registry change helps resolve your issue?
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Bentley\ProjectWise\10.00\CustomModules\rendsvccli "Application Mask" : REG_DWORD = 1
Thank you and HTH,Bob
Answer Verified By: Adrian Abshere
Thanks much Bob; that appears to have done the trick. Not, unfortunately, something I'm at liberty to deploy to my users, so we'll look forward to the 10.4 release.