Help with MSI (Microsoft Installer) error 1601: The Windows Installer service could not be accessed. Contact your support personnel to verify that the Windows Installer service is properly registered.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

1
It is possible that you may see this error if you are attempting to run the installation without sufficient access to do so. Try logging on as administrator and running the installation as a troubleshooting measure.
Also see:
Windows Installer Error 1719
Answered 01/23/2004 by: AppDeploy.com
Red Belt

Please log in to comment
1
I was also getting this error before I found out it was a compatibility issue between "Windows SP SP2" and "Zenworks 6.5 SP1"...
In 'Local Policies' - 'User Rights Assignment', put the 'SERVICE' user in "Impersaonate a client after authentication", then restart.
Its caused due to the policy having been created on a PC with Windows XP SP1.
Answered 10/12/2006 by: richijenkin
Yellow Belt

Please log in to comment
1
I found another solution if the others don't work... Seems that there is an issue with the permissions of the registry. Here is how to fix it.Download and install SecEdit from microsoft, and in a command prompt in the directory SecEdit is installed use the following commandsecedit /configure /cfg %windir%\inf\defltbase.inf /db defltbase.sdb /verboseWhen it gets done, it will either say that there are warnings or there are errors, if there are errors, go to %windir%\security\logs\scesrv.log and review all the errors, go to the registry keys specified as errors, take ownership of them and replace ownership of subkeys. Re-Run command again and repeat process until it only SecEdit only gives warnings. Warnings are ok, and can be ignored.
Answered 06/25/2008 by: PCExpert
Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity