I am having a asp web application running through IIS...If i insert data in a form from my system..The application connects to SQL Server 2008 and insert data.. i am able to insert...if i do the same process through my network systems ..i am getting error as "500 - internal server error. there is a problem with the resource you are looking for, and it cannot be displayed"..How to overcome this ?
First, you will have to activate Detailed Server Errors (see Classic ASP on IIS7: refusing to send errors to browser on 500 Internal Server Error for instance), to see what causes the error.
It may be a DB error, but it could also be a script syntax error or something else. Classic ASP is not compiled, so even simple syntax errors show up only when the code is executed.
First check you could connect to SQl2008 successfully with the credentials you gave in your asp application.
Then check if the user has got permissions to insert data into the database.
This error usually comes up when either of the above cases is true.
good luck
Related
I am running an ASP.NET service under IIS on my dev box (Windows 10). I am posting to a localhost URL and I get a 403 back. Nothing too strange there.
However, when I attach to the app pool process and set a breakpoint (or look at my logs) there is no evidence that the service ever got called. I see logging done when the service initializes but nothing when the call happens.
I stopped the relevant application pool (which is v4.0, Integrated) and tried again. I got the expected 503 back so I know I have the right app pool but I am at a loss to find out what part of IIS (because it is not in my code) is returning a 403. I tried turning on Failed Request Logging for 403 which generated some output for the call but the logging provided no significant information.
How does one troubleshoot such a circumstance?
P.S. This code has worked fine before. I have debugged it many times w/o problems on the same machine.
I've got a problem that for a website I'm administering, users are getting a 500 error. It happens across the site in a number of random places, like performing an Ajax query, navigating from page to page, etc. In the IIS error request log, what I'm seeing is two errors, back-to-back: ASP_CLIENT_DISCONNECTED and ASP_LOG_ERROR. Users are reporting problems usually happen when they're navigating from page to page. The 500 error appears and it just sits there. If they get the error, they usually refresh and it goes away.
The chain of calls right before the error look like the following.
ISAPI_START
CALL_ISAPI_EXTENSION
ASP_START_REQUEST
ASP_NEW_SESSION_CREATED
ASP_QUEUE_REQUEST
ASP_DEQUEUE_REQUEST
ASP_CLIENT_DISCONNECTED
Error 17:46:48.254
ASP_LOG_ERROR
Error LineNumber="", ErrorCode="ASP 0147", Description="500 Server Error" 17:46:48.254
MODULE_SET_RESPONSE_ERROR_STATUS
ModuleName="IsapiModule", Notification="EXECUTE_REQUEST_HANDLER", HttpStatus="500", HttpReason="Server Error", HttpSubStatus="0", ErrorCode="The operation completed successfully. (0x0)", ConfigExceptionInfo=""
EDIT 0: I think that the key may lie in that ASP_NEW_SESSION_CREATED line. I don't have any hard evidence to support that, just a gut feeling.
A few more details about my environment, I'm using an Application Pool that is in Classic Mode using the .NET Framework v2.0.5.2707. As part of the web site, I have two web applications that use a .NET 4.0 Application Pool in Integrated mode. The web applications aren't being used at all so I don't think they come into play.
Any suggestions about how to approach this one are greatly appreciated.
mj
We found the answer. There was an Ajax request that was timing out on the server and causing the problem. Some of the other calls were indeed due to user impatience.
Hi I have been tasked with moving an asp application to a new server, however I receive the following error:
ADODB.Connection error '800a0e78'
Operation is not allowed when the object is closed.
I am not sure what i'm missing as I don't have much experience with asp. I have registered a dll file with windows moved the DB accross and scoured every forum I can find to look for similar issues, however they all say that there is a coding issue. The site has been running smoothly for 18 months on another server so I don't see how there could be any problem with the code. Thanks in advance.
The most likely cause if it was working previously, is that your connection isn't set up correctly. Perhaps the database is in a different location, perhaps it's using different credentials, perhaps a provider is missing, perhaps an ODBC connection is missing.
The reason you are seeing "operation is not allowed when the object is closed" is likely because there is some "on error resume" type code where your db connection code exists, which is transparently swallowing the connection errors. So the code continues thinking that the connection is open.
I wonder if refreshing page with runtime error will overload the web server. For example I did refreshed domain.com/default.asp?id=99999999999999999999999999999999999999999 page which generates following error:
Microsoft VBScript runtime error '800a000d'
Type mismatch: 'Cint'
/default.asp, line 9
This caused server not respond for all sites hosted on it or my IP was blocked for some time by the firewall.
It depends on what the rest of the code around that error looks like (which you can't see). You won't overload the server in the sense of DoS too many requests (flood) since those would be handled before the request gets to IIS to process on the server side.
But if the code where the page breaks does other processing based on that value it could crash IIS or the app pool. It could also be stuck waiting on a passed DB call and has to timeout before the server responds. It will either time out or reset itself and that is when you see the site functional again.
Either way the code or the website/server should be setup better to alleviate the problem. Hopefully the admins will figure that out when they investigate why the site keeps crashing due to your web hits ;)
Issue seems to be type casting. Try below steps.
Add this line on top of the page where you get this error:
"Option Explicit"
You can get more meaning ful error message:
This link provide details for each error message.
We've got a web system running SQL Server 2005 for the back end, and ASP.Net for the front end (using .net 2.0).
Every now and then, the system barfs out the error in the title: 'SQLOLEDB' failed with no error message available, result code: E_FAIL(0x80004005).
The web system runs just fine 24/7, and then every now and then will toss this out on a select or some such. I've tried re-running the exact select that throws the error, but (of course) it works fine when I do it. And, to answer the obvious follow-up question, no we haven't done any code changes or upgrades to speak of lately.
Has anyone ever run into this before? Nosing around on google seems to only turn up situations where Access has some kind of file issue (permissions, missing data file, etc.)
Firstly, it's probably not SQL Server throwing out the error, and if it is, it's probably not while running the SQL statement itself, but if it is, it's almost certainly going to be peculiar to a login that doesn't have permissions, not the SQL command itself.
The 0x80004005 error is a general permissions failure, and it can occur in just about anything, but it's most likely to be in another layer.
I've seen it in authentication when the account the application is running under does not have access to the network to open a connection to the SQL Server. The SQL Server never even sees the request, but the client will say that the server cannot be found.
If it's intermittent, that could point to an intermittent domain controller issue, but that would depend on how your Windows Servers and Active Directory are set up, and how your application is connecting to SQL Server.
To solve this one, your netadmins will need to really know their Windows logging functionality and track it down for you.