Unable to login remote FileNET Enterprise Manager (FEM) or configure GCD.

Technote (troubleshooting)


Problem(Abstract)

Unable to login remote FileNET Enterprise Manager (FEM) or configure GCD.

Resolving the problem

Unable to login remote FileNET Enterprise Manager (FEM) or configure GCD. Getting error "hr=0x800706ba The RPC Server is unavailable" trying to configure GCD after entering the host name of the CE server.

This was caused by a port beening blocked when the client machine trying to talk to the CE server. After restricting the ports DCOM uses and opening these range of ports, problem resolved.


The CE client connectivity uses DCOM and RPC for communication with the CE server etc. After researching DCOM port usage, by default it will use any port between 1100-65000 for communication between client and server. So, all incoming DCOM and RPC requests will first come in on port 135 and are then switched to an available port between 1100 and 65000 (hence why it is so important to keep port 135 open).

So, the varying port usage is due to DCOM and the default range that it uses. You can restrict the ports it uses by following the below procedure:

1. Start the DCOM Configuration utility (dcomcnfg.exe).
2. Click the Default Protocols tab, which
3. Right-click a DCOM transport protocol (e.g., Connection-Oriented TCP/IP), then select Properties.
4. Set the port range you want to use (i.e. 6000-6008)

Here is a fairly good Microsoft article that talks about configuring DCOM to communicate through a Firewall with restricted ports.

-
The instruction is a little bit different for Win XP and Windows 2003.
Start the DCOM Configuration utility (dcomcnfg.exe) then expand Component Services.
Right-click on My Computer - Click the Default Protocols tab, which
Click a DCOM transport protocol (e.g., Connection-Oriented TCP/IP), then select Properties.
Set the port range you want to use (i.e. 6000-6008)
In most cases, just configuring the port range values on the RPC server side isn't sufficient. You might also need to configure the DCOM ports on the RPC client side because DCOM uses a callback mechanism that requires a separate connection between the server and the client. This callback mechanism can't reuse the existing client-server connection.

Historical Number

20003419

Product Alias/Synonym

P8 CONTENT ENGINE

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

FileNet Content Manager
Content Engine

Software version:

3.x

Operating system(s):

Platform Independent

Reference #:

1277552

Modified date:

2013-12-12

Translate my page

Machine Translation

Content navigation