cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Community Helping Community

LMS 3.2.1 CmfDbMonitor Connection Error

2113
Views
5
Helpful
0
Comments
Enthusiast

A while back I ran across a quirky issue that consumed a number of hours to resolve. I documented it and perhaps it can save you some effort.

The problem description indicated that from within any portal page an error is displayed stating that the DCR server is down.

It was determined that services dependant on CmfDbMonitor were not starting.

Process= CmfDbMonitor
State  = Waiting to initialize.
Info   = Server started by admin request

And from the logs:

CmfDbMonitor ERROR {Thu Aug 18 16:46:26 2011} SQLDriverConnect: 
[Sybase][ODBC Driver][SQL Anywhere]Connection error:
Found server but communication error occurred; SqlState: 08001

Output of cwjava -cw <NMSROOT> com.cisco.nm.cmf.dbservice2.DBConnection cmf 
shows it cannot connect to JVM.

We then validated the database and received no errors!

But...

C:\Documents and Settings\Administrator>C:\PROGRA~1\CSCOpx\bin\cwjava -cw C:\PRO
GRA~1\CSCOpx\ com.cisco.nm.cmf.dbservice2.DBConnection cmf

java.sql.SQLException: JZ006: Caught IOException: java.net.ConnectException: Con
nection refused: connect
        at com.sybase.jdbc2.jdbc.ErrorMessage.raiseError(ErrorMessage.java:533)
        at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead(ErrorMessage.java:837)
        at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3558)
        at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3503)
        at com.sybase.jdbc2.tds.Tds.login(Tds.java:421)
        at com.sybase.jdbc2.jdbc.SybConnection.tryLogin(SybConnection.java:247)
        at com.sybase.jdbc2.jdbc.SybConnection.regularConnect(SybConnection.java:223)
        at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:198)
        at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:132)
        at com.sybase.jdbc2.jdbc.SybDriver.connect(SybDriver.java:179)
        at java.sql.DriverManager.getConnection(DriverManager.java:582)
        at java.sql.DriverManager.getConnection(DriverManager.java:154)
        at com.cisco.nm.cmf.dbservice2.DBConnection.<init>(DBConnection.java:224)
        at com.cisco.nm.cmf.dbservice2.DBConnection.<init>(DBConnection.java:107)
        at com.cisco.nm.cmf.dbservice2.DBUtil.getDBConnection(DBUtil.java:29)
        at com.cisco.nm.cmf.dbservice2.DBConnection.main(DBConnection.java:822)

CmfDbEngine           Program started - No mgt msgs received    9012
CmfDbMonitor          Waiting to initialize.                    9748

Next we attempted a dbping -z -c "eng=cmfEng" and received Ping server successful. However dbping -z -c "dsn=cmf" returned:


Attempting to connect using:
DBN=cmfDb;DBF=C:\PROGRA~1\CSCOpx\databases\cmf\cmf.db;ENG=cmfEng;START=dbsrv10;A
STOP=yes;DSN=cmf;LINKS='tcpip{HOST=localhost;DOBROADCAST=NO;ServerPort=43441}'
Attempting to connect to a running server...
Trying to start TCPIP link ...
TCP using Winsock version 2.2
My IP address is 10.3.65.65
My IP address is 127.0.0.1
    TCPIP link started successfully
Attempting TCPIP connection (address 127.0.0.1:43441 found in sasrv.ini cache)
Looking for server with name cmfeng
Trying to find server at address localhost
Found server, verifying server name
Verification of server name failed
Sending broadcast to find server
Found database server at address 127.0.0.1:43441
Found database server cmfeng on TCPIP link
Connected using client address 127.0.0.1:3051
Connected to server over TCPIP at address 127.0.0.1:43441
Communication function sconn::receive code 4
Communication function ApplicationConnect code 3
Client disconnected
Cannot connect to server
Ping server failed -- Connection error: Found server but communication
error occurred.

Note Startup Parameters:


-x tcpip{HOST=localhost;DOBROADCAST=NO;ServerPort=43441} -m -ti 0 -gm
200   -c 8M -n cmfEng C:\PROGRA~1\CSCOpx\databases\cmf\cmf.db -n cmfDb

Finally we saw a dll that did not appear to be needed as it is primarily used by APC.  pl15w2sp.dll

618771299_pl15w2sp.png

The dll is related to LSP (http://en.wikipedia.org/wiki/Layered_Service_Provider)

A common issue is corruption of the Winsock catalog in the registry, and the entire TCP/IP  stack could fail.

The ultimate fix was found here: http://www.rarst.net/software/layered-service-provider-fix/

CreatePlease to create content
Content for Community-Ad
FusionCharts will render here

This widget could not be displayed.