I have faced this before ,, well, there is an error occurred on the DB record regarding the date and time at which the RCC is stopped.
as a solution you can advance the RCC clock to skip this error.
Advancing the clock on in the RCC database is version specific. This will potentially skip any problem.......
Note: These are sample dates only. Select the correct date.
Note: RCC downloads in three hour chunks, so advance clock by three hours if still a problem.
Note: Depending on version 2.5 / 2.6, sqlcmd -S.\SQLEXPRESS -dmaster -Usa -PYR46L43! may be replaced with sqlcmd -S.\RCCSQLEXPR -dmaster -Usa -PYR46L43!
Prior to RCC 2.4.309
From command line:
C:\WINNT\SYSTEM32>cd\mysql\bin
C:\mysql\bin> mysql
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 125 to server version: 3.23.53-max-nt
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
mysql> use ccrdb
Database changed
mysql> select * from rptrequesttimes;
+--------------------+---------------------+---------------------+-----------------+
| RPTRequestTimes_id | endDate | CurrentBCMTime | WallboardUpdate |
+--------------------+---------------------+---------------------+-----------------+
| 0 | 2005-02-11 09:00:00 | 2005-02-22 08:02:34 | 0 |
+--------------------+---------------------+---------------------+-----------------+
1 row in set (0.00 sec)
mysql> update rptrequesttimes set endDate = '2005-02-10 09:05:00';
where enddate is maximum of three hours after the invalid XML 'stuck point'.
RCC 2.4.309-2.4.xxx inclusive:
From command line:
C:\WINNT\SYSTEM32>cd\program files\mysql\mysql server 4.1\bin
C: \program files\mysql\mysql server 4.1\bin>mysql–-port=3309
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 162505 to server version: 4.1.14-nt-log
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
mysql> use ccrdb
Database changed
mysql> select * from rptrequesttimes;
+--------------------+---------------------+---------------------+-----------------+
| RPTRequestTimes_id | endDate | CurrentBCMTime | WallboardUpdate |
+--------------------+---------------------+---------------------+-----------------+
| 0 | 2005-02-11 09:00:00 | 2005-02-22 08:02:34 | 0 |
+--------------------+---------------------+---------------------+-----------------+
1 row in set (0.00 sec)
mysql> update rptrequesttimes set endDate = '2005-02-10 09:05:00';
where enddate is maximum of three hours after the invalid XML 'stuck point'.
RCC 2.5.xxx and later:
From command line:
C:\WINNT\SYSTEM32>cd \
c:\cd "C:\Program Files\Microsoft SQL Server\90\Tools\Binn\"
sqlcmd -S.\SQLEXPRESS -dmaster -Usa -PYR46L43!
>use ccrdb
>go
>select * from rptrequesttimes
>go
Confirm the correct end date matches that of the invalid XML. Set the endDate to a later date and time (no more than three hours after though). For example:
>update rptrequesttimes set endDate = '2007-09-20 09:05:00.000'
>go
>select * from rptrequesttimes
>go
>exit
exit
If you have an account on Nortel website these documents could help you:
*NN40040-302_05.01_rccsuog.pdf
*NN40040-400_02.01_Troubleshooting_Guide.pdf
*NN40040-601_01.01_RepExp.pdf
I hope this will solve it...
