An unexpected error has occurred – SharePoint

We did a fresh MOSS install on Server 2003 SP2 for a development server. Just a complete install using NTLM and a SQL Server 2005 database server. The install ran fine as well as the Configuration Wizard but when it opened CentralAdmin after the configuration wizard ran I got the following:

Then I made the following changes since “An unexpected error has occurred” is not as descriptive as it could be:

1. Edit the web.config file in Notepad for the site Central Administration (C:\Inetpub\wwwroot\wss\VirtualDirectories\….is a number)
2. Look for “CallStack” in the SafeMode section, change the value from false to true.
3. Look for “CustomErrors” in System.Web section, change the value from On to Off.
4. Save the file and close it.
5. Execute IISReset.

Changing this will give you a more descriptive error so you can troubleshoot the issue easier. Once this was changed we did an IIS reset and went back to Central Admin to get this message:

If unreadable:

Server Error in ‘/’ Application

This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

I researched this error and found that it was a common issue with ASP.NET and you could do a workaround for it. Here is the link to the workaround or you can read the copied info below.

**Make a backup copy of your web.config before you edit it**

http://support.microsoft.com/kb/911722

Important These steps may increase your security risk. These steps may also make the computer or the network more vulnerable to attack by malicious users or by malicious software such as viruses. We recommend the process that this article describes to enable programs to operate as they are designed to or to implement specific program capabilities. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this process in your particular environment. If you decide to implement this process, take any appropriate additional steps to help protect the system. We recommend that you use this process only if you really require this process.

To work around this problem, change the configuration in the application-level Web.config file. Specify that ASP.NET use the Triple Data Encryption Standard (3DES) algorithm to process view state data. To do this, follow these steps:

1. In a text editor such as Notepad, open the application-level Web.config file.
2. In the Web.config file, locate the <system.web> section.
3. Add the following <machineKey> section to in the <system.web> section:

   <machineKey validationKey=”AutoGenerate,IsolateApps” decryptionKey=”AutoGenerate,IsolateApps” validation=”3DES” decryption=”3DES”/> 

4. **NOTE**If you just insert this key in the web.config it will not work. You must search for “machinekey” and paste over the original text to ensure it works.

5. **NOTE** If you copy this script directly into your web.config you will need to remove the double quotes and replace them or they will be in the wrong format for SharePoint to respond.

6. Save the Web.config file.

7. Restart the Microsoft Internet Information Services (IIS) service. To do this, run the following command at a command prompt: iisreset

Important Theoretically, the 3DES algorithm is less secure than the AES (Rijndael) algorithm. We recommend that you use the AES algorithm whenever possible to help secure your system. Important These steps may increase your security risk. These steps may also make the computer or the network more vulnerable to attack by malicious users or by malicious software such as viruses. We recommend the process that this article describes to enable programs to operate as they are designed to or to implement specific program capabilities. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this process in your particular environment. If you decide to implement this process, take any appropriate additional steps to help protect the system. We recommend that you use this process only if you really require this process.

**Note**  Once again, always always make a backup copy of your web.config before editing it. You may also have this same problem after you create your Shared Services Provider etc. You will have to make the same changes to the web.config for each separate IIS instance.

Advertisement