Install as an admin, check application event log for MSI installer errors
Test as an admin, check application event log for MSI installer errors
Test as Limited user, check application event log for MSI installer errors
Test as a second user, a limited user, check application event log for MSI installer errors
Note: If
your package includes changes to the User hive, then MSI will trigger
to install those changes the 1st time a user launches that
application. (This is normal)
If
MSI triggers over and over again for the same user then your
“KeyPath” is probably a moving target for that component.
See “Troubleshooting
Unwanted Repairs with Event Viewer”
Wise Article #: 1531.
As long as you have the WSI and the source files (loose files or inside the MSI) you can. If you have files that were located in the file conflict repository then that may cause some problems depending on the situation.
If for one reason or another you must re-install Wise Package Studio Pro on the “Packaging server” the biggest concern is what happens to the contents of the Wise share point. An initial test showed that very little is touched. The database seems to not be touched but it wasn’t being used prior to the test. The projects folder, the most important folder, was not touched at all. The safest thing to do is to backup the entire Wise share point and try it.
Update: I talked to Wise tech support. He said that you move the Share Point physically and then you rebuild the index file in Software Manager. (Setup menu -> Network Index Properties, “Rebuild using file/directory Structure”)
This will rebuild the wamdb.idx file in the share point. That’s it!
Note:
This scenario was with Wise Package Studio v4.01. It may or may not
apply with more current versions of WPS. Backup your Sharepoint before such thing. In Wise Package Studio version 5 and up, you might need to run DBSetup.exe after moving.