give full details of this ORA-12988: cannot drop column
from table owned by SYS
Thursday, October 23, 2008
give full details of this ORA-12988: cannot drop column
Monday, September 29, 2008
How do I increase timeout values?
How do I increase timeout values?
tag Server.ScriptTimeout = 180
To change this value for an entire application, open Internet Services Manager, go to the Home Directory tab of the application, click on configuration, and alter the ASP Script timeout field on the "App Options" tab. If you do not have access to the web server directly, you can also use ADSI to change this value on a per-application basis. Keep in mind that with this method you can only override the default with a value GREATER than that stored in the metabase - if you try to lower the current value, the change will not take effect.
The minimum value for ScriptTimeout is 0 (which means never time out). If you try to set it to a negative number (-1 is a common pitfall; it is often associated with "infinite"), you will get the following:
error '80004005'
Unspecified error
The maximum value for ScriptTimeout is 2^32-1, or 2147483647. If you try to set it to 2147483648 or higher, you will get the following error:
Microsoft VBScript runtime (0x800A0006)
Overflow: 'server.scripttimeout'
If you need this much time, you need to investigate your script, because it must be horribly inefficient. And no user (or even browser) will ever wait that long for a page to render.
Session.Timeout
This setting controls how long, in minutes, a user's session will last. While it is wise to keep this value short for efficiency's sake, there are cases where that's just not enough time for users to get things done in your application (for example, if you have a client-side tool where the user is changing properties but not making requests to the server until they are done). The default is 20 minutes, and once 20 minutes of inactivity has occured, the session expires and all session variables are lost. You can increase the session timeout in an ASP page or in global.asa's Session_onStart() method with the following code:
Session.Timeout = 45
To change this value for an entire application, open Internet Services Manager, go to the Home Directory tab of the application, click on configuration, and alter the Session timeout field on the "App Options" tab. This metabase setting is also exposed to ADSI.
conn.connectionTimeout
Where conn is an ADODB.Connection object that is not yet open, the connectionTimeout property will indicate the amount of time, in seconds, to wait for an ASP application to initially connect to the data source. The default is 15 seconds; to override the default, use syntax as follows:
server side
Set conn = CreateObject("ADODB.Connection") conn.ConnectionTimeout = 120 conn.Open
commandTimeout
CommandTimeout tells the server how long to wait, in seconds, for completion of any command sent to the data source. This value is editable before and after the connection has been opened. The default is 30 seconds, but you can override it like this:
server side
Set conn = CreateObject("ADODB.Connection") conn.Open
conn.CommandTimeout = 120
Note that you can also apply a commandTimeout value to a command object, and it will behave independent of the commandTimeout value associated with the connection object. So for specific stored procedures or other commands being executed explicitly through the ADODB.Command object, you could have a longer timeout than that of the connection object. The syntax for the command object is almost identical:
<% Set cmd = CreateObject("ADODB.Command") cmd.CommandTimeout = 120 %>
Note that Oracle drivers do not support the commandTimeout property, up to and including MDAC 2.7. See more information.
http://classicasp.aspfaq.com/general/how-do-i-increase-timeout-values.html
tag Server.ScriptTimeout = 180
To change this value for an entire application, open Internet Services Manager, go to the Home Directory tab of the application, click on configuration, and alter the ASP Script timeout field on the "App Options" tab. If you do not have access to the web server directly, you can also use ADSI to change this value on a per-application basis. Keep in mind that with this method you can only override the default with a value GREATER than that stored in the metabase - if you try to lower the current value, the change will not take effect.
The minimum value for ScriptTimeout is 0 (which means never time out). If you try to set it to a negative number (-1 is a common pitfall; it is often associated with "infinite"), you will get the following:
error '80004005'
Unspecified error
The maximum value for ScriptTimeout is 2^32-1, or 2147483647. If you try to set it to 2147483648 or higher, you will get the following error:
Microsoft VBScript runtime (0x800A0006)
Overflow: 'server.scripttimeout'
If you need this much time, you need to investigate your script, because it must be horribly inefficient. And no user (or even browser) will ever wait that long for a page to render.
Session.Timeout
This setting controls how long, in minutes, a user's session will last. While it is wise to keep this value short for efficiency's sake, there are cases where that's just not enough time for users to get things done in your application (for example, if you have a client-side tool where the user is changing properties but not making requests to the server until they are done). The default is 20 minutes, and once 20 minutes of inactivity has occured, the session expires and all session variables are lost. You can increase the session timeout in an ASP page or in global.asa's Session_onStart() method with the following code:
Session.Timeout = 45
To change this value for an entire application, open Internet Services Manager, go to the Home Directory tab of the application, click on configuration, and alter the Session timeout field on the "App Options" tab. This metabase setting is also exposed to ADSI.
conn.connectionTimeout
Where conn is an ADODB.Connection object that is not yet open, the connectionTimeout property will indicate the amount of time, in seconds, to wait for an ASP application to initially connect to the data source. The default is 15 seconds; to override the default, use syntax as follows:
server side
Set conn = CreateObject("ADODB.Connection") conn.ConnectionTimeout = 120 conn.Open
commandTimeout
CommandTimeout tells the server how long to wait, in seconds, for completion of any command sent to the data source. This value is editable before and after the connection has been opened. The default is 30 seconds, but you can override it like this:
server side
Set conn = CreateObject("ADODB.Connection") conn.Open
conn.CommandTimeout = 120
Note that you can also apply a commandTimeout value to a command object, and it will behave independent of the commandTimeout value associated with the connection object. So for specific stored procedures or other commands being executed explicitly through the ADODB.Command object, you could have a longer timeout than that of the connection object. The syntax for the command object is almost identical:
<% Set cmd = CreateObject("ADODB.Command") cmd.CommandTimeout = 120 %>
Note that Oracle drivers do not support the commandTimeout property, up to and including MDAC 2.7. See more information.
http://classicasp.aspfaq.com/general/how-do-i-increase-timeout-values.html
Why do I get non-database-related 80004005 errors?
Why do I get non-database-related 80004005 errors?
see this article
http://tutorials.aspfaq.com/8000xxxxx-errors/80004005-errors.html
see this article
http://tutorials.aspfaq.com/8000xxxxx-errors/80004005-errors.html
Response object error 'ASP 0100 : 8007000e'
Response object error 'ASP 0100 : 8007000e'
Out of memory
Unable to allocate required memory.
Have anybody seen this error before, what does it actually mean?
Out of memory
Unable to allocate required memory.
Have anybody seen this error before, what does it actually mean?
Ajax error if postback huge pages:sys.webforms.pagerequestmanagerservererrorexception error code:12030
I use ajax and updatepanel, I have a problem that one page sometimes display an error: sys.webforms.pagerequestmanagerservererrorexception error code:12030,even I just click an button (the button don't process any thing, just post back),but sometimes it is ok.
I use httpwatch to check it, found the postback data about 100kb, if I open other same pages with small data than above page, all is ok, if the error come from this? i.e. ajax don't support huge data to postback?
anyone can tell me why and how to resolve it?
I use httpwatch to check it, found the postback data about 100kb, if I open other same pages with small data than above page, all is ok, if the error come from this? i.e. ajax don't support huge data to postback?
anyone can tell me why and how to resolve it?
Friday, September 19, 2008
General network error.
Microsoft OLE DB Provider for SQL Server error '80004005'
[DBNETLIB][ConnectionRead (recv()).]General network error. Check your network documentation.
/default.asp, line 107
what is this error??
Auto-Display of Syntax Errors in C#
Is there a way in C# to have your syntax errors get marked as soon as you make them, instead of having to build first? VB does this. It underlines them with red squigglies as soon as you type in a variable that doesn't exist yet, for example. But so far I haven't figured out how to make the IDE do the same thing when the language is C#.
Subscribe to:
Comments (Atom)