I am using WindowsXP Pro and ASP. After installed the Frontpage 2003, each time when a script error occur, a "Just-In-Time Debugging" window popup, how to stop it ?
I have turn on "Disable script debugging", and turn off "Display a notification about every script error" in IE Option.
I've just inherited a web site. Someone's just asked me "what database table fields are looked at in a particular search?" You'd think this would be easy, but I'm looking at an ASP page that when printed out is >16 pages and has 20 include files. And no comments. It's just a series of scary logic. I really need to run this though in "debug mode", seeing what every variable is set to at each stage. If this were an ASP page calling a VB COM object I'd have no problems, however, I've no idea how to trap this in debug mode using standard ASP code. I know the debugger often start up when there's an error in the code, but there isn't. So, can anyone enlighten me as to how I can step into code using simple ASP (not .Net).
Need to start developing asp pages on windows 2003. I have not touch asp in few years. I would like to now how can I start of.
What should I use as a program to edit asp pages that have vbscript? I would like to debug too if possible But there is not really a debug in ASP pages.
my client took out hosting for their new site with WebFusion. On their shared package, they wouldn't offer ASP debugging, which basically made it extremely difficult to debug their complex CMS system on this server. We were told that upgrading to a VPS would solve this issue, but still a standard error message is showing instead of useful ASP error messages.
I've logged into remote desktop of the server, gone into IIS and gone to 'Web Sites > Right click > Properties > Home directory > Configuration > Debugging' and checked: 'Enable ASP Server side script debugging' and 'Enable ASP Client side script debugging' and 'Send detailed ASP error messages to client'.I've then restarted IIS.
It still gives me the same generic error message though.how to get this simple thing working?
just applying the basic MD5 function with a basic form. Here's the error i get
Microsoft VBScript runtime error '800a000d'
Type mismatch: 'm_l2Power'
Does anyone have a clue? i'm just applying the same function that is posted everywhere and applying it to a simple form that holds strings. i assume that passwords should always be strings. it's very basic yet i don't know why i'm getting this error.
When I try to debug ASP pages using Visual InterDev 6 I get the following Microsoft Development Environment dialog box that asks:
"Unable to set server into correct debugging state automatically. You may not be able to debug ASP pages. Do you want to continue launching the debugger?"
The prompts you have are Yes, No, and Help. If you click Yes it launches IE, but the ASP page doesn't break on the breakpoints I have set. Is there a setting that I need to modify somewhere? I'm using PWS in conjunction with VI to debug, before I push the ASP page out to our Intranet.
Before we upgraded our intranet server to Windows 2000, when I had an ASP error the page used to load up to the point where it was crashing out and then I would get an error message. This allowed me to response.write values to find out where the error was happening.
Since we upgraded, all I get now is a 'page cannot be displayed' with the error message on it. This means that I can't response.write values anymore and makes debugging a lot more difficult.
Is there a setting somewhere that controls how the message is displayed? Is this in IIS or is it a browser issue?
How to Debug ASP Pages from client machine? I have "windows 2000 server" installed on server machine and "windows 2000 Professional" on development machine, they are connected thru LAN. We use Visual Interdev to edit ASP Pages.
When I tried to open a project in VIDev, It asks me for servername, mode, I entered my servername and Local Mode, then it asks for domain/username and password. Now which password I should enter here?
Is there any tool for debugging ASP scripts? I wanted to do some tracing and check whether the execution of my statements and queries are in the correct order or not.
Is there a way we can debug ASP pop-up windows. The usual pages I am able to debug using the script-debugger from the IE and Visual Studio. The whole data for the popup is obtained from the xml files and I would like to debug the onchange events that occur in the popup.
I am used to Compilers. assemblers and a lot of other systems that at least give error numbers or some help in identifying and/or isolating syntax errors, undefined or multiply defined variables, etc etc.
When I make an error in an ASP program I only get a message saying that the program could not be executed.Can anyone recommend some good debugging tools or maybe an ASP code checker.
I've been using this installation of .NET for about 3 months without problems.After not using it for about ten days, I came back to my project and when I tried to run it with Debug>Start (F5), it comes up with this error.
"Error while trying to run project: Unable to start debugging ohn the web server. Could not start ASP.NET or ATL server debugging. Verify that ASP.NET or ATL server is correctly installed on the server."
Before I start de installing things,does anybody have any simple clues as to why this is happening?
I have asp page which is using activex exe component ...how can I debug from asp page to the component...I am using visual basic to create my activex component.
I am currently developing a website in ASP (VBScript) using MS Visual C#.NET IDE. I just create a new "ASP.NET Web Application" and point to my local webserver (IIS) of my website address.
Then I go through each file/folder and right-click, selecting "Include in project". The IDE is nice in that it checks, verifies id tags, etc. What am wondering is whether it's possible to debug my ASP website using the MS Visual Studio.NET's debugger.
I did a google search for 'debugging ASP VBScript' and got:
if there is a possibility to debug the ASP code like you can do in PHP? Just like in PHP I want to get a result which tells me whats wrong when the code is executed.
It has been years since I worked with ASP, having moved on to ASP.NET. However, I have just inherited a project adding some enhancements to an existing ASP site. What is the best tool to use for debugging ASP pages these days?
Is there a good way to debug ASP programs? The scenario, I have a function called GetRecordSet which is exactly what it does - gets record sets for various sql statements. But the problem is when there is a DB error I cannot identify where the error is coming from as all the error statement says is the error is in GetRecordSet. I use Dreamweaver as I had the iniial design configured on DW.
I've inherited some code from someone else, and with the move to a new server some problems have arisen. I've spent a while trying to nut them out, but I just can't seem to make progress and I'm hoping a fresh perspective from some other people will help.
First problem:
If you go here you will see a list of Bed and Breakfasts. If you click on "Azimuth Country Estate" (the third one down) you will see an example of a perfectly working setup. It opens in a popup window and everything appears nicely. Now click on "Bilinga Bed and Breakfast" (the fifth one down). You will see that halfway down the page in the popup window there is the following error:
Microsoft OLE DB Provider for ODBC Drivers error '80020009' Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done. /morbobge/popups/standard.asp, line 0
I looked this error up on Google and found that it has to do with Text fields not being the last fields drawn from the database. So I went back to the query and instead of saying "SELECT *" I explicitly selected each field in the database and made sure that the Text fields were last. Sadly this hasn't fixed the problem.
Any suggestions?
Second problem:
If you go here you will find what is supposed to be the events diary. Sadly, it cuts off at Day 1. I haven't been able to work out why.
I haven't posted any code for either of these problems, simply because it is all such a huge rambling mess that I have no idea which bits to post. Instead, I have attached a zip file with the two offending files in it, in the hope that some kind person will take a peep and help me out here
I have MS Visual Studio 2003 on Windows XP Pro. I have IIS running on this machine and I am trying to debug some existing code which has both ASP and ASP.NET components. When I try and launch the debugger from VS, I am told it can't because the project is of output type class library. The error indicates I should set the start action to start external program or start URL. I tried both of these and cannot seem to get the debugger to attach to the process. However, I can load the webpage and surf to an error which causes another session of VS to come up. Unfortunatly, the error is not one that I can debug because I can not get break points to work and the debugger will only come up when it hits the error. My start page is default.asp and I have tried setting a break point in it to no avail. How can I debug this script?
I installed the Microsoft Script Debugger 1.0.7295 and am trying to debug client side javascript. I m not able to set break points on the page; that option is disabled no matter how I open up the script debugger.I have tried opening the page in the following ways:
1) with the "debugger;" in the client-side java script 2) through IE menu 3) planting a javascript error in the client-side code, so the process must stop and ask "Do you want to debug...?
I have an ASP 3.0 page that contains an ActiveX control that I wrote in VC++ v6.0. Under Visual Interdev I can debug the ASP code just fine. However, when I get to an ASP line that references my ActiveX control the debugger does not go inside my C++ code allowing me to debug the ActiveX control.
If I load the ActiveX control project from VC++ with Internet Explorer as the debug executable I have the same problem. Break points in the ActiveX control's code are not respected. I know I'm compiling in Debug mode,how to get these breakpoints to be respected?
When I want to debug my web site written with ASP.NET using C# I get this error message:
unable to start debugging on the web server. unable to connect to web server. verify that the web server is running and that HTTP request is not block by firewall.
When I try run the project, I get an error as "unable to start debugging on the web server. the project is not configured to be debugged. " . I'm running it on Windows 2000. I've made sure that debug=true in the web.config file and the authentication mode = "Windows".
I also get an error when I try it on IE5 as :"Parser Error Message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS " .
I have Visual Studio 6.0 (Interdev only) installed on Windows XP Professional (IIS 5.1 platform). I have also installed Visual Studio 2005.
I want to debug ASP applications on IIS. Because debugging under non-administrative account doesn't work, I assigned my domain account into Administrators local group. I installed Inderdev Server and Remote machine debugging from Visual Studio 6 CD#2. I set appropriate user rights to Catalog Class and Machine Debug Manager components like in Q192011. I also applied changes described in Q312880.
I am ready to move my ASP web site onto a remote host. The problem is that when I use Terminal Services to see the host machine, the error does not show up. (I was told that debugging info is only sent to the 'console' session, no others). And the whole thing locks up when there is a server error. How can I see the server errors through Terminal Services?
I've been given an ASP site built, tested and working on IIS 5.1 to be hosted on IIS 6. I've gone through the process of enabling ASP, parent paths, and debugging in the IIS Management console. My first ASP works as expected, however, a link to a second gives me the error:
HTTP 500 - Internal server error
This is not a lot to go on, so my question is can i turn on debugging/error messages to give me more of a starter?
I'm facing some errors such as Type Mistmatch & Exception Occured in web application which has gone live. These errors are very rare and are not consistant in behaviour.
I would like to debug my web application right from login to find out as to what is reason for these errors. I have downloaded Windows Script Debugger but I'm not able to debug the asp pages at all. I'm not able to put a breakpoint in the asp pages. Even the keyword Stop is not working. Code:
I have asp pages running from a hosting server. In there I open a bunch of connection to an access database. When we ported over to win2k3, the site started going down, or hanged (with no response).
I am suspecting a set of possibilities: 1-we could have reached access max db connections, 2- we could have some leaking left-open connection that we are not closing 3- there might be some security restrictions on win2k3 that are blocking the site or it might be other reasons.
how to debug or troubleshoot this given that we don't own the hosting server (and we don't want to debug on it as well;). Are there some tools, or iis/asp options that we can use to trace down from where is comming the issue?