Service Startup Issue: Documentum 6.6 Dev Edition on Windows Server 2008 R2

Hi Folks,

I recently installed Documentum 6.6 (Dev Edition) on a Windows Server 2008 (R2) VM. The installation went without a hitch, and I selected the bundled Microsoft SQL Server 2005 as I did not have it running already on the machine.

However, when I try to start the service via Administrative Tools > Services, DmServer service fails to start. Turning on the debug logs, I found the following in the DmServerOemService.log file:

INFO | jvm 1 | 2011/01/25 06:22:23 | Non-daemon thread count = 5 - 1(system) = 4

INFO | jvm 1 | 2011/01/25 06:22:24 | java.lang.Exception: Repository start command returned 2

INFO | jvm 1 | 2011/01/25 06:22:24 | at com.documentum.install.servicewrapper.impl.Service.startComponentProcess(Service.java:199)

INFO | jvm 1 | 2011/01/25 06:22:24 | at com.documentum.install.servicewrapper.impl.Service.startComponent(Service.java:176)

INFO | jvm 1 | 2011/01/25 06:22:24 | at com.documentum.install.servicewrapper.impl.Service.startAll(Service.java:254)

INFO | jvm 1 | 2011/01/25 06:22:24 | at com.documentum.install.servicewrapper.impl.JavaServiceWrapperType3$StartupApplication.run(JavaServiceWrapperType3.java:183)

INFO | jvm 1 | 2011/01/25 06:22:24 | WrapperManager.stop(1) called by thread: Thread-1

INFO | jvm 1 | 2011/01/25 06:22:24 | Send a packet STOP : 1

DEBUG | wrapperp | 2011/01/25 06:22:24 | read a packet STOP : 1

DEBUG | wrapper | 2011/01/25 06:22:24 | JVM requested a shutdown. (1)

DEBUG | wrapper | 2011/01/25 06:22:24 | wrapperStopProcess(1) called.

DEBUG | wrapper | 2011/01/25 06:22:24 | Sending stop signal to JVM

DEBUG | wrapperp | 2011/01/25 06:22:24 | send a packet STOP : NULL

INFO | jvm 1 | 2011/01/25 06:22:24 | Received a packet STOP :

INFO | jvm 1 | 2011/01/25 06:22:24 | Non-daemon thread count = 2 - 1(system) = 1

INFO | jvm 1 | 2011/01/25 06:22:25 | Thread, Thread-1, handling the shutdown process.

INFO | jvm 1 | 2011/01/25 06:22:25 | calling listener.stop()

INFO | jvm 1 | 2011/01/25 06:22:25 | Stopping all service components.

Has anyone else encountered this issue, and found a workaround? Any help would be greatly appreciated.

Thanks in advance!

Find more posts tagged with

Comments

Julien.Fontaine

Chandurs,

To have more information on your trouble, try to start the services independently. First the Java Method Server, then the docbroker and the docbase (the database first).

chandurs

Hi Julien,

Thanks for the response. I tried starting services one by one, but ran into the same issue. Digging further, I came across entries in the "DmServerOem.xml" file which seems to indicate that one of the Documentum related services, the "DmServer" service, is not registered successfully.

Only the following services are registered:

Connection Broker

Database Server

Due to the missing DmServer service, the DmServerOem (wrapper) fails with error code 2. If you have any information about how to recreate the service (or the necessary command-line arguments for it), please let me know.

Thanks again!
Sandeep

Miller-zzMST

Hi Sandeep,

After installation I have 6 services (my Documentum home is c:\documentum, user home is c:\program files\documentum, installation owner is user D630, OS is WinXP):

