T
Tomas
Hello,
We are experiencing a native exception during merge replication between SQL
Server CE 2.0 and SQL Server 2000 SP3.
Configuration:
Windows Mobile 2003
..NET Compact Framework SP2
SSCE 2.0
SQL Server 2000 SP3
The exception is an access violation, which occurs during the call to the
Synchronize method of the SqlCeReplication object. When the exception
occurrs the following message is displayed:
A native exception has occurred in app.exe. Select Quit and then restart
this program or select Details for more information:
ExceptionCode: 0xc0000005
ExceptionAddress: 0x01397a98
Reading: 0x22000000
Most synchronizations work without problems, but when this error occurs it
isn't possible to synchronize with the PDA where the error occurred until
the database file is removed. No error is reported in the replication
monitor on the server. Instead the synchronization is reported as
successful. However, when this error has occured the PDA will try to
download the same changes from the server in every synchronization attempt.
Any changes on the PDA are successfully applied to the server, which
suggests that the error occurs during the download phase.
We have been suspecting that the reason for this error is corrupt database
files. This conclusion seems to be contradicted by the fact that it is still
possible to read and change data in the PDA database after this error has
occured.
Regards,
Tomas
We are experiencing a native exception during merge replication between SQL
Server CE 2.0 and SQL Server 2000 SP3.
Configuration:
Windows Mobile 2003
..NET Compact Framework SP2
SSCE 2.0
SQL Server 2000 SP3
The exception is an access violation, which occurs during the call to the
Synchronize method of the SqlCeReplication object. When the exception
occurrs the following message is displayed:
A native exception has occurred in app.exe. Select Quit and then restart
this program or select Details for more information:
ExceptionCode: 0xc0000005
ExceptionAddress: 0x01397a98
Reading: 0x22000000
Most synchronizations work without problems, but when this error occurs it
isn't possible to synchronize with the PDA where the error occurred until
the database file is removed. No error is reported in the replication
monitor on the server. Instead the synchronization is reported as
successful. However, when this error has occured the PDA will try to
download the same changes from the server in every synchronization attempt.
Any changes on the PDA are successfully applied to the server, which
suggests that the error occurs during the download phase.
We have been suspecting that the reason for this error is corrupt database
files. This conclusion seems to be contradicted by the fact that it is still
possible to read and change data in the PDA database after this error has
occured.
Regards,
Tomas