Posts

Showing posts with the label User Profile

" Invalid URI: The URI is empty. Contact your system administrator for help in resolving this problem" SharePoint 2013

Image
I had a task to create a proof of concept environment for SharePoint 2013 for a presentation to a top level exec. Installed and Configured a SharePoint 2013 farm on couple of VM's with dedicated WFE/APP and SQL Server boxes, as this will be used as a POF and the reqcuirements were not clear how long the boxes will be used. MS has released the deployment guide for 2013 must read before thinking of creating a new farm. Created a new web application on the new farm and a root level Site Collection based on Team Site Template. Till this moment everything was looking good. On accessing the Site got the following error : SharePoint returned the following error: Invalid URI: The URI is empty. Contact your system administrator for help in resolving this problem. My first encounter with an issue on 2013 on a vanilla environment, thought it would be good to have this as a reference. To resolve this, I had to create and configure my site i.e. Created a new web app for my site C

Restore SharePoint MySites from Backup

Image
All managers from the company were waked with this emails like: Subject: The My Site of X Y is scheduled for deletion The My Site of X Y is scheduled for deletion in 14 days. As their manager you are now the temporary owner of their site. This temporary ownership gives you access to the site to copy any business-related information you might need. To access the site use this URL: https://mysites.portal.domain.local/personal/xy Pretty uncomfortable. The day before this I deleted the AD Sync Connection from SharePoint's User Profile Service Application and this caused it. The sync job ran and with no connections SP thought that all the users have been deleted. Theoretically there should be 14 days until these profiles are deleted but for some reason I can't see past activity for the use users. Long story short, I need to restore MySites from a backup .   The Process The restoring process is simpler than thought. Later I found out that I had to restore the User Profi

User Profile Application ‘Unable to process Create message’

Issue: Unable to add user properties for user profile connection. Getting Unable to process Create message error in the event log and ULS logs. Error’s in the event log and ULS Logs: OWSTIMER.EXE (0x075C)            0x0DD4 SharePoint Portal Server User Profiles      9q17     High            UserProfileApplication.SynchronizeMIIS: Failed to configure ILM MA, will attempt during next rerun. Exception: Microsoft.ResourceManagement.WebServices.Faults.ServiceFaultException: Unable to process Put message     at Microsoft.ResourceManagement.WebServices.Client.Resource.Update()     at Microsoft.ResourceManagement.WebServices.ResourceManager.UpdateResource()     at Microsoft.Office.Server.UserProfiles.Synchronization.ILMMAConfiguration. UpdateSQLConnectionInformation(String server, String databaseName, String user, String domain, SecureString password)     at Microsoft.Office.Server.UserProfiles.UserProfileConfigManager.UpdateILMMA(String databaseServerIlm, String da

SharePoint 2010 User profile sync connection creation failed: "Unable to process Create message"

Today I was helping one of my customer with creating the UPS sync connection on SharePoint 2010 environment and ran into the below errors, after going through all the dramas I was able to found the cause and fix it. Thought of sharing it with all: SharePoint Errors: ERROR Unable to process Create message In the Application event log: Source: Forefront Identity Manager Event ID: 3 Microsoft.ResourceManagement: System.InvalidOperationException: Retrieve schema failed at Microsoft.ResourceManagement.Utilities.ExceptionManager.ThrowException(Exception exception) at Microsoft.ResourceManagement.ActionProcessor.SyncConfigActionProcessor.Create(String typeName, IList`1 createParameters, Guid creator, Guid cause) at Microsoft.ResourceManagement.ActionProcessor.SyncConfigActionProcessor.ProcessInputRequest(RequestType request) at Microsoft.ResourceManagement.ActionProcessor.ActionDispatcher.ProcessInputRequest(RequestType request) at Microsoft.ResourceMana