The values in the watch window are shown as Error when you debug with Visual Interdev 6.0

Article translations Article translations
Article ID: 833831 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

When you try to debug an application remotely from a client by using Microsoft Visual InterDev 6.0, the values in the watch window are shown as Error.

RESOLUTION

To resolve this behavior, follow these steps:

Note:You must configure Distributed Component Object Model (DCOM) Permissions both on the server computer and on the client computer.
  1. The server and the client must be in the same workgroup.
  2. The user name and the password that are used to access the application must be the same in both the computers and must be a member of the administrators group.

Run the application in the low isolation level on the server

Configure the Web application to run in the low isolation level on the server. To do this, follow these steps:
  1. Start Internet Information Services (IIS) Manager.
  2. Right-click the sample Web application that is named WebApplicationSample that you want to remotely debug, and then click Properties.
  3. In the WebApplicationSample Properties dialog box, on the Directory tab, click Low [IIS Process] in the Application Protection list, and then click OK.

Allow the client to attach to the Inetinfo.exe process

Configure the Web application on the server to allow the client to attach the Inetinfo.exe process. To do this, follow these steps:
  1. Start Internet Information Services Manager.
  2. Right-click the sample Web application that is named WebApplicationSample that you want to remotely debug, and then click Properties.
  3. In the WebApplicationSample Properties dialog box, on the Directory tab, click Configuration. The Application Configuration dialog box appears.
  4. In the Application Configuration dialog box, on the Debugging tab, click to select the Enable ASP server-side script debugging check box, and then click to select the Enable ASP client-side script debugging check box under the Debugging Flags section.
  5. Click OK to close the Application Configuration dialog box.
  6. Click OK to close the WebApplicationSample Properties dialog box.
  7. Reset IIS (if necessary).

Install components

Follow these steps:
  1. On the Web server, install the components from the VID_SS folder that is located on CD 2 of Microsoft Visual Studio 6.0.
  2. On the Web server, install the components from the SCRPT_SS folder that is located on CD 2 of Visual Studio 6.0.

Configure DCOM permissions

Windows 2000 Server

When the operating system on the computer is Microsoft Windows 2000 Server, you must configure DCOM permissions. To do this, follow these steps:
  1. Click Start, and then click Run.
  2. In the Run dialog box, type dcomcnfg.exe in the Open box, and then click OK.
  3. Click the Default Properties tab in the Distributed COM Configuration Properties dialog box.
  4. Click to select the Enable Distributed COM on this server check box, click Connect in the Default Authentication Level list, and then click Identify in the Default Impersonation Level list.
  5. Configure the Catalog Class. To do this, follow these steps:
    1. On the Applications tab of the Distributed COM Configuration Properties dialog box, click Catalog Class in the Applications list, and then double-click. The Catalog Class Properties dialog box appears.
    2. In the Catalog Class Properties dialog box, on the General tab, click Connect on the Authentication Level list.
    3. On the Security tab, click Use custom access permissions, and then click Edit.
    4. To debug, add the following users and groups, and then grant them the Allow Access user right:
      • System
      • Interactive
      • Administrators
      • Debugging account
    5. On the Security tab, click Use custom launch permissions, and then click Edit.
    6. To debug, add the following users and groups, and then grant them the Allow Launch user right:
      • System
      • Interactive
      • Administrators
      • Debugging account
    7. On the Security tab, click Use custom configuration permissions, and then click Edit.
    8. To debug, add the following users and groups, and then grant them the Full Control user right:
      • System
      • Interactive
      • Administrators
      • Debugging account
    9. Click the Identity tab.
    10. On the Identity tab, click The interactive user.
    11. Click OK to close the Catalog Class Properties dialog box.
  6. Configure the Machine Debug Manager. To do this, follow these steps:
    1. On the Applications tab of the Distributed COM Configuration Properties dialog box, click Machine Debug Manager in the Applications list, and then double-click Machine Debug Manager. The Machine Debug Manager Properties dialog box appears.
    2. On the General tab, click Connect in the Authentication Level list.
    3. Click the Security tab.
    4. On the Security tab, click Use custom access permissions, and then click Edit.
    5. To debug, add the following users and groups, and then grant them the Allow Access user right:
      • System
      • Interactive
      • Administrators
      • Debugging account
    6. On the Security tab, click Use custom launch permissions, and then click Edit.
    7. To debug, add the following users and groups, and then grant them the Allow Launch user right:
      • System
      • Interactive
      • Administrators
      • Debugging account
    8. On the Security tab, click Use custom configuration permissions, and then click Edit.
    9. To debug, add the following users and groups, and then grant them the Full Control user right:
      • System
      • Interactive
      • Administrators
      • Debugging account
    10. Click the Identity tab.
    11. On the Identity tab, click The interactive user.
    12. Click the Location tab.
    13. On the Location tab, click to select the Run application on this computer check box.
    14. Click OK to close the Machine Debug Manager Properties dialog box.
  7. To apply the settings, restart your computer.

Windows XP client or in Windows Server 2003

