stuck 401 worksheet

Try this:

Delete the worksheet, create a new 401 at HQ and backdate the effective date to any time before the date of the 401 you deleted. See if this one completes.

If your back date is what is hanging it - because the date is so old and the info contained is so massive - you can always backup and restore the db on your SQL box and try pushing the connection through on the same client. This means the store can not have any system movement, and no other stores should connect at the same time (i.e. change your port, etc.). Dually, when I have had to do this I have started with backdating for yesterday, processing - then slowly working back week by week, processing after each WS before issuing the later. This is tedious and time consuming, but has worked for us in the past.

Thanks. I backed up the store database, restored it locally, and ran the 401 fine. I still need to run backdated 401 on the store to catch sales since the backup was made, but that should be much smaller.

The underlying issues appears to be poor line quality on that locations DSL. We're getting 5-15% packet loss. 401's must be really sensitive to that.

Jim

"jocelynp" wrote:

401's can be an enigma. The weird thing is the packets dropping. I would say that it can always involve poor data quality, however I have run stores on the slowest of slow connections (dialup and satellite) and they seem to run. Are your stores wireless? My biggest issue was the 401's bumping into each other. I had thought in that past that having multiple connection ports would allow for two stores to connect at the same min if they were on different ports - man was I wrong there.

When back dating those WS' just make sure you go in small steps, especially if the 401's are running stubbornly.