" /> How to troubleshoot sql log error messages in SCI - Genesys CTI User Forum

Author Topic: How to troubleshoot sql log error messages in SCI  (Read 3866 times)

Offline BobTheBuilder

  • Newbie
  • *
  • Posts: 3
  • Karma: 0
How to troubleshoot sql log error messages in SCI
« on: February 10, 2012, 11:22:37 AM »
Advertisement
Hi

I am guessing I have something misconfigured because I am getting this error message in SCI.

2/10/2012 11:00:46 AM SCI063 Unable to execute SQL: "select count(*) from G_LOG_MESSAGES where (G_LOG_MESSAGES.PRIORITY = 5) ". Error message: "[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'G_LOG_MESSAGES'. " 
2/10/2012 10:59:33 AM SCI033 Unable to establish connection with Solution Control Server on w2003gen:7002. Reason: server not responding. Application monitoring and start/stop functionality will be unavailable.
2/10/2012 10:58:44 AM  Solution Control Interface Version 8.1.000.06 started

I have a running LogDBServer and setup DAP to a SQL Server.  I have a MessageServer with a DAP to the LogDBServer in Connections tab.

Ideally I would like to know how to eg look at logs to see how to troubleshoot this problem.  Or if not at least get some tips :)

Bob

Offline Steve

  • Sr. Member
  • ****
  • Posts: 298
  • Karma: 11
Re: How to troubleshoot sql log error messages in SCI
« Reply #1 on: February 10, 2012, 12:50:16 PM »
I would start by looking up the error code SCI033 in the help. That suggests-

Make sure that SCS is running on the specified host.
Check the network connectivity between the specified host and the computer running SCI.
Make sure that SCS's configuration is correct in the Configuration Layer.
Check the Genesys Migration Guide and Release Notes for information about version compatibility between SCS and SCI. Upgrade SCI if necessary


Work through these, then think about restarting SCS or maybe the server that is hosting it.

Offline BobTheBuilder

  • Newbie
  • *
  • Posts: 3
  • Karma: 0
Re: How to troubleshoot sql log error messages in SCI
« Reply #2 on: February 10, 2012, 01:20:43 PM »
Thanks.

It was the SCI063 I was most interested in.  Accidentally pasted the other error in.

I was using two DAP's and I think that you can only successfully use one - eg first DAP found is used.  so I changed to only use a single DAP and problem was resolved.