I have an interesting problem I can not find an explanation for, the error I'm receiving is:

"Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied. "

The rest of the (data-aware) page load up OK. All data come from the same database, same username (SA account has been used temporaraly to eliminate table level permissions etc) & password...

It's error-ing out on an ASP line that retrieves a recordset, however, other pages that retrieves data from the same table loads up OK.

Funny thing is, the same application tested on other servers - is working fine.

I have checked the rights to the database and the table itself, and they are OK.

Anything else I can check (apart from doing a re-install)? It's not really my machine, it's a clients machine so I can't really do a re-format/install when I want to...

Connection String used is : Driver = "Driver={SQL Server};Server=;Uid=sa;Pwd=;Database=MyDB"


Wind is your friend
Matt

__________________
Wind is your friend
Matt

Hi Matt,

Any possiblity of posting some code here?

Why not compare the code on the other page that works fine with that of the page that errors out.

May be you can try isolate the code that is trying to extract just that particular column alone.

Also snsure that you are using the same connection string that works fine on the other page. Not sure if you are using include file in place of the connection string.

May be posting come code would shed some light on that.

Cheers!

_________________________
- Vijay G
Strive for Perfection

Thanks Vijay/happygv!

I am using an include file for the connection string, so yep, it is a global/same one used for all.

I took your advice and isolated the code that was causing the problem. Basically, same page just stripped out all the other extra bits - and it worked.

I could post the isolated code here, but that one works... the problematic one is about 700 lines and requires inputs from other pages.

I have a feeling that this is a server/hardware issue...

Here's the code: (simplified)

<% option explicit %>


<% SubDirLevel = 1 %>
<%
  dim Conn
  dim SQL
  Dim ProdManComments

  set Conn=server.createobject("ADODB.Connection")
  Conn.Open(GetConnectionString(iC_MainDB, SubDirLevel))
  SQL = "SELECT PMComment, PMCommentDate, LinkedKA, Supplier.Alias FROM COAssessPMComments LEFT OUTER JOIN Users AS Supplier ON Supplier.ID = COAssessPMComments.PMUserID"

  Set ProdManComments = Conn.Execute(SQL)
  DO WHILE NOT ProdManComments.EOF
    Response.Write(ProdManComments(0) & "<BR>")
    ProdManComments.MoveNext
  LOOP
  Set ProdManComments = Nothing
  conn.close
  Set conn = Nothing
%>

and the connection string is as above.

Thanks again! at least now I have something to base my recommendation on.

Wind is your friend
Matt

Hi Matt,

It is really wierd to see this error only for that page. Does that happen only to that page?(I still can't believe) Can you check if that happens for just that column alone? I can't really think of anything else as per this error. Can you also check if the datatype of that column is responsible for something like that? May be you can check if the network cable is not loose behind the CPU;)(but not only when you access this page). Just a try. But that too should be ruled out as you say is happens only for that page. Got to drill out every possiblity to find a firm answer to this.

Cheers!:)

_________________________
- Vijay G
Strive for Perfection

Thanks again Vijay/happygv!

I checked the server's EventLog/Applications and found that there is a constant error stating : "Error 17809, Severity 20, State 1 : Could not connect. The maximum number of '7' configured user connections are already connected. "

I could run sp_configure to change it, but do you think that that would be what's causing this? I don't think anybody else are accessing it when I do since it's still under development.

If you execute a query to retrieve a recordset, and then close the ASP block by using "%>", and then somewhere you open it again "<%" and issue another query (leaving both recordsets active) - does that count as 2 SQL user connections ?

Thanks again, and I appreciate all your help!


Wind is your friend
Matt