I have a crazy one for you. I upgraded a client from GP 10.0 to GP2013. The upgrade was smooth sailing, all work on the server was great. Upgraded forms & reports, no problem. No failed tables or other errors of any kind. Ran GP Utilities on the server, with no issues.
Installed GP2013 on the first workstation. The install was smooth sailing, no errors or issues of any kind. Prior to launching GP Utilities, my NIC Card shows I am connected to the domain, and I can ping the server, browse the internet, and see all my other workstations under the "Network" heading in Windows Explorer. My ODBC tests successfully.
When I launch GP Utilities, it hangs and eventually (45 minutes later) returns an error message. DexSQL log shows a variety of connection errors such as:
/* Date: 06/24/2013 Time: 19:05:44
SQLSTATE:(08001) Native Err:(10060) stmt(0):*/
[Microsoft][SQL Server Native Client 10.0]TCP Provider: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
*/
/*
/* Date: 06/24/2013 Time: 19:05:44
SQLSTATE:(08001) Native Err:(10060) stmt(0):*/
[Microsoft][SQL Server Native Client 10.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to*/
/*
/* Date: 06/24/2013 Time: 19:05:44
SQLSTATE:(S1T00) Native Err:(0) stmt(0):*/
[Microsoft][SQL Server Native Client 10.0]Login timeout expired*/
/*
After I end-task, my NIC card shows I am connected to an unmanaged network, and I can no longer browse the internet, ping the server, or test my ODBC successfully.
However, I CAN still ping the other workstations in my domain, both by name and by IP.
Getting the NIC (network) card reset back to the domain has been a hit-and-miss process for me. I toggle back & forth between static & dynamic IP addresses. I disable/enable. I shut down & restart. I use Windows Explorer to attempt to view contents on another workstation, which allows me to enter credentials. I then re-do all the other steps (ping, disable/enable, restart/shut down), and eventually, the network connection comes back.
One of the errors I keep seeing is that the DNS Server is not responding. However, nothing has changed on the server; this is all on the workstation.
I could go on, but I think I am rambling. Let's maybe start with this, and see if you have clarification questions, and tell me what you guys think!
Thanks,
Lyn