[Microsoft][ODBC SQL Server Driver]Timeout expired

I keep getting the above error when i run a sql from my web page. The query runs fine in enterprise manager. What is worng . Please help.

sql="SELECT top 1 * FROM V_ISSUE WHERE ISSUE_ID=" & issueid & " order by issue_id"

if Session("rs").State = 1 then Session("rs").Close
Session("rs").Open sql,Session("MyConn")Please Try this Code

sql="SELECT top 1 * FROM V_ISSUE WHERE ISSUE_ID=" & issueid & " order by issue_id"

Session("rs").Open sql,Session("MyConn")

Session("rs").close
Set Session("rs")=Nothing

[Microsoft][ODBC SQL Server Driver]Timeout expired

Hi:
I am getting this error when the .asp page tries to connect to the DB server.
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver]Timeout expired
The web server is Windows 2000 Advanced Server, Dual CPU with
Hyperthreading, P4 with 2 GB RAM. The database is SQL 2000 Standard Edition
with SP3 and Cumulative Patch for Microsoft SQL Server (815495)MS03-031
installed on a remote server with the same config. I have also tried all the
possible variations like increasing the VBscript timeout in IIS from 90 to
300 and Global transaction timeout in COM+ applications from 60 to 300. This
however is not helping either. When I check the anonymous concurrent sessions
I find atleast 950 connections at any given time. Also installed MDAC 2.7
Refresh on both the servers.
Can any one help me on this please.
Mitul Z.
Hi Mitul,
This error message is somewhat a generic error message for ODBC. Here are
some ideas for troubleshooting the issue.
1. From the server hosting your web server, can you connect to the SQL
Server using Query Analyzer? If you do not have Query Analyzer available,
you can test connectivity by creating a test ODBC DSN and using the test
facility. Can you connect to the SQL Server with these techniques?
2. If you can connect using Query Analyzer or an ODBC test DSN, then the
issue is with the asp page itself. If you cannot connect to the SQL Server
using these tests, the problem is with ODBC configuration or a network
level problem is at play.
If you suspect a network problem is at play, Network Monitor traces will be
very helpful for your troubleshooting. That will at least allow you to
know if your connection request is reaching the SQL Server.
Please let me know if this information helps.
Thank you.
Gary
This posting is provided "AS IS" with no warranties, and confers no rights.

[Microsoft][ODBC SQL Server Driver]Timeout expired

Hi:
I am getting this error when the .asp page tries to connect to the DB server
.
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver]Timeout expired
The web server is Windows 2000 Advanced Server, Dual CPU with
Hyperthreading, P4 with 2 GB RAM. The database is SQL 2000 Standard Edition
with SP3 and Cumulative Patch for Microsoft SQL Server (815495)MS03-031
installed on a remote server with the same config. I have also tried all the
possible variations like increasing the VBscript timeout in IIS from 90 to
300 and Global transaction timeout in COM+ applications from 60 to 300. This
however is not helping either. When I check the anonymous concurrent session
s
I find atleast 950 connections at any given time. Also installed MDAC 2.7
Refresh on both the servers.
Can any one help me on this please.
Mitul Z.Hi Mitul,
This error message is somewhat a generic error message for ODBC. Here are
some ideas for troubleshooting the issue.
1. From the server hosting your web server, can you connect to the SQL
Server using Query Analyzer? If you do not have Query Analyzer available,
you can test connectivity by creating a test ODBC DSN and using the test
facility. Can you connect to the SQL Server with these techniques?
2. If you can connect using Query Analyzer or an ODBC test DSN, then the
issue is with the asp page itself. If you cannot connect to the SQL Server
using these tests, the problem is with ODBC configuration or a network
level problem is at play.
If you suspect a network problem is at play, Network Monitor traces will be
very helpful for your troubleshooting. That will at least allow you to
know if your connection request is reaching the SQL Server.
Please let me know if this information helps.
Thank you.
Gary
This posting is provided "AS IS" with no warranties, and confers no rights.

[Microsoft][ODBC SQL Server Driver][SQL Server]I/O error (bad page ID)

Hi!

Im having this error when doing a query to a SQL Server 2000 Database:

Microsoft OLE DB Provider for ODBC Drivers error
'80004005'

[Microsoft][ODBC SQL Server Driver][SQL Server]I/O error
(bad page ID) detected during read at offset
0x000000003ac000 in file 'E:\Program FIles\Microsoft SQL
Server\MSSQL\Data\sitioIAC_Data.MDF'.

It doesnt happend in some queryes trough a ASP file.

What could it be??

Thank You
JuanRun DBCC CHECKDB against that table(s) with REPAIR_ALLOW_DATA_LOSS option. Refer to BOL for more information on DBCC CHECKDB & CHECKTABLE topics.

[Bug] Jump to report from a Table (second page on HTML)

This seems like a bug:
I created a "jump to report" action on a TABLE in my report.
It works fine. But - when the table becomes long, and exceeds one
page on the HTML viewer, the "Jump to report" doesn't work anymore.
It keep throwing up blank pages.
Has anyone else encountered this?One question, is this from the IDE or from a deployed report. I have had a
variety of funky oddities that are only in the IDE, the deployed report
works fine.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Harsh" <harsh.vb@.gmail.com> wrote in message
news:1e70ecdd.0411130717.8685260@.posting.google.com...
> This seems like a bug:
> I created a "jump to report" action on a TABLE in my report.
> It works fine. But - when the table becomes long, and exceeds one
> page on the HTML viewer, the "Jump to report" doesn't work anymore.
> It keep throwing up blank pages.
> Has anyone else encountered this?