HQ Upload Data

(0) Share

Report

Posted on by Community Member

We was having some trouble with the worsheet 401 Upload Data, cause log transaction was to big.

I cleanup the log but when synchronize again whit the worksheet have to much transaction to upload and the server freeze and i have to restart system, when try again doing a new worksheet 401, upload dato but only a few days not complete.

How can resinchronize all data again?, cause we have a bad data on HQ now.

*This post is locked for comments

I have the same question (0)

All responses (9)

Answers (0)

Jeff @ Check Point ... 13,382 on at

Like (0)

Report

Re: HQ Upload Data

Javier,

Back date a 401 to whenever you want to recover. It will not dupe the data.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Re: HQ Upload Data

Im doing that. but i have a problem when i make a new worksheet whit back date never finish, at HQ client only recieve Timeout errors.

Was this reply helpful? Yes No
Jeff @ Check Point ... 13,382 on at

Like (0)

Report

Re: HQ Upload Data

Javier,

Try increasing the timeout for HQ Client.

Open the Regedit program and go to this key;

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Retail Management System\Headquarters\Client\Timeout

or

for 64 bit OS

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Retail Management System\Headquarters\Client\Timeout

Change the Message entry to 3600 for a 1 hour time out

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Re: HQ Upload Data

HI Jeff, i look at the key and there is an entry for message. what is that one for as i increased the timeout settings to 7200 but its times out after 15mins each time. i saw the mssage entry in the timeout key and it says 15. does it stand for?

Was this reply helpful? Yes No
Jeff @ Check Point ... 13,382 on at

Like (0)

Report

Re: HQ Upload Data

David,

You must restart the machine or HQ for the changes to take effect.

Was this reply helpful? Yes No
Clint Skog on at

Like (0)

Report

Re: HQ Upload Data

If you continually experience timeouts when backdating, try to shorten up the time you are backdating. It may be trying to push too much info at once.

Was this reply helpful? Yes No
Suggested answer

Jim Deady 433 on at

Like (0)

Report

Re: HQ Upload Data

We had a similar problem with HQ synchronization.

Along with the client side registry entry that was mentioned above (HKLM\Software\Microsoft\Retail Management System\Headquarters\Client\Timeout\Message), there is a server side registry entry. On the HQ Server machine, change:

HKLM\Software\Microsoft\Retail Management System\Headquarters\Common\Options\CommandTimeout

to the same value as the Message value. I recommend something large like 36000 (10 hours). You can always reset the value to something more reasonable (3600) after the large sync is done.

Was this reply helpful? Yes No
Ryan Sakry 3,425 on at

Like (0)

Report

Re: HQ Upload Data

We have also had problems doing a large backdated 401 in the past. To work-around we disabled uploading of journals and this fixed it. Once the back-dated 401 processed we re-enabled uploading of journals. For that time-frame, the customer was ok with leaving the journals just at the store level, but they could certainly be moved up to HQ by other means if you need!

Was this reply helpful? Yes No
Jim S. Bernardo 455 on at

Like (0)

Report

Re: HQ Upload Data

Journals are rather heavy and we've observed this in bandwidth challenged stores.

How did you manage to upload the journals now to the HQ Server?

Was this reply helpful? Yes No