Skip to main content

James Milne

Go Search
Home
Downloads
 Help (new window) 
 

James Milne > Categories
Fixing Person.aspx vs UserDisp.aspx

 

A great article that outlines a number of fixes for this well known issue.

http://sharepoint.microsoft.com/blogs/LKuhn/Lists/Posts/Post.aspx?ID=47

Nice to see all the fixes listed in one place.

How to get more information from an “Unexpected Error Occurred”!

A common problem with troubleshooting SharePoint is getting past the "Unexpected Error Occurred" or the "Unknown Errors Occurred" messaged that get displayed from time to time. It would be nice if these messages displayed an error number or gave you a hint at what when wrong, but alas, they don't provide much information at all.

You can however turn off the custom Error messages and see some real detail by making a few changes to the Web.Config file.

  1. Open the Web.Config of the web application that is causing you problems. This should be located in "C:\InetPub\wwwroot\wss\virtualDirectories\<AppName><Port>\Web.config"
  2. Find the following settings listed in the "Before" Column and change them to the values listed in the "After" column:

Before

After

<SafeMode MaxControls="200" CallStack="false"

<SafeMode MaxControls="200" CallStack="True"

</httpHandlers>
<customErrors mode="On" />

</httpHandlers>
<customErrors mode="Off" />

<compilation batch="false" debug="false" />

<compilation batch="false" debug="True" />

 

After saving the Web.Config file the application pools should cycle, if not then you may need to do an "iisreset /noforce" from the command prompt.

Editing Audience Rule generates Error message: “An error has occurred while accessing SQL database or system resources. If this is the first time you have seen this message, please try again later.”

 

Problem

When trying to edit a rule on an Audience you are presented with the following error message:

"An error has occurred while accessing SQL database or system resources. If this is the first time you have seen this message, please try again later. If this problem persists, please contact your administrator."

 

Cause

The audience was made up of a number of rules that aggregated specific users into the audience. There were approximately 5 rules that referenced users specifically. The problem was caused due to the fact that some of the initial rules were referencing invalid users. These rules had become "invalid" because they referenced user entries that had been removed from the profile database. What seemed really odd was the fact that if you edit a rule further down the list you would receive the above "bogus" error message. This seemed like a real "red herring" because it has nothing to do with the current rule that you are trying to edit.

Solution

To resolve this issue you simply need to remove the invalid rules from the Audience rules list. Working out which rules are "invalid" can be a little e tricky. I just started at the top of the list and worked my way down the list and attempted to edit each entry. The Rules that could not be edited or saved I then deleted from the audience.