An Unexpected Error Has Occurred Sharepoint 2013 Central Administration
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeOnline20132010Other VersionsRelated ProductsLibraryForumsGallery Ask a question Quick access Forums home an unexpected error has occurred sharepoint 2010 Browse forums users FAQ Search related threads
An Unexpected Error Has Occurred Sharepoint 2010 New Site Collection
Remove From My Forums Answered by: Sharepoint Central Administration - Site sharepoint an unexpected error has occurred web parts maintenance page comes up with "Unexpected Error" SharePoint > SharePoint Legacy Versions - Setup, Upgrade, Administration and Operations Question 0 Sign
Sharepoint Export To Excel An Unexpected Error Has Occurred
in to vote Hi all, I have successfully installed Microsoft SharePoint 2007 Server (aka MOSS) on a Windows 2003 Server operating system. SQL Server is also installed. I have successfully run the Configuration Wizard. When I sharepoint 2013 central administration server error in '/' application click on Start->Programs->blah, blah, blah->SharePoint Central Administration, a browser window opens with the following information: In the caption => Error - Microsoft Internet Explorer In the URL (web address) => http://myServerName:13464/default.aspx In the main browser window => Go back to site (this is a hyperlink) => ERROR => An unexpected Error has occurred => Troubleshoot issues with WSS (this is a hyperlink) I have opened IIS and found that the SharePoint site exists with a port listening on 13464 and the default website under the wwwroot directory is stopped while the SharePoint site is running. Also, from a command prompt,
· March 17, 2012 I recently installed a new SharePoint Server 2010 Enterprise for a client. I also installed a SQL
Sharepoint 2013 Central Administration Runtime Error
Server 2008 R2 Standard. Both were installed on separate Windows Server 2008
Sharepoint 2013 Central Administration Http Error 503. The Service Is Unavailable
R2 servers running in a virtual VMware environment. PROBLEM After I successfully created the User Profile Synchronization (UPS) sharepoint 2013 central administration tutorial application and started the service, everything looked good. Then I went to Manage service applications in Central Administration under Application Management and clicked on the hyperlink for the newly created UPS 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 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 your error. Reset IIS after UPS had been provisioned. This is the most common fix https://blog.zubairalexander.com/how-to-fix-the-error-an-unexpected-error-has-occured-when-you-try-to-configure-a-newly-created-ups-service/ 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 cache folder In Windows Server 2008, the configuration cache is in the following location: Drive:\ProgramData\Microsoft\SharePoint\Config In Windows Server 2003, the configuration cache is in the following location: Drive:\Documents and Settings\All Users\Applicati
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 http://sharepoint.stackexchange.com/questions/24665/user-profile-service-an-unexpected-error-has-occurred Learn more about Stack Overflow the company Business Learn more about hiring developers https://sharepointnoob.wordpress.com/2009/06/03/an-unexpected-error-has-occurred/ or posting ads with us SharePoint Questions Tags Users Badges Unanswered Ask Question _ SharePoint Stack Exchange is a 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 an unexpected up and rise to the top User Profile Service = “An unexpected error has occurred.” up vote 1 down vote favorite 1 This is for a new SP 2010 install. I have a server running SP 2010. In IIS I have created an empty web site, "share.example.com". In SP Central Admin, I have created a web application bound to the IIS site, and that's working fine. an unexpected error In Central Admin > App Mgmt > Service Apps (shorthand there), I delete the default "User Profile Service" and create a new instance, bound to my web application, and using typical default values, as works in other cases. My user profile servce gets created, but when I click "Manage" in the ribbon, I get the SP 2010 error screen. "Error An unexpected error has occurred. Troubleshoot issues with Microsoft SharePoint Foundation. Correlation ID: 7be01822-5ad0-465a-9df2-45fc6a1cb86d Date and Time: 12/5/2011 8:15:57 AM " (the Coorelation ID changes each time). I have deleted-and-redone that service many times, also changing the name of the re-created service too. No luck. Messed with changing default values, etc. No love. Nothing. Using ULS Viewer, nothing obvious crosses my path, and I'm not getting much luck with it. 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 haven't looked into it yet. Any suggestions on solving this puzzle? service user share|improve this question edited Dec 6 '12 at 19:39 ali Jafer 15k11634 asked Dec 5 '11 at 17:21 Alan M
fresh MOSS install on Server 2003 SP2 for a development server. Just a complete install using NTLM and a SQL Server 2005 database 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 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 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 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 implementing this process in your particular environment. If you decide to implement this process, take any appropriate additional steps to help protect the system. We recommend that you use this process only if you really require this process. To work around this problem,