INFO: How to Read the Viddbg.exe Output

ID: Q237561

The information in this article applies to:

Microsoft Visual InterDev, version 6.0
on the following platforms: winnt

SUMMARY

When setting up server-side debugging in Visual Interdev you can use the Viddbg.exe logging tool to help determine what needs to be changed in order to configure debugging correctly. The tool can be downloaded from:

http://msdn.microsoft.com/library/techart/samples/5257.exe

The information contained in this article is to be used in conjunction with the "Microsoft Visual InterDev 6.0 Debugging" white paper to configure debugging correctly.

http://msdn.microsoft.com/library/techart/msdn_videbugging.htm

If you are setting up remote debugging make sure that you are a member of the administrators group on both the Web server and the client computer before running this tool. If you are setting up local debugging you will need to be an administrator on the client/server computer. This is a basic requirement to use Visual Interdev debugging.

You should run this tool on the Web server as well as the client computer if you are setting up remote debugging and on the client/server computer, and if you are setting up local server debugging. This article describes what the output should look like on the respective computers and what to look out for.

The information in this article applies to the output of Viddbg.exe both on the client and the server computer.

MORE INFORMATION

The following code is what the output should look like:


Visual Interdev Debugging Setup Verification - Server

Machine Name : MYMACHINENAME
Current User : MYDOMAIN\myusername

DCOM Permissions
--------------------------------------------------------
	Machine Debug Manager Launch permission list
		Access permitted to NT AUTHORITY\INTERACTIVE.
		Access permitted to NT AUTHORITY\SYSTEM.
		Access permitted to MYDOMAIN\myusername.
		Access permitted to MYMACHINENAME\IWAM_MYMACHINENAME.

	Machine Debug Manager Access permission list
		Access permitted to NT AUTHORITY\INTERACTIVE.
		Access permitted to NT AUTHORITY\SYSTEM.
		Access permitted to MYDOMAIN\myusername.
		Access permitted to MYMACHINENAME\IWAM_MYMACHINENAME.

	Catalog Class Launch permission list
		Access permitted to MYDOMAIN\myusername.
		Access permitted to BUILTIN\Administrators.
		Access permitted to NT AUTHORITY\INTERACTIVE.
		Access permitted to NT AUTHORITY\SYSTEM.
		Access permitted to MYMACHINENAME\IUSR_MYMACHINENAME.
		Access permitted to MYMACHINENAME\IWAM_MYMACHINENAME.

	Catalog Class Access permission list
		Access permitted to MYDOMAIN\myusername.
		Access permitted to NT AUTHORITY\SYSTEM.
		Access permitted to NT AUTHORITY\INTERACTIVE.
		Access permitted to MYMACHINENAME\IUSR_MYMACHINENAME.
		Access permitted to MYMACHINENAME\IWAM_MYMACHINENAME.

Debugging Options
--------------------------------------------------------
	Script options
		Attach to running programs	Enabled
		Just-In-Time debugging		Enabled
	Java options
		Attach to running programs	Enabled
		Just-In-Time debugging		Enabled

ASP.DLL Version Information
--------------------------------------------------------
	Location: 	C:\WINNT\System32\inetsrv\asp.dll
	FileVersion: 	4.02.0622
	File Size: 	330448 bytes

	VID Debugging requires 4.02.0622 (330448 bytes) or greater.

VID Server Components
--------------------------------------------------------
	Checking APPID Key
 		{Default Value} 	Catalog Class
 		DllSurrogate 			

	Checking ClassID Key
 		{Default Value} 	Catalog Class
 		AppID 		{6EB22881-8A19-11D0-81B6-00A0C9231C29}

If the Visual Interdev server side components are not installed on either the server or the client you will get the following warning in the output of the Viddbg.exe.

***VID Server Components are not installed correctly.***

You may also get the following error message when trying to debug without the Visual Interdev Server Components installed.

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 Visual Interdev server side components can be installed by running Setup.exe in the VID_ss directory on Visual Studio CD2 or Visual Interdev CD1.

The previous error may also happen if you have not setup the permissions for the computer debug manager and the catalog class correctly. The DCOM Permissions section of the Viddbg.exe identifies the permissions that are currently set up for both of these components. If the Remote Computer Debugging components are not installed the components can be installed by running Setup.exe from the scrpt_ss directory on the Visual Interdev CD1 or Visual Studio CD2.

If your debugger is not stopping at breakpoints in server-side code then the most probable cause is that you do not have a valid Asp.dll. The output of the Viddbg.exe identifies the version and size of your Asp.dll. Visual Interdev debugging requires an Asp.dll that is version 4.02.0622 or later. If the Asp.dll is version 4.02.0622 make sure that it is at least 330448 bytes. If you do not have a valid Asp.dll you will need to install Windows NT Service Pack 4 or later on the computer with the invalid Asp.dll.

REFERENCES

For more information, see the "Microsoft Visual InterDev 6.0 Debugging" white paper on the Microsoft Developer Network (MSDN) Online:

http://msdn.microsoft.com/library/techart/msdn_videbugging.htm

Please see the following articles in the Microsoft Knowledge Base for more information regarding the Visual InterDev Server Components:

Q220846 INFO: Redistributing the Visual InterDev 6.0 Server Components

Please see the following site for information on obtaining Service Packs for Windows NT:

http://www.microsoft.com/NTServer/all/downloads.asp

Additional query words: kbVisID600 kbScript kbDebug

Keywords : kbNTOS kbDSupport
Version : WINDOWS:6.0
Platform : WINDOWS
Issue type : kbinfo