THREAD: main; MSG: [DFC_SESSION_DOCBASE_UNREACHABLE] Docbase "BMSUAT" is unreachable; ERRORCODE: ff;

suchiSonali

Dear Experts,

While trying to connect to Docbase and get an session i am getting the below errors.

I have verified the firewall is disabled in content server.

i am able to do telnet to port 1489 .

dfc.properties is having correct value.

Error ::::::

===================

4985 [main] WARN com.documentum.fc.client.impl.connection.docbase.DocbaseConnection - [DFC_SESSION_RETRYING_OPEN] Retrying session establishment to "BMSUAT". Error was "[DFC_SESSION_DOCBASE_UNREACHABLE] Docbase "BMSUAT" is unreachable"

9235 [main] WARN com.documentum.fc.client.impl.connection.docbase.DocbaseConnection - [DFC_SESSION_RETRYING_OPEN] Retrying session establishment to "BMSUAT". Error was "[DFC_SESSION_DOCBASE_UNREACHABLE] Docbase "BMSUAT" is unreachable"

13485 [main] WARN com.documentum.fc.client.impl.bof.classmgmt.ModuleManager - [DFC_BOF_COULDNT_CONNECT_TO_REGISTRY] Unable to connect to module registry, docbase name BMSUAT username dm_bof_registry.

DfServiceException:: THREAD: main; MSG: [DFC_SESSION_DOCBASE_UNREACHABLE] Docbase "BMSUAT" is unreachable; ERRORCODE: ff; NEXT: null

at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.establishNewRpcClient(DocbaseConnection.java:251)

at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.open(DocbaseConnection.java:118)

at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.<init>(DocbaseConnection.java:92)

at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.<init>(DocbaseConnection.java:56)

at com.documentum.fc.client.impl.connection.docbase.DocbaseConnectionFactory.newDocbaseConnection(DocbaseConnectionFactory.java:26)

at com.documentum.fc.client.impl.connection.docbase.DocbaseConnectionManager.getDocbaseConnection(DocbaseConnectionManager.java:74)

at com.documentum.fc.client.impl.session.SessionFactory.newSession(SessionFactory.java:29)

at com.documentum.fc.client.impl.session.PrincipalAwareSessionFactory.newSession(PrincipalAwareSessionFactory.java:35)

at com.documentum.fc.client.impl.session.PooledSessionFactory.newSession(PooledSessionFactory.java:47)

at com.documentum.fc.client.impl.session.SessionManager.getSessionFromFactory(SessionManager.java:111)

at com.documentum.fc.client.impl.session.SessionManager.newSession(SessionManager.java:64)

at com.documentum.fc.client.impl.session.SessionManager.getSession(SessionManager.java:168)

at com.documentum.fc.client.impl.bof.classmgmt.ModuleManager.connect(ModuleManager.java:358)

at com.documentum.fc.client.impl.bof.classmgmt.ModuleManager.init(ModuleManager.java:313)

at com.documentum.fc.client.impl.bof.classmgmt.ModuleManager.getInstance(ModuleManager.java:36)

at com.documentum.fc.client.security.impl.DfcIdentityPublisher.<init>(DfcIdentityPublisher.java:44)

at com.documentum.fc.client.security.internal.RegistrationMgr.register(RegistrationMgr.java:34)

at com.documentum.fc.impl.RuntimeContext.<clinit>(RuntimeContext.java:191)

at com.documentum.fc.client.DfClient.<clinit>(DfClient.java:700)

at com.petrofac.ebms.bof.util.LoginManager.init(LoginManager.java:58)

at com.petrofac.ebms.bof.util.LoginManager.<init>(LoginManager.java:47)

at Test_login.main(Test_login.java:8)

13500 [main] WARN com.documentum.fc.client.security.internal.RegistrationMgr - [DFC_SECURITY_GR_PUBLICATION_FAILED] Publication of DFC instance with global registry failed

DfException:: THREAD: main; MSG: [DFC_BOF_GLOBAL_REGISTRY_UNAVAILABLE] Unable to connect to the global registry no session; ERRORCODE: ff; NEXT: null

at com.documentum.fc.client.security.impl.DfcIdentityPublisher.<init>(DfcIdentityPublisher.java:55)