1	DmServerOem	"C:\Program Files\Documentum\tools\javaServiceWrapper\3.2.0\bin\dctmservice.exe" -s "C:\Documentum\oem\conf\wrapper.conf""
2	DmServerdocumentum	C:\Documentum\product\6.6\bin\documentum.exe -docbase_name documentum -security acl -init_file C:\Documentum\dba\config\documentum\server.ini -run_as_service -install_owner D630 -logfile C:\Documentum\dba\log\documentum.log
3	DmDocbroker	C:\Documentum\product\6.6\bin\dmdocbroker.exe -init_file C:\Documentum\dba\Docbroker.ini -logfile C:\Documentum\dba\log\Docbroker.Docbroker.log -port 1489 -run_as_service
4	DmMethodServer	"C:\Program Files\Documentum\tools\javaServiceWrapper\3.2.0\bin\dctmservice.exe" -s "C:\Documentum\jboss4.3.0\server\serviceConfig\MethodServer\conf\wrapper.conf""
5	MSSQL$DOCUMENTUMDB	c:\Documentum\mssql\MSSQL.1\MSSQL\Binn\sqlservr.exe -sDOCUMENTUMDB
6	SQLWriter	c:\Program Files\Microsoft SQL Server\90\Shared\sqlwriter.exe""

First 5 of them are started manually. Only for SQLWriter startup type os automatic. When I need to run the system I just start the 1st service DmServerOem.

First 4 of them are runned under installation owner account. MSSQL$DOCUMENTUMDB - under NetworkService account. SQL Writer - under LocalService account.

Also I attached the .reg files with Deocumentum services: separate file for 1 service.

- Konstantin

ndbhatt

Hi Konstantin,

I am facing exact same issue as Sandeep. All services run fine except for the Documentum Master Service which keeps stopping as soon as I try to start it again.

Here's what the DmServerOemService.log reads repeatedly

TATUS | wrapper | 2011/01/26 21:40:13 | --> Wrapper Started as Service
STATUS | wrapper | 2011/01/26 21:40:13 | Launching a JVM...
INFO   | jvm 1    | 2011/01/26 21:40:14 | Wrapper (Version 3.2.0) http://wrapper.tanukisoftware.org
INFO   | jvm 1    | 2011/01/26 21:40:14 |
INFO   | jvm 1    | 2011/01/26 21:40:19 | Starting Documentum Master Service Service components...
INFO   | jvm 1    | 2011/01/26 21:40:22 | Starting Database Server...
INFO   | jvm 1    | 2011/01/26 21:40:24 | java.lang.Exception: Database Server start command returned 1
INFO   | jvm 1    | 2011/01/26 21:40:24 | at com.documentum.install.servicewrapper.impl.Service.startComponentProcess(Service.java:199)
INFO   | jvm 1    | 2011/01/26 21:40:24 | at com.documentum.install.servicewrapper.impl.Service.startComponent(Service.java:176)
INFO   | jvm 1    | 2011/01/26 21:40:24 | at com.documentum.install.servicewrapper.impl.Service.startAll(Service.java:254)
INFO   | jvm 1    | 2011/01/26 21:40:24 | at com.documentum.install.servicewrapper.impl.JavaServiceWrapperType3$StartupApplication.run(JavaServiceWrapperType3.java:183)
INFO   | jvm 1    | 2011/01/26 21:40:25 | Stopping all service components.
INFO   | jvm 1    | 2011/01/26 21:40:29 | Application Server is already stopped
INFO   | jvm 1    | 2011/01/26 21:40:33 | Repository is already stopped
INFO   | jvm 1    | 2011/01/26 21:40:37 | Connection Broker is already stopped
INFO   | jvm 1    | 2011/01/26 21:40:41 | Database Server is already stopped
INFO   | jvm 1    | 2011/01/26 21:40:41 | All components stopped.
STATUS | wrapper | 2011/01/26 21:40:42 | <-- Wrapper Stopped
STATUS | wrapper | 2011/01/26 21:42:17 | --> Wrapper Started as Service
STATUS | wrapper | 2011/01/26 21:42:18 | Launching a JVM...
INFO   | jvm 1    | 2011/01/26 21:42:18 | Wrapper (Version 3.2.0) http://wrapper.tanukisoftware.org

