An Unexpected Error Has Occurred. Sharepoint 2007
Contents |
Online and Microsoft Planner An Unexpected Error Has Occurred, or Unknown Error in WSS 3.0 ★★★★★★★★★★★★★★★ Brian Smith - MSFTMarch 23, 200723 0 0 0
An Unexpected Error Has Occurred Sharepoint 2010
With Project Server 2007 being a WSS 3.0 application you may come an unexpected error has occurred sharepoint 2010 new site collection across either of these error messages. The Unexpected error can appear on web part pages, and the Unknown an unexpected error has occurred sharepoint 2013 error is more likely on pages without web parts. The two errors are really telling you the same thing - This page (or web part) needed some data - but the
An Unexpected Error Has Occurred Sharepoint 2013 Central Administration
data doesn't fit what I was expecting. If you get this then you probably need to raise a support call (see http://support.microsoft.com for options available to you) - or search through the KBs to see if there is a fix for the specific problem you are seeing (depending when you read this there may or may not be fixes up there right
An Unexpected Error Has Occurred Sharepoint Import Spreadsheet
now). But for some potential immediate relief from the problem here are a few tips that may at least get that page displaying again. The problem could occur on a number of different pages - but just to give some context lets talk about the "My Tasks" page. This will be displaying the "My Assignments" view by default, but in fact as this web part loads the SQLstored procedurebehind the scenes will be bringing in data for any of the views that a specific user has access to from the drop down of views. So even if "My Assignments" is the default - if you also havea custom view in the list that perhaps includes some custom fields then this data will also have been retrieved (and could be the culprit!). Soidentifying the bad data will help us with your support call and also hopefully get that page working again.Thinking in rows and columns - any customization will be changing the columns - and the rows will depend on things such as date ranges,tasks and assignments. So things you can try:- If
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: An unexpected error has occurred. SharePoint > SharePoint 2010 - Setup, Upgrade, Administration and Operations Question 0 Sign sharepoint an unexpected error has occurred web parts maintenance page in to vote Hi - I upgraded to SP2010. Two top-level sites
An Unexpected Error Has Occurred Sharepoint 2010 Central Administration
have this error message. but their subsites work. any ideas? no customizations. thanks Error An unexpected error has occurred. Troubleshoot an unexpected error has occurred. sharepoint 2010 correlation id issues with Microsoft SharePoint Foundation. Correlation ID: f5b9d2f1-15f1-4244-ba74-a07a418737b2 Date and Time: 2/20/2011 2:08:12 PM Sunday, February 20, 2011 7:24 PM Reply | Quote Answers 1 Sign in to vote great! now you can see https://blogs.msdn.microsoft.com/brismith/2007/03/23/an-unexpected-error-has-occurred-or-unknown-error-in-wss-3-0/ your errors on screen! :) Try to install templates and let us know if you would face anymore problems. Also FYI,http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/b9c46272-ef83-446d-917d-0050daee4fc1 Hope this helps you! N i T i N http://www.niteen.co.cc Marked as answer by XRS Monday, February 21, 2011 9:07 PM Monday, February 21, 2011 5:52 PM Reply | Quote All replies 0 Sign in to vote We are going to need a bit more information on https://social.technet.microsoft.com/Forums/en-US/640026d7-98d3-47d7-937a-ada1953cd9a2/an-unexpected-error-has-occurred?forum=sharepointadminprevious this one. Can you go into the ULS log and pull out the error plus a bit before and after that are associated with that Correlation ID? Sunday, February 20, 2011 9:42 PM Reply | Quote 0 Sign in to vote Ha good luck...don't you love Sharepoint? Try adding ?contents=1 to the end of your URL and see if there is a web part error. Did you do an inplace orout of placeupgrade? Did you run your pre-upgrade checks and make sure all your customizations and features were supported, etc? It could be a million different issues...the logs will be the best place to go. Monday, February 21, 2011 4:50 AM Reply | Quote 0 Sign in to vote yes, it is an inplace upgrade. 0 errors in preupgrade check. 0 errors during production configuration wizard. i did recreate a new web server farm with a new farm configuration, no luck. why is it so difficult to troubleshoot using these correlation IDs? i can't seem to find any in the ULS logs. we also have 0 customizations. great. strange this is that even though top-level site gives those errors, subsites work. e.g., http://sp2010/finance ---- gives error http://sp2010/finance/budget ----works fine adding ?conten
instead of "an unexpected error has occurred?"--read http://dereksan.blogspot.com/2011/02/sharepoint-20072010an-unexpected-error.html on, this post will describe how to do just that.I'm sure every SharePoint developer has run across the infamous "unexpected https://sharepointnoob.wordpress.com/2009/06/03/an-unexpected-error-has-occurred/ error:" So… All you have to do is look in the extremely friendly ULS logs, conveniently located at: For SharePoint an unexpected 2010:%Program Files%\Common Files\Microsoft Shared\Web Server Extensions\14\LOGSFor SharePoint 2007:%Program Files%\Common Files\Microsoft Shared\Web Server Extensions\12\LOGSAnd then, starting from the most recent file, start searching for the "Correlation ID" mentioned in the error. Note, there are quite a few ULS readers available an unexpected error that can make this a bit easier. However, also note, that, if you have multiple web front ends, it can be a task just figuring out which server logs to even look at.When I eventually found the right log file and searched through using that Correlation ID until I found an error, I discovered this:02/02/2011 13:53:00.91 w3wp.exe (0x1A80) 0x0464 SharePoint Foundation Runtime tkau Unexpected Microsoft.Reporting.WebForms.MissingReportServerConnectionInformationException: In remote mode, the Report Viewer control requires session state be enabled or Report Server connection information specified in the config file. atMicrosoft.Reporting.WebForms.ReportViewer.EnsureSessionOrConfig() at Microsoft.Reporting.WebForms.SessionKeepAliveOperation.CreateRequest(ReportViewer viewer) at Microsoft.Reporting.WebForms.ReportViewerClientScript.SetViewerInfo(ReportViewer viewer, String reportAreaId, String promptAreaRowId, String docMapAreaId, String fixedTableId, String promptSplitterId, String docMapSplitterId, String docMapHeaderOverflowId, String directionCacheId, String browserModeCacheId) at Microsoft.Reporting.WebForms.ReportViewer.OnPreRender(EventArgs e) at System.W..
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: Edit the web.config file in Notepad for the site Central Administration (C:\Inetpub\wwwroot\wss\VirtualDirectories\….is a number) Look for “CallStack” in the SafeMode section, change the value from false to true. Look for “CustomErrors” in System.Web section, change the value from On to Off. Save the file and close it. 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 part