issupport1
asked on
Windows Installer is not working. Unable to install any MSI packages. SBS 2003 Server.
Experts,
I have a 2003 SBS Server.
When installing any .msi package I get the following error:
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2755.
In the Application Log I get the following:
Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 10005
Date: 3/23/2011
Time: 11:43:47 PM
User:
Computer:
Description:
The description for Event ID ( 10005 ) in Source ( MsiInstaller ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Product: Windows Small Business Server 2008 Migration Preparation Tool -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2755. The arguments are: 1632, D:\Technology\SBS 2008\TOOLS\SOURCETOOL.MSI,
Data:
0000: 7b 33 31 30 44 34 31 39 {310D419
0008: 39 2d 43 46 33 33 2d 34 9-CF33-4
0010: 35 43 36 2d 42 34 34 33 5C6-B443
0018: 2d 32 39 32 36 46 34 41 -2926F4A
0020: 44 37 43 42 35 7d D7CB5}
This happens with multiple msi files. I am logged on with an administrative account. I have reboot the server, unregistered and registered the msiexec.exe file. Windows updates also fail to install.
Thank you for all of the help.
I have a 2003 SBS Server.
When installing any .msi package I get the following error:
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2755.
In the Application Log I get the following:
Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 10005
Date: 3/23/2011
Time: 11:43:47 PM
User:
Computer:
Description:
The description for Event ID ( 10005 ) in Source ( MsiInstaller ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Product: Windows Small Business Server 2008 Migration Preparation Tool -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2755. The arguments are: 1632, D:\Technology\SBS 2008\TOOLS\SOURCETOOL.MSI,
Data:
0000: 7b 33 31 30 44 34 31 39 {310D419
0008: 39 2d 43 46 33 33 2d 34 9-CF33-4
0010: 35 43 36 2d 42 34 34 33 5C6-B443
0018: 2d 32 39 32 36 46 34 41 -2926F4A
0020: 44 37 43 42 35 7d D7CB5}
This happens with multiple msi files. I am logged on with an administrative account. I have reboot the server, unregistered and registered the msiexec.exe file. Windows updates also fail to install.
Thank you for all of the help.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
1. The windows installer engine is running.
2. The windows installer service startup is set to manual
3. The msiexec version is 4.5.6001.22159
4. I have done the following without any change:
MSIExec /unregister
MSIExec /regserver
5. I turned on all windows installer logging options via a registry key per http://support.microsoft.com/kb/223300
I checked the log after a failed MSI installation.
I found the following error just before the Return Value 3 : Server returned unexpected error 1632
I googled this error and found the following:
Where 2 is the error and 3 is the setup trying to install.
The error (2) is most often reported as 1632 ("The Temp folder is either full or inaccessible. Verify that the Temp folder exists and that you can write to it.")
This error may occur if there are insufficient privileges on the %windir%\Installer folder, or the inability of the Windows Installer service to create the %windir%\Installer folder.
I checked the temp folder - no issues here.
I checked the installer folder and found that I could not access it, nor could I modify the permissions. It seems to be corrupted. I renamed the folder and then created another folder with the same name.
I am now able to install msi packages.
2. The windows installer service startup is set to manual
3. The msiexec version is 4.5.6001.22159
4. I have done the following without any change:
MSIExec /unregister
MSIExec /regserver
5. I turned on all windows installer logging options via a registry key per http://support.microsoft.com/kb/223300
I checked the log after a failed MSI installation.
I found the following error just before the Return Value 3 : Server returned unexpected error 1632
I googled this error and found the following:
Where 2 is the error and 3 is the setup trying to install.
The error (2) is most often reported as 1632 ("The Temp folder is either full or inaccessible. Verify that the Temp folder exists and that you can write to it.")
This error may occur if there are insufficient privileges on the %windir%\Installer folder, or the inability of the Windows Installer service to create the %windir%\Installer folder.
I checked the temp folder - no issues here.
I checked the installer folder and found that I could not access it, nor could I modify the permissions. It seems to be corrupted. I renamed the folder and then created another folder with the same name.
I am now able to install msi packages.
issupport1,
Thank you for sharing your fix! It has resolved out issue as well. However, we previously moved our installer folder to another partition and created a symlink to it from C:\. to manage disk space consumption. Not sure how this will pay out in long run.
Thank you for sharing your fix! It has resolved out issue as well. However, we previously moved our installer folder to another partition and created a symlink to it from C:\. to manage disk space consumption. Not sure how this will pay out in long run.
ASKER