When the operating system on the computer is Microsoft Windows Server 2003 or Microsoft Windows XP client, you must configure DCOM permissions. To do this, follow these steps:
  1. Click Start, and then click Run.
  2. In the Run dialog box, type dcomcnfg.exe in the Open box, and then click OK.
  3. In the Component Services dialog box, expand Component Services, expand Computers, expand My Computer, and then expand DCOM Config.
  4. Configure the Machine Debug Manager. To do this, follow these steps:
    1. Right-click Machine Debug Manager under the DCOM Config section, and then click Properties.
    2. In the Machine Debug Manager Properties dialog box, on the General tab, click Connect in the Authentication Level list.
    3. On the Location tab, click to select Run application on this computer check box.
    4. On the Security tab, click Customize under Launch Permissions, and then click Edit.
    5. In the Launch Permissions dialog box, add the following users and groups, and then click OK:
      • System
      • Interactive
      • Administrators
      • Debugging account
    6. On the Security tab, under Access Permissions, click Customize, and then click Edit.
    7. In the Access Permissions dialog box, add the following users and groups, and then click OK:
      • System
      • Interactive
      • Administrators
      • Debugging account
    8. On the Security tab, click Customize under Configuration Permissions, and then click Edit.
    9. In the Change Configuration Permission dialog box, add the following users and groups, and then click OK:
      • System
      • Interactive
      • Administrators
      • Debugging account
    10. On the Identity tab, click The interactive user, and then click OK to close the Machine Debug Manager Properties dialog box.
  5. Configure Catalog Class. To do this, do as follows:
    1. Right-click Catalog Class under the DCOM Config section, and then click Properties.
    2. In the Catalog Class Properties dialog box, on the General tab, click Connect in the Authentication Level list.
    3. On the Security tab, click Customize under Launch Permissions, and then click Edit.
    4. In the Launch Permissions dialog box, add the following users and groups, and then click OK:
      • System
      • Interactive
      • Administrators
      • Debugging account
    5. On the Security tab, click Customize under Access Permissions, and then click Edit.
    6. In the Access Permissions dialog box, add the following users and groups, and then click OK:
      • System
      • Interactive
      • Administrators
      • Debugging account
    7. On the Security tab, click Customize under Configuration Permissions, and then click Edit.
    8. In the Change Configuration Permission dialog box, add the following users and groups, and then click OK:
      • System
      • Interactive
      • Administrators
      • Debugging account
    9. On the Identity tab, click The interactive user, and then click OK to close the Catalog Class Properties dialog box.
  6. To apply the settings, restart your computer.

Steps to manual debug: Attaching to a running process

  1. Start Visual InterDev.
  2. On the Debug menu, click Processes.
  3. In the Processes dialog box, type the name or the IP address of the computer to attach to. If you do not know the computer name, click Machine, and then use the Browse for Computer dialog box to locate the server where you want to debug.
  4. In the list of processes, click the Inetinfo.exe process, and then click Attach.

    Note If you want to debug client script in addition to server script, you must also attach to the Iexplore.exe process
  5. The process that you chose in step 4 appears in the Debugged Processes list. Close the Processes dialog box, and then use the Running Documents window to choose the ASP page to debug. You can step through scripts and test variables and expressions. However, to run a page, you must open it in your Web browser. Additionally, you cannot edit the pages that you are debugging.

Windows XP client

If the client that you are trying to debug is running Windows XP and if you are working in a workgroup instead of in a domain, you must follow these steps to debug the client:
  1. On the server, in DCOM permissions for the Machine Debug Manager, make sure that the identity is set to "this user" and that the user information that is entered is the account that you will use to log on to the Windows XP client computer. You do not have to be logged on to the server to debug.

    Note If you must make this change, you must restart the server for the changes to take effect.
  2. On the Windows XP client computer, enable the Guest user account. To do this, follow these steps:
    1. In Control Panel, double-click Administrative Tools.
    2. Double-click Computer Management.
    3. In the Computer Management window, open the Local Users and Groups folder. Double-click the Guest account.
    4. On the General tab, click to clear the Account is disabled check box.
  3. On the Windows XP client computer, follow these steps:
    1. In Control Panel, double-click Administrative Tools.
    2. Double-click Local Security Policy.
    3. In the Local Security Settings window, click the Local Policies folder, and then double-click User Rights Assignments.
    4. Open the policy that is named Deny access to this computer from the Network, and then remove the Guest account from the policy.

      Note You must restart the computer for this change to take effect.

STATUS

This behavior is by design.

REFERENCES

For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
244272 Description of Visual InterDev 6.0 debugging resources
258929 How to debug ASP applications manually against Windows 2000 Web Server
230507 You cannot find a project on Web server or to set server into correct debugging state
For more information, visit the following Microsoft Web sites:
http://technet2.microsoft.com/WindowsServer/en/library/4b9e6078-6b7d-4cc1-a927-77c1eab7c1341033.mspx?mfr=true

http://msdn2.microsoft.com/en-us/library/aa239576(VS.60).aspx

Properties

Article ID: 833831 - Last Review: April 29, 2007 - Revision: 5.3
APPLIES TO
  • Microsoft Visual Studio 6.0 Enterprise Edition
Keywords: 
kbserver kbclient kbdebug kbprb KB833831

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com