Cisco Cisco Agent Desktop 8.5 Guia De Resolução De Problemas
Cisco CAD Troubleshooting Guide
56
April 3, 2014
d. Ensure that the port or named pipe used to connect to the CAD SQL
instance on the Recording and Statistics Database Configuration node is
valid and available for use by the CAD SQL instance on each server.
valid and available for use by the CAD SQL instance on each server.
You can see what ports are in use on the system and what the CAD SQL
instance is using to listen for connections with the
instance is using to listen for connections with the
netstat
command.
Verify that what the CAD SQL instance on both servers are using to listen
for connections are the same and match what is entered on the
Recording and Statistics Database Configuration node.
for connections are the same and match what is entered on the
Recording and Statistics Database Configuration node.
NOTE: Use the command line
netstat-abo
to get a listing of
all the processes that are listening for connections and the
ports on which they are listening. If you cannot find the
process for the CAD SQL instance in the output of this
command, then the CAD SQL instance in not running or there
is something wrong with the CAD SQL instance configuration.
ports on which they are listening. If you cannot find the
process for the CAD SQL instance in the output of this
command, then the CAD SQL instance in not running or there
is something wrong with the CAD SQL instance configuration.
■
If all these steps were performed correctly, but the FCRasSvr database is
still not created, this suggests a credentials, permissions, or firewall issue
is preventing the execution of the CAD SQL scripts required to create the
database. Verify the correctness of these items. To assist troubleshooting
further, move onto the next troubleshooting item, but replace the
parameter
still not created, this suggests a credentials, permissions, or firewall issue
is preventing the execution of the CAD SQL scripts required to create the
database. Verify the correctness of these items. To assist troubleshooting
further, move onto the next troubleshooting item, but replace the
parameter
-d FCRasSvr
with
-d master
, which will help identify
connectivity issues to the SQL instance.
9. Ensure that you can run a SQL query between both systems, from each
system. Follow these steps:
a. On server A, log in as the user attempting to authenticate into the SQL
instance. This can be simulated with the Run-As feature in Windows. To
use the Run-As feature on versions of Windows prior to Server 2008,
right-click on the command prompt executable and select Run as. For
Server 2008 and later, hold down the Shift key, then right-click on the
command prompt executable and select Run as different user.
use the Run-As feature on versions of Windows prior to Server 2008,
right-click on the command prompt executable and select Run as. For
Server 2008 and later, hold down the Shift key, then right-click on the
command prompt executable and select Run as different user.
b. As the CAD SQL instance user, open a command prompt, and enter the
following queries for systems using Windows (NT) Authentication:
TCP/IP
sqlcmd -E -S tcp:<ServerA HostName or IP address>\<CAD SQL
Instance Name>,<port number> -d FCRasSvr -Q "SELECT
@@VERSION"
Instance Name>,<port number> -d FCRasSvr -Q "SELECT
@@VERSION"
sqlcmd -E -S tcp:<ServerB HostName or IP address>\<CAD SQL
Instance Name>,<port number> -d FCRasSvr -Q "SELECT
@@VERSION"
Instance Name>,<port number> -d FCRasSvr -Q "SELECT
@@VERSION"
Named Pipes
sqlcmd -E -S np:\\<ServerA HostName or IP address>\pipe\
MSSQL$<CAD SQL Instance Name>\sql\query -d FCRasSvr -Q
"SELECT @@VERSION"
MSSQL$<CAD SQL Instance Name>\sql\query -d FCRasSvr -Q
"SELECT @@VERSION"