HQ Client issues persist - v2.0.0115

[Terrible Tom]

So I tried the Named Pipes & TCP/IP thing in the Client Network Utility.
Things improved slightly, but...

Check Stores simply does not work. The request is *never* answered and the
HQ Client is stuck for a *very* long time. Any Check Stores request (from
Store Ops or from POS) basically kills all Store-to-HQ communications for 30
minutes or so.

A/R requests (POS terminal queries HQ for A/R info when making an account
payment) seem to work fine--much better than before the Named Pipes 'fix'.

Worksheets are still taking a lot longer to process, especially WS401.

Any ideas for resolving this issue? For me, Check Stores is the most
important feature of an HQ environment--and it is not working at all.


Tom

 

[Doug Pic-N-Pac]

Sorry tom that I dont have a answer to your question. But i was wondering if
any one else was having this problem? Im not sure I want to install the
hotfix until I know whats going on.

 

[Terrible Tom]

Don't do it all at once.

After my experience, I would recommend the following:

Backup HQ and the Store Ops database you plan to use for the test.
Stop all HQ Server/Client communications.
Be sure to exit HQ Client at all locations!
Upgrade the HQ Server ONLY.
Upgrade the HQ Client machine and one register at the test location.
Start HQ Server, test all forms of HQ Server/Client communications...
From POS > Check Stores, Make Payment
From SO Manager > Check Stores
From HQ Manager/Client - run several test worksheets, not just WS401

If everything works smoothly, proceed with the upgrade.

If things aren't smooth, you will have to uninstall all RMS applications on
the upgraded machines, re-install from CD, call MS to reactivate the HQ
Client and POS license keys, apply whatever HotFix you were previously
running and then restore from backup.

Ouch.

I am looking at uninstalling/reinstalling/re-HotFix 2.0.0109 at four
locations and nearly 50 PCs, with 4 HQ clients and 8 POS licenses to
reactivate over the phone.

Hot Fix 2.0.0115 may be the most costly software install ever.

Sad but true,
Tom

 

[DRS Support]

If things aren't smooth, you will have to uninstall all RMS applications

on the upgraded machines, re-install from CD, call MS to reactivate the HQ
Client and POS license keys, apply whatever HotFix you were previously
running and then restore from backup.

This should not be necessary. You can revert back to the prior version in
about a minute per PC.
Go to Control Panel, Add/Remove Programs, enable "Show updates" at top of
screen.
Scroll down to Microsoft Dynamics RMS and remove only hot fix #9 (KB
945792 which is v2.0.0115).
Your system is now restored to the prior version. There is nothing extra to
do. You can optionally install hot fix #8 (2.0.0114) if you'd like.

TIP: If you are prompted to insert the 2.0 CD during an update, you can copy
the MSI file from the CD to a shared folder on the network and browse to
that folder when prompted. The file you need (Microsoft Dynamics RMS Store
Operations.msi) is located in the SO folder on the 2.0 CD. Alternately you
could place this file on a USB flash drive and insert that if prompted.

Digital Retail Solutions
www.digitalretailer.com/RMSaddins -- v1.x and 2.x compliant
Trial downloads -- www.digitalretailer.com/trial
Search this newsgroup -- http://tinyurl.com/2lmk4w

 

[JorgeIT]

To ALL
I just to have same problem, after all my research I found that there are
a few update that windows download and install automatic that break HQ and
RMS, as a solution this is what I did and now everything work relly well.
1.-be sure all the aplications are close
2.- run a clean up tool for NE?T framework and remove all versions
3.- install NET framework 2.0 and be sure to NOT INSTALL SP1 framework or
any security update after that or any other version
4.- turn off automatic update
after this you HQ will run

Jorge IT

 

[Shaun]

After applying the hotfix, our chain of 40 stores comms has deteriorated to
practically impossible to the point all the data at HQ is now wrong. I am
considering legal action against microsoft to get them off their backsides
and to put out a hotfix to address the mess that they have created. Anyone
else want to jump onboard?

Our stores take upwards of 45 min to an hour and a half to comm... and thats
on the LAN