asp.net debugging Error Resolution collection (2) __.net

A server error in the "/webapplication1" application.
--------------------------------------------------------------------------------to the path "d:/windows/microsoft.net/ framework/v1.1.4322/temporary asp.net files/webapplication180d7be/b46d84c0 "Access was denied.

Description:An unhandled exception occurred during the execution of the current WEB request. Check the stack trace for more information about the error and where the error occurred in the code.

Exception Details:System.UnauthorizedAccessException: On the path "d:/windows/microsoft.net/framework/v1.1.4322/temporary asp.net Files/ Access to Webapplication180d7be/b46d84c0 "was denied.

ASP.net is not authorized to access the requested resource. Consider granting the ASP.NET request identity access to this resource. ASP.net has a base process identity that is used when the application has no impersonation (typically, on IIS 5, on IIS 6 for network services). If the application is being emulated, the identity will be anonymous (typically IUSR_machinename) or authenticated request users.

To grant ASP.net write access to a file, right-click the file in Explorer, select Properties, and then select the Security tab. Click Add to add the appropriate user or group. Highlight the ASP.net account, and select the box that corresponds to the required access rights.

Insufficient debugging permissions
Try:
By design, asp.net requires read, execute, and list access to the ASPNET account (Aspnet_wp.exe process account) on the root Web site or on any virtual directory. This is required so that asp.net can access the content file and can monitor file changes.
Solution
To add read, execute, and list access permissions for the ASPNET account on the root Web site or on any virtual directory, follow these steps:
In Windows Explorer, browse to the folder that contains the root Web site (c:/inetpub/wwwroot by default) or the virtual directory.
Right-click the folder, and then click Properties.
On the Security tab, click Add.
Type the computer name/aspnet (for example, on a computer named WebDev, type Webdev/aspnet), and then click OK.
The following ASPNET account permissions are allowed:
Read and Execute
List Folder Contents
Read

Click OK to close the Properties dialog box and save your changes.
Note: If the Everyone group or user group already has read access to the root Web site or virtual directory, you do not need to perform these steps.
-------
Add Iusr_youcomputername and ASPNET two users to c:/windows/microsoft.net/framework/v1.1.4322/temporary asp.net Files/ Access permissions for the WEBAPPLICATION1DD84B00/B065EEC7 directory, set to full access,
--------
Will asp.net the user (specifically what is not very clear:< can be viewed in the security-user/user group) to the directory
C:/windows/microsoft.net/framework/v1.1.4322/temporary asp.net Files
Permission to write or higher.

