Microsoft OLE DB Provider for ODBC Drivers error '80030e31'
[Microsoft][ODBC SQL Server Driver] Timeout expired
/poststatuscheck.asp, line 39 <-- this would vary
So I searched and found that changing this
cOperations.Open ("DSN=Operations; user id='uname'; password='password'")
to this
cnOperations.Open ("Provider=SQLOLEDB; Data Source=x.x.x.x; Network=DBMSSOCN; user id='uname'; password='password")
makes it work like its suppose to.
The questions I have are...
What is the difference between these two types of connections? I know one uses data source and the other dsn.
Should I be concerned about security with this new method? Should I be concerned with anything in this new method? Is it possible to fix the old method?
Having some problems updating a recordset, despite the fact that I've used the bulk of the code sucessfully in other projects. I seem to be able to add records no problem, but when I try to update them I get Code:
When i pulling weekly report from the system which using ASP as programming language and SQL Server 2000 as database, an error pop up showing that "Timeout Expired". The report supposes in Microsoft Office Spreadsheet. I tried to query the same stored procedure using Microsoft Query Analyzer and it works. I am not sure what's wrong.
I have a web page displaying results from a query including 4 table joins (so pretty slow anyway). I keep getting the following error message
Microsoft OLE DB Provider for SQL Servererror '80040e31'
Timeout expired /it/fees.asp, line 310
I have the following at the top of my fees.asp page:
<% Server.ScriptTimeout = 300 %> and have also set the ASP Script Timeout to 300 seconds in IIS, Home Page, Configuration, Options. I get the above error message after approx 45 seconds and the query should take approx 1 minute to run.
I have a dynamically generated update statement which has a rathe large IN clause making comparisions on an indexed and keyed integer field. Here's the code below: ....
I am getting the error Time out expired , I have tried every thing increased Server.scripttimeout to 90000 response.buffer=false .. etc even then I m gettin the error.
I have 3 ASP pages. Page1 has file upload feature where the user selects a file and clicks on upload button. Page2 takes that uploaded file and process the records to insert into the database. Page3 shows that records from the database. Code:
I need to capture the Script timeout error if that is possible. I know I can increase the timeout value in the server settings or in the scripts itself but I really want to make sure that no timeout situation will results as the standard script timeout error page.
I have a site that utilizes online forms. The problem is people could easily spend well more than 20 minutes filling out the forms before submitting them. To avoid the default timeout of 20 minutes (or whatever) I added a Session.Timeout = 120 to the forms page. I also checked IIS and set the connection timeout property to 120 minutes as well.
sessions still seem to be timing out well short of the 120 minute cutoff. (I haven't yet tested to see if it's still 20 minute default or somewhere between 20 and 120).
Is there anywhere else this setting might be controlled? Is there any simple way to do some sort of "keep-alive" from the page so that the server thinks it's active?
How do you get a web app to not show the 'page has expired...' error and refresh and requery when you hit the back button after submitting a form? I just want the old data to still be displayed in the form so the user can go back, make a few changes, and submit again.
I checked knowledge base for this and I do not have "Do not save encrypted pages to disk" checked and the user is running IE 6.0.2900.2180.xpsp_sp2_rtm.040803-2158 I am running server2003 and IE 6.0.3790.0 update version 3283 and I don't have the problem.
I want to show users a custom "Page Expired" page when users go back to the previous page by clicking the "Back" button of the browser (or when he right-clicks anywhere on the current page & selects "Back" from the menu). How do I do this?
I have a count down and a body onload linked to a function that closes the connection on my main page to ensure no user will not leave the page without logout.The problem is that my main page opens several others which I´d ike to close as well after logout.Can I rely on If sessionID="" to close those windows?
I have a form that users fill in and the results are put into a DB by an asp script, this script will then redirect the users to another page where a receipt number is generated and displayed. How can I make the form expire after the user sends the information and the receipt is issued.
At the moment I am getting the following Expired Warning if a user logins into a secure page and attempts to press the 'back' button:
Warning: Page has Expired The page you requested was created using information you submitted in a form. This page is no longer available. As a security precaution, Internet Explorer does not automatically resubmit your information for you.
To resubmit your information and view this Web page, click the Refresh button. Is there someway to gracefully stop this from happening...in other words.to re-display the login page? Also, what is causiing this? Session Variables?
"Warning: Page has Expired The page you requested was created using information you submitted in a form. This page is no longer available.
As a security precaution, Internet Explorer does not automatically resubmit your information for you.
To resubmit your information and view this Web page, click the Refresh button. "
I'm developing an e-commerce site from scratch.
I've noticed on other e-commerce websites that use other development tools such as php or probably "websphere" (java) that when clicking the back button this message appears during a checkout process. This is good because it reduces customer error in many ways.
I'm using ASP and response.redirect mostly. But, I've noticed that even setting a page timeout to zero won't stop the caching of the page. My customer, who just submitted a form, can just click the back button and the cached page just comes up.
I have a web pagewhich queries a db and displays information on the subsequent page. On the subsequent page if I click back to previous page (this is a button with javascript code on it), it takes me to the previous page but the page says - "warning page expired".
When I am in my company work environment, I dont get this page, it properly displays the information on the previous page but when I go to the client site, it gives me the problem All of us are on the same IE version and service packs. Could this be a programming issue or a security issue.
I have a application which is a global login for other applications. Basically application A checks all the user login information and then lists all the applications B-Z that the user has access to.
I have a global.asa file in application A and individual global.asa files in applications B-Z. Applications B-Z are under the Application A directory. Can I have global.asa files in each of the application folders? Does the pages look for the closest global.asa file?
I have to keep track of user login time and logout tme for each application. The problem I run into is how do I record the user logout time when the session expires?
How do you get a web app to not show the 'page has expired...' error and refresh and requery when you hit the back button after submitting a form I just want the old data to still be displayed in the form.
I checked knowledge base for this and I do not have "Do not save encrypted pages to disk" checked and am running IE 6.0.2900.2180.xpsp_sp2_rtm.040803-2158.
We have a web application where we want a user to be able to change his/her password if the password has expired but we are unable to do this with ASP at the moment because we can't log the user into the database without a valid password.
We do not want to store any "admin" user info to connect to the database to change the users password for security issues.Does anyone have any ideas of how we could go about doing this?
how i can build a script to list deleted domains ? then obviously i can add more features on from there, ive looked everywhere and all of them seem to be php so i cant see how they do it.
I installed ASPUpload component evaluation version on my personal computer for development and testing purposes and now one month has completed, and the component has expired.
I re-installed evaluation copy but it didn't work.
What's the best way to inform a user if their session has expired? It seems like upon logging into the system, when the first variables are created I could create a session variable that just stores a number, and then at the top of every page check to see if that variable is empty or not, but I'm not sure. What's the best way to do this? And if that is the best way, do I just compare it to a string of ""? or null?
in asp i want to check if user inactive for 10 minutes..than i want to kill his session and display a page showing message into this page ..."your session has expired" .
I have page for user to update his/her details. What i want is after idle for more than 20 mins, the page will redirect to login page automatically. So that the user knows that his/her session already expired and need to login again.
But it doesn't working. This is because if he/she update the details (after idle more than 20 mins), and click the Submit button, it will go to login page and all the data will be lost. Code:
I have an asp page that is producing a report via some heavy SQL queries with dynamically chosen parameters from the users of the page. I can run it on my development server (takes about 35 minutes to produce) , however when it is run on the production server it will execute for about 3 minutes, then bring me to a Page Cannot Be Displayed.
I think this might be some sort of timeout, but I have no idea as to how to stop it. I've changed the timeout property of the Server, I have even put in a buffer flush if the client isConnected.
I am using sql server 2000. From the asp page i am calling a stored procedure that does all the processing that includes:
1. create the query dynemically according to the selections made by the user. 2. run query 3. if records found, create a comma delimited list 4. pust that file on a file server, from where the user can then download the file
it return -1 if an error has accoured, 0 if no records are found, or file id if the records are found and file is written and moved to its location successfully.
i have increased the script timeout time to 800 ...
