asp.net Debugging Some Problems summary _ practical skills

I've been doing this all day yesterday, and we're almost done! , and never turn off the machine again, because of the main idea, almost all of the net installation, debugging problems are I met, fortunately, I recorded him one by one, at the same time, in CSDN find some relevant solutions, do not dare to enjoy, for everyone to learn and exchange.

The cause is this, when the machine run IE suspended animation, I use the bad, on the apart hot start, the result is an accident.

reopen is vs2003.net inside is doing project, a long time no response, the machine became unusually slow, of course, out of professional sensitivity, immediately came to a ctrl+alt+del, this bad, CPU occupancy 100%, has been high, running IE, no response. First instinct, is it a trick?

Speed first, shutdown restart, immediately open KV2006 genuine anti-virus software, killed, and nearly 2 hours of torture, my machine, a cancer of the shadow is not (absolutely no pornography, I am five good youth)! Another ctrl+del+alt, look at the task Manager, see if there is an "alien" invasion of our territory, on Baidu to see Windows this task Manager comparison of water, so I went to the next one is said to be more drag aports to carry out process analysis, At first it was suspected that Svshost.exe had been raped! (A lot of articles said Win2000 only 2 this dongdong, and I walked out of three), put him close off, CPU or 100%, a process is closed, the result is the same.----The first possibility: the possibility of the machine is excluded!


Because there is no hint at first, but the CPU is tortured, but open vs2003 normal, I try to open other items incredibly normal! is my program out of the question? Apart, get yesterday's backup program out (this is normal), rename the current source file, get the backup in (I often do this, no previous errors), restart, open project, the problem remains .... Second possibility: the possibility of a program problem is also excluded!


Is this how it's being tortured? A CSDN has been posted on the project, and there is no good solution to it. Always can't wait!

There are netizens said to use the agent to the Internet and caused this problem, I did not use the agent Internet! There are netizens say is not some BT and so on, such as the problem caused by the CPU resources, I apart on the negative, niche I never use BT electric Donkey, and so on, at first? There is a user posted to let me put the SMTP virtual server first off, and then start, I followed his method to try, or not AH! What about new projects? I did not think of this method, you can create a new project to the original code reference to the past on the line Ah! The mind flashed a thought, open vs2003.net, New project, KAO, finished, no movement, died. Another look at the Ctrl+alt+del, cpu100% did not say, a straight line is in front of my eyes continue to across ...

I'm starting to wonder if IIS is in trouble?? found that under IIS to open the original project is not, the CPU is also occupied 100%! anyway are going to die, do not engage in white do not engage, do not know. So, restart the machine, I put the original project when IIS automatically corresponding to the virtual directory deleted, while creating a different named Project, which has a new problem:
Unable to find script library:/aspnet_client/system-web/v1.14322/webuivalidation.js

The problem is not difficult, very good solution:
The method is:
Click start → run: c:\winnt\microsoft.net\framework\v1.14322\aspnet-regiis-c
Ok

This problem solved, and I think I should put the project now named the original project name, so that the original code again, should be able to solve it! Say less, act again---- The result! No, it's back to the original cpu100%.

