The re-toss of IIS publishing Web application

There have been many published programs in recent months that have encountered problems that could not be accessed after the various IIS publishing Web programs. Originally thought to all kinds of problems have been touched almost, but today for a problem toss a big day. The specific process is as follows:

To publish the Web application on a server2008 R2 64-bit system, the application pool is set to:. NET 4.0 Classic mode, and start 32-bit application is set to True. This is based on previous experience, set, and often works. But today we are jumping out of such a mistake:

Based on past experience, this problem is done:

"Cause: Different development environments and deployment environments (System 64bit and system 32bit)Workaround: IIS application Pool Select the name of the program pool you are using, right-click Advanced Settings General, enable the 32-bit application, and change to true. " now that the 32-bit application has been started, it doesn't make sense to make the mistake, so I think I'll check all the libraries and sites in VS and see if the target platform is X86 (the site can't set the target platform when it's generated), and then regenerate it again. Again, it's the same problem. Baisibuxie, tried many times; a Web application that was previously published successfully was configured to not enable 32-bit applications; The following error occurs when you think of the second method, set all target platforms to any CPU in VS, and then do not enable 32-bit applications: Online provides a way to generate <machinekey> and then configure it in Web Config. The blog of "Winter Sunshine" quoted by Bo friends: " machinekey Generation Method

Open the following URL: http://www.aspnetresources.com/tools/keycreator.aspx

Click: Generated

Generated machinekey:

MachineKey

<machinekey
Validationkey= " 86b6275ba31d3d713e41388692fca68f7d20269411345aa1c17a7386dacc9c46e7ce5f97f556f3cf0a07159659e2706b77731779d2da4b53bc47bffd4 Fd48a54 "
decryptionkey= "9421e53e196bb56db11b9c25197a2ad470638efbc604ac74cd29dbbcf79d6046"
validation= "SHA1"
decryption= "AES"
/>

How to use machinekey:

Add machinekey to <system.web></system.web> between Web. config files

The role of machinekey:

1. The encryption and decryption of the cookie data when ASP. NET uses forms authentication. To make sure that this part of the data is not tampered with
2. ViewState encryption and decryption of data. To ensure that this part of the data is not tampered with.
3. The session state identity is validated when using an out-of-process session (out-of-process session).

For more detailed information, please refer to:

http://msdn.microsoft.com/zh-cn/library/ms998288 (en-us). aspx

" after the implementation of this method, it is still wrong to find. Find the Niang again, the problem to be solved: http://www.iwms.net/td7397.aspx Above is the problem solving process, there are many do not understand the place, are based on the online approach to try one by one. More research on IIS is needed later on.