You may receive an "Error code 80080005 -- server execution failed." error message when you start many COM+ applications (870655)
The information in this article applies to:
SYMPTOMSImportant This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base: 256986 Description of the Microsoft Windows Registry When you start many Microsoft COM+ applications manually from the Component Services Microsoft Management Console (MMC) snap-in where each COM+ application is running under a different user account, you may receive the following error message: Catalog Error: An error occurred while processing the last operation. Error code 80080005 -- server execution failed. The event log may contain additional troubleshooting information.
You will receive an error message that is similar to the following in the application log of Event Viewer:
Type: Error
Source: DCOM
Category: None
Event ID: 10010
Date: 31/03/2004
Time: 15:13:30
User: NT AUTHORITY\SYSTEM
Computer: MSHSRMSWEBP0007
Description:
The server {F1673109-CF44-468D-9E23-FE4116F84CFA} did not register with DCOM within the required timeout.
CAUSEIf many COM+ applications run under different user accounts that are specified in the This User property, the computer cannot allocate memory to create a new desktop heap for the new user. Therefore, the process cannot start.WORKAROUNDWarning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. To work around this problem, modify the value of the following registry subkey: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\Windows To do this, follow these steps: - Click Start, click Run, type regedit, and then click OK.
- In Registry Editor, locate the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems By default, the Windows entry in the subkey has a value that is similar to the following (all on one line):%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows
SharedSection=1024,3072 Windows=On SubSystemType=Windows
ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3
ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off
MaxRequestThreads=16 - Right-click the Windows entry, and then click Modify. The Edit String dialog box appears.
- In the Value data box, locate SharedSection, add 512 to SharedSection, and then click OK.
The newly changed Windows entry reads as follows:%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows
SharedSection=1024,3072,512 Windows=On SubSystemType=Windows
ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3
ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off
MaxRequestThreads=16
REFERENCESFor more information, visit the following Microsoft Developer Network (MSDN) Web site:
Modification Type: | Major | Last Reviewed: | 6/28/2004 |
---|
Keywords: | kbtshoot kberrmsg kbSnapIn kbDCOM kbCompModel kbprb KB870655 kbAudDeveloper |
---|
|