Event ID 10006 and 1530: COM+ application not working in Windows 10

Download PC Repair Tool to quickly find & ready Windows errors automatically

Yous have a COM+ server awarding in which the identity is configured to run as a specific user. After working for some time, the application may stop working and keep declining. You have to restart the COM+ application to resolve the consequence. In today's post, we will place the crusade and then provide the resolution to the issue of a COM+ application may stop working in Windows 10 when a user logs off.

A COM+ application is the primary unit of administration and security for Component Services and consists of a group of COM components that generally perform related functions.

By creating logical groups of COM components every bit COM+ applications, yous tin can accept advantage of the following benefits of COM+:

A deployment telescopic for COM components.
A common configuration scope for COM components, including security boundaries and queuing.
Storage of component attributes non provided by the component programmer (for example, transactions and synchronization).
Component dynamic-link libraries (DLLs) loaded into processes (DLLHost.exe) on demand.
Managed server processes to host components.
Creation and management of threads used past components.
Access to the context object for resource dispensers, allowing acquired resources to be automatically associated with the context.

Consequence ID 10006 & 1530, COM+ application not working

When a COM+ application stops working in Windows when a user logs off, you may encounter an fault that resembles the following in the Application log on the client automobile. If the client executable runs on the same computer as the COM+ server application, y'all will see this mistake on the COM+ server:

Event Blazon: Mistake
Upshot Source: DCOM
Event Category: None
Result ID: 10006
Date: 10/17/2009
Fourth dimension: 1:36:39 PM
User: Domain\user
Computer: *****
Clarification:
DCOM got error "Unspecified error " from the computer 'servername' when attempting to activate the server: {AAAAAAAA-AAAA-AAAA-AAAA-AAAAAAAAAAAA}

You'll also see events that resemble the following in the Awarding log of the calculator on which the COM+ application runs:

Log Proper noun: Application
Source: Microsoft-Windows-User Profiles Service
Date: 10/26/2009 8:22:xiii AM
Upshot ID: 1530
Job Category: None
Level: Warning
Keywords: Archetype
User: Organisation
Computer: SERVERNAME
Clarification:
Windows detected your registry file is still in use past other applications or services. The file volition be unloaded now. The applications or services that hold your registry file may not office properly later.

Detail –
i user registry handles leaked from \Registry\User\S-1-v-21-1049297961-3057247634-349289542-1004_Classes:
Process 2428 (\Device\HarddiskVolume1\Windows\System32\dllhost.exe) has opened key \REGISTRY\ USER \ Due south-i-v-21-1123456789-3057247634-349289542-1004_CLASSES

What causes Upshot ID 10006 and 1530

According to Microsoft;

The User Profile Service will force the unloading of a user contour when that user logs off. This is a situation where the functionality of forcing the unload of the user contour may break an application if registry handles are not closed in the process. This new User Contour Service functionality is the default behavior.

The user identity that is associated with the COM+ awarding is logged on when the COM+ application is first initialized. So, this issue is triggered if this user were to log off of the machine and so the user'south profile would get unloaded and the COM+ application tin can no longer read registry keys in the profile of the user identity.

To resolve this upshot, yous'll need to modify the default beliefs of the User Profile Service via Group Policy Editor (gpedit.msc).

Here's how:

Launch Local Group Policy Editor.
Navigate to the following path:

Computer Configuration > Authoritative Templates > System > User Profiles

On the correct pane, double-click the Do not forcefully unload the user registry at user logoff entry to edit it's properties.
Now change the setting from Not Configured to Enabled past selecting the corresponding radio push button which disables the new User Profile Service feature.
Click Apply > OK.

The policy-setting 'Do not forcefully unload the user registry at user logoff' counters the default behavior of the Windows client operating system. When enabled, the User Profile Service will not forcefully unload the registry, instead, it waits until no other processes are using the user registry before it unloads it.

Hope this helps!

Obinna Onwusobalu, has studied Information & Communication Applied science and is a smashing follower of the Windows ecosystem. He runs a computer software clinic. He says it'due south best practice to create a Organisation Restore Point before making whatever changes to your PC.