I am running Vista 64 bit, 8GB RAM and AMD 4000+ processor. I am using Documentum 6.6 OEM. I have had successfully installed it before and used it for over a month until I tried to install forms builder and process builder on same machine. I tried reinstallation over a dozen times with same result.

I am clueless as to why Documentum Master Service keeps stopping in few seconds.

Any insight to resolve this problem is highly appreciated.

Thanks,

Nikhil

chandurs

Hi Konstantin,

Thanks a lot for your response, and sending across the REG files. This was *very* helpful.

Nikhil and anyone else, here's what I did:

1. Examined the DmServerdocumentum.reg file to figure out the command line arguments being passed to documentum.exe

2. Noticed that the installer had, in fact, failed to create a repository. Now, I am not sure if this is part of the installation, so I may be wrong.

3. Ran the following program to create a repository: C:\Documentum\product\6.6\install\Server_Configuration_Program.exe

4. After setting the ports, passwords, creating a new DB user and database, reached the "Next Steps - Edit Installation Scripts" stage

At this stage, the config program tries to run a bunch of scripts starting with "Docbase HeadStart", "Update Format Objects", etc. These are a bunch of *.ebs scripts.

The headstart script itself failed, and from my understanding of the script, it was trying to look for the Verity full text indexing engine, which I don't have on my server. In order to work around this issue, I edited the headstart.ebs script to explicitly set a value for the "ftEngine" variable. Here is what I did:

ftEngine = "Lucene" 'This line added by me; the rest is as it was.

If ftEngine = "Fast" Then

FTVendorStr = "fast"

ElseIf ftEngine = "Lucene" Then

FTVendorStr = "lucene"

ElseIf ftEngine = "dsearch" Then

FTVendorStr = "dsearch"

Else

Print "Invalid fulltext vendor " & ftEngine & " specified."

DmExit(-1)

End If

Once this change was done, the rest of the setup went smoothly, and a repository was created. It still remains to be seen if everything is the way it should be; I will update this post if I run into any further issues.

Thanks again for your help!

ndbhatt

Hi Chandurs,

How did the install go after changes implemented by you?

I tried following the steps depicted by you in your earlier post. I wasn't able to make the services working. However, I have uninstalled documentum but now reinstall doesn't work. I suspect something went awry with my registry while I tried to manual delete SQL registries.

I will wait for some more suggestions, if any, for a day or two. If not, then I will have no choice, but to reinstall my OS and redo all over again.

Thanks,

Nikhil

rodriguez_luis

I'm trying to follow thw steps of Chandurs, changing my HeadStart.ebs for one corrected between the installation of Content Server and the creation of the repository ... but now I take an error message about "not able to create Index Agent" ...

Any clue to SOLVE the installation problem or any other workaround?

chandurs

Hi Luis,

Do you recall at what stage of the installation you see this message? The installation shows a list of steps that will be executed, in order. Perhaps if you can find the step and look at the relevant EBS script, we can find something.

Again, I am not familiar with EBS, I just managed to figure it out by looking at the source and coming up with a quick-fix, nothing more. The developer edition installation seems to have a lot of issues.

Cheers,

Sandeep

rodriguez_luis

Finally it worked, but I can't understand ...

I changed the HeadStart file between Content Server install and repository creation. Then the repository WAS NOT created.

After this, I launched again the ServerConfig, I created a new repository with a new database connection, and without any other change, it worked fine ...

This should be a bug in the installer, I'll try to open a SR about it.

chandurs

Thanks, that'd be great if you can open an SR.

Also, you're right in executing ServerConfig, my assumption was it would be executed as part of the installation, apparently I was wrong.

chandurs

Hi Luis,

Any luck in opening the SR and/or a solution for the deployment issue?

Thanks,

Sandeep