January 25, 2011 at 11:55 am
I think this is a inherited disability of SQL that shows itself once in awhile. Just wondering if anyone may have seen it or know more about it. Finding anything in the MSKB for something like this is nigh impossible if it exists.
We have 2 buildings in town on the same internal network. Clients in the building that does not house the servers has intermittent ODBC server not found errors. It will happen on one user PC and then go away. Then happen on another user PC. They all have the exact same ODBC settings that were pushed out to them over a year ago. This has happened on SQL ODBC driver 2008, 2005, and the one built into WinXP Pro. They use the same ODBC configuration on all users in both buildings, and its intermittent, not consistant. Now, to ensure that it works again we simply change the ODBC from just using the "servername\instance" to use the full DNS name of the server/instance and the port number and then it will not re occure on that PC. I.E. "servername.companyname.com\instancename,1433" we are in process of pushing this setting out to all PC's to stop the help desk calls. But Im so curious if this is a known issue, or at least customer known issue. We had a similar issue couple years ago with laptops in the same building as the servers, same error, in the old driver, ODBC config, uncheck the dynamic port box and add the servername and port number would fix it. That was also intermittent. Maybe it can be chalked up to a certain kind of network behavior that SQL doesnt like that only occures occasionally or something like that.
Edit/addition, ok its weird how this works, may have just found an answer. Apparently it has something to do with either allowing all user PC's to update DNS using Active Directory, which is a security issue, or updating DHCP to improve the situation.
January 25, 2011 at 12:44 pm
- What's the actual error message your apps receive ?
- Can it be applying win updates on a dns server ( including reboot ) somewhere in your chain causes this issue ?
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
January 26, 2011 at 8:28 am
Looks like I did forget to put the error in there. Its a general ODBC error, server not found. Reconfiguring the ODBC using just the servername "servername\instance" to "servername.companyname.com\instance,1433" fixes it on the local PC.
The ActiveDirectory\DNS\DHCP thing I added on to my first post is a good enough answer. Im just a desktop jockey with SQL admin experience/aspirations, so the more self important teams will have to do the enterprise level problem management fix. Im just in it for the info\personal growth. And calls closed daily.
January 26, 2011 at 2:20 pm
We receive many "sspi handshake failed" at dns-server reboot time (win 2003 domain). transparency with secondary dns servers doesn't seem so transparent after all 🙁
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply