Community
Showing results for 
Search instead for 
Do you mean 
Reply

Synchronisation has Failed. A system Assertion check has failed

Tuned Listener
Posts: 32
Country: Canada

Synchronisation has Failed. A system Assertion check has failed

[ Edited ]

We have currently 2 computers who synchronize into a server. One of the computer sychronization work just fine but the other one will return the following error message:

 

Synchronisation has Failed. A system Assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. to check for database corruptionm consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from technical support.

 

 

all using ACT! by Sage 2009 (11.0) Version 11.1.183.0.

 

Both are running Windows XP 

 

Anyone have any idea how I could fix this problem?

 

thank you

Message Edited by alexissga2 on 01-06-2010 11:41 AM
Moderator
Posts: 4,395
Country: USA

Re: Synchronisation has Failed. A system Assertion check has failed

[ Edited ]

Run through database maintenance on the main and remote database.  Once done, attempt to sync again.

 

Database Rebuild and Repair Procedures

Message Edited by dlunceford on 01-07-2010 02:18 PM
Tuned Listener
Posts: 32
Country: Canada

Re: Synchronisation has Failed. A system Assertion check has failed

Tried that already, it won't let me repair and automatically ask me if I wanna try another way to repair the DB. I clicked yes and same thing, they cannot repair the DB.

 

the db was Locked.

 

I don't have the exact error message and canno't retrieve it for now, I will try to add it later. Although I think the error was not very informative and only mention that they couldnt repair.

Tuned Listener
Posts: 32
Country: Canada

Re: Synchronisation has Failed. A system Assertion check has failed

[ Edited ]

Error 1Error 2

 

Those are the 2 errors I get when I to repair

 

And the following is the error message I get when I try to syncrhonize:

Sync error

 

Information into the Log:

 

> A severe error occurred on the current command.  The results, if any,

> should be discarded.

> Location:               logrec.cpp:683

> Expression:           FALSE

> SPID:                      64

> Process ID:           996

 

 

Message Edited by alexissga2 on 01-08-2010 08:03 AM
Tuned Listener
Posts: 32
Country: Canada

Re: Synchronisation has Failed. A system Assertion check has failed

Anyone?
Bronze Elite Contributor
Posts: 2,518
Country: USA

Re: Synchronisation has Failed. A system Assertion check has failed

If the Act repairs failed to resolve this problem I would suggest contacting our Database Services team. 

 

http://www.act.com/support/databaseservices/databaserepair/ 

 

Call 770-492-6477 or e-mail us at dbrepair.act@sage.com 

Tuned Listener
Posts: 32
Country: Canada

Re: Synchronisation has Failed. A system Assertion check has failed

I think I will back up both remotes and create a database from one of them and import the other one then create new remotes.

 

This should work

 

What do you think?

Platinum Super Contributor
Posts: 5,275
Country: USA

Re: Synchronisation has Failed. A system Assertion check has failed

I recommend just creating a new remote to replace the one that is getting the errors. 

 

If there are no errors when the new remote sync's and there is data in the 'broken' remote that you need to recapture:

- backup your main database and the new remote

- in the old remote > Lookup by Contact Activity with a date just before the last successful sync (of old remote)

- then use File > Export to your new remote database

- selecting 'Current Lookup' for the criteria

- once the Export is complete > test the sync of the new remote

- it the sync now fails with the new remote, you can use the backup to restore it without having to create a new remote

 

Note: if the error was due to corrupted data, the export from the old remote to the new remote may re-introduce the problem data.

Greg Martin
Sage