Moro, en pysty asentamaan skypeä, iTunesia tai Windows media playeria koska tietokone valittaa että: "Windows-asennuspalvelua ei voitu käyttää. Ota yhteyttä tukihenkilöstöön ja varmista, että Windows-asennuspalvelu on rekisteröity oikein."
Eli mikä tähän auttais kone on itse koottu vähän aikaa sitten(pelikäyttöön) ja asian tunteva kaveri tilas osat ja kokosi tämän.. Mikähän tähän auttaisi?
Lainaus:First, try the old faithful reboot; this error may be the result of an RPC error. If a reboot does not clear the RPC error, you have bigger problems than installing MSI packages!
Reregister the Windows Installer service by typing "msiexec /unregister" and then "msiexec /regserver" at the command line.
The System account should have "Full Control" permissions to the HKEY_CLASSES_ROOT hive of the registry.
Ensure the Windows Installer service is not disabled by typing "NET STOP MSISERVER" and "NET START MSISERVER" at the command line.
Lainaus: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.
Lainaus: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 command
When 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.
Lainaus: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