13system.reflection.targetinvocationexception: The target of the call has an exception. ---> system.unauthorizedaccessexception: Access Denied. ---the end of the inner exception stack trace---at System.RuntimeType.InvokeDispMethod (String name, BindingFlags invokeattr, Object target, object[) args, boolean[] byrefmodifiers, Int32 culture, string[] namedparameters) at System.RuntimeType.InvokeMember (String name , BindingFlags invokeattr, Binder Binder, Object target, object[] args, parametermodifier[] modifiers, CultureInfo culture , string[] namedparameters at System.Type.InvokeMember (String name, BindingFlags invokeattr, Binder Binder, Object targe T, object[] args at System.DirectoryServices.DirectoryEntry.Invoke (String methodname, object[] args) at Aspnetc.pubFunction.IISManager.Create (VirtualDirectory newdir) in F:/ziliao1/aspc/pubfunction/iismanager.cs:line 132

If you are using it under ASP.net, remember to add the
Otherwise, "Exception details: system.unauthorizedaccessexception: Deny Access" appears.

Enter user name and password when IIS accesses site

1.iis-> site-> Properties-> Directory Security-> authentication and access control-> enable anonymous access
2. I wonder if you have added this "Iusr_yourname" INTERNET Guest account! If not added it should be caused by this problem.
(In the Default Web site---Properties-----Directory Security-----Edit------Browse-----Advanced-----Find Now "to find this account, double-click Add)
3. Put your site files in the directory, the full change to everyone to try again first. What the upstairs said in general, the default is not wrong.
4 Add the folder permissions of the IIS directory to the IUSER_ machine name

"Visual Studio. NET has detected that the specified Web server is not running ASP.net version 1.1 ... "The solution to choose from the Great_domino Blog
keyword, Visual Studio. NET has detected that the specified Web server is not running the ASP.net version 1.1 ... "solution
Source

Yesterday colleague MM is debugging a. NET Web server with a "Visual Studio." NET has detected that the specified Web server is not running ASP.net version 1.1. The mistake, asked me to help do, had a long time, just to fix, what exactly is the problem

She deleted the "Default Web Site" in IIS. I created a new site, running normally, is unable to compile, the new is not, there is a 1.1 version error, the previous error is because the server used fixed IP, and the administrator will attribute the IP address to the specified IP address. Now it is also necessary to make a summary.

Try the following steps:

1. Of course, first of all, to determine whether the version is really installed 1.1, view the path c:/winnt/microsoft.net/framework/v1.1.4322

2. Also many people know, reinstall Aspnet_regiis, how to install, do not say much, online a lot.

3. Reboot IIS and restart the ASP.net service program

4. If your Web server uses a fixed IP: Make sure that your Internet Information service uses the "Default Web site" and that the IP address in its properties is "(All Unassigned)" Rather than the IP address you have specified. You can modify the name of the default Web site, but do not delete, once deleted, as long as new, the name is strictly "Default Web site" can also be restored

5. If your IE uses an agent, hook up Bypass proxy Server for local adresses

6. If you already have a Web site, please uninstall it, do not reinstall Vs.net, as long as you reinstall IIS.

7. If still not, that is really no way, then reload iis,framwork,.net, operating system bar

Finally, a security issue, try not to point IIS to the default path c:/inetpub/wwwroot this path is vulnerable to attack, it is best to point to a new path, and then delete the Wwwroot folder, you need to upload files, you must stop uploading. HTA "file, do a good job of access to the Web site, shielding the implementation of HTA files, do database backup work.

is a little experience in the work, for everyone's reference, less detours.

It's a bug, really.

1. Your Web server uses fixed IP: Make sure that your Internet Information service uses the "Default Web site" and that the IP address in its properties is "(All Unassigned)" Rather than the IP address you have specified. Then try again in return to Vs.net, which may be resolved.
2. When the above methods do not solve the problem, consider the solution in MSDN as follows:
Visual Studio. NET cannot determine if ASP.net version 1.1 is running on the WEB server computer. This error can occur in several different situations. Check to see if the following is the case:
A, make sure that the. NET Framework version 1.1 is installed on the WEB server computer. For more information, see Visual Studio. NET Software requirements.
b, if ASP.net is already installed on the WEB server computer, but you still experience this error, it may be a configuration issue. To correct a problematic installation or configuration, you can use the ASP.net utility named aspnet_regiis. This command-line utility can be found in a path similar to the following:
c:/windows/microsoft.net/framework/v1.1.nnnn/
where nnnn represents the four-bit build number. Look under the highest version number. Use the/I switch to run the utility:
aspnet_regiis/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.

Don't need it, under the vs.net of the program's vs.net tool vs.net command prompt
Input:
Aspnet_regiis-r

The problem will be solved.
Take a closer look at the meaning of Aspnet_regiis's parameters.
Query Parameters Aspnet_regiis/all
All the parameters are listed
---------------------------------------------
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.

Unspecified Error

Description:an unhandled exception occurred during the execution of the current Web request. Please review the "stack Trace for" Information about the error and where it originated in the code.

Exception Details:System.Runtime.InteropServices.COMException: Unspecified error

An error occurred while trying to run the project: Debugging could not be started on the WEB server. You do not have permission to debug this server.
Verify that you are a member of the Debugger Users group on the server.
1. Log in as Administrator.

2. Run the Computer management in the Administrator tools.

3. Select the Local Users and Groups/groups node.

4. Double-click the Debugger Users Group in the right pane.

5. Click the Add button in the Debugger Users Properties dialog box.

6. Type the user account and click OK.


The device is not ready. Description:An unhandled exception occurred during the execution of the current WEB request. Check the stack trace for more information about the error and where the error occurred in the code.

Exception Details:System.IO.IOException: The device is not ready.
Posted on 2006-03-23 11:15 dotnet Garden Reading (1843) Comments (1) Edit favorite References 

Favorites to 365Key categories: AspNet

Feedback private void Prepareconnection ()

{

String connstr=system.configuration.configurationsettings.appsettings["Connectionsqlserver"];

Connection=new SqlConnection (CONNSTR);

String Strsql= "select * from Questions";

Command = connection. CreateCommand ();

Command.commandtext= strSQL;

Command.commandtype=commandtype.text;

Adapter= New SqlDataAdapter ();

Adapter. SelectCommand = command;

CommandBuilder = new SqlCommandBuilder (adapter);

Adapter. Updatecommand=commandbuilder.getupdatecommand ();

Adapter. Deletecommand=commandbuilder.getdeletecommand ();

Adapter. Insertcommand=commandbuilder.getinsertcommand ();

}

Why it appears:

Dynamic SQL generation for UpdateCommand is not supported for SelectCommand that do not return any key column information.

Note: An unhandled exception occurred during the execution of the current WEB request. Check the stack trace for more information about the error and where the error occurred in the code.

Exception Details: system.invalidoperationexception: UpdateCommand dynamic SQL generation is not supported for SelectCommand that do not return any key column information.

SOURCE Error:

Line 39:adapter. SelectCommand = command;

Row 40:commandbuilder = new SqlCommandBuilder (adapter);

Line 41:adapter. Updatecommand=commandbuilder.getupdatecommand ();

Line 42:adapter. Deletecommand=commandbuilder.getdeletecommand ();