Depressed, make oneself a bit wohuo! Shutdown, restart the 48th time, I opened the VsNet2003, despair, anyway, dead, dead also want to see how a dead law just go, I opened this project, and so he CPU run, see the final result is what! Snail-like running (The status bar has "open a Web server, such as text prompts) ..." After about 30 minutes (I drank two cups of tea), I jumped out of a dialog box:

Visual Studio cannot create or open an application because this computer is not running a Web server, start the Web server, and then continue with the next action

This is simply fart, my IIS is obviously open! In the case of cpu100%, I have the patience to reopen the IIS view and restart IIS. At the same time in another machine Baidu related information, some people said to: Wwwroot folder access permissions set to everyone, this did not play a role, because I this folder is originally shared out (of course, may be the issue of different). The method is:
Permission issues, you may asp.net that the user does not have write operations on Wwwroot.
Workaround: Try:
Control Panel--"Management tools--" Computer Management-"Local Users and groups
The ASPNET user is then added to the Administrators group.

After this torture, I simply restart the machine again, to see if there is any new adverse reactions vs2003.net, hey, it really happened.
A new error message.

The home directory of the IIS Default Web site; local Path setting

To "C:\Inetpub\wwwroot". On the local area network, the client can use "http://localhost/Mydir/index.aspx" access. In order to facilitate client access, I have IIS default

The home directory > local path of the site is set to "C:\Inetpub\wwwroot\Mydir". At this point, the client can use "http://localhost/index.aspx" access. However, I was

Vs.net 2003 development Environment when this project (MYWEB) is opened, the following issues occur if:

Unable to get the project file from the WEB server. The WEB project "MyWeb" could not be opened. File path "C:\Inetpub\wwwroot\Mydir" and URL

"Http://localhost/Mydir" does not match. The two need to map to the same server location.

HTTP Error 404:not Found

There are two other options:

What do you want to do:
1 retry using a different folder share path
2. Try to open the project through the FrontPage Server Extensions

I think that this problem should be a virtual path problem, the path to its hint, I opened IIS, found the default site path C:\Inetpub\wwwroot\, and my project path is also correct. Accidentally found that the CPU is not accounted for 100%, it seems the original problem is resolved, But the new problem comes out again, is not fold, first csdn the community to see if there is no similar problem, fortunately, a lot of methods;

Method 1. Enter iis-> Default Web site-> right-click "Properties"-> Directory Security-> authentication and access control-> edit-> Change your anonymous login to Administrator and enter the password

I tried it, it didn't work.

Method 2:: Reload IIS
Open the Windows Components wizard.
Click Application Server in Components, and then click Details.
In the Application Server dialog box, under Child components of the application server, click Internet Information Services (IIS), and then click Details.
In the Internet Information Services (IIS) dialog box, under Child components of Internet Information Services (IIS), do any of the following:
To add an optional component, select the check box next to the component you want to install.
To remove an optional component, clear the check box next to the component you want to delete.
Click OK until you return to the Windows Components wizard.
Click Next, and then click Finish.

I'll keep it for later.

Method 3: Select the File menu--> open items on the Web, and then locate the disk (such as E:\webfile) where you put the item, and then open the project with the. vbproj (CS). Note: Do not open. sln.
The next step is to regenerate the solution.
This I tried, it does not seem to work, because the new project is not good, the original can not open

That's how I solved it.
Method 4:
A:1. Open IIS Manager.

2. Right-click "Default Web Site" and select Properties.

3. Click "Http Header".

4. Click "MIME Types".

5. Click "New".

6.   In extension, enter ". tmp". (No quotes required)

7.   In the MIME type, enter "Temp". (No quotes required)


Alas, engaged for a long time, finally got out! Some mistakes in the vs.net2003 let us baffled, in order to let everyone in the face of these problems when some of the tricks, I have to take some common problems are found out, the dismissal is helpful to everyone.

problem One: Unable to create Web application
Source: http://dev.csdn.net/develop/article/19/19725.shtm

1. When the site home directory does not create the application:

Through the FP extension + virtual directory to establish the WebApp, the following steps:

(1), right-click the site---All Tasks--Configure Server Extensions

(2), create a virtual directory * * * * and configure it with the application

(3), create a Web project in VS, name is * * *

(4), through the FP extension to build the web



2, when the site home directory to create the application:

The first method--FP extension:

(1), right-click the site---All Tasks--Configure Server Extensions

(2), create a Web project in VS, name yourself

(3), through the FP extension to build the web

The second method--web sharing:

(1) Change the IP address to all unassigned in IIS

(2) Change the address to 127.0.0.1 or localhost



3. Try the following methods when you are not yet established:

(1) "Site"---right---properties---"All Tasks"---recalculate hyperlinks on the Web

Then, under Vs.net, the FrontPage Server Extensions are created



(2) indicates that you want to access the project files directly on the WEB server through file sharing, and you do not need to install the FrontPage Server extensions on that server.

When you install Visual Studio. NET, you create a VS Developers user group and grant the user group read/write permissions to the Inetpub\Wwwroot folder. Any user who wants to use a file share on a computer to create a WEB project needs to be added to the VS Developers user group. The new VS Developers Group does not have any members, so even users who install Visual Studio must manually add themselves to the group.

If you do not want Visual Studio to be installed on the server, you can create the VS Developers group by installing only the server components from the Visual Studio Setup program.

(3) under Win2003:

In Vs.net, in order to test the URL and UNC, VS. NET generates a. tmp file under the directory and then makes a request to the file via HTTP. However, in IIS 6, for security reasons, the TMP file is not registered, and by default, the block then generates an HTTP 404 error.

To resolve this issue, refer to the following methods:

1. Open IIS Manager.

2. Right-click "Default Web Site" and select Properties.

3. Click "Http Header".

4. Click "MIME Types".

5. Click "New".

6. In extension, enter ". tmp". (No quotes required)

7. In the MIME type, enter "Temp". (No quotes required)

There is also a workaround where you can use the following command line:

%SystemDrive%\inetpub\adminscripts\adsutil.vbs set W3svc/1/root/mimemap. tmp,temp

When you create a Web application, VS. NET needs to create a temporary file with a suffix named. tmp under the creation path.
When Vs.net creates a project, the project file is sought from the Web folder as HTTP, and temporary files are also sought. Because IIS does not set the. tmp file to a MIME type under some installation steps, IIS returns an unknown file type error to vs.net, which means that the file cannot be found. \ windows2003 So vs.net that your IIS path is set incorrectly.


problem Two: ASPX projects cannot be debugged
Causes and Solutions
1. A debugging process has been started (two projects are open at the same time and one is already being debugged): Only one can be started at the same time;
2, in the configuration file debug= "false": change to true;
3, the virtual directory does not establish an application (or empty name): In the Virtual directory Properties "Application" click to create
4, project configuration for release: Point Menu "Build"-Configuration, select "Debug"
5, "You do not debug the server permissions": Modify the security settings of IE, "automatically use the current username and password login"


problem Three: Automation server cannot create object

Causes and Solutions
1.: Modify the registration Form ([Hkey_local_machine\software\classes\clsid\{0d43fe01-f093-11cf-8940-00a0c9054228}\progid]
@= "Scripting.FileSystemObject"), change FileSystemObject to an arbitrary name

2. Run Regsvr32 Scrrun.dll


problem four: Unable to start debugging on the Web server
Causes and Solutions
Does the 1.Web application have web.config files? Does the Web.config file set the Debug property to True?
2. Are you a member of the Debugger Users (Debugger users) group?
3.IE Internet Options-> Security->intranet-> Custom Level-> User authenticated "automatically log on with current user and password


question five:
The Web server reported the following error: "http/1.1 Bad Request

Causes and Solutions
1. There are two IP addresses. So localhost error, change the IP address in IIS to "All Unassigned" on the line

2. The first step is to re-register asp.net in IIS and run the following command: Aspnet_regiis-i
Step two: Go to IIS Manager, change the "Default Web Site"-"Properties"-"Site" to "(All Unassigned)", and click "Web Service Extensions" to change "asp.net v1.1.4322" to "allow".


question six: Microsoft Visual Studio. NET 2003 cannot open an existing ASP.net 1.1 Web project in the following situations:? Set ASP.net 1.1 to "prohibit" in the Web service Extensions list.

and
In the WEB service Extensions list, set ASP.net 1.0 to allow.

and
The computer is running Microsoft Windows Server 2003.
When you try to create a new ASP.net 1.1 project, you may receive the following error message:

Visual Studio. NET has detected that the specified Web server was not running ASP.net version 1.1.You would be unable to run asp.net Web applications or services.

Causes and Solutions

Please change the status of ASP.net 1.1 to allow in the Web service Extensions list in IIS 6.0. To do this, follow these steps: 1. Click Start, point to Programs, and then click Control Panel.
2. Double-click Administrative Tools, and then double-click Internet Information Services (IIS).
3. Click Web Service Extensions.
4. In the details pane, click ASP.net v1.1.4322 in the Web service Extensions list.
5. Click Allow to change the status from "Prohibit" to "allow".

If your IIS is not a version of 6.0. You can use the following methods:
-Start-All Programs-microsoft Visual Studio. Net2003-visual Studio.NET tool-visual Studio. NET 2003 command prompt

After opening the CMD command window above, enter: aspnet_regiis/i


question seven: attempting to open a Web project, the Web server reports the following error: http/1.1 Internal Server Error

Causes and Solutions
1. Use the proxy to surf the internet
2.regsvr32 Script.dll
3. First step: First, use Add/Remove Programs, the IIS component FrontPage Extended service, reinstall again.
Step two: To Administration tools, Internet Options, default sites, right-key properties. The home directory. On the hook to write permission, click Create. OK
4. Run Regsvr32 Scrrun.dll

question eight:
Vs.net has detected that the established Web server is running a asp.net1.1 version, and you cannot run ASP.net Web applications or services
Reasons and Solutions:
1. Reasons: Delete the "Default Web Site" In IIS, create a new site of your own, run normally, you can't compile it, you can't build it, there's not a 1.1 version error, the previous error is because the server uses a fixed IP, and the administrator attributes the IP address to the specified IP address.
Solution: 1. Of course, first determine, whether the version is really installed 1.1, view the path C:\WINNT\Microsoft.NET\Framework\v1.1.4322, reinstall aspnet_regiis, determine your "Internet Information Services "The Default Web site" is used and the IP address in its properties is "(All Unassigned)" Instead of the IP address you have specified, IE uses the agent to hook up the Bypass proxy Server for the local adresses.
Another: The parameters of aspnet_regiis


Issue nine: HTTP redirection request failed
Reason: Whether to use forms validation in the program, modify the relevant validation settings inside the web.config


Issue 10: vs.net development asp.net new project prompts "Unable to establish a connection to the server
Problems with IIS
Run C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe-i


Issue 11: Error attempting to run Project: Cannot start debugging on the Web server. Failed to start ASP.net or ATL Server debugging
Explanatory notes
http://support.microsoft.com/?scid=kb;zh-cn;318465
Running in DOS command window
Enter winnt\microsoft.net\framework\v1.1.4322
CD C:\WINNT\Microsoft.NET\Framework\v1.1.4322
Execute aspnet_regiis.exe/i


Issue 12: VS 2003 error message when new project: VC package not available or not registered
To work around this problem, you need to run visual Studio. NET hotfix. This problem can be addressed more effectively because the hotfix enforces the registration of items that are not registered in the installer.

Follow these steps to run the hotfix:
In the beginning, point to Settings, click Control Panel, and then click Add/Remove Programs, click Visual Studio. NET in the list of listed installed programs, and then click Change/delete; click Visual Studio. NET Installation dialog box 1 2 3 items in the second item;
Click "Repair/Reload" and follow the on-screen instructions.
More information: Ways to reproduce the problem
To reproduce this problem, it's best to have two operating systems installed on separate partitions, and two Windows XP professional will do that.
1. Install visual Studio. NET under one operating system;
2. Under another operating system, visual Studio. NET, which changes the installation's default path during the installation process to match the path of the first installation. (Two installation results will be successful)
3, and then start the second installation of Visual Studio. NET (You'll find that this problem recurs).
This form of installation is never recommended, even if the two installation options are identical, and you will save disk space, but this approach has a great chance of potential problems. If a visual Studio. NET changes the file and registration options, and these changes are not recorded in another visual Studio. NET, resulting in the potential danger of unpredictable results.

In addition, if you reinstall the system after reinstalling Vs.net to the same directory before the reload system (did not delete the original file in this directory), there may be "VC package is not available or not registered" This error tip!

Issue 13: Error trying to run project: Unable to start debugging on the WEB server
Problems and Solutions:
1. Debug ASP.net project
Check to see if the project has a valid Web.config file, web.config whether the file sets "Debug" to "true", and whether the debug verb is associated with. aspx
2. Debugging an ISAPI Application
Debugging an ISAPI application requires special attention to setup steps. The general steps for debugging preparation include:

Create a solution for the server application with an option to run the service interactively.
Set permissions in the User Manager. You must log off and log on again for the permissions to take effect.
Stop and restart the service.

3
Step1:. Integrated Window Authentication
Right-click My Computer-> manage-> services and Applications-> Internet Information Services Manager
-> site-> Default Web site-> Properties-> Directory Security tab-> authentication and access control block-> "edit"-> Select Integrated Windows Authentication (for the WIN2003 system, Other systems are roughly the same)

Step2. After integrated authentication, the following Windows user accounts are used for anonymous users.
User name is machine name \IUSR_ machine name, password system is added automatically. This user belongs to the Guests user group and cannot be changed.
Built-in account for anonymous access to Internet information services

Step3. logged-in users belong to the Debuger group and adminstrator groups (debug permissions and Full control of files), and the ASPNET user is part of the Administrator group (Operation apsx file permissions)

Step4. Log on automatically using the current username and password in IE (log off again to be valid)
Tools-> "Internet Options"-> "Custom Level"-> "automatically log on with current username and password"

Step5. Check that the Keep HTTP connection check box is selected, if not, select.

STEP6:. No application Created
Control Panel--> Management tools-->internet Information Service--> Find your project
--> Property--"virtual directory option, there is a < application name, followed by a < Button",
To see if it is created or deleted, if it is created, click on it and the button will become deleted and then saved.


Issue 14: The Web server reports the following error. Unable to resolve server name and address
I query the relevant information, found that this is not a vs.net problem, but your system problems, there are cases: when the network connection is unblocked, this error will naturally disappear, of course, you first check your program in the web.config to see if there is an external IP address or URL, Also check to see if the database is connected to the extranet. And then look at the virtual path in the csproj file, if it's not wrong, it's your system.

Issue 15: Visual Studio. NET cannot create or open an application. Most likely the problem is that the required components are not installed on the local WEB server. Please run visual Studio. NET installer and Add Web development components

Reason:
The path to the virtual directory created in IIS is not the same as the real path in the project, so we can solve
Find the Csprojl.info in the project this file with the SLn file first, with notes open, view the first three lines of these two files, there must be a virtual directory path, first of all, we want to ensure that the two files in the path is the same. And then open IIS, It can be solved by creating a new virtual directory based on the path you have in Csproj.info and SLN.

Issue 16: Visual Studio. NET cannot create or open an application. The problem is most likely because the required components are not installed on the local Web local server. Please run visual Studio. NET installer and Add Web development components

Reason: Generally when you open a project from another machine or from another place to your own machine, this error occurs, mostly because it is not placed in the IIS default root directory, which means that you may not be able to set up a virtual directory that you can use, and of course there is no reference to the related component in the project.

The following are common methods found on the Web:


1. Verify that IIS is installed. One way to do this is to open Control Panel and choose Internet Services Manager. If IIS is installed, you will be able to use this utility to stop and start it.
If IIS is not installed, in Windows Control Panel, select Add or Remove Programs, and then select Add/Remove Windows components. In the list, select Internet Information Services (IIS) and continue with the installation. For more information, see Windows Help.

Security Note When you install IIS, it is strongly recommended that you ensure the security of your WEB server computer. For more information, see file webserver.htm that belongs to the installation document. The location of the file on the installation CD is disk1\setup\webserver.htm. After Visual Studio is installed, the file can also be found at the%install%\csetupmm\webserver.htm of the hard disk.
2. Install or reinstall the. NET Framework. Run the Visual Studio.NET installation and select option 1 "Windows Component Update."
Note If you are sure that the current version of the. NET Framework is installed on the WEB server computer, you can skip this step.
3. Open the Windows Run window, and then type the following to enable ASP. NET:
aspnet_regiis.exe/i
Prompts you to open the Command window directly from the correct directory of the command. From the Windows Start menu, point to Programs, Visual Studio. NET 2003, Visual Studio. NET Tools, and then select Visual Studio. NET command prompt. After the window is open, type aspnet_regiis/i.
4. Install the Visual Studio. NET server component.
A. Run the Visual Studio. NET installation again and select option 2 "Visual Studio. NET".
Tip You can run the installation from Control Panel by selecting Add or Remove Programs, selecting Microsoft Visual Studio. NET (The specific name varies slightly depending on the version and language you are installing), and then clicking Change/Remove.
B. Select Add or Remove Features.
C. Open the Server Components node and select Web development.
D. Click Update Now! ”
5. Perform a security lock on IIS, but then enable asp.net.
If you are using IIS 5.0 running on Windows 2000 or Windows XP, you can use the IIS Lockdown Tool (version 2.1).


Issue 17: The project you are trying to open is a local project and needs to be opened by specifying its file path

Workaround: Create a new project and add all the folders in your current project to the new project

Issue 18: "You cannot start a project with a class library output type directly. Go to the Debug tab under Configuration settings in the project properties setting to start an external program or start a URL, alternatively, you can add a non-library item referenced by this project to the solution and set it to start.
Reason: The solution contains two or more projects, no startup projects are set up, or unsupported files are set up for startup projects, can start chopping projects only Web projects, form projects, and console etc.
Solve:
Method 1: Menu-> Item-> Property output type to Windows application
Law 2: Solution Explorer-> right--> set startup Project

question 19:
Press F5 to run the ASP.net project in Vs.net 2003, and the dialog box with the error prompts appears as follows:
Error while trying to run project:unable to start debugging on the Web server. You don't have permission to debug the application. The URL for this project was in the Internet zone.

How to Solve:
This problem can not be an exception, the cause of this problem is likely to be the issue of permissions, when you encounter the situation can not be debugged, you can try to do the following two steps
1, IE browser-> Internet Options-> security-> Internet Customization level-> user authentication--> login: Automatically use current username and password
2. Right-click on the project in Solution Explorer, select Properties, select "Configure Properties"/"Debug" in the open window, and change "Enable ASP.net debugging" to "Ture"


Query parameters prompt under the vs.net command Aspnet_regiis/all of the program's Vs.net vs.net tool
For the time being so much, and then add to it, hope to be useful to everyone:


There are some MSDN related stuff, put it up for everyone, look at the problem when you have a little help
Web Project and source code management integration in Visual Studio. NET
Http://msdn.microsoft.com/library/chs/default.asp?url=/library/CHS/sccvs70 ... ntrolintegrationinvisualstudionet _convert.asp
Q: Cannot start debugging, catastrophic error (common errors that occur when debugging ASP.net applications in Visual Studio. NET)
a:http://support.microsoft.com/?id=306172

Problems and solutions of ASP.net debugging

The most common one, asp.net can not debug: The browser can start normally, and the code is also normal operation, but the breakpoint is invalid.

1. This is mainly because of the setting of IE browser, IE6 IE7 of the default advanced options, prohibit script debugging this does not tick, but IE8 disabled script debugging.

If you disable script debugging, it will appear above the situation, the browser can start normally, and the code is also normal operation, but the breakpoint is invalid.

In my impression, it seems that this is only related to JS debugging, and now found also related to ASP.net debugging.

2. Another possibility for this debugging error is that the ASP.net debugger is not used in the project's options. in property page = = "start option = =" ASP.net tick.