Me too...

Me also!

I'm wondering whether it could be a tcpip related issue, that's the only common thing between the offending webpage and the web pages with database connections!?
It's very strange and quite impossible to track down.

By the way, thanks for your help anyways!

While showing this error SQL Server does not exist or access denied, do you see any line number and filename details shown along with it?

_________________________
-Vijay G
Strive for Perfection

Hi,

Please check you SQL Server Authentication Mode, it might be running in Windows integrated Authenticated mode and you were trying to access via using a user name and password. In this case you need to change that to mixed mode of authentication.

Charul Shukla

Hi,

The SQL Server authentification is setup to both.

I set the web site on my local machine to replicate the error and this is what I get

Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite (send()).
/fabviewprod/fabviewhome.asp, line 36


line 35 & 36 are:
  GetSQLTimeStr = "select getdate()"
  Set DBDateRs = fabviewConn.Execute(GetSQLTimeStr)

What is the connection string that you are using? Can you post that too? Looks that needs to be changed.

You can refer to the standard connection strings here.
http://www.connectionstrings.com

Hope that helps
Cheers!

_________________________
-Vijay G
Strive for Perfection

Hi

This might be a long shot but is there any firewalls between your IIS and SQL? Maybe a "personal FW" on your development machine? If so check that ports 1433 & 1434 (Integrated Security) are open. Else I would have tried reinstalling or upgrading MDAC on the webserver. Have you tried the page on another IIS machine?

Regards
Marnus

I had the same error message and my problem had to do with conflicting protocols. When I added "Network=DBMSSOCN;" to my connection string my page started working again.

I got my information through the microsoft website: http://support.microsoft.com/defaul...kb;EN-US;328383

Here is what helped me:

Specify the protocol in your connection string. For example: "DSN=DSNName;SERVER=servername;DATABASE=YourDataBa seName;Network=DBMSSOCN;Address=IP_Address,1433;UI D=YourUID;PWD=YourPassword;"

In this example, you specify the network protocol as "DBMSSOCN", which means that you want to use the TCP/IP protocol. If you specify the protocol inside your connection string, Dbnetlib only uses the specified protocol and does not try any other protocol. Similarly, to enable Named Pipe protocol only, use a connection string similar to this: "DSN=DSNName;SERVER=servername;DATABASE=YourDataBa seName;Network=DBNMPNTW;Address=\\.\pipe\sql\query ;UID=YourUID;PWD=YourPassword;"

Hi jmrosseau,

Yes that looks fine, but so far the original poster(haidee_mccaffrey) has not shown us what he uses as the connection string for fabviewConn. So being unclear on that, it is hard to suggest.



Maybe, had he posted the code that are related to fabviewConn, it would have been easy for one to conclude on error, than posting our suggestion on assuming.

_________________________
- Vijay G
Strive for Perfection