An Unexpected Error Has Occurred. Sharepoint Web Parts Maintenance Page
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeOnline20132010Other VersionsRelated ProductsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Web Parts Maintenance Page: An
An Unexpected Error Has Occurred Sharepoint 2010
unexpected error has occurred. SharePoint > SharePoint Legacy Versions - Setup, an unexpected error has occurred sharepoint 2010 new site collection Upgrade, Administration and Operations Question 0 Sign in to vote When I try to access any
An Unexpected Error Has Occurred Sharepoint 2013
site, document library or any other web part, following error page appeared: "An unexpected error has occurred. Web Parts Maintenance Page: If you have permission, you can use an unexpected error has occurred sharepoint 2007 this page to temporarily close Web Parts or remove personal settings. For more information, contact your site administrator. Troubleshoot issues with Windows SharePoint Services. " This is happening on all sites on the server :(Any ideas? Tuesday, January 06, 2009 11:18 PM Answers 1 Sign in to vote Hello, Please try the following method: an unexpected error has occurred sharepoint 2013 central administration 1. Open web.config file of current web application 2. Change the trust level from WSS_Minimial to WSS_Medium 3. Run iisreset Then, see whether it helps. Regards,JerryXing-Bing Yu Marked as answer by malikfarhan Tuesday, January 13, 2009 12:43 AM Monday, January 12, 2009 5:24 AM 0 Sign in to vote Hrmm... Did anything change with the account? Password/permissions? I'd give the configuration wizard a go.Administrative Tools --> SharePoint Products and Technologies Configuration Wizard, next, yes, do not disconnect, next, no will continue to host, and then Next to kick it off. Your sites will be offline while it runs though, but I suspect this won't be a huge issue as they are already broken... Marked as answer by malikfarhan Tuesday, January 13, 2009 12:42 AM Wednesday, January 07, 2009 12:02 AM All replies 0 Sign in to vote What was the last thing that was done to the SharePoint server? Have you installed any web parts or add ons? You could t
for a quick overview of the site Help Center Detailed answers to
An Unexpected Error Has Occurred Sharepoint Import Spreadsheet
any questions you might have Meta Discuss the workings web part maintenance page error in sharepoint 2010 and policies of this site About Us Learn more about Stack Overflow the company Business
Web Part Maintenance Page Error In Sharepoint 2013
Learn more about hiring developers or posting ads with us SharePoint Questions Tags Users Badges Unanswered Ask Question _ SharePoint Stack Exchange is a https://social.technet.microsoft.com/Forums/sharepoint/en-US/a4e104a1-a295-488b-95dc-629b479a1583/web-parts-maintenance-page-an-unexpected-error-has-occurred?forum=sharepointadminlegacy question and answer site for SharePoint enthusiasts. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Web Part maintenance page: An unexpected error has occurred up http://sharepoint.stackexchange.com/questions/139233/web-part-maintenance-page-an-unexpected-error-has-occurred vote 1 down vote favorite In SharePoint 2013 page, under Page edit mode, when I try to add my custom Web Part, I got following error as shown in picture: Then I append ?contents=1 at the end of Page URL: http://mysite/default.aspx and deleted the corrupt Web Part and Page successfully renders. But when I again try to add web part, i got same error again. what is reason behind that error? As web part is working perfectly in development server but throwing this error on production? Any idea to fix this ULS Logs show this Error: System.Web.HttpUnhandledException' was thrown. ---> System.NullReferenceException: Object reference not set to an instance of an object. at WebPart.CreateChildControls() at System.Web.UI.Control.EnsureChildControls() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.Process
can use this page to temporarily close Web Parts or remove personal settings. For more information, contact your site administrator. Web parts maintenance page If you have permission, you can use this http://www.dotnetsharepoint.com/2013/09/web-parts-maintenance-page-if-you-have.html page to temporarily close Web Parts or remove personal settings. For more information, contact your site administrator. lakshmitulasi Jasti 22:24 1 Comment Errors&Solutions , SharePoint 2013 , SharePoint2010 Advertisements An unexpected error has occurred. Web parts maintenance page If you have permission, you can use this page to temporarily close Web Parts or remove personal settings. For more information, an unexpected contact your site administrator. I added visual web part in my VS2010. I written some code and deployed, once deploy successes. I am trying to open web part page URL. If faced this error as shown. My web part page url is http://SharePoint:14343/sites/Home/Pages/default.aspx Then add Web part page url will be http://SharePoint:14343/sites/Home/Pages/default.aspx?contents=1 Now you are able to delete that an unexpected error particular web part. Generally this issue will come because of our code errors,now we want to debug the code for that. Go to the web config navigation C:\inetpub\wwwroot\wss\VirtualDirectories\14343 Open the web file and find for call stack and customerror mode change call stack = "true" and customerror mode = "Off" Now we can get a beautiful error which we can able resolve our issue. Advertisements SHARE SHARE SHARE lakshmitulasi Jasti RELATED POSTS Blogger Comment Facebook Comment 1 comments: George Couch13 January 2016 at 23:03This is what I needed to solve the problem. I so appreciate it!ReplyDeleteAdd commentLoad more... Newer Post Older Post Home Subscribe to: Post Comments ( Atom ) Subscribe Via Email Subscribe to our newsletter to get the latest updates to your inbox. ;-) Your email address is safe with us! Popular Posts Backup and Restore SharePoint 2013 site collection using PowerShell If you want to take backup/restore your site collection in SharePoint, we can do with PowerShell Commands. Backup site collection in S... how to create rdlc report in c# windows