predpostavljam da znas engleski ako neznas imas google translete i lagano.Ovo bi trebalo pomoc:
SYMPTOMS
After you upgrade to Windows Installer version 2.0, the Windows Installer Service may not start, and you may receive the following error message:
The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or the Windows Installer is not correctly installed. Contact your support personnel for assistance.
CAUSE
This behavior can occur when either of the following conditions exist:
• In the DCOM permissions, the default authentication level is set to None, and the default Impersonation level is set to Anonymous.
• The system account does not have Full permissions on a folder or registry key that the Windows Installer is trying to access. This is NTFS-specific.
SOLUTION
Method 1: Unregister and re-register the Windows Installer
1. Click Start, click Run, type MSIEXEC /UNREGISTER, and then click OK. Even if you do this correctly, it may look like nothing occurs.
2. Click Start, click Run, type MSIEXEC /REGSERVER, and then click OK. Even if you do this correctly, it may look like nothing occurs, or you may briefly see an hourglass. After you run this command, the operation is complete.
3. Try your Windows Installer-based application again.
Back to the top Back to the top
Method 2: Verify the DCOM permissions
This method involves changing the DCOM default impersonation level to Identify, removing the Msisip.dll file, and then reinstalling SP 3 for Windows 2000.
To do this, follow these steps:
1. Click Start, click Run, type dcomcnfg, and then click OK.
2. On the Default Properties tab:
a. In the Default Authentication Level list, click Connect.
b. In the Default Impersonation Level list, click Identify, and then click OK.
3. Click Start, click Run, type explorer /select, %windir%\system32\msisip.dll, and then click OK.
4. Rename the Msisip.dll file as Msisip.old.
5. Reinstall Windows 2000 Service Pack 3.
Back to the top Back to the top
Method 3: Give Full Control permission to the SYSTEM account
1. Start Windows Explorer, right-click the computer's root hard drive, and then click Properties.
2. Click the Security tab, and then click Add.
3. In the Select Users, Computers, or Groups dialog box, click the SYSTEM account, click Add, and then click OK.
4. Under Allow, click to select the Full Control check box, and then click OK.
5. Click the TEMP folder and then verify that the SYSTEM account has full control.
Back to the top Back to the top
Method 4: Verify the registry permissions
1. Click Start, click Run, then type Regedt32.
2. For each of the registry hives, follow these steps:
a. Select the hive.
b. For Windows XP, on the Edit menu, click Permissions.
For Windows 2000 and Windows NT 4, on the Security menu, click Permissions.
3. Verify that the SYSTEM account has been added and that it has Full control. If it does not, add the SYSTEM account with Full control.
Back to the top Back to the top
Method 5: Fix the broken security key for the MsiServer service
1. Start the computer by using Windows 2000.
2. Click Start, click Run, type regedit.exe, and then rename the following key to Old_Security:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSIServer\Security
3. Restart the computer (you must do this).
4. Run Instmsiw.exe for installer 2.0 again; this corrects the broken security key for the MSI service.
14 comments
Labels: 1635, error code 1603, Windows Live Messenger Installation Error 1601
DiggIt Del.icio.us Furl Blinkbits
Windows live messenger setup error code 1603
1) Click Start > Run
2) Type msiexec /unreg and press enter and wait until it appears to have finished.
3) Go back to Start > Run
4) Type msiexec /regserver and press enter.
5) Try to install MSN Messenger again. Good luck!
If this doesn't work, try:
C:\documents and settings\all users\application data\microsoft\
Then select the folder "IdentityCRL" remove the folder. Since the error is occuring due to "ppcrlconfig.dll" directory correction. Then run the setup and this time it will be able to install.
braul1o bar si preveo ono so sam ja napisao
