Share
Report
190
Hi All
Has anyone had any issues with processing the first 401 after upgrading HQ and SO to FP1?
We have a database with over a million records in the POEntry table alone, and correspondingly high record counts in other tables.
During the database upgrade to 2.02 (from 2.0) FP1 adds columns to certain table (such as PO, POEntry etc.).
As such the first 401 to run after upgrading both HQ and store seems to want to upload all the records in those tables that have been added to.
HQ client will run for around an hour and then gives up, the 401 status is left as 0 (still to process) and the next time the polling schedule come around the same 401 starts again.
Having run SQL Profiler it seems the SQL transactions still run in the back ground (both DB's are on the same SQL Server) and after around 24 hours the transactions appear complete.
My plan then set the worksheet status to completed and kick off another 401, though this seems slightly messy and is a fudge to get around a (presumably) test scenario.
Has anyone else had similar problems and any better solution to this issue? What additional processing will be missed by simply doing this (such as what else does HQ Client do on completion of a w/sheet except updating the w/sheet status)?
Any help will be grateful
*This post is locked for comments
All responses (
Answers (
