New answers tagged

1

Sharepoint 2010 to SharePoint 2013 inplace upgrade is not supported. I'd try to carve out a separate server for the time being in order to install SharePoint 2013 and pull over your content databases after you create a farm. https://technet.microsoft.com/en-us/library/ee617150.aspx?f=255&MSPPError=-2147217396


1

If you can read the line above the form, It is clearly mentioned that Use this page to edit this user profile by changing values for the following properties. Properties that are mapped to the external data source will be overwritten the next time user profiles are imported. The icon indicates that each property of your user profile is mapped with some ...


0

There are couples of things which you should confirm. install the SMTP server locally according to Office 365 settings You need SPO licensing for user " To setup your on-premise SharePoint server to use Exchange Online, you need to build SharePoint Online (SPO) accounts for those users and assign the appropriate SPO licenses." ...


0

You can configure Your SMTP setting for server from IIS IIS > select server > SMTP Email Enter your SMTP Server name,port and specify credential according your SMTP server


0

I saw this happening today after our SharePoint 2013 server was updated with the latest windows updates. I added the service accounts running the application pools to the local security policy "log on as a batch job" and started the app pools in IIS and that seemed to resolve the issue. SharePoint 2013: Service Account Configurations and Permissions


1

In order to Get the SharePoint 2013 workflows Option in Designer, You have to Install and Configure. Installation of Workflow Manager 1.0 Configuration of Workflow Manager Install the Workflow Clients on the All server in the farm( if wfm not install on them) Register workflow Proxy with SharePoint Server. To publish the Workflow you have to provision ...


0

PowerShell did not help... Health Analyzer 'Repair Automatically' did not help... (saw errors in the ULS logs that it tries to access the site...that does not exists anymore and so cannot remove the app) Only solution left: Remove those records from the AppInstallations table in the content database.



Top 50 recent answers are included