IIS5 & SQL Server 2000

First off, I'm not sure whether this is an IIS or SQL question so forgive me
if I'm posting off topic.
I am in the process of moving a number of webs from a single box running NT4
(sp6a), IIS 4 & SQL Server 7 to separate boxes running Win2k Server (sp4),
with SQL Server 2000 on one and IIS 5 on the other. The webs are asp based.
The connection strings are configured to use SQLOLEDB with the server name
appearing somewhere in the string.
The problem is that when you try to connect the web to SQL Server it
generates an "SQL Server Does Not Exist or Access Denied" error message (as
per kb328306). I have gone through all of the options in this article and
am certain that all the SQL protocols in use (TCP/IP, Named Pipes etc) are
fully functional. However when I change the server name to the server IP
address in the connection string, it works.
Oh, while I remember, both servers have valid dns entries so it shouldn't be
a cased of unresolved names.
The question then is, is this something to do with differences in the way
IIS 5 works as against IIS 4.
Long life and prosperity to anyone who can help me out with this - my head
hurts and the wall is about to collapse...
TIA
Nigel
Use Query Analyzer and select @.@.servername.
If this name is DIFFERENT than the Windows name of that server, you have
identified the problem... This occurs whenever a server is renamed, and when
master is moved from one server to another...
If that is the case
sp_dropserver oldservername
sp_addserver newservername, local
Otherwise I would still suspect it is a DNS problem .
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Nigel Q" <nigel.quiggin@.rnib.org.uk> wrote in message
news:%23326oeYPEHA.556@.tk2msftngp13.phx.gbl...
> First off, I'm not sure whether this is an IIS or SQL question so forgive
me
> if I'm posting off topic.
> I am in the process of moving a number of webs from a single box running
NT4
> (sp6a), IIS 4 & SQL Server 7 to separate boxes running Win2k Server (sp4),
> with SQL Server 2000 on one and IIS 5 on the other. The webs are asp
based.
> The connection strings are configured to use SQLOLEDB with the server name
> appearing somewhere in the string.
> The problem is that when you try to connect the web to SQL Server it
> generates an "SQL Server Does Not Exist or Access Denied" error message
(as
> per kb328306). I have gone through all of the options in this article and
> am certain that all the SQL protocols in use (TCP/IP, Named Pipes etc) are
> fully functional. However when I change the server name to the server IP
> address in the connection string, it works.
> Oh, while I remember, both servers have valid dns entries so it shouldn't
be
> a cased of unresolved names.
> The question then is, is this something to do with differences in the way
> IIS 5 works as against IIS 4.
> Long life and prosperity to anyone who can help me out with this - my
head
> hurts and the wall is about to collapse...
> TIA
> Nigel
>
|||Thanks for the reply Wayne
The server is a new build and the Windows name & SQL name are identical.
Cheers
Nigel
"Wayne Snyder" <wsnyder@.computeredservices.com> wrote in message
news:utU7XrZPEHA.1312@.TK2MSFTNGP12.phx.gbl...
> Use Query Analyzer and select @.@.servername.
> If this name is DIFFERENT than the Windows name of that server, you have
> identified the problem... This occurs whenever a server is renamed, and
when[vbcol=seagreen]
> master is moved from one server to another...
> If that is the case
> sp_dropserver oldservername
> sp_addserver newservername, local
> Otherwise I would still suspect it is a DNS problem .
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
>
> "Nigel Q" <nigel.quiggin@.rnib.org.uk> wrote in message
> news:%23326oeYPEHA.556@.tk2msftngp13.phx.gbl...
forgive[vbcol=seagreen]
> me
> NT4
(sp4),[vbcol=seagreen]
> based.
name[vbcol=seagreen]
> (as
and[vbcol=seagreen]
are[vbcol=seagreen]
IP[vbcol=seagreen]
shouldn't[vbcol=seagreen]
> be
way
> head
>
|||If you can use the ip address to connect but not the server name, then it
is a name resolution problem of some kind.
If you go to a command prompt on the IIS machine and issue the following
command:
ping -a <ip address of SQL Server machine>
does it return the proper machine name. If not then the problem is name
resolution.
Is this a default instance or is it a named instance. If it is the latter
are you specifying the full name <machine\instnce>.
Use the cliconfg utility on the IIS machien to make sure there is no alias
pointing incorrectly to the SQL Server machine.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Ping <ServerName> returns correct IP
Ping -a <IP> returns correct Servername
This is a default instance of SQL Server, & no aliases have been set.
Nigel
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
news:jHi8wXaPEHA.3080@.cpmsftngxa10.phx.gbl...
> If you can use the ip address to connect but not the server name, then it
> is a name resolution problem of some kind.
> If you go to a command prompt on the IIS machine and issue the following
> command:
> ping -a <ip address of SQL Server machine>
> does it return the proper machine name. If not then the problem is name
> resolution.
> Is this a default instance or is it a named instance. If it is the latter
> are you specifying the full name <machine\instnce>.
> Use the cliconfg utility on the IIS machien to make sure there is no alias
> pointing incorrectly to the SQL Server machine.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>
|||"Nigel Q" <nigel.quiggin@.rnib.org.uk> wrote in message news:<#326oeYPEHA.556@.tk2msftngp13.phx.gbl>...
<snip>

> The problem is that when you try to connect the web to SQL Server it
> generates an "SQL Server Does Not Exist or Access Denied" error message (as
> per kb328306). I have gone through all of the options in this article and
> am certain that all the SQL protocols in use (TCP/IP, Named Pipes etc) are
> fully functional. However when I change the server name to the server IP
> address in the connection string, it works.
This sounds very similar to the problem I have been experiencing
recently. (See msg ID
<Xns94E76C28F7CF6canimalmydejacom@.207.46.248.16>).
When I got those errors, the security log on the SQL server showed
hundreds of failed logins for WORKSTATION/aspnet. You might see if
you have the same thing. I am wondering if using a name rather than
an IP address is forcing a named pipes connection (overriding even
Net=dbmssocn). Just a wild guess, haven't tried to explore that.
This problem includes apps that worked fine until recently. I have
also had similar problems connecting by server name with WinForms .NET
apps.
Regrettably, I do not have a solution, other than using IP instead of
name.
Since the problem appeared out of the blue, I am guessing that running
one of the recent security updates is the cause. With luck, MS will
recognize this as an issue and correct it. I would be happy to post
more info if someone from MS has questions. (Note that the email
address above is broken, I'll only see newsgroup postings.)
Matt