Author Topic: Unable to start the LibSrvr service in Configurator (Win fix pack 8.5.0.5)  (Read 3822 times)

sumit.uppal

  • Guest
Hi,

On Windows 2008 - 64 bit server -
- Installed DB2
- Installed OnDemand for Windows 8.5.0.0
- Created the DB, sys log, etc
- Installed fix pack 8.5.0.5

Now when I try to start the LibSrvr service from the configurator it says 'Starting' and then 'Stopped'. Checked the Windows Event Viewer and I get the following message -

"The OnDemand LibSrvr (ARCHIVE) service terminated with service-specific error The handle is invalid.."

Please suggest if anyone has faced this issue and how to resolve this.

XML from the Event viewer -
 <System>
    <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
    <EventID Qualifiers="49152">7024</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2012-08-24T15:02:38.189211400Z" />
    <EventRecordID>5881</EventRecordID>
    <Correlation />
    <Execution ProcessID="492" ThreadID="816" />
    <Channel>System</Channel>
    <Computer>CTSINTBMVCOE16.AXAP8DEV.COM</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">OnDemand LibSrvr (ARCHIVE)</Data>
    <Data Name="param2">%%6</Data>
  </EventData>

sumit.uppal

  • Guest

Update:

Brought the version down to fix pack 8.5.0.1 for Windows 64 bit and it worked fine and was able to start the service. Something is wrong with 8.5.0.5 for Windows.


Alessandro Perucchi

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1002
    • View Profile
Hello Sumit,

can you try also with version 8.5.0.2, 8.5.0.3, 8.5.04?

I ask that, because between V8.5.0.1 and 8.5.0.2 there is a huge change concerning the code pages.
Meaning that if you have the same problem with 8.5.0.2+, then the problem is not CMOD but yours, since you didn't follow the upgrade path between 8.5.0.1 -> 8.5.0.2+.

Hint, read the README, and add the ARS_ORIGINAL_CODEPAGE settings after the launch of "arsdb -I <instance> -u" will tell you which value to use.

Sincerely yours,
Alessandro
Alessandro Perucchi

#Install #Migrations #Conversion #Educate #Repair #Upgrade #Migrate #Enhance #Optimize #AIX #Linux #Multiplatforms #DB2 #Windows #Oracle #TSM #Tivoli #Performance #Audits #Customizing #Availability #HA #DR #JavaApi #ContentNavigator #ICN #WEBi #ODWEK #Services #PDF #AFP #XML

sumit.uppal

  • Guest
Hi Alessandro,

As per your recommendation, did the following -

- Installed 8.5.0.0
- Installed the fix pack for 8.5.0.1 on top of the install (Was able to start the Lib server)
- Installed the fix pack for 8.5.0.2 on top of the install (Lib server not starting)
- Installed the fix pack for 8.5.0.3 on top of the install (Lib server not starting)
- Installed the fix pack for 8.5.0.4 on top of the install (Lib server not starting)
- Installed the fix pack for 8.5.0.5 on top of the install (Lib server not starting)

After running the arsdb command, it gave back territory - US, Code page 1208, Code set - UTF-8.

Please share your thoughts on how to debug this issue.

Kind regards,
Sumit