Change DB Connect string for Dynamics GP 10

We have a Dynamics GP 10 VM (Terminal Server) that runs the client and another SQL VM that holds the database.

We're restructuring network currently.  The IP address of the SQL VM has changed to a new subnet (Computer Name unchanged to not break SQL).  DNS is all good to go and routing.

We normally have a consultant come in for anything to do with GP, changing the server address/name the GP client connects to should be simple.

Can someone shed some light on where I can change this ??

The ODBC connection is correctly set to the SQL machine name and Tests successfully. However a Process monitor log shows GP Client is trying to connect direct to the old SQL IP, not the DNS name.
MemxITAsked:
Who is Participating?
 
Steve EndowConnect With a Mentor Microsoft MVP - Dynamics GPCommented:
Hi,

Interesting issue.  I've seen several bizarre problems with DSNs for GP that are never explained or resolved--unfortunately each one is slightly different.

Some things to try:

1. Try running nbtstat -R, just in case there is some local network name cached. Shouldn't matter, but...

2. Have you verified the server network protocols and client network protocols that are enabled on your new SQL Server in Configuration Manager?

3. Have you completely deleted the old DSN and created a new one?

4. Is your GP VM running 32-bit or 64-bit windows?  If 64-bit, are you positive that you are properly setting up the 32-bit DSN for GP? (using C:\Windows\SysWow64\obdcad32.exe and NOT the 64-bit ODBC icon in Administrative Tools)  


Thanks,

Steve Endow
Dynamics GP Certified Trainer
Dynamics GP Certified IT Professional
0
 
Abdulmalek_HamshoCommented:
Have you deleted the old DNS entry for the old SQL server in the DNS server?

You have t make sure that the DSN (not DNS) created at the client side (in Administrative Tools -> Data Sources (ODBC)) are using DNS name rather than IP address.
0
 
MemxITAuthor Commented:
Yes, DNS is tidy and correct... Resolves Name and reverse IP... ODBC connection is using proper DNS and passes the ODBC connect test.  Dynamics GP client hangs for a couple minutes before erroring out when entering username/password.  Resource Monitor reveals it's connecting to the old IP.  If I fake a 2nd NIC in the client and the SQL server that are the old IPs, it connects to the old IP no problem and continues.

Is the ODBC connection the ONLY connection you configure for it ??  I was thinking maybe it used that connection to pull configuration via ODBC, then the configuration it pulled contained MS SQL information it would connect with.   That's was purely a guess b/c the ODBC looks fine and works fine.
0
Cloud Class® Course: CompTIA Healthcare IT Tech

This course will help prep you to earn the CompTIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings.

 
MemxITAuthor Commented:
The 32bit ODBC in x64 is a good point.. I'm not the 'SQL' guy at work, I'm the network/systems admin.  I was wondering that very thing earlier because I know 32bit app accesses 32bit services.  I'll check the 32bit ODBC tomorrow, I bet that's where it's set.
0
 
MemxITAuthor Commented:
Just tried it remotely, that did the trick!!

Thank you! :-)
0
 
MemxITAuthor Commented:
C:\Windows\SysWow64\odbcad32.exe

Slight type-o in the solution, correct file name above.
0
 
Steve EndowMicrosoft MVP - Dynamics GPCommented:
Hi,

Sorry about the typo!  Looks like you figured it out though.

Glad that worked!  It's actually a very common issue due to the way that x64 Windows hides the 32-bit ODBC settings.

Thanks,

Steve Endow
Dynamics GP Certified Trainer
Dynamics GP Certified IT Professional
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.