An Unexpected Error Has Occurred. Sharepoint 2007 Central Administration
Contents |
is invalid) ★★★★★★★★★★★★★★★ Christopher T. HaunJanuary 11, 20120 0 0 0 Problem Summary: SharePoint Administrators lost the ability to browse successfully to an unexpected error has occurred sharepoint 2013 central administration Central Admin on a SharePoint 2010 server Errors: 1)In the browser: An
An Unexpected Error Has Occurred Sharepoint 2010
Unexpected Error Occurred 2)In the ULS Log: w3wp.exe 0x15EC SharePoint Foundation Runtime Unexpected System.Runtime.InteropServices.COMException: The handle is invalid. an unexpected error has occurred sharepoint 2010 new site collection (Exception from HRESULT: 0x80070006 (E_HANDLE)) 2fce79ff-3aed-440c-b4f7-78fa5d7a10d5 3)Process Monitor: “BAD IMPERSONATION” Root Cause Application of a Group Policy to the OU that includes the WFE removed the IIS_IUSRS group from the an unexpected error has occurred sharepoint import spreadsheet local security policy on the server for the user right assignment of “Impersonate a client After Authentication.” The IIS_IUSRS group needs the ability to impersonate clients after authentication because this is how the SharePoint/IIS Application Pool impersonates the SharePoint Administrator who is trying to reach Central Admin. Recommended Solution: The local group IIS_IUSRS needs to be allowed to be
Sharepoint An Unexpected Error Has Occurred Web Parts Maintenance Page
listed in the Impersonate a Client After Authentication right. Please work with your Active Directory Administrator and/or Security teams to determine what needs to happen in Group Policy to make sure the Central Admin servers (or even all WFEs) have this. Applies to: SharePoint 2010 and IIS 7.0 References: KB 981949 shows that the IIS_IUSRS group is supposed to (by default) have the Impersonate right. http://support.microsoft.com/kb/981949 - Description of default permissions and user rights for IIS 7.0 in Windows Server 2008 http://learn.iis.net/page.aspx/140/understanding-built-in-user-and-group-accounts-in-iis/ - Understanding Built-In User and Group Accounts in IIS 7Understanding the New IIS_IUSRS Group Comments (0) Cancel reply Name * Email * Website Follow UsPopular TagsIIS SharePoint ASP.NET Performance Kerberos workflow authPersistNonNTLM latency WEBDAV IE8 MIME Internet Explorer Offloading TCP Chimney TOE Broadcom debugdiag Visual Studio TCPChimney Archives November 2014(1) October 2014(1) September 2014(1) July 2014(1) June 2014(3) May 2014(3) April 2014(3) March 2014(1) February 2014(3) All of 2014(18) All of 2013(18) All of 2012(5) All of 2010(2) All of 2009(5) All of 2008(5) Privacy & Cookies Terms of Use Trademarks © 2016 Microsoft
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more an unexpected error has occurred. sharepoint 2013 about Stack Overflow the company Business Learn more about hiring developers or posting sharepoint 2013 central administration unexpected error ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack
An Unexpected Error Has Occurred. Sharepoint 2010 Correlation Id
Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up An unexpected error has occurred up vote 1 down vote favorite https://blogs.msdn.microsoft.com/chaun/2012/01/11/sp2010-central-admin-an-unexpected-error-has-occurred-handle-is-invalid/ I have created an asp.net web application on my local machine and I am deploying it to sharepoint. For that I am refereing the following Deploying ASP.NET Web Applications in the Windows SharePoint Services 3.0 _layouts Folder [http://msdn.microsoft.com/en-us/library/cc297200.aspx] Its works perfect on my local machine but when I was trying to deploy the same on clients machine it was giving me the "An unexpected error has occurred." Error. The http://stackoverflow.com/questions/1997803/an-unexpected-error-has-occurred scenario is, There is not visual studio install on my clients machine so what I was doing is I simply copying my solution folder in 12'hives LAYOUT folder along with the bin folder. Then when I was try to access it by hitting the URL http://[machineName]/_layouts/[MyCustomFolder]/default.aspx it was giving me the error mention above. Can anyone help me to solve this issue..? Thanks in advance.. Sachin sharepoint moss wss share|improve this question asked Jan 4 '10 at 6:24 Sachin 3383830 We can just provide unknown answers for unexpected errors. Please add more log details etc. And note the SO is not a support site. Its for programming. But perhaps someone had the same experience may help. –Chathuranga Chandrasekara Jan 4 '10 at 6:29 add a comment| 3 Answers 3 active oldest votes up vote 5 down vote Unexpected error might be anything, You need to see what is the root cause of the Error, Open the Web.Config file of the IIS SharePoint WebSite Search for the CallStack and change it to CallStack="true" Search for the CustomError and change it to CustomError="Off" Browse the page you will get to know the actual issue that causes the error You yourself can rectify it , i
fresh MOSS install on Server 2003 SP2 for a development server. Just a complete install using NTLM and a SQL Server 2005 database https://sharepointnoob.wordpress.com/2009/06/03/an-unexpected-error-has-occurred/ 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 http://blogs.msmvps.com/obts/2006/11/06/moss-2007-quotan-unexpected-error-has-occurredquot-when-creating-mysite-serverfarm-option/ 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 unexpected error 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 an unexpected error 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 implement
Articles Short Views sisnedanac SPPS03_Tips Testing Toys Uncategorized Vista Stuff WUS XML-XSL Tips XSL Articles Archives March 2010 February 2010 December 2009 November 2009 December 2008 October 2008 September 2008 August 2008 December 2007 July 2007 June 2007 May 2007 April 2007 March 2007 February 2007 January 2007 December 2006 November 2006 October 2006 September 2006 June 2006 December 2005 November 2005 October 2005 September 2005 August 2005 July 2005 June 2005 May 2005 April 2005 March 2005 February 2005 January 2005 December 2004 November 2006 M T W T F S S « Oct Dec » 12345 6789101112 13141516171819 20212223242526 27282930 Meta Log in Entries RSS Comments RSS WordPress.org MOSS 2007: "An unexpected error has occurred" when creating MySite (serverfarm option) November 6th, 2006 by obts From: "Prem"Newsgroups: microsoft.public.sharepoint.portalserverSubject: MOSS 2007: "An unexpected error has occurred" when creating MySite (serverfarm option)Date: 5 Nov 2006 15:42:24 -0800 Scenario: Installation MOSS with option ‘serverfarm', Central Admin works fine, Creation top level site works fine, Creation MySite gives "an unexpected error has occurred". No entry in event viewer. I have tried to install a top level site plus MySite as seperate applications and seperate sites (with different port numbers) many many times, none were successful. Can someone please direct me to a step-by step setup of a top level collaboration site plus a Mysite? Note: I use MSSQL2005, so not the default installation, but the serverfarm option. PLEASE!! ************************************** From: "Prem"Newsgroups: microsoft.public.sharepoint.portalserverSubject: Re: MOSS 2007: "An unexpected error has occurred" when creating MySite (serverfarm option)Date: 5 Nov 2006 17:04:29 -0800 OK, I finally managed to do it: What i forgot, was to create a shared services server and setup MySite as shared services application. The error message has disappeared. I now have the following 6 sites visible in IIS: - Default Web Site (I use for Exchange 2007, gives trouble if shared with MOSS)- Sharepoint Central Administration v3- ToplevelPortal- SharedServices- MySite- OfficeServerWebServices ************************************** From: "S.S. Ahmed"