Cisco Cisco Agent Desktop 9.0 Fehlerbehebungsanleitung
Troubleshooting Recording and Statistics Service SQL Server Replication Problems
March 13, 2015
57
This can be simulated with the Run-As feature in Windows. Hold down the
Shift key, then right-click on the command prompt executable and select Run
as different user.
Shift key, then right-click on the command prompt executable and select Run
as different user.
For more information about provisioning users for SQL refer to the Cisco CAD
Installation Guide.
Installation Guide.
Also, more information can be found here:
4. Ensure that CAD SQL instance password does not contain any special
characters (for example, & | = ; <). Although these are valid characters per
MSSQL specification, they will not work with the CAD scripts that interface
with the SQL engine.
MSSQL specification, they will not work with the CAD scripts that interface
with the SQL engine.
5. In SQL Server Management Studio, connect to the CAD SQL instance and run
the
sp_helpserver
query. If the server name given does not match what the
CAD SQL instance recognizes as the server name, then you must change the
server name in SQL Server Management Studio. To change the server name:
server name in SQL Server Management Studio. To change the server name:
a. Run the query:
sp_dropserver ‘<server name>\<instance>’,‘droplogins’
where:
<server name>
is the incorrect server name given by the
sp_helpserver
query
<instance>
is the name of the CAD SQL instance
Click Ok.
b. Then run the query:
sp_addserver ‘<server name>\<instance>’,‘local’
where:
<server name>
is the correct server name
<instance>
is the name of the CAD SQL instance
c. Click OK.
6. Ensure there are no firewall issues between the primary and secondary
systems. For troubleshooting, completely turn off the firewalls on both
systems. At a minimum, firewall exceptions are required for SQL Server, SQL
Server Agent, and SQL Server Browser for the CAD SQL instance CAD on both
servers.
systems. At a minimum, firewall exceptions are required for SQL Server, SQL
Server Agent, and SQL Server Browser for the CAD SQL instance CAD on both
servers.
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:
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: