Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

PRB: Client-Side Debugging Causes Errors in Business Desk


View products that this article applies to.

This article was previously published under Q302854

↑ Back to the top


Symptoms

When you open a catalog in the Business Desk, the following error messages may occur:
MessageBox:
Unable to load Query Builder.
-and-
MessageBox:
The profile catalog could not be loaded. The catalog may be corrupt or missing.

URL: http://<server>/<sitebd>/catalogs/editor/QBProperties.asp
Error code: -1072896681
Reason: Invalid xml declaration.

Line 8, char 3

↑ Back to the top


Cause

This problem can occur when client-side debugging is enabled on the Business Desk site.

↑ Back to the top


Resolution

Disable client-side debugging on the Business Desk site. To do this:
  1. Open the Internet Services Manager.

    Open the properties for the Virtual Directory of the Business Desk site.

    On the Virtual Directory tab, click Configuration in the Application Settings section.

    On the App Debugging tab, click to uncheck the Enable ASP client-side script debugging option.

  2. Open the properties for the Virtual Directory of the Business Desk site.

    On the Virtual Directory tab, click Configuration in the Application Settings section.

    On the App Debugging tab, click to uncheck the Enable ASP client-side script debugging option.

  3. On the Virtual Directory tab, click Configuration in the Application Settings section.

    On the App Debugging tab, click to uncheck the Enable ASP client-side script debugging option.

  4. On the App Debugging tab, click to uncheck the Enable ASP client-side script debugging option.

↑ Back to the top


More information

Client-side debugging passes the following tag within the XML document:
<!-- METADATA TYPE="ASP_DEBUG_INFO" -->
				
This invalidates the XML. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
297995� PRB: ASP_DEBUG_INFO Tag Is Inserted into HTML When You Debug with Visual InterDev 6.0
Note that you may receive a slightly different set of errors if you have debugging enabled in the HTC files:
Site terms could not be loaded. The catalog may be corrupt or missing.
URL: http://<server>/<sitebd>/catalogs/editor/QBEnumeratedValues.asp
Reason: Invalid xml declaration.

Line 7,char 3: '<?xml version='1.0' encoding='windows-1252' ?>'
-and-
Unable to load Query Builder.
-and-
The profile catalog could not be loaded. The catalog may be corrupt or missing.
URL: http://<server>/<sitebd>/catalogs/editor/QBProperties.asp
Error code: -1072896681
Reason: Invalid xml declaration.

Line 8, char 3


Steps to Reproduce this Behavior

  1. Enable client-side and server-side debugging on the Business Desk site.

    Create a project to the Business Desk site by using Microsoft Visual InterDev.

    Open the Global.asa file in the Business Desk site, and then set the MSCSEnv environment variable to DEVELOPMENT.

    Set the BizDesk.asp file as the starting file.

    Start the debugger.

    You should be prompted with the following message:
    This project is not set up to enable ASP debugging. Would you like to enable ASP debugging on this project?
    Choose Yes if you want to debug .asp pages
    Choose No if you want to debug .htm pages only.
    Select Yes.

    You should then be prompted with credentials for debugging. Supply the proper credentials.

    Open a catalog in the Business Desk. The error messages occur.

    Disable client-side debugging in the Internet Services Manager for the site. The error does not occur.
  2. Create a project to the Business Desk site by using Microsoft Visual InterDev.

    Open the Global.asa file in the Business Desk site, and then set the MSCSEnv environment variable to DEVELOPMENT.

    Set the BizDesk.asp file as the starting file.

    Start the debugger.

    You should be prompted with the following message:
    This project is not set up to enable ASP debugging. Would you like to enable ASP debugging on this project?
    Choose Yes if you want to debug .asp pages
    Choose No if you want to debug .htm pages only.
    Select Yes.

    You should then be prompted with credentials for debugging. Supply the proper credentials.

    Open a catalog in the Business Desk. The error messages occur.

    Disable client-side debugging in the Internet Services Manager for the site. The error does not occur.
  3. Open the Global.asa file in the Business Desk site, and then set the MSCSEnv environment variable to DEVELOPMENT.

    Set the BizDesk.asp file as the starting file.

    Start the debugger.

    You should be prompted with the following message:
    This project is not set up to enable ASP debugging. Would you like to enable ASP debugging on this project?
    Choose Yes if you want to debug .asp pages
    Choose No if you want to debug .htm pages only.
    Select Yes.

    You should then be prompted with credentials for debugging. Supply the proper credentials.

    Open a catalog in the Business Desk. The error messages occur.

    Disable client-side debugging in the Internet Services Manager for the site. The error does not occur.
  4. Set the BizDesk.asp file as the starting file.

    Start the debugger.

    You should be prompted with the following message:
    This project is not set up to enable ASP debugging. Would you like to enable ASP debugging on this project?
    Choose Yes if you want to debug .asp pages
    Choose No if you want to debug .htm pages only.
    Select Yes.

    You should then be prompted with credentials for debugging. Supply the proper credentials.

    Open a catalog in the Business Desk. The error messages occur.

    Disable client-side debugging in the Internet Services Manager for the site. The error does not occur.
  5. Start the debugger.

    You should be prompted with the following message:
    This project is not set up to enable ASP debugging. Would you like to enable ASP debugging on this project?
    Choose Yes if you want to debug .asp pages
    Choose No if you want to debug .htm pages only.
    Select Yes.

    You should then be prompted with credentials for debugging. Supply the proper credentials.

    Open a catalog in the Business Desk. The error messages occur.

    Disable client-side debugging in the Internet Services Manager for the site. The error does not occur.
  6. You should be prompted with the following message:
    This project is not set up to enable ASP debugging. Would you like to enable ASP debugging on this project?
    Choose Yes if you want to debug .asp pages
    Choose No if you want to debug .htm pages only.
    Select Yes.

    You should then be prompted with credentials for debugging. Supply the proper credentials.

    Open a catalog in the Business Desk. The error messages occur.

    Disable client-side debugging in the Internet Services Manager for the site. The error does not occur.
  7. You should then be prompted with credentials for debugging. Supply the proper credentials.

    Open a catalog in the Business Desk. The error messages occur.

    Disable client-side debugging in the Internet Services Manager for the site. The error does not occur.
  8. Open a catalog in the Business Desk. The error messages occur.

    Disable client-side debugging in the Internet Services Manager for the site. The error does not occur.
  9. Disable client-side debugging in the Internet Services Manager for the site. The error does not occur.

↑ Back to the top


Keywords: KB302854, kbprb

↑ Back to the top

Article Info
Article ID : 302854
Revision : 2
Created on : 10/16/2002
Published on : 10/16/2002
Exists online : False
Views : 396