Home > Unexpected Error > An Unexpected Error Has Occurred Sharepoint 2010 Central Administration

An Unexpected Error Has Occurred Sharepoint 2010 Central Administration


It is becoming a highly recommended CU and I too recommend this as a base level for SharePoint 2013. Add the following section to in the section:   **NOTE**If you just insert this key in the web.config it will not work. There is no such thing as "Office Server 2010." There was a Microsoft Office SharePoint Server (MOSS) 2007 but Microsoft SharePoint Server 2010 is not "Office Server 201o."

After I installed Look for anything unusual on the SQL Server 2008 R2 server. weblink

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 Also there is NO advanced option available in the SharePoint Products and Technologies wizard if on the original install you chose the "Complete - Install all components" option. Not really very helpful I know but thats all it says. No luck. https://social.technet.microsoft.com/Forums/sharepoint/en-US/7eb1a6f2-ff9e-47db-9fa4-1e59bfe34b10/sharepoint-central-administration-site-comes-up-with-unexpected-error?forum=sharepointadminlegacy

Sharepoint 2013 Central Administration Unexpected Error

To have more details you need to do:     1. Once you configure the EP in SharePoint after the initial creation of the web application it puts entries into the web.config file for the EP site. Save the Web.config file.

more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed I am listing all the solutions I tried because some of them are most likely to fix your error. This TechNet article explains this issue in detail and the need for this workaround: http://social.technet.microsoft.com/Forums/sharepoint/en-US/2d5919f9-a1f1-4517-8d61-cc1929474609/sharepoint-2013-site-collection-restore-is-now-rigid-and-inflexible-in-comparison-with-sharepoint?forum=sharepointgeneral#2d5919f9-a1f1-4517-8d61-cc1929474609 Known issues to be aware of when backing up site collections on SharePoint 2013 RTM When a backup This can be resolved by installing the April 2013 CU.

Its good to be aware of this especially when setting up maintenance windows. An Unexpected Error Has Occurred. Sharepoint 2013 Execute IISReset.   Then when you call the Central administration again you will have more details.   For us the error was:      The implementation is not part of Windows platform FIPS validated Please comment below if you have any questions on this blog and we would be happy to answer these for you. 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.

Recommended Solution: The local group IIS_IUSRS needs to be allowed to be listed in the Impersonate a Client After Authentication right. Sorry, something went wrong. Share it and empower the world. All rights reserved.

You may also like... 0 Configuring remote access client accounts for lockout December 26, 2005 2 What is Office Online Server and Why SharePoint 2016 Needs it?

An Unexpected Error Has Occurred. Sharepoint 2013

Therefore you could have two of these long upgrades ahead of you. You can reduce this time even further by using some third party scripts which you will find online. Sharepoint 2013 Central Administration Unexpected Error 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 An Unexpected Error Has Occurred. Changes To Your Data Cannot Be Saved Sweden 15.

Health Analyzer has no errors. have a peek at these guys Changing this will give you a more descriptive error so you can troubleshoot the issue easier. You cannot unlock the site in quotes in lock in central administration as you will find all the options are greyed out. System crash 3.

Delete all the XML configuration files in the GUID folder. Clear the file system cache per this KB article: http://support.microsoft.com/kb/939308. Browse other questions tagged sharepoint moss wss or ask your own question. check over here When I do Start-programs- Microsoft Office Server - Sharepoint 3.0 Central Administration it fires up the web and just says "Error" "an unexpected error has occurred".

Please also note you must install the March CU first before the April CU. 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. Netherlands 8.

These steps may also make the computer or the network more vulnerable to attack by malicious users or by malicious software such as viruses.

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. I have a server running SP 2010. In my case the server is called SP2007 and the domain is testdynamics, therefore the entry is SP2007.testdynamics.com?? Things to watch out for when upgrading from SharePoint 2010 Following an upgrade from SharePoint 2010 you may come across difficulty when using the create a new item form, edit form

Google and Bing have not been my friends on this, although some other posts over on msdn make me suspect it's possibly the web site name != netbios name, but I share|improve this answer answered Dec 31 '14 at 15:33 Tesfaye Hillo 1 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Its for programming. this content In may case, all the updates were already installed, except for the update 2560890.

To work around this problem, change the configuration in the application-level Web.config file. SOLUTION Here are some of the actions I took. To have more details you need to do:     1. SharePoint 2010 Search this Blog Archives September 2016 M T W T F S S « Aug 1234 567891011 12131415161718 19202122232425 2627282930 CategoriesCategories Select Category About this blog(4)

South Africa 11. Related 1 Comment Posted by Laura on June 3, 2009 in SharePoint Common Issues ← Reset Crawled Content in MOSS2007 Kerberos Authentication inSharePoint → One response to “An unexpected Check out this post for more info: http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=107Chris Caravajal MCTS SharePoint Help Free Windows Admin Tool Kit Click here and download it now August 4th, 2010 6:09am OK so I have Linked 0 SharePoint 2007 Custom Page Error Related 2Profile User DB error in WebPart1Why would clicking “View All Site Content” generate an error?0Sharepoint WSP Solutions and page URL's0WSPBuilder and Code behind

Thanks, Farhan August 2nd, 2010 5:07pm Thanks for the prompt response. 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 Free Windows Admin Tool Kit Click here and download it now August 6th, 2010 12:55pm This topic is archived. Canada 5.

In it, you'll get: The week's top questions and answers Important community announcements Questions that need answers see an example newsletter By subscribing, you agree to the privacy policy and terms I have a stand alone install of MOSS 3.0 on a Windows 2008 64 Std server. As suggested by Emmanuel, kindly reinstall the wss and update us with the result. I researched this error and found that it was a common issue with ASP.NET and you could do a workaround for it.

These steps may also make the computer or the network more vulnerable to attack by malicious users or by malicious software such as viruses. What significance could the information in Donald Trump's tax return have to his campaign? Ohio 9. I have to ask when you say "Have you tried re running the wizard keeping sure you selected "this server will host the CA" do you mean the Sharepoint tech configuration