DCOM server could not register

I get this error

Source: DCOM
Event_ID: 10010

"The server {6FC4FDAE-96C8-11D3-9F9C-005004053207} did not register with DCOM within the required timeout."

This is for a specific exe, which when working on the local system works fine, but when starting under a non-built-in administrator, a crash occurs. I need exe to run under a non-built-in administrator.

I am currently getting this problem on a Win 2k3 machine with Citrix.

However, I also encountered this problem on an XP computer before.

Any tips for solving the problem?

+3
source share
3 answers

XP IT-. , - , DCOM .

, DCOM , .

+1

... , ... , .... ( , )

DCOM . DCOM , , / , DCOM . 80/20... , .

-, : Fire Up SecPol.MSC , / . .

DCOM. http://support.microsoft.com/kb/892500

-, , , , DCOM. , ( ). , , , . ... secpol.msc\ \ \ : ( )

-, ...

( ), ; . , , , . , , .

-, , .

, . , netbios exename (135/139udp). ; .. .

-, ... ( ) . , , .

, dcomcnfg . DCOM : , . Dcomcnfg . ( ) http://www.opcfoundation.org/DownloadFile.aspx?RI=326

, ....

+7

DCOM ... , , .

, , CoRegisterClassObject . , COM. ( ..) , . , , , .

What I will do is first monitor the server activity using ProcMon . This will simplify the search for any access issues and also show you the appropriate stack trace. If debugging is required, you can enable the debugger as soon as exe is started after these instructions . Finally, if the problem occurs on a machine without VS, you can use WinDBG to debug the process.

+1
source

Source: https://habr.com/ru/post/1712847/


All Articles