Chapter 11: Troubleshooting
Troubleshooting Replication
242
Troubleshooting
Replication
Table 16 contains a series of troubleshooting symptoms and their possible
causes that can help in locating and correcting technical issues.
If you need to call Aladdin’s Technical Support, it would be helpful to have on-
hand the
sccservers.ini
file from each SafeWord server, and make sure its
filename contains the server’s IP address and/or name.
Important: If any of the resolutions listed here involve changing the sccservers.ini
file, the Admin server will need to be restarted for the change(s) to take effect.
Table 16:
Troubleshooting replication
Symptom
Poss. cause
Resolution
When attempting to connect to
MySQL, the message below
appears.
ERROR 2003: Can't connect to
MySQL server on 'localhost'
(10061)
Note: This message can occur
when attempting to login using
the MySQL command line
login, QueryChangeLog.bat,
MonitorChangeLog.bat, or
AddReplPeer.bat.
Terminal
Services is
running in
execute
mode.
Switch Terminal Services
to install mode so MySQL
is executed using local
workstation paths.
Use one of the following 2
methods:
1
Run the following
command first ‘change
user /install’.
2
Run the scripts listed to
the left using the
tsexec.exe
.
Examples:
tsexec.exe
AddReplPeer.bat
<IPaddress>
tsexec.exe
QueryChangeLog.bat
txexec.exe mysql –u root -
ppassword
Replication is not working.
•
QueryChangeLog.bat
never
shows entries in the
ChangeLog. (Empty Set)
•
No errors found in
SccAdSrvrlog.txt
or
SafeWord EV log
.
Replication is
not enabled in
the
sccservers.ini
file.
Verify
#DBActionListenerClass
line in
sccservers.ini
file is
uncommented. This line
must be uncommented in
order to turn replication ON
and for DB changes to be
propagated to the
ChangeLog.
More...