August 13, 2009 at 12:52 pm
245755 Error
DBNETLIB][ConnectionOpen
(Connect()).]SQL Server does not exist or access denied.
Juris Accounting, Windows Server 2003,
I am getting this error whenever I attempt to connect a system that has a new operating system installed. (Windows XP). Existing systems are unaffected, setting up new users on systems already connected to the domain is no problem. I have tried every combination of cliconfg.exe with no luck. I discovered this issue about 30 days ago. The accounting program and related systems have been in use for about 4 years without incident.
I have a system with Windows 7 RC installed; it connects to the Juris database without problem. The same system with Windows XP installed on a different hard drive returns the above error.
Any ideas of help on this would be greatly appreciated.
August 15, 2009 at 2:17 am
Make sure your system has no firewall enabled.
Take the help from Sys Admin and ask them to check the DNS Entries, if trying to connect using windows authentication make sure this machine is in domain.
See there can be N number of reasons.
You need to see this from a very broad prospective.
Regards,
Sarabpreet Singh 😎
Sarabpreet.com
SQLChamp.com
Twitter: @Sarab_SQLGeek
August 15, 2009 at 2:17 am
And yes try to ping the server and see if its working on not.
Regards,
Sarabpreet Singh 😎
Sarabpreet.com
SQLChamp.com
Twitter: @Sarab_SQLGeek
August 17, 2009 at 11:42 am
The system is a member of the domain, I can ping the server with the problem workstations. Firewall disabled. THe network is static IP addressed.
On an established workstation client using Windows XP that the client software was prviously installed on;
The SQL database works without issue. I can establish new profiles with no problem.
Taking a workstation and wiping the drive and reloading XP and re-installing the client software;
The SQL database is not accessable. (24575 error, client not found or access denied).
On a workstation that was previously joined to the domain but the SQL client software was not installed on, I get the same SQL error.
Seems to me that this is pointing to a Group policy setting on the server, So far I have not been able to find it.
Thanks
Bill
THe beatings will continue until morale improves!
August 18, 2009 at 12:54 pm
Fixed!
August 18, 2009 at 2:11 pm
bheinson (8/18/2009)
Fixed!
What was the problem? It would be helpful for anyone else who has a similar issue to know what you had to do to fix this problem.
thanks
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
August 19, 2009 at 9:54 am
After a lot of head banging and much knashing of teeth, my server specialists ("Why do you saddle me with these kinds of problems? he asked, I replied "Because I can figure out the simple ones!") We installed a sniffer (etheral). Traced the problem to a missing Reverse DNS Lookup Zone.
Why the server or the Juris program insisted on suddenly needing a reverse DNS zone I will never know. Adding a reverse DNS lookup zone solved the issue.
August 19, 2009 at 10:39 am
Thank you for the feedback - I am sure it will help someone down the road.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply