Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements
Webcast-Catalyst9k
New Member

CiscoWorks2k crashes - frustrating HELP!

CW2k 5th Ed, RME 3.4 with latest IDU, Campus 3.2 with latest IDU. Running on Win2k Server SP2. Server has no other application installed.

CiscoWorks experiencing frequent crashes. Here is what looks like on the CmfDbMonitor.log. And the same applies to EssentialsDbMonitor.log. Whenever, it happened we have to stop and restart services. This recurrance since day one of installation. Attempted reinstall new OS, and CW2k from scratch and getting same results.

CmfDbMonitor {Fri Oct 24 15:29:11 2003} Running DbMonitor version 2.1

CmfDbMonitor {Fri Oct 24 15:29:12 2003} Sending Initial OK Message to process manager.

CmfDbMonitor ERROR {Mon Oct 27 10:29:28 2003} SQLDriverConnect: [Sybase][ODBC Driver][Adaptive Server Anywhere]Unable to connect to database server: Database server not running; SqlState: 08001

CmfDbMonitor WARNING {Mon Oct 27 10:29:28 2003} Failed to connect to database. Retry number = 1 of 10.

CmfDbMonitor ERROR {Mon Oct 27 10:30:58 2003} SQLDriverConnect: [Sybase][ODBC Driver][Adaptive Server Anywhere]Unable to connect to database server: Database server not running; SqlState: 08001

CmfDbMonitor WARNING {Mon Oct 27 10:30:58 2003} Failed to connect to database. Retry number = 2 of 10.

CmfDbMonitor ERROR {Mon Oct 27 10:32:28 2003} SQLDriverConnect: [Sybase][ODBC Driver][Adaptive Server Anywhere]Unable to connect to database server: Database server not running; SqlState: 08001

CmfDbMonitor WARNING {Mon Oct 27 10:32:28 2003} Failed to connect to database. Retry number = 3 of 10.

CmfDbMonitor ERROR {Mon Oct 27 10:33:58 2003} SQLDriverConnect: [Sybase][ODBC Driver][Adaptive Server Anywhere]Unable to connect to database server: Database server not running; SqlState: 08001

CmfDbMonitor WARNING {Mon Oct 27 10:33:58 2003} Failed to connect to database. Retry number = 4 of 10.

CmfDbMonitor ERROR {Mon Oct 27 10:35:28 2003} SQLDriverConnect: [Sybase][ODBC Driver][Adaptive Server Anywhere]Unable to connect to database server: Database server not running; SqlState: 08001

CmfDbMonitor WARNING {Mon Oct 27 10:35:28 2003} Failed to connect to database. Retry number = 5 of 10.

CmfDbMonitor ERROR {Mon Oct 27 10:36:58 2003} SQLDriverConnect: [Sybase][ODBC Driver][Adaptive Server Anywhere]Unable to connect to database server: Database server not running; SqlState: 08001

CmfDbMonitor WARNING {Mon Oct 27 10:36:58 2003} Failed to connect to database. Retry number = 6 of 10.

CmfDbMonitor ERROR {Mon Oct 27 10:38:28 2003} SQLDriverConnect: [Sybase][ODBC Driver][Adaptive Server Anywhere]Unable to connect to database server: Database server not running; SqlState: 08001

CmfDbMonitor WARNING {Mon Oct 27 10:38:28 2003} Failed to connect to database. Retry number = 7 of 10.

CmfDbMonitor ERROR {Mon Oct 27 10:39:58 2003} SQLDriverConnect: [Sybase][ODBC Driver][Adaptive Server Anywhere]Unable to connect to database server: Database server not running; SqlState: 08001

CmfDbMonitor WARNING {Mon Oct 27 10:39:58 2003} Failed to connect to database. Retry number = 8 of 10.

CmfDbMonitor ERROR {Mon Oct 27 10:41:28 2003} SQLDriverConnect: [Sybase][ODBC Driver][Adaptive Server Anywhere]Unable to connect to database server: Database server not running; SqlState: 08001

CmfDbMonitor WARNING {Mon Oct 27 10:41:28 2003} Failed to connect to database. Retry number = 9 of 10.

CmfDbMonitor ERROR {Mon Oct 27 10:42:58 2003} SQLDriverConnect: [Sybase][ODBC Driver][Adaptive Server Anywhere]Unable to connect to database server: Database server not running; SqlState: 08001

CmfDbMonitor WARNING {Mon Oct 27 10:42:58 2003} Failed to connect to database. Retry number = 10 of 10.

CmfDbMonitor ERROR {Mon Oct 27 10:44:28 2003} Unable to connect to database after trying 10 times.

CmfDbMonitor ERROR {Mon Oct 27 10:44:28 2003} Cannot connect to the database. Shutting down the process CmfDbMonitor.

1 REPLY
New Member

Re: CiscoWorks2k crashes - frustrating HELP!

The issue seems to be with the Database. Re-initialise the database connections. May be it could work.

173
Views
0
Helpful
1
Replies
CreatePlease to create content