June 16, 2005 at 8:37 am
Hi! So, here is my set up. I have an ASPX page on one server (server 'x') and the db is on another (server 'y'). When i had both the page and the DB on the same server, everything worked great and there was zen, but now that i've moved them accross, i get this error
[Microsoft][ODBC SQL Server Driver][Shared Memory] SQL Server does not exist or access denied.
[Microsoft][ODBC SQL Server Driver][Shared Memory] ConnectionOpen(Connect())
Sometimes. Not all the time. I'd say for every 3 or 4 successful hits, one of them will error. I've done all the really basic stuff (set up a db account, set server y to allow windows and sql user requests, gave the login permissions, etc) and i have no idea why it works and then the next minute it doesn't. I've tried and my work won't let me go back to putting both of them on the same machine.
my IIS is set up for no annonymous user and windows authentication, and my web.config has impersonation enabled with integrated authentication.
Any help would be awesome!
Joel
June 17, 2005 at 11:04 am
I know this is ignorant sounding, but did you change the connection string from [local] to the new SQL box?
June 17, 2005 at 1:28 pm
lol, yes i did. i think the problem was the sql server with the sql server 2k. I restarted it, and it hasn't happened since. I'm just currious as to what it was. . .
June 18, 2005 at 3:41 pm
I wonder if the local client on the web server eventually tried the local only protocol after not getting through with TCP/IP or Named Pipes? Anyway, I'd run the client network utility and check the enabled protocols. And, on the sql server, I'd check the enabled protocols with the server network utility.
I've seen situations where an alias, on the client side, was required and even setting the port (1433 or whatever). I've also seen where the registry settings of enabled protocols did not necessarily reflect what was enabled.
It seems like "reboot" is step 1 in most troubleshooting.
June 19, 2005 at 10:53 am
yeah, i had checked the ports (we're not doing named pipes) and 1433 is enabled within the network, and rebooting wasn't an option until the end of the day, because the server is host to other db's that were being used pretty much all working day.
quick question, is named pipes better than ports?
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply