Moss 2007 An Unexpected Error Has Occurred
Contents |
Online and Microsoft Planner An Unexpected Error Has Occurred, or Unknown Error in WSS 3.0 ★★★★★★★★★★★★★★★ Brian Smith - MSFTMarch 23, 200723 Share 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 2010 Site
error messages. The Unexpected error can appear on web part pages, and the Unknown error an unexpected error has occurred sharepoint 2010 central administration is more likely on pages without web parts. The two errors are really telling you the same thing - This page (or web part)
An Unexpected Error Has Occurred. Sharepoint 2010 Correlation Id
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 sharepoint 2010 export to excel an unexpected error has occurred 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 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 fix,
30, 20072 Share 0 0 Change the following values in your web.config file so that you can see what the actual error is:https://blogs.msdn.microsoft.com/brismith/2007/03/23/an-unexpected-error-has-occurred-or-unknown-error-in-wss-3-0/ "urn:schemas-microsoft-com:office:office" /> 1. Change CallStack="false" to CallStack="true" 2. Change
Registration Register for the EPMFAQ Forums Search This Site: Recent Posts Blog Move Project Conference 2009 Early Bird Registration Now Open! Infrastructure Update Intel Infrastructure Update Caveats for http://www.epmfaq.com/ssanderlin/project-server-2007/looking-behind-an-unexpected-error-has-occurred-messages Cost Resources Advice when Posting to the Project Server Support Newsgroups Popular Tagsadministrator http://www.techerator.com/2011/11/sharepoint-2007-troubleshooting-%E2%80%98unexpected-error%E2%80%99-while-editing-web-parts/ administratorpassword admpass businessdrivers businessneeds clearconfigurationcache configurationcache consultant contractor cubebuild cumulativeupdate database databasemaintenance dba demovpc epm2007demo error forums hotfix infrastructureupdates maintenance maintenanceplan maintenanceplans olap password permissionlevel permissions Project2007 projectworkspace queueerror reindex reindexing requirements role serviceaccount sharepointlist siteowner sp1 sql sqlprofiler strategicvision stsadm timerjob vpc workaroundsTopics/Categories .NET Administration Configuration Customization Database Administration Defects Development an unexpected EPM Consulting FAQ From The Field General HotFixes and Service Packs HowTo Implementation and Deployment MOSS 2007 Project 2007 Project Server 2007 PSI PWA Quick Tips Reporting SQL Analysis Services and OLAP SQL Reporting Services SQL Server SSP Support T-SQL Usability VBA WSS 3.0 Blogroll Andrew Connell Ben Howard Bill Raymond Brian Smith Christophe Fiessinger Faisal Masood gantthead Gord Schmidt Heather Solomon Jack Dahlgren Larry an unexpected error Duff Mark Schneider Microsoft Project Team Microsoft Project Users Group MSProjectExperts MSProjectExperts Group Blog Project Management Institute (PMI) Project Programmability Project Server Experts Projectified Rod Gill Scott Wagner Stephen Sanderlin Tony Zink Treb Gatte Archives December 2009 March 2009 July 2008 June 2008 May 2008 April 2008 March 2008 February 2008 January 2008 December 2007 Looking behind "An unexpected error has occurred" messages posted March 31st, 2008 by Stephen Sanderlin (2 votes, average: 5 out of 5) Loading ... At one time or another, almost everybody recieves an error while working in Project Server 2007's Project Web Access. By default, SharePoint (and therefore Project Server 2007) are configured to present what are known as "custom" errors. These are an inherent part of ASP.NET that allow developers to create friendly error pages to report errors rather than the stock ones provided by the .NET Framework. These pages are generally simplistic and often leave out a great deal of information, such as stack traces. The reason for these pages is chiefly to spare the user the gory details of whatever unhandled exception just occurred. Unfortunately, not every error is or can be logged. This caus
a comment One of the great things about SharePoint is the ability for non-technical users to update page content without the assistance of a development team. On the other hand, one of the terrible things about SharePoint is the ability for non-technical users to update page content without the assistance of a development team. I recently had a client that was experiencing difficulties when attempting to edit web parts on certain pages in their Intranet site, running on SharePoint 2007. For starters, clicking on the web part’s Edit menu would make the browser window scroll back to the top of the page, rather than opening the Edit menu as it should. No big deal. Who needs to edit a web part, anyway? If that wasn’t bad enough, any time they would drag and drop a web part to a different web part zone on the page, they would receive the wonderful “An unexpected error has occurred” error, preventing them from saving the changes to the page. To add some madness to the mayhem, the issues only occur in Internet Explorer. Since IE is the only browser officially supported by SharePoint 2007, SharePoint uses a dumbed-down page editing interface in other browsers. While much less user-friendly, the simplified interface would allow my client to successfully edit and move web parts without encountering errors. Troubleshooting the problem As my first step in troubleshooting the problem, I edited the web.config file, turning off Custom Errors and enabling the stack trace output. The hope was that this information would point me in the right direction to solving the problem. While the new error message is much less cryptic than “unexpected error”, it was rather unexpected and perplexing at first. “GUID should contain 32 digits with 4 dashes.” Gee, thanks! I know what a properly formatted GUID should look like, but a GUID is never used as user input on the page. Why is it passing in an invalid GUID to the SPWebPartManager? Shouldn’t SharePoint be able to keep track of these GUIDs on its own? This g