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?
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?
see this article
http://tutorials.aspfaq.com/8000xxxxx-errors/80004005-errors.html
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?
Ajax error if postback huge pages:sys.webforms.pagerequestmanagerservererrorexception error code:12030
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#
Syntax error: line 1 using Microsoft ASP.NET AJAX
Syntax error: line 1 using Microsoft ASP.NET AJAX
I read the last post from Rick Strahl about IE 7 Script Errors. Yes, I found this already on some sites, too, so I started to find the real issue.
For this I started the great Fiddler tool to analyse where the problem is. When you have Script Debugging enabled in your Internet Explorer settings you will get an alert when the script error appears. Don't click on this alert and have a look at the Fiddler output. When I open the example web page Rick is talking about it will always stop at the request for /atlasglob.axd. The web server will send an http error message 302 Found with an redirect to /Message-MSDN.htm?aspxerrorpath=/atlasglob.axd.
In Fiddler you can add JavaScript to handle requests more in detail. So I added two lines to prevent loading of this file:
After reloading the page no script error appears, and the page is currently working the same. If you look through all the requests you will see that the MSDN web page is already using Atlas.js. Is there a common problem with Microsoft ASP.NET AJAX when the atlasglob.axd could not be found? And why is it missing, a configuration errorif (oSession.url.indexOf("atlasglob.axd")>-1) {
oSession.oRequest.FailSession(403, "", "");
}