I have a Windows 2003 (SP1) server set up as the primary Active Directory domain controller. We run an application on this server which does an RPC call to another program on the same server in order to launch this program. It is architected this way because in some installations the program RPC calls might exist on a remote server.

The odd thing is this application can successfuly, using RPC and DCOM, launch an application on another windows 2003 server. THat other server can launch an application back on the AD server.

The only thing failing is when the AD server tries to launch the application locally on itself.

THe error code is related to permission problems.

Here is a test script you can use to test RPC:

Copy the following into test.vbs:

Const ServerIPAddress = ""

Set process=GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & ServerIPAddress & "\root\cimv2:Win32_Process")

result = process.Create ("C:\Windows\notepad.exe",null,null,processid)

WScript.Echo "Method returned result = " & result
WScript.Echo "Id of new process is " & processid

If Not err = 0 then
WScript.Echo Err.Description, "0x" & Hex(Err.Number)
end if


Make sure the path to notepad.exe is correct. This script runs fine on ever server except if the server is an active domain controller.

What is unique about a domain controller which would prevent RPC from running on and launching a local application? There are no firewall or port issues that I can find.