Yesterday fine, today cannot connect

[1DMF]

Hi,

I installed MS updates yesterday on our 2003 SBS server, then rebooted.

Now no-one can connect to the SQL db from our MS Access database.

We keep getting

[DBNETLIB][ConnectionOpen (Invalid Instance()).]Invalid connection

Any ideas what this means, why we are now getting it and how I can fix the problem.

Thanks,

1DMF.

"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!

 

[1DMF]

well further investigation show the SQL log with the folowing message...

SuperSocket Info: Bind failed on TCP port 1433

i found one thread regarding this saying to do a [/code]netsh winsock restet[/code] but that didn't help.

the only MS KB I could find seems to refer back to 2006 and SP2, well I have SP4 installed, so I don't think the hotfix should be applied. I'm assuming it was fixed by SP4.

The only thing that has chnaged were MS updates lastnight and now SQL is down.

I've uninstalled the updates , rebooted, but it made no difference, and now auto update has re-installed the updates again.

Still same problem, no clients can connect to SQL?

"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!

 

[gmmastros]

I'm guessing it's a firewall issue, but take a look here:
faq962-5481

-George

"The great things about standards is that there are so many to choose from." - Fortune Cookie Wisdom

 

[1DMF]

Firewall? what makes you say that.



"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!

 

[gmmastros]

It's just a guess. The link I provided will help you determine if my guess is right.

-George

"The great things about standards is that there are so many to choose from." - Fortune Cookie Wisdom

 

[1DMF]

I can see the server , ping it etc..

I;ve changed the port on SBSMonitoring as it seems for some reaon it grabbed 1433 , so I cahnged it to 1434 and let the default DB use 1433 , now the bind error has gone , but still no client connections allowed?

"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!

 

[mutley1]

What version of SQL are you running......SP2 / SP4......for what? SP reference for SQL or Windows?

If you can pass on the editions / versions we may be able to help a bit more.

Thanks,

M.

 

[1DMF]

It's SQL2000 SP4 on SBS 2003 SP2.

I got it working in the end, I changed SBSMonitoring to use port 1434 and put the default DB back to 1433, rebooted and all seems fine.

I'm a little confused why adding SBSMonitoring etc.. into SQL EM caused this.

Perhaps it was to do with the latest update, but I tried uninstalling them and it didn't make a difference, so they're back on.

All a bit wierd, everything was working fine, rebooted after windows update, SQL stopped working.

The only change to SQL was bringng in the instances of SBSMonitoring, Sharepoint and Sophos into the SQL EM so I could see them.

Perhaps there is some default thing going on where all instances when imported into the group are assigned port 1433 hence the conflict, It's the only thing off the top of my head I can think of.

Unless you guys can come up with a better explanation?


"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!

 

[mutley1]

Sorry - I was thinking ages back when we hand a named pipes issue after SP4, but this relates to NT4 machines. Checl out the registry setting though in this article out of interest, and check in enterprise manager to see how the clients are connecting.

http://support.microsoft.com/kb/823492

- like I say, don't think this is the issue but I was the error message and SP4 that stuck in the back of my mind....

Rgds,

M.

 

[1DMF]

Thanks for the link, but reading through, it doesn't seem to related to my problem or my OS or SQL version.

I'm assuming (rightly or wrongly) that it is some issue with SBS and SQL EM when bringing instances in.

It must assign by default the same TCP/IP port binding which was causing a conflict.

Again I'm assuming you cannot have multiple instances of SQL listening on the same port number.

Since changing SBS Monitoring port under 'Network Configuration' -> TCP/IP to 1434 , allowing the default DB to use 1433 it's been fine.

I checked Sophos's instance and it has a port of 2865 , so no conflict there!

What is curious is that SharePoint doesn't have a protocol defined, let alone a TCP/IP port assigned?

I didn't think you could bring instances into SQL without the TCP/IP network configuration port or some protocol being set.

I'm assuming as it's part of the OS being an SBS server , there's something somewhere allowing TCP/IP connections or an internal thing going on.

I'm not bothered, we don't use SharePoint Services (never understood it myself), and i'm not getting any errors, so if it aint broke!!!

Hey ho, you live and learn I guess!


"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!