Community
Showing results for 
Search instead for 
Do you mean 
Reply

Misreporting Syncronization

Nickel Contributor
Posts: 410
Country: Canada

Misreporting Syncronization

Using ACT 10.02 (hotfix) I have scheduled dailing syncing of my home RDB file with the master database at work. I updated the Network Sync Service to 10.02 witht he latest hotfix, and I sync successfully each and everyday.

The problem is whenever I launch ACT it keeps (mis)reporting that I have not synced in 30+ days.

My access to the database and syncing capabilities seems unaffected, but this false error message is an annoyign bug that I'm sure one of my customers will report experiencing themselves soon - and I'll have to fix it.

To make matters worse, I have a laptop with a separate RDB file that sync's witht he office and it started producing the same behaviour. In the laptops case, I was simply cut a new RDB file and it now works fine - and doesn't not report the error.

Anyone else have this experience, and more importantly is anyone aware of a fix for this problem?

Ken Quigley, BA, MCSE, ACC, APT
Toronto, Ontario
www.keystroke.ca
Platinum Elite Contributor
Posts: 14,384
Country: Australia

Re: Misreporting Syncronization

Have you checked the Scheduler log to ensure it has run and the Sync log to make sure it completed?

 

Have you tried manually running a sync (Tools | sync) to see if that works?

Nickel Contributor
Posts: 410
Country: Canada

Re: Misreporting Syncronization

I checked the sync log and it confirmed a detailed report of the recent successful syncs.

What's more, everytime I run the sync manually, it works perfectly.

 

Funny enough, I had a customer call this morning with the same issue, so I suspect this is a genuine bug because she is syncing succesfully every day, but still getting the warraning message that she hasn't.

 

Kq\

Ken Quigley, BA, MCSE, ACC, APT
Toronto, Ontario
www.keystroke.ca
Platinum Elite Contributor
Posts: 14,384
Country: Australia

Re: Misreporting Syncronization

Do you sill get the error after the manual sync?

Did this only start after the Hotfix?

Do you have other remote users? Do they get the same?

Nickel Contributor
Posts: 410
Country: Canada

Re: Misreporting Syncronization

Firstly, my thanks to you for your quick replies.

 

Yes, we still get the warning messages after the manual sync. 

And yes, these syncing issues only occured after the application of the hotfix on the Network Sync.

I'm not aware of other remote users on that network experiencing the same problem, but they may not have reported either.

 

Ken Quigley, BA, MCSE, ACC, APT
Toronto, Ontario
www.keystroke.ca
Platinum Elite Contributor
Posts: 14,384
Country: Australia

Re: Misreporting Syncronization

Would be useful to find out if it's all users...

 

Hotfix1 had quite a few sync fixes, so it's likely that this is the cause.... I only hope that it's just a warning and that the RDBs don't all expire at 90-days (or whever you set it to).

 

I have rebuilt my sync a couple of times, so I haven't seen it

Nickel Contributor
Posts: 410
Country: Canada

Re: Misreporting Syncronization

I'll call the customer to see if that is the case with all RDB users.

 

As for the expiry date, my home RDB is well past the expiry date and continues to sync daily without interruption.

 

 

Ken Quigley, BA, MCSE, ACC, APT
Toronto, Ontario
www.keystroke.ca
Platinum Elite Contributor
Posts: 14,384
Country: Australia

Re: Misreporting Syncronization

Nickel Contributor
Posts: 410
Country: Canada

Re: Misreporting Syncronization

I thought it was 30, but I might be wrong.

I've looked into it a bit further and I plan to check the sync details under HELP/ABOUT/DATABASE SETTINGS, and see what the sync date and sync retain date is. 

 

Stay tuned, but I do believe there is a bug here.

 

Ken Quigley, BA, MCSE, ACC, APT
Toronto, Ontario
www.keystroke.ca
Platinum Elite Contributor
Posts: 14,384
Country: Australia

Re: Misreporting Syncronization