windows ce - SQL Server 2008 data loss with CE replication -


I am using SQL Server 2008 CE replication, and some data loss (i.e. After complete sync)

I get the following entries in the Application log:

Replication-Replication Merge Subsystem: Agent 0033007 B-0043-0039-4400-440036003300 Failure Internal Error: A Synchronization Request A reading action by the device or IIS server returned an incorrect number of bytes while attempting to process. [,,,,,]

Replica-Replication Merge Subsystem: Agent 0045007 B-0038-0037-3200-430036004200 Failure Internal Error: either the computer running IIS is out of memory or a wrong session ID A request was sent in. [Session ID ,,,,,]

Replica-Replication Merge Subsystem: Agent 0033007 B-0043-0039-4400-440036003300 Failed table validation validation failed. Try to re-sync [,,,,,]

Replica-Replication Merge Subsystem: Agent 0043007 B-0036-0044-4400-320032003000 Failure Could not start merge process membership. Ensure that the membership registration is present on the publisher, and if necessary re-register the subscription.

Replication-Replication Merge Subsystem: The agent 0036007B-0037-0042-4500-370036003600 failed authentication on the computer running IIS. [,,,,,]

The messages indicate that IIS is running out of RAM. It is using approximately 22 MB, and the W3WP is using approximately 70 MB. SQL Server consumed most of the remaining 4GB RAM, there are plenty of disk space

Update

Add more RAM to help machine problem (I have missed memory exceptions) However, I still have problems.

It seems that it takes a lot of time for users' data to run before verification 'verification' work on the database (I'm talking> 20 minutes) that I contribute to this problem I can do

I was getting this exact error. The real problem was IIS pool timeout! Therefore, the slower and slower database, the process will become slower and slower as long as the device takes up to 20 minutes, due to which the pool session is time expired so that it is backend choke after the next request . Therefore, one option is to increase the timeout but !! The solution I used to use was to increase the process buffer beside the customer as mentioned here:

This is my post when I work through this

An interesting idea is that you can merge the PC once and then put that file on the device, of course it will not fit in your scenario.


Comments

Popular posts from this blog

c# - sqlDecimal to decimal clr stored procedure Unable to cast object of type 'System.Data.SqlTypes.SqlDecimal' to type 'System.IConvertible' -

Calling GetGUIThreadInfo from Outlook VBA -

Obfuscating Python code? -