Docbroker was down on the Microsoft Cluster Services(Windows 2008 Sererv/SQL 2008 Server)

exsoft

Hi, everyone.

1. I installed DCTM 6.5.2 on the Windows 2008 Server/SQL 2008 Server with MCS(Microsoft Cluster Services)

2. I started Content Server on the both nodes, that is good.(Docbroker, Docabse both were good working.!!!)

3. Using MCS, created resource group for Content Server and then tested failover.

4. I received the following situation

. Docbroker offline

. Docbase online

. I din't understand this situation.

Pls help me ASAP.!!!!

Thanks/B.K.Hwang

Find more posts tagged with

Comments

Francois Dauberlieu

As far as I remember (not in front of a 'proper box so I can't check), Server 2008 and SQL 2008 are not yet supported so that could be the source of the problem. Maybe in 2008, Microsoft changed some of the clustering stuff.

apriam_i

Hi!

Please, post here docbrocker log.

exsoft

Hi,

There is no error on the Docbroker.log

This is event log.

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

DMDOCBROCKER 응용프로그램 이벤트

오류 있는 응용 프로그램 dmdocbroker.exe, 버전 0.0.0.0, 타임스탬프 0x4a252f89, 오류 있는 모듈 ntdll.dll, 버전 6.0.6002.18005, 타임스탬프 0x49e03824, 예외 코드 0x80000003, 오류 오프셋 0x00010004, 프로세스 ID 0x11fc, 응용 프로그램 시작 시간 0x01ca62cc33f51acc.”

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

Thanks/B.K.Hwang

exsoft

Hi,

Pls send me solution, if you know Microsoft's change.

Thanks/B.K.Hwang

apriam_i

Pls, open Documentum Management Console, tab "Docbroker", button "VIew Log".

Does ping to cluster IP address goes well?

Francois Dauberlieu

Can you translate the log for us, I'm not too good in other languages than French, English and Dutch

exsoft

Hi,

This is docbroker.log.

Thanks/B.K.Hwang

EMC Documentum Connection Broker (version 6.5.0.221 SP2 Win32)
(c) Copyright EMC Corp., 1994 - 2009
Thu Dec 03 16:24:03 2009 726000 [DM_DOCBROKER_I_START]info: "Docbroker has started. Process id: 4908"
Thu Dec 03 16:24:03 2009 730000 [DM_DOCBROKER_I_REGISTERED_PORT]info: "The Docbroker registered using port (1489)."
Thu Dec 03 16:24:03 2009 730000 [DM_DOCBROKER_I_LISTENING]info: "The Docbroker is listening on network address: (INET_ADDR: family: 2, port: 1489, host: SKSHIPMISSQL1 (169.254.1.153, 9901fea9))"
Thu Dec 03 16:24:03 2009 731000 [DM_DOCBROKER_I_LISTENING]info: "The Docbroker is listening on network address: (INET_ADDR: family: 23, port: 1489, host: SKSHIPMISSQL1 (FE80:0:0:0:9C2C:97AB:71FB:996, 00000000))"

Francois Dauberlieu

Just to see, can you switch off the Firewall on this box to see if it works ? if it does, allow TCP connections to port 1489

apriam_i

Tell me please, does ping to cluster IP address goes well?

exsoft

Hi,

Yes, ping to cluster IP goes well and ping to Cluster hostname goes well, also.

Thanks/B.K.Hwnag

Francois Dauberlieu

doesn't mean you can reach the port though

apriam_i

Pls, on problem node open Documentum Management Console, tab "Docbroker", button "Edit Service".

post here Description and Command values.

bdipso

Hi,

Did you find a solution to your problem? I have the same thing.

Docbroker is not starting from the cluster, with the error which I can see from system event log :

Faulting application dmdocbroker.exe, version 0.0.0.0, time stamp 0x4a252f89, faulting module ntdll.dll, version 6.0.6001.18000, time stamp 0x4791a783, exception code 0x80000003, fault offset 0x00010004, process id 0x1558, application start time 0x01caa0c6c2d34821.

What I did is :

1) Add -host <hostname> parameter to Docbroker service startup

2) Add Virtual Hostname within dependencies in cluster

When I start docbroker on one of the nodes (that has the resources) I am able to start Repository service from the Failover Cluster Management, but not DocBroker.

Any help is greatly appreciated.

Thanks.

bdipso

This is the answer that we get from the support team about the issue:

We have continued to investigate EMC Service Request XXXXX - Installing CS on Windows 2008 with MSCS support failing.

From searching we found that you¿re hitting bug CS-12396 - documentum binaries fails after installing version 6.5 SP1.

The engineers / developers are aware of the bug and the issue has been fixed in the next release, Content Server 6.5 SP3. Unfortunately there is no option to provide a hot fix for this issue because it requires build changes.

The recommendation would be,
- Continue using Content Server 6.5 SP2 and upgrade to 6.5 SP3 when its released.
- Install Content Server 6.5 SP3 when it is released.

Please note that Content Server 6.5 SP3 is due to be released in approximately 2 months time from now.