Tag Info

New answers tagged

0

looks like their is missing updates or missing PSconfig wizard.from the versions numbers, one farm is on Service Pack 1 and one is on May 2015 CU. I think one farm get the updates and other is still behind. You have to apply same update on 2nd farm. Check more about version numbers here: http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=346


1

Audiences have to be built and compiled before they can be used. Audiences are built in the User Profile Service area of Central Administration and are based on user profile properties. For example, you could create a Marketing audience where the membership includes everyone with the Department of Marketing. Once defined and compiled, it is available in ...


1

You can use the [Force][1] Paramter. Force = Specify to overwrite an existing backup file if it already exists. Your command should be looks like this Backup-SPSite -Identity http://xyz -Path D:\SP_BACKUPS\test.bak -force


0

I dont think their is any way to peform the incremental backups on the Site collections level. The Backup-SPFarm cmdlet creates a backup for the entire farm or individual components within the farm. It can also be used to back up just the configuration settings of a farm to be used as a farm template for other SharePoint farms. If you want to back ...


0

This type of error is due to wrong AAM settings or IIS bindings.So make sure You Alternate Acess Mapping settings are correct. if their is any bindings at IIS level should reflect the correct If you are using FQDN with Loadbalancer then make sure DNS point to correct entry. If still having the issue, Its great if yo share the Screen Shots / Error ...


0

A related answer was posted here by Vadim Gremyachev. It turns out checking the IsSiteAdmin property on the current user object directly isn't a reliable result; instead, checking for the property on Site.RootWeb.SiteUserInfoList was a reliable approach for me. CurrentUser.IsSiteAdmin should be true but returns false Another way to determine whether ...


1

I had the same problem and resolved it as follows: Run PowerShell with SharePoint modules Execute following command: Set-SPSite <URL> -owneralias "i:0#.w|< domain\user >" It looks like this is a bug which occures when the user profile import was not run correctly, the last thing I don't know yet, but it's my best guess



Top 50 recent answers are included