An Unexpected Error Has Occurred Moss 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 With Project Server 2007 being a WSS 3.0 application you may come across either of these an unexpected error has occurred sharepoint 2007 error messages. The Unexpected error can appear on web part pages, and the Unknown error sharepoint an unexpected error has occurred 2010 is more likely on pages without web parts. The two errors are really telling you the same thing - This page (or web part) sharepoint an unexpected error has occurred web parts maintenance page needed some data - but the 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
An Unexpected Error Has Occurred Sharepoint 2010 New Site Collection
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 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 an unexpected error has occurred sharepoint 2013 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 it is a web part page then go to the Web Part Maintenance and either reset the part - or remove it and then add it back again. This will have the effect of defaulting the web page settings and if the bad data happened to be beyond the "current tasks" range or other filter specific to the part this may get things working. This isn't a fix - just avoiding the bad stuff for now. If you have customized then try removing any additional custom fields or other added fields from the view. Again this isn't a fi
instead of "an unexpected error has occurred?"--read on, this post will describe how to do just that.I'm sure every SharePoint developer has run across an unexpected error has occurred sharepoint 2013 central administration the infamous "unexpected error:" So… All you have to do is look
An Unexpected Error Has Occurred Sharepoint Import Spreadsheet
in the extremely friendly ULS logs, conveniently located at: For SharePoint 2010:%Program Files%\Common Files\Microsoft Shared\Web Server Extensions\14\LOGSFor
An Unexpected Error Has Occurred Sharepoint 2010 Central Administration
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 https://blogs.msdn.microsoft.com/brismith/2007/03/23/an-unexpected-error-has-occurred-or-unknown-error-in-wss-3-0/ a few ULS readers available 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 http://dereksan.blogspot.com/2011/02/sharepoint-20072010an-unexpected-error.html 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... 4384d11b-0b4a-4164-ab5e-9643ab891e27In this particular case, I can see that I am using a control that requires Session State, but it's not enabled. Wouldn't it have been nice if instead of having to go through all of that log searching I could have just gotten a message like this:So, the first thing I do in my development environment is configure a few items in the web.config so that I get real error messages on the page. Please make sure that you do NOT use these settings in production, because aside from not wanting end users to see the hideous yellow and red error message
· March 17, 2012 I recently installed a new SharePoint Server 2010 Enterprise for a client. https://blog.zubairalexander.com/how-to-fix-the-error-an-unexpected-error-has-occured-when-you-try-to-configure-a-newly-created-ups-service/ I also installed a SQL Server 2008 R2 Standard. Both were installed on separate Windows Server 2008 R2 servers running in a virtual VMware environment. PROBLEM After I successfully created the User Profile Synchronization (UPS) application and started the service, everything looked good. Then I went to Manage service applications in Central Administration under Application Management an unexpected and clicked on the hyperlink for the newly created UPS application so I can configure Active Directory synchronization connection. Unfortunately, I received the following dreaded error. An unexpected error has occurred. SOLUTION Here are some of the actions I took. I am listing all the solutions I tried because some of them are most likely to fix an unexpected error your error. Reset IIS after UPS had been provisioned. This is the most common fix for the above error. Verify that in addition to all the other necessary services, the two Forefront Identity Manager services have started successfully. SharePoint Web Services Root application pool in IIS has started. Health Analyzer has no errors. Both UPS services in Services on Server have started. Recycle SharePoint Central Administration v4 application pool in IIS. Look for anything unusual on the SQL Server 2008 R2 server. Make sure the three UPS databases exist (Profile, Sync, and Social). Make sure the account you are logged in as, e.g. SP_Admin, is a member of both the Farm Administrators and the local administrators group on the SharePoint server per this KB article http://support.microsoft.com/kb/981229. Reboot the SharePoint server. Clear the file system cache per this KB article: http://support.microsoft.com/kb/939308. You will find the instructions on Chaitu Madala's blog much easier to follow. Stop the Windows SharePoint Services Timer service (Found in Windows Services) Navigate to the