at com.documentum.fc.client.security.internal.RegistrationMgr.register(RegistrationMgr.java:34)

at com.documentum.fc.impl.RuntimeContext.<clinit>(RuntimeContext.java:191)

at com.documentum.fc.client.DfClient.<clinit>(DfClient.java:700)

at com.petrofac.ebms.bof.util.LoginManager.init(LoginManager.java:58)

at com.petrofac.ebms.bof.util.LoginManager.<init>(LoginManager.java:47)

at Test_login.main(Test_login.java:8)

USER_NAME : dm_bof_registry Entered PASSWORD : dm_bof_registry DOCBASE : BMSUAT

17860 [main] WARN com.documentum.fc.client.impl.connection.docbase.DocbaseConnection - [DFC_SESSION_RETRYING_OPEN] Retrying session establishment to "BMSUAT". Error was "[DFC_SESSION_DOCBASE_UNREACHABLE] Docbase "BMSUAT" is unreachable"

22001 [main] WARN com.documentum.fc.client.impl.connection.docbase.DocbaseConnection - [DFC_SESSION_RETRYING_OPEN] Retrying session establishment to

Best Regards

Sonali

Find more posts tagged with

Captiva

Comments

Alvaro_de_Andres

Are you sure the docbase ports are opened? you can check /etc/services or %WINDIR%\System32\drivers\etc\services to check which ports are used by the cs

suchiSonali

Dear Alvaro ,

Thank you for your response.

Kindly explain in brief what exactly i need to check .

I am able to telnet.

I am able to get session from other UAT server machine but when i try to connect from Dev i am not able to get UAT Docbase session.

[DFC_SESSION_DOCBASE_UNREACHABLE] Docbase "BMSUAT" is unreachable"

Best Regards

Sonali

Alvaro_de_Andres

1489 is the docbroker port, after the initial connection clients use the repository ports and you can find those in the files I told you before in unix/windows. You should also disable/allow your program in the machine in which you're running your program

Haroon_A

verify your docbroker log and see if it uses the specified port.

suchiSonali

Dear Ahmad,

I have checked docbroker log.

How ever i found this error in docbase log.

Wed Jan 08 00:19:41 2014[DM_STARTUP_I_DOCBASE_OWNER_NOT_FOUND]: The database user (BMSUAT) is not a valid NT User. This is the user specified in your server.ini file as the database_owner attribute. If you are running the optional Replication Services package you will need to create a valid NT User account for this user.

Best Regards

Sonali

suchiSonali

Can anyone let me know what all permissions needed for connecting to a content server from any other server and get the docbase session.

We are using Documentum 6.5 SP2 Content server.

I am ablt to telnet but not able to get the docbase session.

Julien.Fontaine

Did you change or deactivate your DB User of the Content Server ?

Haroon_A


suchiSonali wrote:

Dear Ahmad,

I have checked docbroker log.

How ever i found this error in docbase log.

Wed Jan 08 00:19:41 2014[DM_STARTUP_I_DOCBASE_OWNER_NOT_FOUND]: The database user (BMSUAT) is not a valid NT User.  This is the user specified in your server.ini file as the database_owner attribute.  If you are running the optional Replication Services package you will need to create a valid NT User account for this user.

Best Regards
Sonali

I really doubt this error has anything to do with your initial error. This error happens if you don't have a docbase owner account, but i don't believe it should cause any issue. (if you don't want to see this error, simply create a local user [BMSUAT] on the content server).

Can you verify your docbase log, to see which docbroker (port) your docbase is projecting at startup? you should see something like this: Make sure it's projecting to right dockbroker and port.


[DM_DOCBROKER_I_PROJECTING]info:  "Sending information to Docbroker located on host (HOSTNAME) with port (1489).  Information: (Config(docbase_name), Proximity(1), Status(Open))."

p5C0U5dOmY1230900515271

Hi Sonali,

Can you please check, if the docbroker port is being used by any other docbrokers and was there any recent modifications made on the Server configuration object for your UAT repository?

Seems some changes have been made leading to this issue, where the docbroker port or Configuration files have been modified inadvertenly

Regards,

Rakesh