Applies To
	Product(s):	eB Services
	Version(s):	15.X
	Environment:	N/A
	Area:	COM+
	Subarea:	N/A
	Original Author:	Gintautas Bajoriunas, Bentley Technical Support Group

 

 

 

 

 

 

 

Problem Description

eB system becomes unresponsive and throws an error when you try to login or use the system and when trying to restart COM+ component Error Messages received: (Error code 80004002 - No such interface supported)

 The only way to restart COM+component is to restart whole application server.

You may see an error like this in the application server event log on
Event Type:        Error
Event Source:    DCOM
Event Category:                None
Event ID:              10006
Date:                     10/17/2009
Time:                    1:36:39 PM
User:                     Domain\user
Computer:          *****
Description:
DCOM got error "Unspecified error " from the computer ‘servername’ when attempting to activate the server: {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}

You'll also may see events like this in the application event log of the machine where the COM+ applications runs:
Log Name:      Application
Source:        Microsoft-Windows-User Profiles Service
Date:          10/26/2009 8:22:13 AM
Event ID:      1530
Task Category: None
Level:         Warning
Keywords:      Classic
User:          SYSTEM
Computer:      SERVERNAME
Description:
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. 

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

Reason

The user identity associated with the COM+ application is logged on when the COM+ application is first initialized. If this user were to log off of the machine then the user's profile would get unloaded and the COM+ application can no longer read registry keys in the profile of the user identity. Starting with Windows Vista the User Profile Service will force the unloading of a user profile when that user logs off. This is a situation where the functionality of forcing the unload of the user profile may break an application if registry handles are not closed in the process. This new User Profile Service functionality is the default behavior.

Steps to Resolve

As a workaround it may be necessary to modify the default behavior of the User Profile Service. The policy setting 'Do not forcefully unload the user registry at user logoff' counters the default behavior of Vista and newer operating systems. 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. The policy can be found in the group policy editor gpedit.msc). The policy is located under:
Computer Configuration->Administrative Templates->System-> User Profiles
'Do not forcefully unload the user registry at user logoff'
Change the setting from "Not Configured" to "Enabled" which disables the new User Profile Service feature.
'DisableForceUnload' is the valueadded to the registry.