December 4, 2002 at 2:31 pm
Had a problem that came up yesterday, I resolved the problem, but don't know what caused it.
The SQL 7 boxes are on the same network segment, same domain.
Server A(SQL 7sp3) to Server B SQL Server 7 sp3
Server D Oracle 8i on NT
Server E Oracle 8i on AIX
Server F UDB on AIX
Server C(SQL 7sp3) to Server B
Yesterday server A lost connection to server B, the end user apps were getting [SQL Server]OLE DB provider 'SQLOLEDB' reported an error. The provider ran out of memory. A similar error was reach (see error 11044) through EM when I right clicked on the properties of the link server.
I deleted the link server and then clicked new link server and got a RPC is not listening error.
Query analyzer from A to B works fine. Link server C to B works fine.
Nothing new has been added to Server A. Server A had not seen a reboot for a
month. Nothing in the error log or Events log.
I fixed this by net stop mssqlserver
net start mssqlserver
add the Link Server
Test the views.
Any idea on what happened or what caused just SQLServer.exe to stop taliking to RPC. Why didn't the other link servers break? When I click on add link server, at this point it shouldn't have an idea whether I'm building a link to Oracle or SQL Server. So if it tells me the RPC is not listening shouldn't have been dead for all?
Any thoughts, ideas, suggestions. Stopping and starting a web sqlserver database is not a viable solution. Not sure if this will ever happen again.
thanks
John Zacharkan
John Zacharkan
December 4, 2002 at 2:33 pm
Your poor overworked SQL server got fed up with handling the 1000's of unsolicited reqeusts and decided to throw a fit until you gave it some personal attention.
No wait a minute .... that was one of my kids. Sorry.
Nope no idea.
December 4, 2002 at 6:40 pm
I have not seen or heard this anywhere else. Unless you can get a pattern it might be a fluke. However a few thoughts.
Do you have any apps that open sockets for clients to attach? I wrote and app and recently after a week of running it started getting internal errors (which I am researching) and ultimately it interfered with some of SQLs open sockets but nothing else.
Try SP4 may be a known issue.
Try updating you MDAC, 2.5 and 2.6 have several fixes around provider memory leaks and this looks like it could be the case here.
Other than that I am just taking a stab in the dark.
December 6, 2002 at 6:42 am
Thanks,
There's a preferance to leave the production web database servers alone while the holiday season is on.
Think I'm just going to see if it happens again.
quote:
Try SP4 may be a known issue.
Try updating you MDAC, 2.5 and 2.6 have several fixes around provider memory leaks and this looks like it could be the case here.
Other than that I am just taking a stab in the dark.
John Zacharkan
John Zacharkan
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply