Re: Microsoft OLE DB Provider for SQL Server (0x80004005)
From: AMills (AMills_at_discussions.microsoft.com)
Date: 09/16/04
- Next message: AMills: "Re: Microsoft OLE DB Provider for SQL Server (0x80004005)"
- Previous message: AMills: "Re: Microsoft OLE DB Provider for SQL Server (0x80004005)"
- In reply to: Bob Barrows [MVP]: "Re: Microsoft OLE DB Provider for SQL Server (0x80004005)"
- Next in thread: Bob Barrows [MVP]: "Re: Microsoft OLE DB Provider for SQL Server (0x80004005)"
- Reply: Bob Barrows [MVP]: "Re: Microsoft OLE DB Provider for SQL Server (0x80004005)"
- Reply: Bob Barrows [MVP]: "Re: Microsoft OLE DB Provider for SQL Server (0x80004005)"
- Reply: Bob Barrows [MVP]: "Re: Microsoft OLE DB Provider for SQL Server (0x80004005)"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 16 Sep 2004 09:37:05 -0700
Bob:
Here is my ASP code that is used:
strSQL = "EXEC dbo.pci_Student_Certs_Monthly_Data_Load @MonthDate='" &
strDate & "'"
objConn.Execute(strSQL)
Also: the changes that Microsoft suggested was to add this line to my
connection string:
OLE DB Services = -2;
Thanks
Andy
"Bob Barrows [MVP]" wrote:
> AMills wrote:
> > Hello Guys:
> >
> > We are getting the following error and not sure why.
> >
> > Microsoft OLE DB Provider for SQL Server (0x80004005)
> > [DBNETLIB][ConnectionRead (WrapperRead()).]General network error.
> > Check your network documentation.
> >
> > This error is being generated from an ASP page to a SQL Server 2000
> > database. This error ONLY occurs when running from the web-page.
> > When we run the Stored Procedure on the database server itself: this
> > error is not generated.
> >
> > When researching: Microsoft says it might be a connection pooling
> > issue.
>
> ??
>
> > However: this is the only stored procedure that generates
> > this error. And when making the modifications suggested by
> > Microsoft, we still recieve this error. The SP is not returning a
> > recordset, and the code is not expecting one in return.
> >
> > Would anyone be able to tell us what is wrong and what is causing
> > this error?
> >
> > Thanks
> > Andy
>
> Start here: http://www.aspfaq.com/show.asp?id=2009
> If it does not provide your answer, then show the code you are using to
> generate this error. And detail the changes that were "suggested by
> Microsoft" so we don't cover the sme ground.
>
>
> Bob Barrows
> --
> Microsoft MVP -- ASP/ASP.NET
> Please reply to the newsgroup. The email account listed in my From
> header is my spam trap, so I don't check it very often. You will get a
> quicker response by posting to the newsgroup.
>
>
>
- Next message: AMills: "Re: Microsoft OLE DB Provider for SQL Server (0x80004005)"
- Previous message: AMills: "Re: Microsoft OLE DB Provider for SQL Server (0x80004005)"
- In reply to: Bob Barrows [MVP]: "Re: Microsoft OLE DB Provider for SQL Server (0x80004005)"
- Next in thread: Bob Barrows [MVP]: "Re: Microsoft OLE DB Provider for SQL Server (0x80004005)"
- Reply: Bob Barrows [MVP]: "Re: Microsoft OLE DB Provider for SQL Server (0x80004005)"
- Reply: Bob Barrows [MVP]: "Re: Microsoft OLE DB Provider for SQL Server (0x80004005)"
- Reply: Bob Barrows [MVP]: "Re: Microsoft OLE DB Provider for SQL Server (0x80004005)"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|