Solved Cyclic Redundancy check error error_crc

[tbudde]

I own two identical laptops. Both started having the same problem two days ago. Model is CQ61-410US Notebook from Compaq. Running Windows 7 Home Premium. 64-bit operating system.
I started getting a cyclic redundancy check error (error_crc error per MS Windows). The error occurs when I attempt to syncronize either of my two laptops with the ACT software from Sage loaded on the remote server. I have been successfully syncing these laptops for the two years in the same fashion. Only today have I begun having this problem. And I have two other computers that are syncing without a problem. I did a restore back to yesterday morning before a Windows critical update was installed. That did not help. Because it is a problem with only these two laptops, my suspision is that it has something to do with the laptops and some kind of an update that has affected them. Any help would be greatly appreciated!

Sync file from today from one of the two clients not working:



======= SYNC SESSION - 2/1/2012 12:04:48 PM ========
[ Info | 2/1/2012 12:04:48 PM ]Message: Sync remote client created. [ Info | 2/1/2012 12:04:48 PM ]Message: Checking if schema changes are available for sync. [ Info | 2/1/2012 12:04:50 PM ]Message: Client establishing synchronization with server database: SERVER_5_28_10 [ Info | 2/1/2012 12:04:56 PM ]Message: Initial Handshake completed. [ Info | 2/1/2012 12:04:56 PM ]Message: Checking if data changes are available for sync. [ Info | 2/1/2012 12:05:00 PM ]Message: Client initialized database send session: 49 [ Info | 2/1/2012 12:05:19 PM ]Message: Client initialized. [ Info | 2/1/2012 12:05:19 PM ]Message: Client schema synchronized. [ Info | 2/1/2012 12:05:54 PM ]Message: Server initialized. [ Info | 2/1/2012 12:05:55 PM ]Message: Server schema synchronized. [ Error | 2/1/2012 12:06:05 PM ]Message: File synchronization failed. [ Error | 2/1/2012 12:06:05 PM ]Message: Synchronization has failed. Server Error Description: Data error (cyclic redundancy check).

 

[Lemur]

a crc error may point to corrupted data. please try running chkdsk on both PCs. What really concerns me is it's happening to both computers.

Please do this first and get back to us.

 

[tbudde]

CRC checkdisk

Thanks for your suggestion! I ran the chkdsk on one of the laptops yesterday. Still the same error.

 

[Lemur]

Please run it on both. It have have been a crc in trying to sync the bad file from one pc to the other.

 

[tbudde]

I did a chkdsk on the server. It found an error. See below. I am not sure what to do to repair it. The server runs MS 2003. It is hosted at godaddy and is a dedicated server. All I run on it is ACT software from Sage.

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\tbudde>cd\

C:\>chkdsk
The type of the file system is NTFS.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
132416 file records processed.
File verification completed.
769 large file records processed.
0 bad file records processed.
0 EA records processed.
5 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
412987 index entries processed.
Index verification completed.

Errors found. CHKDSK cannot continue in read-only mode.


Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\tbudde>cd\

C:\>chkdsk
The type of the file system is NTFS.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
132416 file records processed.
File verification completed.
769 large file records processed.
0 bad file records processed.
0 EA records processed.
5 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
412987 index entries processed.
Index verification completed.

Errors found. CHKDSK cannot continue in read-only mode.

 

[Lemur]

For Win Server 2003, you have to have at least SP1 installed. I would hope SP3 is installed. Anyhow, you really should have your network administrator handle this.

Windows Server 2003

You must put the physical disk resource in maintenance mode before you run a "chkdsk /F" command against a volume on a Microsoft Windows Server 2003-based computer. You must do this to prevent the physical disk resource from going into a failed state.

 

[tbudde]

Thank you for your help! I didn't use the /F. But, the chkdsk did work! It found some errors, corrected them, and now my computers are syncing fine. Thanks so much!!

 

[Lemur]

Glad to help. Another satisfied customer.