Moss 2007 Central Administration An Unexpected Error Has Occurred
Contents |
UPS Service by Zubair Alexander · March 17, 2012 I recently installed a new SharePoint Server 2010 Enterprise for a client. an unexpected error has occurred sharepoint 2013 I also installed a SQL Server 2008 R2 Standard. Both were
Sharepoint 2010 An Unexpected Error Has Occurred
installed on separate Windows Server 2008 R2 servers running in a virtual VMware environment. PROBLEM After I successfully
An Unexpected Error Has Occurred. Sharepoint 2007
created the User Profile Synchronization (UPS) application and started the service, everything looked good. Then I went to Manage service applications in Central Administration under Application Management and clicked
An Unexpected Error Has Occurred. Sharepoint 2010 Correlation Id
on the hyperlink for the newly created UPS 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 an unexpected error has occurred sharepoint 2010 new site collection after UPS had been provisioned. This is the most common fix 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
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 about Stack sharepoint 2013 central administration unexpected error Overflow the company Business Learn more about hiring developers or posting ads with us an unexpected error has occurred sharepoint import spreadsheet Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a sorry something went wrong an unexpected error has occurred. sharepoint 2013 community of 6.2 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 I have created an https://blog.zubairalexander.com/how-to-fix-the-error-an-unexpected-error-has-occured-when-you-try-to-configure-a-newly-created-ups-service/ 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 scenario is, There is not visual http://stackoverflow.com/questions/1997803/an-unexpected-error-has-occurred 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 3393830 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 , it might be as simple as missing dll share|improve this answer an
on January 27, 2009 in SharePoint When trying to access the Shared Service Provider (SSP) I received the following generic error: An unexpected error has occurred. Yes, the detail http://www.sharepointed.com/2009/01/27/an-unexpected-error-has-occurred/ is overwhelming and pointed me directly at the problem. To allow the .aspx page to show the detail behind the error I had to make a small change to the web.config file. In https://www.brightwork.com/blog/sharepoint-2013-some-common-administrative-issues my case the web.config file in question was located in the following location: C:\Inetpub\wwwroot\wss\VirtualDirectories\7788 How did I know where this was located? If you are in Central Administration and hover over the name unexpected error of your SSP with your mouse, you should see the path at the bottom of the browser windows. If not, right click and select Copy Shortcut and paste it into notepad. Example: http://sambets:7788/ssp/admin The 7788 pointed me to the folder that contained the web.config I needed to edit. Once you have located the needed web.config file make a copy of it. Open the original web.config file and an unexpected error make these two changes.
exciting transition to SharePoint 2013, we have experienced a number of issues, which took us some time to overcome. In this blog I want to share with you some of these principle issues, to save you time when making the transition to the SharePoint 2013 platform! 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 or display form on certain lists in your site. You may receive the following messages. Sorry, something went wrong. An unexpected error has occurred. This will affect all lists which were created from a list template at any time in the past inside of SharePoint 2010 after you migrate to SharePoint 2013 RTM (reproduced with SharePoint 2013 RTM(base level) Server and Foundation). This can be resolved by installing the April 2013 CU. Therefore if your upgrading from SharePoint 2010 you must take on the April 2013 CU for SharePoint 2013. SharePoint 2013 restore changes to be aware of when migrating sites from one SharePoint 2013 server to another On SharePoint 2010, you could restore sites collections in the following scenarios using backup-spsite and restore-spsite PowerShell commands. 1. Move a site from SharePoint 2013 Foundation (April 2013 CU) to SharePoint 2013 Server (April 2013 CU) 2. Move a site from SharePoint 2013 Foundation (RTM) to SharePoint 2013 Foundation (April 2013 CU) Now on SharePoint 2013 you will get the following error 0x80070003 if you try this. We have found a workaround though. Workaround Instructions are here: http://www.brightworksupport.com/migrating-a-sharepoint-2013-site-collection-from-a-lower-cu-to-a-server-with-higher-cu/ Note: This procedure will work when moving a site from any lower CU to any higher CU version or a site from SharePoint Foundation to SharePoint Server. 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 is interrupted on SharePoint 2013 RTM