Summary of online, two very basic questions answers.

Question 1 answer:

After upgrading a server into a domain controller, install the ASP.NET, after configuring IIS, find that the * .aspx file cannot be run, each run tells me the internal error of the server, and will add the following in the system application log 2 errors

The ASPNET_WP.EXE failed because the username and / or password provided in the ProcESSModel section of the configuration file is invalid.

ASPNET_WP.EXE is not started. Failed HRESULT: 80004005

* .Asp files are running normally, please guideline, what is the problem?

There are several ways to solve,

One of the fastest but unsafe is: Change the Machine.config file, which is located in C: /Winnt/Microsoft.net/ Framework / V1.0.3705 (ASP.NET 1.0 is like this, if your version is 1.1, file Candle Name Different) / config /, set the properties of the username in one component to System, just because it is the default setting to Machine,

So the user name visited ASP.NET is ASPNET, and this account is a local account, and the account we log in is the account of the domain controller, not the account of the local machine, which causes ASPNET_WP.EXE to find a local localmachinename / The ASPNET account cannot be started.

This method I experimentally verified the above situation. But it is unsafe, but when you release the ASP.NET web page, the browsing user is a System property in your domain, which will bring security hidden dangers. Best way Just, it is also recommended by Microsoft. Add an ASPNET account to your domain to set the appropriate permissions without changing the machine.config file.

solution

To resolve this issue, use one of the following methods: • Create a weak account with the correct permissions, then configure the section of the Machine.config file to use the account. • Set the username property to System in the section of the Machine.config file. • Configure the section of the Machine.config file to use the administrator account. Note: In ASP.NET 1.1, the ASPNET's process identifies IWAM_MACHINENAME, so there is no such problem.

Note: If the ASP.NET application is allowed to run as a System or administrator account, it will bring serious security issues. If any of these alternatives, the code running in the ASPNET_WP.EXE process will have the right to access domain controllers and domain settings. The executable starting from the ASPNET_WP.EXE process runs in the same context, and they also have access to domain controllers.

Therefore, Microsoft recommends using the first alternative method. To use the first alternative, follow these steps: 1. Create a user account called ASPUSER on your computer and add this account to the user group.

Note: This account can also be used if you change the password of the ASPNET account created by .NET Framework. You must know the password of this account because you need to add this password to the section in the later step. 2. Grant the ASPUSER or ASPNET account "as a batch job login" user permission. Make sure this change appears in the Local Security Policy settings.

Note: To grant this account "as a batch job login" user permission, you may have to grant this user permission in each of the following security policies (starting from the Control Panel / Management Tool):

• Domain Controller Security Policy • Domain Security Policy • Local Security Policy

Note: You may have to restart the server so that these changes take effect. 3. Make sure that the ASPUSER or ASPNET account has the right to access all directories and files necessary for the ASPNET_WP.exe process and provide services for the ASP.NET page. For additional information about what permissions that must be granted this account, click the article number below to view the article in the Microsoft Knowledge Base: 317012 Info: ASP.NET and Request ID 4. Open the Machine.config file. The path of this file is:% systemroot% / Microsoft.Net / Framework / V1.0.3705 / Config. 5. In the section of the Machine.config file, change the username and password properties to the name and password of your account you created in the first step. For example: username = "domainname / aspuser" password = "ASPUSERPASSWORD" 6. Save the changes to the Machine.config file. Question 2 answer:

After VB.NET, how to pack production installations

No .: QA004467 Establishment date: October 17, 2001 Last modified Date: July 26, 2002 Category:

Visual Basic - Production installer http://www.china-askpro.com/vbasic20.shtml

NOVA: Operating System: Windows2000 Advented Server Programming Tools: VB.NET Question: Hello! I am learning VB.NET programming, my problem is how to pack the production program installation wizard after the birth, just like VB6. Level: Intermediate

Reply:

You can select "Install and Deploy Project" when you choose to create a new project, and select Install Wizard in the dialog. It is best to open your VB.NET solution before building a new project, so you can choose "Add to Solution" when you select a file name for the new project. The advantage of this is that more prompts will be obtained in the wizard. There are not many steps in the wizard, and the VB6 is almost, and it will be done according to the prompt. There is a significant difference that does not include the establishment of a shortcut in this wizard. Establishing a shortcut job is set in the properties window of the newly established installation and deployment project. VB.NET established projects are based on Windows Installer's .msi files, relatively large. If you add a file of Windows Installer, approximately 8m. There is also a need to distribute the .NET frame file DotNetfx.exe, approximately 20m.