Author Topic: Cfg DBServer can't connect to database  (Read 1450 times)

Offline CGB

  • Newbie
  • *
  • Posts: 13
  • Karma: 0
Cfg DBServer can't connect to database
« on: January 25, 2018, 06:21:19 AM »
This is awkward... I've been a few years playing with Genesys in a lab machine over VMWare but suddenly I can't do it anymore. I was building some strategies yesterday when something failed on VMWare, I got an error message and the everything get closed automatically. I opened again Vmware, powered on the virtual machine and since then... the cfg dbserver is not able to connect the database. Maybe the vmware failure corrupted anything but it doesn't make much sense for me...

Anyway... this is what cfg dbserver says...

 +0953  Connection to multiserver created, host 'localhost', port '1042', socket '136'
 +0953  MSG_STARTDB status='DBM_SUCCESS'
ODBC: id='1.1' req='3' Protocols versions: dbclient='00010004' dbserver='00010004' dblib='00010004'
 +0000  Database Access Point in TKVList:
 +0000    section "dbclient":
 +0000      "max-binding-memory" = 250
 +0047  00811808,hDBC=6820680,6820680
 +0047  Open DB: username = 'user1', database = 'config', dbserver = 'labgns'
+17453  Could not connect to SQL Server using SQL Native Client driver. Attemting default MS SQL Server driver...
 +37609  odbcerr: [Microsoft][ODBC SQL Server Driver]Dialog failed
 +37609  MSG_ERROR status='dbNotOpened' msg='[Microsoft][ODBC SQL Server Driver]Dialog failed '


23:08:14.421 Dbg 10749 Forwarding response '3.1' from 'MS SQL: 1.1' to 'App: 1'
23:08:14.421 Dbg 10734 Send message 'MSG_DISCONNECTED' to 'App: 1', request id '-1'
23:08:14.421 Dbg 10734 Send message 'MSG_DISCONNECTED' to 'MS SQL: 1.1', request id '-1'
   /Statistics               
    name                      = MS SQL: 1.1
    app_name                  = App: 1
    req_rcvd                  = 5
    req_sent                  = 4
    data_rcvd                 = 1269
    data_sent                 = 181
    msg_error                 = 1
    msg_log                   = 1
Client MS SQL: 1.1 is being closed. Current numofclients=0
Listener (port id = internal-0-0 fd = 264) is being closed. Checking for clients on listener...
Listener with port id = internal-0-0 has been closed and deleted from list of current ports. Number of db app connections affected: 0
Client App: 1 is being closed. Current numofclients=1
23:08:14.578 Std 05023 Process './dbclient_msql' stopped
   /./dbclient_msql         
    pid                       = 184
    id                        = 0
    expiration_time           = 2018-01-23T23:08:44
    client copy               = 0
    DbClient name             = MS SQL: 1.1
   /Statistics               
    name                      = App: 1
    req_rcvd                  = 4
    req_sent                  = 5
    data_rcvd                 = 165
    data_send                 = 189
    invalid_params            = 0
    abandoned_req             = 0
    abandon_req_fail          = 0
    error_start_client        = 0
    invalid_register_req      = 0
    msg_error                 = 0
    pending_requests          = 0
    pending_queue_size        = 0
    max_pending_requests      = 1
    max_pending_queue_size    = 23
GServer (0xc07228) is being removed. numofclients = 0,current numofserveritems = 1
GServer: new_client: fd=276, found server=232
23:08:24.421 Trc 04521 New client 1115 connected from '127.0.0.1'
23:08:24.437 Dbg 10745 'App: 127.0.0.1:1115' registered; protocol version '1.4' id '2'
23:08:24.437 Dbg 10734 Send message 'MSG_EXTPACKETS' to 'App: 2', request id '0'
23:08:24.437 Dbg 10750 Start client request, dbprocesses per client '1'
23:08:24.437 Dbg 10734 Send message 'MSG_CLIENTSTARTED' to 'App: 2', request id '6'
23:08:24.453 Std 05022 Process './dbclient_msql' started
23:08:24.453 Dbg 10741 'App: 2' has put request id='8' type='MSG_SETCOMMIT' into queue
GServer: new_client: fd=300, found server=264
23:08:24.500 Trc 04521 New client 1118 connected from '127.0.0.1'
23:08:24.500 Dbg 10745 './dbclient_msql' registered; protocol version '1.4' id '2.1'
23:08:24.500 Dbg 10734 Send message 'MSG_OPENDB' to 'MS SQL: 2.1', request id '7'
23:08:24.500 Dbg 10734 Send message 'MSG_EXTPACKETS' to 'App: 2', request id '0'
23:08:24.500 Dbg 10734 Send message 'MSG_EXTPACKET' to 'MS SQL: 2.1', request id '0'
23:08:24.500 Dbg 10743 'MS SQL: 2.1' is spare
23:08:29.640 Dbg 10739 ODBC: id='2.1' req='-1'

