DA 6.5 SP1: [DFC_SESSION_DOCBASE_UNREACHABLE]

I just installed Content Server 6.5 SP1 on a dev VM with Windows Server 2008 and Oracle 11g. A test repository was created and comes up just fine. I added exceptions for both the connection broker and the repository ports for the Windows 2008 firewall.

I then deployed DA 6.5 SP1 to Tomcat 6.0.18 and when I attempt to login, I get the following (the same occurs with Webtop 6.5 SP1):

DfServiceException:: THREAD: Thread-1; MSG: [DFC_SESSION_DOCBASE_UNREACHABLE] Docbase "cebd65sp1" is unreachable; ERRORCODE: ff; NEXT: null

at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.establishNew

RpcClient(DocbaseConnection.java:246)

at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.open(Docbase

Connection.java:113)

at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.<init>

(DocbaseConnection.java:87)

at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.<init>

(DocbaseConnection.java:54)

at com.documentum.fc.client.impl.connection.docbase.DocbaseConnectionFactory.newDo

cbaseConnection(DocbaseConnectionFactory.java:26)

at com.documentum.fc.client.impl.connection.docbase.DocbaseConnectionManager.getDo

cbaseConnection(DocbaseConnectionManager.java:74)

at com.documentum.fc.client.impl.session.SessionFactory.newSession(SessionFactory.

java:29)

at com.documentum.fc.client.impl.session.PrincipalAwareSessionFactory.newSession(P

rincipalAwareSessionFactory.java:35)

at com.documentum.fc.client.impl.session.PooledSessionFactory.newSession(PooledSes

sionFactory.java:47)

at com.documentum.fc.client.impl.session.SessionManager.getSessionFromFactory(Sess

ionManager.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.web.preset.PresetUtils.isPresetRepositoryAccessible(PresetUtils.

java:376)

at com.documentum.web.preset.PresetUtils.isPresetsTurnedOn(PresetUtils.java:342)

at com.documentum.web.preset.PresetListener.notifyApplicationStart(PresetListener.

java:161)

at com.documentum.web.env.NotificationManager$ApplicationEventNotificationSender.n

otifyStartEventForListener(NotificationManager.java:435)

at com.documentum.web.env.NotificationManager$EventNotificationSender.notifyStartE

vent(NotificationManager.java:397)

at com.documentum.web.env.NotificationManager.doApplicationStart(NotificationManag

er.java:212)

at com.documentum.web.env.NotificationManager.contextInitialized(NotificationManag

er.java:111)

Installing a copy of DA 6.0 SP1 works just fine. Maybe I missed it, but I didn't see any special new instructions for configuring DA after deployment. Anyone have any idea what my problem might be? I'm guessing the new web applications use a new connection method?

Find more posts tagged with

Comments

brownce

Anyone at all have my same setup but can connect just fine?

mszurap

Can you login/connect to the content server locally with iapi or idql?

brownce

Yep, no problems connecting on the Content Server itself.

Since a D6 SP1 client can connect just fine from the same application server, my guess is that EMC changed the way DFC connects to repositories and Windows 2008 is blocking it somehow, probably in the establishNewRpcClient class.

ldallas

is this repository the global registry? have you verified that connectivity and user credentials?

brownce

Yes, it's the global registry, and connecting to it with DA 6.0 SP1 does not report any global registry connection problems (it would say on the initial Administration screen in DA if it was not able to connect to the global registry). Both clients use the same dfc.properties.

A minor update to the problem:

I went into the Windows Firewall with Advanced Security and selected Windows Firewall Properties. Under each profile tab, Domain, Private, and Public, I set Firewall state to off and rebooted the server. After doing this, the DA 6.5 SP1 client finally connected! So apparently there is a difference between having the firewall completely disabled versus setting each profile to allow all inbound connections.

Per EMC Support's suggestion, since they for some reason don't know what all ports should be opened in the firewall, I downloaded WireShark (used to be Ethereal) to see what ports DA 6.5 SP1 was trying to connect to. Oddly, the only packets being sent are to the docbroker (1489) and to the single native repository port! (In my case, 47625).

As it stands now, I reenabled the firewall and set it to block all incoming connections. I created to rules to allow 1489 and 47625 for all three profiles (Domain, Private, Public), and am back where I started. DA 6.0 SP1 connects just fine, but DA 6.5 SP1 reports "Docbase Unreachable" on login attempt.

Maybe someone with experience in port sniffing can offer some suggestions on how to find out what 6.5 is sending that 6.0 isn't.

brownce

Well, it seems to be working now, but I give up trying to figure out what the problem was and why it's all of a sudden working.

As my previous post said, I had the firewall enabled and exceptions set up for the connection broker and repository and DA 6 was connecting but DA 6.5 gave me "Docbase Unreachable". I started adding exceptions starting with 9080 for the Java Method Server, and tried fooling around with an exception set for "Dynamic RPC", since the error referred to establishNewRpcClient in DFC. I thought I had discovered that one had to restart the Firewall service to enable new rules, as it started working after I did this.

I then went back and removed all my rules except the ones for 1489 and 47625, and completely rebooted the content server. It still works. I don't know what's different.

ldallas

I seem to recall habing seen weirdness of this sort caused by DNS caching on the application server. Normally (on windows at least) 'ipconfig /flushdns' would solve it but since you bounced the server and restarted all of the firewall services it could have reinit'd whatever needed to restart. Only a guess.

SameerPathan

Hi Chris,

Check dfc.properties details (webapps\da\WEB-INF\classes). Check hostname and port no mentioned in dfc.properties.

Are you seeing any errors in app server console while starting tomcat?

Thanks,

Sameer

parasj

Content Server - docbroker or repository connection errors are almost always because of firewall restrictions

Note - the firewall could be on the OS or a h/w firewall in between the client and the content server

Do a netstat on your content server to see the ports in use by the docbroker and the repositories. Then ensure (perhaps using a port scanning utility) that these ports are accessible from the client machine.

Usually, servers running in a LAN (private or within a data centre) don't have any connectivity restriction

- Paras