Hi, Of my 11 stores, 2 do not complete auto generated 401 styles. HQ Client sits and waits until it hangs and dies. I upgraded to RMS 2.0 and all stores sit on hotfix 9 build 2.0.0109.
HQ server sits on build 2.0.0105
I am reluctant to apply service packs or hotfixes as I know the carnage it causes or can cause and this costs my business a great deal.
Can anyone give reasons, suggestions, actions as to what I Can do in order to resolve why the 401 hangs. If I delete the 401 and manually recreate it it seems to go fine
I would temporarily cease communications between HQ and the stores that don't have any problems. Delete any open WS401s. Create a new WS401 for
*one* problem store. Have that store's HQ Client connect. Walk away. Let it run for a while. Give it at least an hour or two. If it does finally complete, do the same thing with the second problem store. Once both problem stores have connected and completed a 401, resume HQ communications with the other stores.
Each store connacts once per day and never is scheduled to overlap another store. Here's the state of affairs. I think their is a windows update (on XP) that may be causing this problem. All my other stores poll fine and complete the
401. HQ and the store with issues are on the latest RMS version, 15 I think. All other stores are on version 9 and complete everything just fine without problems. I should mention that all other worksheets other than 401 complete without issues across all stores including the problem store.
I have noticed that HQ server eventually throws the worksheet away and the store never gets to know of this so it continues to wait forever.
I would appreciate any clues to solving this problem before I use one of my tickets to lodge a bug with MS hopefully with a fix.
Each store connacts once per day and never is scheduled to overlap another store. Here's the state of affairs. I think their is a windows update (on XP) that may be causing this problem. All my other stores poll fine and complete the 401. HQ and the store with issues are on the latest RMS version, 15 I think. All other stores are on version 9 and complete everything just fine without problems. I should mention that all other worksheets other than 401 complete without issues across all stores including the problem store.
I have noticed that HQ server eventually throws the worksheet away and the store never gets to know of this so it continues to wait forever.
I would appreciate any clues to solving this problem before I use one of my tickets to lodge a bug with MS hopefully with a fix.
The long delay is because of the recent hotfix (if you've loaded it of course). Our stores went from syncing in a minute or so to 4 hours in some cases. This is becuase HQ recalculates each items weighted average cost at HQ and store with each 401 and this locks the HQ client whilst it is running.
The easy soluti> Dan,
same version, the latest being 2.0.0116 released Friday nite. WARNING, no one outside of MBS has tested this version, so it may cause other problems! My suggestion would be to follow the next instructions.
long time to calculate the Average Cost of Items. It is recommended that one revert back to 2.0.0114 to fix the issue.
Shaun, Thanks for the suggestion. I will try it. However, what actually happens for the two stores who are on version 15 is that the HQ server eventually termnates and throws away the worksheet. I fails to tell the HQ client this and leaves HQ client to die a miserable death by manually having to terminate the hq client session. I will report back when average wieght is unchecked and let you know the results.
On another matter, what concerns me is the quality of RMS overall. From this newsgroup I see many grapling with issues that would directly impact there daily retail operations and hence bottom line for survival. My view is they (including me) have bought an expensive product that creates many many headaches.
My obervations:
1) RMS clients would be left high and dry without this news group
2) Customer source is less than pitiful
3) Resolution of ** REAL** retail processes that RMS performs badly remains untouched from version to version
4) Lack of knowledge of where RMS is going so we can plan our businesses accordingly
You're right about the build quality of RMS ver 2. We have found after installing an additional 2 servers at substantial expense that ver 2 doesnt support terminal services or multi users on citrix so we basically wasted our money after being advised to upgrade the servers by our IT vendor.
BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.