Data source no longer works with server name
Here's an interesting one...
We got in this morning and noticed RDM timing out on connecting to our SQL server on every computer (see attached).
First thing I checked was the SQL server. We had another database that was working fine, I also created a dummy ODBCAD32 entry to RDM just to test it. Tested ok. Rebooted just incase... Still couldn't connect to RDM.
No matter what I did it seemed I could not connect to RDM by computer name. I decided to use the IP and it worked first try. The name, when pinged, resolved correctly to the correct IP so I was baffled.
The only thing that had previously been done last night to this morning was an Exchange anti-spam update (probably not related) and we configured routing and remote access on the same server (which has since been turned off just in case).
I just thought that was weird since everything resolved ok.
If anyone else has an issue... change to IP instead of name. seemed to work for me.
rdmtimeout.jpg
All Comments (2)
This is strange. I have no explanation but thank very much for the tip/workaround. I will keep my eyes open and let you know if I find the source of the problem.
David Hervieux
Odd thing happened.
We have 5 workstations and I upgraded mine and one other first... also changed to IP instead of name (because it appeared name would not work) and upgraded to 8.0.25.0 fine. The next two I upgraded, but did not have to change to IP, and the last one worked fine on an older version using a name instead of IP.
The only other thing I did was "Update Database" from my computer after switching the data source using IP. It may have kicked everything else in gear? I'm not sure...
If you don't know, i'd blame it on the boogie man and move on. I'll let you know if I see anything else. It's working fine now!