Cisco Cisco Agent Desktop 8.5 Guide De Dépannage

Page de 126
Troubleshooting Recording and Statistics Service SQL Server Replication Problems
April 3, 2014
55
7. Ensure that there are no User Account Control (UAC) issues on the two 
systems. For troubleshooting, completely turn off UAC on both systems 
temporarily. If issues are resolved after turning off UAC, then UAC is at fault. 
User permissions need to be remedied in Windows and/or SQL Server. More 
information on the effects of UAC on SQL Server can be found at:
8. Ensure that the FCRasSvr database exists on both servers. This can be 
verified by viewing the databases present in SQL Server Management Studio. 
If this database does not exist, try the following troubleshooting steps:
a. Verify that all the steps in the “Configuring SQL Server 2005 for CAD 8.5” 
and the “Recording and Statistics Database” sections of the Cisco CAD 
Installation Guide
 were performed correctly.
b. If the steps were performed correctly, but the FCRasSvr database still 
cannot be created, verify that the SQL Server, SQL Server Agent, and the 
SQL Server Browser services for the CAD SQL instance are all running in 
the Windows Services list. If they are not set to automatic startup, then 
you must turn automatic startup on.
c. If the required SQL services are running properly, but the FCRasSvr 
database is still not created, try the following: 
— If you are using NT Authentication (recommended), ensure that the 
user entered in the Recording and Statistics Database Configuration 
node of the CAD Configuration Setup utility exists on the local 
machine with correct credentials and administrator permissions. This 
user must also exist as a provisioned administrator for the CAD SQL 
instance.
— If you are using SQL Authentication, ensure that the user entered in 
the Recording and Statistics Database Configuration node exists as a 
login on the CAD SQL instance and has sysadmin privileges on the 
CAD SQL instance. 
Also, the CAD SQL instance Server Authentication mode must be 
configured to use both SQL Server and Windows (NT) Authentication 
(Mixed Mode). The default is Windows (NT) Authentication only. These 
settings can be configured with SQL Server Management Studio. 
Refer to your Microsoft SQL Server documentation for more 
information.
NOTE:  SQL Server Authentication is not recommended as a 
login mechanism by Microsoft. The security best practice is to 
use NT Authentication only.