I am use a docker container for my ASP.NET application. This is a client/server application, where I am using .NET Remoting to communicate with the servers.
in the dockerfile, I register my COM+ Assembly using RegSvcs.exe,
When I run my container, I connect to it’s IP address in my browser, and up comes the client.
When I proceed to access the server, I get the error:
The server process could not be started because the configured identity is incorrect. Check the
username and password. (Exception from HRESULT: 0x8000401A)
This seems to indicate that the COM+ Assembly that I registered does not have the correct identity for access.
When I inspect my docker container, I can see the Login Information as follows:
Logon Type: 5 (Service)
Logon ID: 0x3e7
Account Name: SYSTEM
Account Domain: NT AUTHORITY
UserSid: S-1-5-18
Do I need to modify the COM+ Assembly’s identity to be NT AUTHORITY\SYSTEM to get around this error?
There doesn’t seem to be a way to set the identity using RegSvcs.exe.
Hi Robert,
This is an old thread, but thought I would respond and suggest using global managed service accounts to allow connection to your COM+ service and other network resources.
We are in beginning stages of migrating COM+ applications to docker containers. Have you had the issue of httphandlers and issue.
I’m attempting to resolve, but have not had any success.
If you need some assistance with the setup of gmsa in Windows 2019 images let me know.
We are looking into migrating our application with com+ components into Docker. How did it go for you? Could you share some documentation on the process ?
Hi, I also face the same kind of issue; in the dockerfile, I register my COM+ Assembly using RegSvcs.exe.
But while running the application prompting with below error.
Exception Details: System.Runtime.InteropServices.COMException: An attempt was made to reference a token that does not exist. (Exception from HRESULT: 0x800703F0)
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
`[COMException (0x800703f0): An attempt was made to reference a token that does not exist. (Exception from HRESULT: 0x800703F0)]
System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) +0
System.EnterpriseServices.Thunk.Proxy.CoCreateObject(Type serverType, Boolean bQuerySCInfo, Boolean& bIsAnotherProcess, String& uri) +352
System.EnterpriseServices.ServicedComponentProxyAttribute.CreateInstance(Type serverType) +197
System.Runtime.Remoting.Activation.ActivationServices.IsCurrentContextOK(RuntimeType serverType, Object props, Boolean bNewObj) +14683760
Is there any resolution for the issue in windows container?