Troubleshoot issue with Microsoft SharePoint Foundation

Asked By Bobbye W Terry 10 points N/A Posted on - 11/08/2013

 

Hello,

I am the "administrator" of our organizations P1 plan, yet I am a novice at administering this type of thing.  Up until today we have had no issues.  All of a sudden when users try to open Excel spreadsheets using the "Edit in Browser" function on our Team Site they are intermittently getting the following error message. How can I avoid this annoying error message. Any suggestion would be helpful.

Error.

An unexpected error has occurred.

Troubleshoot issue with Microsoft SharePoint Foundation.

Correlation ID: 0fb5e8e5-22ce-44ee-a12c-c1fdec8ed020

Date and Time:4/25/2012 3:57:20

Go back to site.

Error

An unexpected error has occurred.

Troubleshoot issue with Microsoft SharePoint Foundation.

Correlation ID: 30c92a9c-9a94-70db-0d25-ec9aff3a06f7

Date and Time: 01/07/2013  06:22:36

Why Configure the managed metadata column to use the hidden Note field?

• Status: Open
• Question Views: 2266
• Answer Count: 2
• Vote Up 0 Vote Down

• Answer Accepted: Yes
• Question Category: Microsoft Others

Best Answer by Waters Magner

Go To Solution

Best Answer

Best Answer

Answered By Waters Magner 5 points N/A #172370

Troubleshoot issue with Microsoft SharePoint Foundation

This seems you have encountered SharePoint error message. You can download the ULS logs viewer to get into the detail of the problem. However, you can also update web.config call stack and then the custom error. Finally, you need to have a look at the resulted message. I feel you will then get an elaborate error message and finally solve your problem.

About Waters Magner

Questions
0

Answers
199

Best Answers
32

• Vote Up 0 Vote Down

• Posted on - 11/09/2013
• Question Category: Microsoft Others

Answered By points N/A #172372

Troubleshoot issue with Microsoft SharePoint Foundation

Hello,

Check out what exactly happened.

1. Go to your SharePoint site in IIS which is under “C:inetpub”.
2. Find out “web.config” and open it with Notepad.
3. Make the following changes:
   – set mode="Off" in customErrors tag

– set CallStack="true" in SafeMode tag

Now, refresh the page. It will show up the exact exception. Then, everything will be clear to fix this problem.

About

Questions
0

Answers
6

Best Answers
31531

• Vote Up 0 Vote Down

• Posted on - 05/29/2014
• Question Category: Microsoft Others