1. Home
  2. Point-Of-Sale Software
  3. Sync Error Following Z-out

Sync Error Following Z-out

I have searched and I've found posts on other errors but none of those errors are the same as mine. After my clients close out the offline database sync is generating a "3709" error related to QS Rules and CurrentDateTime. This is followed by a runtime error. I will post more details on the errors when I get them but I'm pretty sure this isn't an ADO error.

In the meantime, the error was rare until I turned on CC/DC processing with Vital/TSys EDC. After I set the CC/DC processing up the error now occurs every night. After the runtime fault the POS shuts down.

The POS can be restarted and all processing appears to be running normally after the errors. I haven't checked yet but I don't know if the offline databases are up to date anymore. I suspect they aren't as the error occurs in the middle of the sync process.

One solution that I saw in other threads was related to machine name lookups. I went ahead and set all DB name fields to the correct IPs (I'm using a static scheme so it's no issue) in order to eliminate lookup timeouts. Unfortunately, this didn't help.

My next thought is to rebuild the offline databases.

Any other thoughts or suggestions?

Reply to
dwtalso
Loading thread data ...

Here's some more data. I still don't have the complete details on the error and one reason is that I can't get the error to occur while I'm present. The error is occuring only when a z-report is run in the evening at closing. I cannot get the error when I perform a z-out in the morning. This means I've got to make some time in the evening, however, it also implies that something is occuring during daily activities that is creating the situation causing the problem.

Dan

"dwtalso" wrote:

Reply to
dwtalso

I wound up rebuilding the offline databases and this corrected my original error.

Now, however, I'm getting a different error during offline sync. This one is related to a failed SQL script selecting from the TransactionHoldEntry table. I'm still digging into this one.

Reply to
dwtalso

I'm getting the same error. Can you let me know if you found out a solution?

"dwtalso" wrote:

Reply to
Jason Kelton

I'll be sure to post whatever I find. I'm still working the issue. It turns out that rebuilding the offline databases did not help. I'm actually getting an error during z-out, an error when transactions are held, and an error when transactions are voided.

The problem is that I have yet to recreate these issues repeatably while I'm on site and the error doesn't get logged with more detail anywhere else on the systems. I ran SQL profiler and logged the errors on the SQL Server side but it didn't give me any more data. Add to that, the errors appear to be related to the length of time that the systems have been running since I never get them in the morning when the registers first start up. It may or may not be related to the number of transactions but I don't know because they do alot of sales plus a lot of inventory management during the day.

So, I plan to run profiler some more and see if I can figure out more there. I've also built a set of virtual machines that match the production environment and I plan to capture all the databases just before closing and see if I can recreate the issues offline.

I'll post up any results.

"Jas> I'm gett>

Reply to
dwtalso

I am also having the same exact issue. I have an open incident with Microsoft and will update you if I make any progress.

Reply to
Ryan

I am getting the same error...anything that can help to fix this would be great:

Error #3709 Method '~' of object '~' failed (Source; QSRules) Select GetDate() as current Date Time after I press enter following message: Runtime error '5' Invalid Procedure call or management Then the POS exits! Thank You, Vince

Reply to
Vince

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.