Saturday 15 Jan 6:00 pm Mountain. Another day, more hangups and failures by the Method engine.
+ Both error-checking options are still checked. QB is open on the master/Admin account.
+ Yesterday's Changes-only synch, launched at 6:45, completed at some point in the evening.
+ The Full synch, which was scheduled for 11:30 pm, completed more-or-less successfully at about 11:45 pm last night.
+ I ran both a Changes and a Full synch this morning. The Full synch completed at 8:47 am.
+ Change-only synchs continued every hour until 12:50 pm today (Saturday).
+ At 12:30 I saved qbsdklog.txt and qbsdkold.txt to my desktop. I'll send them to you via email.
+ After the 12:50 Changes synch completed, I made some changes to various transactions and Customers in QB - in most cases, adding a TxRegion value where there wasn't one, trying to clean up a Dec sales report.
+ After reviewing some QB sales reports, I realized that there were
transactions that been entered after the last time Michael successfully
ran Update Transactions. Since the next synch was scheduled for 60
minutes away, I launched the Update Transactions function from the
Method website.
+ I changed one Rep in QB, making him active. (He had been made inactive by staff mistake on Friday, apparently.)
+ Another synch started running at 12:55 (presumably a Changes-only). If
it was launched by the PUSH feature, then that suggests that the system
will start updating every time changes are made to the database. Given
our experience with the MI engine's performance lately, that's not a
good thing.
+ At 12:57, the Update Transactions routine completed and gave me a confirmation dialog.
+ For the rest of the afternoon the engine showed it was checking records in the Invoices table. Eventually, about 5:45, it showed signs of life, indicating it was working on other tables.
+ At Jan-15-2011 05:07:43 PM Method logged one conflict. I've left it up in the conflicts listing.
+ At 6:00 pm, the engine crashed and threw this error: "MethodIntegrationEngineForUseWithQuickBooks has encountered a problem and needs to close..."
+ 6:40 pm - restarted QB. Upon loading, Method engine immediately began synching. As before, I disconnected Method so that I could turn the troubleshooting options back on, but this time Method hung up and showed nothing but the hourglass.
+ I exited Method, waited, and reopened the application. As quickly as I could I turned on the options, but it had already started synching again.
HOW IS ONE SUPPOSED TO INVOKE THE TROUBLESHOOTING OPTIONS IF THE ENGINE BEGINS SYNCHING IMMEDIATELY UPON LOADING?
+ 6:45 pm - Method continues to show an hourglass. I'll let it sit there, and post again shortly.
Lee