How to fix when one application tries to initialize another application when opened?
I have recently installed AutoDesk 2015 to an associate's computer. When they go to open another program, GRD Selection application from https://www.titus-hvac.com/main/software/teams, I get a popup asking to initialize AutoDesk Architecture 2015. This errors out because my associates are standard users. When I have ran the GRD Selection program as an admin it works as expected. But when I go back and run it again under the user's standard user context, it initializes and fails again.
Any ideas?
When I luanch the GRD Selection App, these are the resulting dialog boxes.
I have installed this program (GRD Selection) to my SurfcacePro3. When I attempt to run the program as a standard user I receive a very similar error.
I have added a link to the related event logs.
https://onedrive.live.com/redir?resid=62AC87CDB10E7BEF!17751&authkey=!AAO3jkf0fG2cxMg&ithint=file%2cevtx
I see the Windows Installer transaction ID, but I am not sure what to do with it.
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
anonymous_9363
8 years ago
Oh dear! :-( Who didn't check the AutoCAD MSIs for machine-level components mixed in with user-level ones? Or it could be user-level components with blank or non-HKCU-based key paths? Indeed, who didn't check the MSIs for ICEs?
Check the Event Log for the entry showing where MSIInstaller (don't you just *love* Microsoft's naming consistency?) begins to repair the AutoCAD product. The component GUID will be detailed. You then have the unenviable task of finding that component in the plethora of MSIs that is involved with an AutoCAD product and fixing it. While you're doing that, check the other MSIs for similar oversights.
Check the Event Log for the entry showing where MSIInstaller (don't you just *love* Microsoft's naming consistency?) begins to repair the AutoCAD product. The component GUID will be detailed. You then have the unenviable task of finding that component in the plethora of MSIs that is involved with an AutoCAD product and fixing it. While you're doing that, check the other MSIs for similar oversights.
Comments:
-
I have added info to my original post. Thanks for the suggestions, but I am not sure what to do with the GUID once I have it. - anonymous_95342 8 years ago
-
Or don't you just love it when vendors supply s**te MSI's and / or expect everybody who ever logs onto a machine to be an Admin... - Pressanykey 8 years ago
Posted by:
anonymous_9363
8 years ago
>I am not sure what to do with the GUID once I have it.
Or employ an application packager because AutoCAD products can be a can of worms if you don't know what you're doing.
You then have the unenviable task of finding that component in the plethora of MSIs that is involved with an AutoCAD product and fixing it. While you're doing that, check the other MSIs for similar oversights.Find the GUID in whatever MSI it's in - you'll need to load them into InstEdit/Orca one by one and work back from there.
Or employ an application packager because AutoCAD products can be a can of worms if you don't know what you're doing.
Posted by:
anonymous_9363
8 years ago
Hold the phone...
An entry in the Event Log you posted contains the detail that you need to run Setup.exe to install the product.
In an enterprise installation, you will almost certainly NOT want to install from SETUP.EXE but apply transforms to the MSIs and use a script to chain the execution of the MSIs/MSTs. You'll find an example of a command file - with the actual commands commented-out - on the media supplied. Use a modified version, i.e. one with your transforms added, to deploy AutoCAD stuff.
An entry in the Event Log you posted contains the detail that you need to run Setup.exe to install the product.
In an enterprise installation, you will almost certainly NOT want to install from SETUP.EXE but apply transforms to the MSIs and use a script to chain the execution of the MSIs/MSTs. You'll find an example of a command file - with the actual commands commented-out - on the media supplied. Use a modified version, i.e. one with your transforms added, to deploy AutoCAD stuff.
Comments:
-
The installer was already ran. Iwth Autodesk i run the setup.exe and create a deployment package from that. Then that link is used to install the package to any number of machines. I am not really sure what you mean with some of your recommend instructions.
"Find the GUID in whatever MSI it's in - you'll need to load them into InstEdit/Orca one by one and work back from there."
whatever MSI its in? Are you talking about the MSI for TrueView or the GRD Selection Program?
How does this smaller program have anything to do with TrueView? - anonymous_95342 8 years ago
Posted by:
anonymous_9363
8 years ago
The TrueView MSIs, yes. I'm pretty sure there's more than one, from memory.
>How does this smaller program have anything to do with TrueView?
From looking at the web page you provided a link for, it has some link or other with TrueView. I would've hoped that you, as - I presume - the administrator, would know what software does what and with what in your workstation estate.
>The installer was already ran
Then, if you want to fix this, you're going to have to uninstall it and re-install using the MSIs/MSTs. The Windows Installer engine is calling for a repair against the MSI but the MSI, internally, is set up to only work when called by the set-up executable.
>How does this smaller program have anything to do with TrueView?
From looking at the web page you provided a link for, it has some link or other with TrueView. I would've hoped that you, as - I presume - the administrator, would know what software does what and with what in your workstation estate.
>The installer was already ran
Then, if you want to fix this, you're going to have to uninstall it and re-install using the MSIs/MSTs. The Windows Installer engine is calling for a repair against the MSI but the MSI, internally, is set up to only work when called by the set-up executable.
Posted by:
anonymous_9363
8 years ago
My mistake: there's one MSI. You'll find it in [deployment folder where the "master" setup.exe extracted the files]\SetupDWGTrueView2015_ENU_64bit\x64\dwgviewr\
From that directory, try executing this command line on the machine in question using the machine's Administrator account:
Choose 'Repair' when prompted.
From that directory, try executing this command line on the machine in question using the machine's Administrator account:
msiexec /i dwgviewr.msi ADSK_SETUP_EXE="1" /l*v %SystemRoot%\TEMP\Repair_DWGViewer.LOG
Choose 'Repair' when prompted.