I don't know a shit about databases so basically I don't know even where to start to look at it... any suggestion?

I found this on the SQL server logs...

2018-01-23 23:08:20.70 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
2018-01-23 23:08:23.60 spid12s     Starting up database 'msdb'.
2018-01-23 23:08:23.60 spid13s     Starting up database 'config'.
2018-01-23 23:08:23.60 spid14s     Starting up database 'LogDB'.
2018-01-23 23:08:23.60 spid15s     Starting up database 'UCSMain'.
2018-01-23 23:08:25.21 spid14s     Error: 9003, Severity: 20, State: 9.
2018-01-23 23:08:25.21 spid14s     The log scan number (68500:344:1) passed to log scan in database 'LogDB' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.
2018-01-23 23:08:25.62 spid14s     Error: 3414, Severity: 21, State: 1.
2018-01-23 23:08:25.62 spid14s     An error occurred during recovery, preventing the database 'LogDB' (database ID 6) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
2018-01-23 23:08:25.62 spid14s     Starting up database 'IxnDB'.
2018-01-23 23:08:25.76 spid15s     2 transactions rolled forward in database 'UCSMain' (7). This is an informational message only. No user action is required.
2018-01-23 23:08:26.31 spid15s     0 transactions rolled back in database 'UCSMain' (7). This is an informational message only. No user action is required.
2018-01-23 23:08:26.31 spid15s     Recovery is writing a checkpoint in database 'UCSMain' (7). This is an informational message only. No user action is required.
2018-01-23 23:08:27.39 Logon       Error: 18456, Severity: 14, State: 16.
2018-01-23 23:08:27.39 Logon       Login failed for user 'user1'. [CLIENT: <local machine>]
2018-01-23 23:08:27.93 spid12s     Starting up database 'CustomerDB'.
2018-01-23 23:08:28.59 spid15s     Starting up database 'Outbound'.
2018-01-23 23:08:29.15 spid9s      Starting up database 'tempdb'.
2018-01-23 23:08:29.64 Logon       Error: 18456, Severity: 14, State: 16.
2018-01-23 23:08:29.64 Logon       Login failed for user 'user1'. [CLIENT: 127.0.0.1]
2018-01-23 23:08:34.28 spid12s     The Service Broker protocol transport is disabled or not configured.
2018-01-23 23:08:34.28 spid12s     The Database Mirroring protocol transport is disabled or not configured.
2018-01-23 23:08:36.31 spid12s     Service Broker manager has started.
2018-01-23 23:08:38.87 spid13s     WARNING: did not see LOP_CKPT_END.
2018-01-23 23:08:38.87 spid13s     Error: 3414, Severity: 21, State: 2.
2018-01-23 23:08:38.87 spid13s     An error occurred during recovery, preventing the database 'config' (database ID 5) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
2018-01-23 23:08:38.87 spid13s     Error: 3414, Severity: 21, State: 1.
2018-01-23 23:08:38.87 spid13s     An error occurred during recovery, preventing the database 'config' (database ID 5) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
2018-01-23 23:08:38.87 spid5s      Recovery is complete. This is an informational message only. No user action is required.
2018-01-23 23:08:40.25 Logon       Error: 18456, Severity: 14, State: 16.
2018-01-23 23:08:40.25 Logon       Login failed for user 'user1'. [CLIENT: <local machine>]

Let see what google says...
« Last Edit: January 25, 2018, 06:32:29 AM by CGB »

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7172
  • Karma: 56330
Re: Cfg DBServer can't connect to database
« Reply #1 on: January 25, 2018, 06:27:38 AM »
Ermmm is your SQL running?
Can you open a ODBC connection via Windows Control Panel? (google is your friend)
Can you access to the SQL Manager? (Google again)


So, basic tests are as you say, on SQL and Windows side to start with.

Offline CGB

  • Newbie
  • *
  • Posts: 13
  • Karma: 0
Re: Cfg DBServer can't connect to database
« Reply #2 on: January 25, 2018, 06:34:51 AM »
Ermmm is your SQL running?
Can you open a ODBC connection via Windows Control Panel? (google is your friend)
Can you access to the SQL Manager? (Google again)


So, basic tests are as you say, on SQL and Windows side to start with.
I've just edit my first post with SQL server errors haha... yeah, in google we trust ;D

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7172
  • Karma: 56330
Re: Cfg DBServer can't connect to database
« Reply #3 on: January 25, 2018, 06:37:13 AM »
Good luck there, seems ugly, hope you had a backup

Enviado de meu E6633 usando Tapatalk


Offline CGB

  • Newbie
  • *
  • Posts: 13
  • Karma: 0
Re: Cfg DBServer can't connect to database
« Reply #4 on: January 29, 2018, 07:25:38 AM »
Well... The DDBB dies... At least I had a backup of the VM, routing strategies and some configurations... it's something ;D