You have a COM + server application in which the identity is configured to run as a specific user. After working for a while, the app may stop working and continue to fail. You must restart the COM + application to resolve the problem. In today’s post, we will identify the cause and then provide a solution to the problem of one COM + application may stop working in Windows 10 when a user signs out.
A COM + application is the main administration and security unit for component services and is made up of a group of COM components that typically perform related functions.
By creating logical groups of COM components as COM + applications, you can take advantage of the following advantages of COM +:
- A deployment scope for COM components.
- A common configuration scope for COM components, including security limits and queuing.
- Storage of component attributes not provided by the component developer (for example, transactions and synchronization).
- Dynamic link libraries (DLLs) of components loaded into on-demand processes (DLLHost.exe).
- Managed server process to host components.
- Creation and management of threads used by components.
- Access to the contextual object for resource distributors, allowing acquired resources to be automatically associated with the context.
Event ID 10006 and 1530, COM + application does not work
When a COM + application stops working in Windows when a user logs out, you may see an error similar to the following in the application log on the client computer. If the client executable is running on the same computer as the COM + server application, you will see this error on the COM + server:
Type of event: error
Source of the event: DCOM
Event Category: None
Event ID: 10006
Date: 10/17/2009
Time: 1:36:39 PM
User: domain user
Computer: *****
The description:
DCOM received the error “Unspecified error” from the computer “user name” when trying to activate the server: {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}
You will also see events similar to the following in the application log of the computer on which the COM + application is running:
Journal name: application
Source: Microsoft-Windows User Profile Service
Date: 10/26/2009 08:22:13
Event ID: 1530
Task category: none
Level: Warning
Keywords: Classic
User: SYSTEM
Computer: SERVERNAME
The description:
Windows has detected that your registry file is still being used by other applications or services. The file will be downloaded now. The applications or services that contain your registry file may not work properly afterwards.DETAIL –
1 user registry manager leaked from Registry User S-1-5-21-1049297961-3057247634-349289542-1004_Classes:
Process 2428 ( Device HarddiskVolume1 Windows System32 dllhost.exe) opened the key REGISTRY USER S-1-5-21-1123456789-3057247634-349289542-1004_CLASSES
What Causes Event IDs 10006 and 1530
According to Microsoft;
The User Profile Service will force a user profile to be unloaded when that user logs out. This is a situation where the force to unload user profile feature can terminate an application if the registry handles are not closed in the process. This new user profile service feature is the default behavior.
The user identity associated with the COM + application is logged in when the COM + application is initialized. Therefore, this problem is triggered if this user were to log out of the machine, the user profile would be unloaded and the COM + application could no longer read the registry keys in the user identity profile. .
To resolve this issue, you will need to change the default behavior of the User Profile service through the Group Policy Editor (gpedit.msc).
Here’s how:
Computer Configuration> Administrative Templates> System> User Profiles
- In the right pane, double-click the Do not forcibly unload the user registry when the user logs off to modify its properties.
- Now change the setting of Not configured at enabled by selecting the corresponding radio button which deactivates the new user profile service function.
- Click on Apply > Okay.
The political framework “Do not forcibly unload the user registry when the user logs off“Against the default behavior of the Windows guest operating system. When enabled, the User Profile service will not forcefully unload the registry, but will wait until no other process uses the user registry before unload it.
I hope this helps you!