Error: 0x800706BE "The remote procedure call failed"
Note: Before troubleshooting this error, ensure that the II_SYSTEM environment variable has been defined globally at the operating system level.
Problems:
• When trying to start the OpenROAD Server from Services, it fails with the following error:
Could not start the OpenROAD Server on Local Computer. Error 1069: The service did not start due to a logon failure.
• When trying to start the service with the command 'net start "OpenROAD Application Server"' it returns the following error:
The OpenROAD Server service is starting.
The OpenROAD Server service could not be started.
A system error has occurred.
System error 16410 has occurred.
• The system cannot find message text for message number 0x401a in the message file for BASE. When trying to start the service using the local system account the error is:
Could not start the OpenROAD Server service on Local Computer.
Error 2147500058: The server process could not be started because the configured identity is incorrect. Check the username and password.
• The Event Viewer displays two error messages:
DCOM got error "Logon failure: the user has not been granted the requested logon type at this computer" and was unable to log on .\ingres in order to run the server:
{9804E903-495A-11D4-A083-00C04F740D30}
• The OpenROAD Server service terminated with the following error:
The server process could not be started because the configured identity is in correct. Check the username and password.
Possible Solution:
The SPO has been set up to be launched as a particular user. Remove this user from the "Deny logon as a batch job" User Rights policy:
The error message provides the name of the user that you need to remove, but if you are uncertain, perform the following steps to find out what user the SPO has been set up to be launched as:
1. From a command prompt window, run the following command:
dcomcnfg
The Distributed COM Configuration Porperties window appears.
2. Select the OpenROAD SPO Server Pool application from the applications list and click the Properties button.
3. Click the Identity tab.
If the "This user" option is selected, then the name of the user is the one listed in the User field. If the "This user:" option is not selected, select it and fill in the User and Password fields using credentials for a local operating system account.
4. Ensure that this user has not been added to the "Deny logon as a batch job" User Rights policy.
Valid on UNIX Only
Problem:
If you start the SPO as "ingres" and then run comtestrso as ingres, it works correctly. However, if you leave the SPO running, open another Telnet window, log on as a different user, and run comtestrso, you get the following error:
% comtestrso Successfully created component. Using interface IRun4GLrs. ===================================== ImageFile: "comtest.img" CmdFlags: "-Tyes -Lcomtest.log" Location: "" Routing: "" Private: 0 ===================================== bind failed due to 125: Address already in use pIRun4GLrs->Initiate; hr = 0x80040155 Releasing interface IRun4GLrs.
Possible Solution:
The “Address already in use” error is caused by the same endpoint. In your environment, you must set the MWRPC_ENDPOINT system environment variable to an unused port (different from the value of the MWRPC_ENDPOINT environment variable that is used by the "ingres" user) because this endpoint is used by "ingres" when it starts SPOCTL (or orspostart). All you need to do is set MWRPC_ENDPOINT to any unused port greater than 10000.
To find an unused port
Enter the following commands:
setenv MWRPC_ENDPOINT 10678
netstat -a | grep $MWRPC_ENDPOINT
If the system displays no entry, the specified port is free to use.
IMPORTANT! Currently OpenROAD only supports one SPO running at a time.
Problems:
• When you try to start SPO using SPOCTL, you get error -2147023174 (0x800706BA "The RPC server is unavailable") in the SPOCTL window and error message "port 135 need root permission" in the Trace window (UNIX terminal).
• When you try to start the rpcss process you get error message "port 135 need root permission".
Possible Solution:
Port number 135 is a privileged port on UNIX and only root can bind to it and accept connections. You must be logged in as root to set up rpcss and bind to port 135. Consult the readme provided with your OpenROAD installation and the Installation and Configuration Guide for platform-specific information on how to set up the rpcss process.
Problem:
When you try to run comtestrso or the Server Manager (VOSA), some eClient applications hang indefinitely.
Possible Solutions:
• Ensure that the II_SYSTEM system environment variable is defined globally at the operating system level.
• If you have eClient applications and OpenROAD 4.1 installed on the same machine, ensure that they are compatible. If they are not, you must un-register and re-register orrso.dll and orps.dll based on which application you want to run at a particular time. The files that come with the OpenROAD 4.1 installation are in the %II_SYSTEM%\ingres\bin directory; those that come with eClient are under %SystemRoot%\Advantage OpenROAD\eClient\bin.
• For eClient applications that hang, ensure that the identity of the OpenROAD RTO RunTime Server is set to "The launching user" in the dcomconfig settings.
