During HQ Client connection to the HQ Server the Store Operations computers seem to freeze for a good 60 to 120 seconds - each and every connect! Is anyone else experiencing this problem and does anyone have any solutions to offer?
HQ Connection to Store Ops
Mar 15, 2007
7 Replies
Are all three versions the same (i.e. HQ, SO and HQ Client)? You find this info under each application's Help> About.
Yes ... Client is 1.3.1002; Server is 1.3.1002; and SO's is 1.3.1002. Have you ever come across this before?
Also ... perhaps you'd know why all ITEMS come across with each 401? See log below.
It appears that something is 'touching' a lot of (all?) items. That could be almost anything, but let start with the obvious: any third party adding, any external reporting applications (Access for example), any SQL Queries being run? Is this a new install or have the store and HQ been connecting for a while - it's common for the first few 401s on a new store database to update all items and all customers several times.
Regarding the original performance question, where are SQL, Store Ops and HQ Client installed? If they are all on the same machine, you are probably just over whelming it's resources. If they are spread across 3 machines, it may just be related to the above issue where you are updating a lot of records at once and may be improved if that is resolved.
Glenn Adams Tiber Creek C> Yes ... Client is 1.3.1002; Server is 1.3.1002; and SO's is 1.3.1002. Have
Glenn,
It's a week old install of HQ ... we don't run anything out of the ordinary at the stores. No SQL programs, no third-party software that would be 'touching" all of the items. We connect every 15 minutes so a 1 to 2 minute FROZEN period is nuts and there is no need to upload all of our items to HQ every 15 minutes. This even occurs after business hours when we connect. No, they are not on the same server.
Any other thoughts about what it might be?
"Glenn Adams [MVP - Retail Mgmt]" wrote:
Glenn,
I just checked the event log ... I stand corrected - the items do not transfer when we connect after business hours. Hmmm ... I'm going to have to investigate this a little further on my end.
Scott
"Lum> Glenn,
Thanks for the better explaination ... still, I am curious, WHAT could possibly be changing the itemdynamic details for so many items within the 15 minute time period between our SO/HQ connections?
"Nashat" wrote:
transferred to HQ for the items having their TimeStamp changed (any sold/transferred item for example). this is why u don't see the items in your event log after working hours
datasource
Join the Discussion
Have something to add? Share your thoughts — no account required.
Didn't find your answer?
Ask the community — no account required