Greetings to all!
I am new to this forum and postings in general, so I thank you for your indulgence if I fail to follow any "protocols" while submitting my issue.
Here's the situation a was submitted from clients of ours, who recently started using our application, along with AutoCAD 2015 on PCs running Windows 7 (64-bit).
When they launch our application, they are immediately presented with a message "Please wait while Windows configures AutoCAD Utility Design 2015", with another message overlapping, asking to "Run Setup.exe to install AutoCAD Utility Design 2015 - English". If the user clicks on the OK button, he then is presented with the authentification window of our application, and upon confirming his credentials, the AutoCAD installer messages come back again and can only be "removed" by clicking OK two times in a row. Our application then fully launches and no other issues with AutoCAD until the next launch. This situation occurs even with an "admin" account.
I have managed to find a kind of "workaround" to this situation, for one of our clients, but I feel like the real / main issue isn't solved and that's what annoys me. The workaround comes in two folds :
1- run the requested AutoCAD module manually, i.e AutoCAD Utility Design 2015 - English in this case, and seeing it through till AutoCAD launches, although the installation was already performed;
2- configure our application to "run as administrator".
If I only perform step 1, the issue remains.
If I run our app as admin, no more messages from AutoCAD installer, and both applications run fine on their own.
At first gance, it looks like a rights / permission level issue, but then why would AutoCad installer be launched when our application has no (know) links to AutoCAD, unless some obscure shared ressource (DLL?? OCX?? other??), where one would interfere with another?? I have read articles about MSI and the KeyPath value being one of the main reference for Windows to determine if a given application maybe corrupted or not, triggering its reinstallation if that value doesn't match the workstation's reality. What then would trigger AutoCAD's installer when our application is launched?
I would appreciate any inputs anyone may have to solve this mystery (to me at least!)
Thanks!
DavetoC