Craig,
We could suggest doing a couple of things:
- Check Windows Event Log (Application) after Cassini failed to install. There might be more clues about what happens. You can export the log as .EVT file and send us for review - we would be happy to do that. Just contact us
by email and we'll respond with the address where yo will send the log. If you device to send us the EVT file, for your privacy we recommend cleaning up the event log, then running the installation to reproduce the problem, and then exporting the EVT file containing only entries related to the error.
Before the next suggestion we would like to ask you under which user name does your MSI installer run in elevated mode? If you know, then you would need to make sure that that user has rights to modify the "C:\Program Files\UltiDev". If you don't know user's identity, please try this:
- When installation runs, use Task Manager to see the user name under which installation runs. Be sure to check "Show processes from all users" on the Processes tab, and sort the list by CPU utilization. Once you established user identity of the process, you should be able to verify whether that use can modify the folder in question.
If none of the above shed the light on what's going on, see if you can make MSI generate an installation log. In regular, non-AD deployment, the command line for installation with logging looks like this: "msiexec.exe /lv intalllog.txt /i <msifile>.msi". Usually logs produced by MSI are very messy, not terribly useful, and exceptionally hard to read, but sometimes they contain clues as to whether to look. If you send the file to us, we'll take a look at it.
Best regards,
UltiDev Team.
Please donate at
http://www.ultidev.com/products/Donate.aspx to help us improve our products.
