When you start multiple COM+ applications from the snap-in MMC you receive the error message. Each application has a different user account which can be run simultaneously on the Microsft Management Console however the error appears when you try to accomplish this.
Three things you can do when Catalog Error: An error occurred while ...
The computer sometimes has difficulty distributing memory for a new user in the COM+ applications which prevents the program from starting and causes error code 80080005. The problem can be solved by making modifications to the registry on the local computer. Make sure you backup the registry before you perform this troubleshooting method.
You can resolve this error problem by clicking on Start
on your main toolbar and then choosing Run
from the menu. When the Command Prompt opens type in regedit
and then press the Enter
key. When the registry editor opens double click on HKEY_LOCAL_MACHINE
and find the System
folder and click on it. Locate and click on CurrentControlSet
and then choose the Control
Session Manager and click on it and then double click on SubSystems
. Look for the Windows entry which looks like: %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 and then right click on the entry. Choose Modify
from the submenu to bring up the Edit String
window and locate Value data
. Under Value Data look for the SharedSection
and then insert 512
and choose OK
. The new entry should look like this: %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
. Proceed to create the COM applications and then right click on each application and and choose Start
To learn more about this error, please check out our Error Analyzer