SP2010: the local farm is not accessible. cmdlets with featuredependencyid are not registered on Power Shell

Hi,

DO you get this when opening SharePoint power shell:

SharePoint is not yet compatible with .Net 4.
Solution:
Force it to run under older version.
Go to you SharePoint 2010 management shell  properties

Here you need to edit the target:

Before: Should be something like this:

ws\System32\WindowsPowerShell\v1.0\PowerShell.exe –NoExit   " & ' C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\POWERSHELL\Registration\\sharepoint.ps1 ' "

After: Add -Version 2

C:\Windows\System32\WindowsPowerShell\v1.0\PowerShell.exe –version 2 –NoExit " & ' C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\POWERSHELL\Registration\\sharepoint.ps1 ' "

Your Shell should now open with no issues.

SP2010 & 2013: Configuring Search in SharePoint 2010 and 2013

Hi,

This is pretty simple to do. Create a SharePoint Search Service Application.

Go to Central Admin and from there open Service Applications

Here You want to make sure you are using the correct account and register it as a managed account.

These two users are quite common: SP_Search or SP_Crawl. Add this user to your WSS_WPG group on the local server.

Next you need to choose App Pools. If you have limited resources available you can use one app pool but for production different app pools is probably recommended.
Search Admin Web Service:

Search App Pool for Search query and site settings:

Now click on OK.

This will run for a while and then give you a successful message.
After this  you will have a Search Service Application.

Here is a error im getting at this moment...Microsoft.Ceres.SearchCore.Services.Seeding
Dont have a solution yet. This happens as soon as you create the Search Service Application, if you delete it your Search App your backup runs with no problems. Error is only on search components.

Now click on the search service application, Content Sources ten o Local SharePoint Sites.
Configure your search crawls.
Depending on solution but i usually set incremental crawl from 5min to 24 hours and then Full Crawl you run the first time and then maybe schedule it again once a month just to be sure incremental did not miss anything. Some people say you only need to run full crawl once.

SP2013 - Backups Failing on Search Service Application

Hi,

Lately everywhere i go Backups are failing... SP2010 and SP2013.

This error is not resolved, i got the cause but no solution...Before you read everything first have a read at the bottom.

The error:
Last failure message: Microsoft.Ceres.SearchCore.Seeding.SnapshotTransferException: Could not send chunk ms\%default\gen.000000000000090c.state

No Crawls was configured yet so configured it(Incremental every 2 hours), ran a full crawl but lo luck.

Now i deleted the search service application and running a backup again. 
And the backup completes with no issues...

Ok, recreating the Search Service Application.
The domain access account i am using this time is the farm account. 
Ok, error is back.
To be continued...

Ok, i did some research regarding SharePoint backups and i am changing the way i do it...
DB's im backing up with either: SQL Server, DPM, Backup Exec (or what ever you use for your backups.

Then SharePoint backup are starting to give me issues. It seems that if farm get bigger SharePoint does not always do the job. So i am backing up the configuration only on SharePoint. You can restore this and then attach your databases.

So sorry, if you need to fix the issue above it was not solved this time but backup strategy adapted.

SP2010: Users can log onto SP2010

Hi, At a client while configuring SP the user noticed they cant access SharePoint with their AD username.

When i looked into it i realised i get this error when trying to access User Profile Synchronisation Service:
System.MissingMethodException: Method not found: 'System.String Microsoft.Office.Server.UserProfiles.SynchronizationRunStatus.get_ConnectionName()'.

i Used the application wizard for this implementation for some of the Service Applications. Since it is a Single WFE environment i don't see a problem using the wizard for user profile sync. Defending myself (:

Solution: Installed June 2012 CU

Ok, not quite solved yet...User Profile Synchronisation Service wont start inside SharePoint...
Looking into it...
Ok, Had to add SP_farm to local administrators, then start the service, then i restarted...
Had to do this twice for some reason.

You are suppose to be able to remove SP_farm from local admins when you are done but have not done this yet.

Doing this post at client so no time for screenshots (: