Server change problems

[csmeutah]

We moved our Great plains data to a new SQL2005 server several months ago. Recently we turned off the original server and now when we switch companies it can take several minutes. We put a sniffer on the workstations and can see that the old server is being pinged several times with the related timeouts.

We have run dexsql logs but of course they only show the sql sproc calls which run fine in management studio.

We've checked the dynamics.set (stripping out all but Dynamics), dex.ini, and translation table (all references are generic db names no servers).

Where else could this old server be referenced?

TIA

 

[jymm]

are you sure it is old server related?

We had the same problem here (v9) and we ended up turning off the home page on some folks GP, but what REALLY did the trick was an un-install & brand new install on the client. Seems that someone in their infinite wisdom had installed modules we did not have license for (just to see them work on a test company). The .set file was back to only the modules we had, but that did not 'do it'.

So - we uninstalled on the client, delete the directories & re-installed the 'basic'... it went from minutes to switch companies to just a few seconds.

I dont get it either, but if you search GP's site (maybe here too) you will find a fair number of folks in the same boat.

this help?

 

[csmeutah]

You know, we found two things. First we had macros pointing to the old server and the program pings it during startup and switching companies. It wasn't a big deal for most but we had four users in the collections department who use the macros to switch companies and 2 minutes was a little long for a customer to wait...
We also had a mekorma check format pointing there as well.
I'll keep an eye out for the home page issue though.

They really should mention these things in the documentation.

Thanks.