Synthetic Transaction Monitoring that you need for the day to day, which ensures your business website keeps running optimally, and that there is no downtime to impact your customer experience.
Course Of The Month
3 days, 9 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
ASP_DEBUG_INFO metafile
Posted on 2001-06-18
When I view the source on any asp page in one particular application I'm working on I see that the first several lines have this metafile inserted first which includes the term ASP_DEBUG_INFO followed by may lines of numbers. All of this is surrounded by regular html comment tags.
I didn't put this in on purpose but I'm thinking VI's debug tools did. It seems that when an error occurs in my asp pages the typical error page (the one which indicates what type of error and what line, etc.) doesn't show up. This "bugs" me since I rely heavily on the hack and detect method of debugging alot more than the debugging tools that come with VI. Probably because I am still learning those tools and am not too comfortable with them.
I want to learn how to get rid of these lines. Any help out there?
I didn't put this in on purpose but I'm thinking VI's debug tools did. It seems that when an error occurs in my asp pages the typical error page (the one which indicates what type of error and what line, etc.) doesn't show up. This "bugs" me since I rely heavily on the hack and detect method of debugging alot more than the debugging tools that come with VI. Probably because I am still learning those tools and am not too comfortable with them.
I want to learn how to get rid of these lines. Any help out there?
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
4
5 Comments
Following is an excerpt of a Microsoft page that holds the solution to this very problem... ;-)
SYMPTOMS
When you view or debug an Active Server Pages (ASP) page, you may notice that the following tag is inserted into the resultant HTML at the top of your page:
<!-- METADATA TYPE="ASP_DEBUG_INFO" -->
When this tag is inserted into the resultant HTML, it may cause problems in the following scenarios:
When you generate XML in your ASP page and send the XML to the client rather than HTML.
When you use the Response.BinaryWrite method to stream binary data to the client (for example, a Microsoft Excel document).
CAUSE
ASP sends down this tag when the following two conditions are met:
The Enable ASP client-side script debugging flag is enabled for the Web application.
An ASPCLIENTDEBUG cookie is present on the client that makes the request.
Typically, when you use automatic debugging with Visual InterDev 6.0, both of these conditions are met. The Visual InterDev debugger requires this tag at run time to automatically map breakpoints in the client script.
RESOLUTION
To resolve this problem, use one of the following methods.
Method 1
Disable the Enable ASP client-side script debugging flag as follows:
In the Internet Services Manager, right-click the Web application with which you are currently working, and then click Properties.
Click Configuration.
On the App Debugging tab, clear the Enable ASP client-side script debugging check box.
Method 2
Delete the ASPCLIENTDEBUG cookie from your client computer as follows:
On your computer, search for a file named username@applicationname*.
After you locate the file, delete it.
NOTE: If you need to debug in the above-mentioned scenarios, you must manually debug the application.
Cheers,
Max.
SYMPTOMS
When you view or debug an Active Server Pages (ASP) page, you may notice that the following tag is inserted into the resultant HTML at the top of your page:
<!-- METADATA TYPE="ASP_DEBUG_INFO" -->
When this tag is inserted into the resultant HTML, it may cause problems in the following scenarios:
When you generate XML in your ASP page and send the XML to the client rather than HTML.
When you use the Response.BinaryWrite method to stream binary data to the client (for example, a Microsoft Excel document).
CAUSE
ASP sends down this tag when the following two conditions are met:
The Enable ASP client-side script debugging flag is enabled for the Web application.
An ASPCLIENTDEBUG cookie is present on the client that makes the request.
Typically, when you use automatic debugging with Visual InterDev 6.0, both of these conditions are met. The Visual InterDev debugger requires this tag at run time to automatically map breakpoints in the client script.
RESOLUTION
To resolve this problem, use one of the following methods.
Method 1
Disable the Enable ASP client-side script debugging flag as follows:
In the Internet Services Manager, right-click the Web application with which you are currently working, and then click Properties.
Click Configuration.
On the App Debugging tab, clear the Enable ASP client-side script debugging check box.
Method 2
Delete the ASPCLIENTDEBUG cookie from your client computer as follows:
On your computer, search for a file named username@applicationname*.
After you locate the file, delete it.
NOTE: If you need to debug in the above-mentioned scenarios, you must manually debug the application.
Cheers,
Max.
Max:
Excellent work!!! Thanks for the info. I previously searched Microsoft Knowledge Base but came up empty. Would you please send me the article #?
Brian
Excellent work!!! Thanks for the info. I previously searched Microsoft Knowledge Base but came up empty. Would you please send me the article #?
Brian
I'll have a look at that again tomorrow...am now home and ready to go to sleep...thanks for the grade A...
Max.
Max.
See...I knew I had forgotten something and when I looked into my email when I came home I noticed this Good Answer email and remembered what I promissed...
Well..here it is...
http://support.microsoft.com/support/kb/articles/Q297/9/95.ASP
Cheers,
Max.
Well..here it is...
http://support.microsoft.com/support/kb/articles/Q297/9/95.ASP
Cheers,
Max.
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
This article provides a case study on how our local youth baseball league deployed a new website, including the platform selection, implementation and benefits to the league.
When setting up new project requests for our site, one of the most powerful tools our team has available to use is Axure (http://www.axure.com/). It’s a tool for creating software and web prototypes that can function and interact as if it were the a…
The purpose of this video is to demonstrate how to manually back up a WordPress Database.
This will be demonstrated using a Windows 8 PC. The Host used will be IPage.com
Log into your Hosting account. IPage will be used for demonstration : Locat…
The purpose of this video is to demonstrate how to reset a WordPress password if you are locked
out and cannot reset the password. A typical use would be if you cannot access the email to which
WordPress would send the password recovery email to…
Suggested Courses
Course of the Month3 days, 9 hours left to enroll
691 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.