URGENT: HQ Client issues getting worse every day

My HQ Server/Client issues since applying HotFix 2.0.0115 are getting worse.

Practically no connection for non-worksheet requests will run successfully. Any attempt to make a payment at the register (POS requests A/R info from HQ) results in a very lengthy delay. Similarly, any attempt to 'Check Stores' from POS or Store Operations Manager appears to be doomed for failure after a lengthy delay.

It appears as though even when the POS operator cancels the request, the HQ Client application refuses to stop trying to fill the request.

HQ Server appears at first to be in a state of 'Not Responding' but if you just let it go, it eventually catches up. I am not a big fan of using Task Manager to 'End Task' on HQ Server.

Is there any way to roll back to version 2.0.0109?

Tom

Reply to
Terrible Tom
Loading thread data ...

Tom, I believe you'd have to uninstall HQ Client/Server and re-install then move to the exact patch version you want.

Reply to
rsakry

Ouch. I feared as much.

I wouldn't want to run 2.0.0115 everywhere except HQ Server/Client, and I was REALLY hoping that the HQ Cost Averaging fix included with .0115 would help with extracting accurate inventory values from HQ.

I really don't want to uninstall/reinstall RMS on 50 systems.

Tom

Reply to
Terrible Tom

Try this:

Credit goes to: J.D. Young Digital Retail Solutions

formatting link
(v1.x and 2.x compliant)

Begin quote

--------------

1) On all PCs

Start, All Programs, Microsoft Retail Management System (Dynamics RMS), Network Client Utility. Make sure Named Pipes and TCP/IP protocols are enabled. Make sure Named Pipes is in the top position above TCP/IP. Yup, the reverse of what other KB articles say to do on CustomerSource. Select Alias tab and add the RMS server name as a Named Piped Alias.

2) On RMS server

MSDE: Start, Run, svrnetcn.exe and make sure same protocol settings apply (Named Pipes above TCP/IP).

SQL 20005 Express: (If full version of SQL 2005 use Enterprise Manager to enable thesesettings.) Start, All Programs, Microsoft SQL Server 2005, Configuration Tools, SQL Server Surface Area Configuration, Surface Area Configuration for Services and Connections. Make sure the setting "Use both TCP/IP and Named Pipes" is enabled. Start, All Programs, Microsoft SQL Server 2005, Configuration Tools, SQL Server Configuration Manager, SQL Native Client Configuraion, Client Protocols, right-click on Named Pipes, select Order, and make sure Named Pipes is in top position (or #2 below Shared Memory).

3) Stop and restart SQL Server services (or reboot server).

----- End Quote

Reply to
Frederic Hurlet

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.