Friday, October 17, 2014

Folder to exclude from the SharePoint Antivirus Scanning: SharePoint 2013

While working on some of the Antivirus Issue and revisiting the AV configuration in each of the SharePoint platform seen many system and log folder also being scanned by AV deployed on SharePoint servers.

MS had published a very useful KB article which gives you information and listing all those servers which can be excluded form the AV scanning on your SharePoint environment.

Though of Sharing with all you guys…!

Wednesday, October 15, 2014

WMI: Windows Management Instrumentation

I was given a task to compare the latest software installed on mane server. Looking at the task though it sounds very simple that  we can compare the list form Control panel and add remove programs.

However, it involves many hours job when it comes to servers. I came across the term WMI which gives you extended functionality to extract such reports.

First of all its important o know about what is WMI: Windows Management Instrumentation (WMI) is the infrastructure for management data and operations on Windows-based operating systems. You can write WMI scripts or applications to automate administrative tasks on remote computers but WMI also supplies management data to other parts of the operating system and products, for example System Center Operations Manager, formerly Microsoft Operations Manager (MOM), or Windows Remote Management (WinRM).

You can use WMI from client applications and scripts. It provides an infrastructure that makes it easy to both discover and perform management tasks. In addition, you can add to the set of possible management tasks by creating your own WMI providers.

Extracting the information of all updates and hotfixes from command promot:

wmic qfe list brief /format:htable > "%USERPROFILE%\hotfix.html"

This produces a nicely formatted list in an HTML file named hotfix.html that gets placed in the User folder.


Applies to: SharePoint Server 2010, Windows Server 2008.

Monday, October 13, 2014

Forefront Identity Manager Stops after servers are rebooted: SharePoint 2010

Issue: FIM synchronization services in our one of the SharePoint environment stops or doesn’t start every time our servers are patched and rebooted.

Error: We have many loges reported in event viewer of the servers. Event ID 3, Event ID 6324, Event ID 3760

Log Name:      Application
Source:        Forefront Identity Manager
Date:          29/06/2014 03:16:04
Event ID:      3
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Server Name.
The TryGetSetting function in SettingsProvider.dll returned an empty set of supported parameters for property, SQLConnectionString.
Event Xml:
    Server Name
    The TryGetSetting function in SettingsProvider.dll returned an empty set of supported parameters for property, SQLConnectionString.
Log Name:      Application
Source:        FIMSynchronizationService
Date:          29/06/2014 03:18:05
Event ID:      6324
Task Category: Server
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Server Name.
The server encountered an unexpected error and stopped.
Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Date:          29/06/2014 03:18:38
Event ID:      3760
Task Category: Database
Level:         Critical
User:          Farm account.
Computer:      Server Name.
SQL Database ‘DB Name; on SQL Server instance ‘SQL Server Instances Name,14331' not found. Additional error information from SQL Server is included below.
Cannot open database "DB Name" requested by the login. The login failed.
Login failed for user ‘Farm account name’.

There are different approaches towards troubleshooting this issue as reason for its occurrence is unknown.


Different people had suggested different things:

Such as adding service account into three groups on local machine:
FIMSyncOperator, FIMSyncJoiners and FIMSyncBrowse 
and errors should go.

FIM Sync service should start before FIM service. However it may not be happening. Currently the service is set to Automatic and can be changing it Automatic (Delayed Start).

We could deploy a script which will check for the service every 60 seconds, and if it is not running, sends an email to the administrator

  • while ((Get-Service "FIM").status -eq "Running")
  • {Start-Sleep -Seconds 60}
  • Send-MailMessage -From FIM@ps.local -To admin@ps.local -Body "FIM Stopped" -SmtpServer server1
  •  Alternatively, you can put a .cmd file in your Recovery Tab of the service,  and use the following command: Powershell Send-MailMessage

In our case we had also found there were several SQL related error and in further investigation we found that server hosting FIM service were rebooted before the SQL server and once the SQL servers were re-booted FIM services always failed to find it reference to connect to SQL.
Rebooting SQL servers after server hosting FIM services had let FIM sync Services in Start state and resolved our issue.

Applies to: SharePoint server 2010, Windows Server 2008, Fore front Identity manager.


snow flakes

blogger widgets Blogspot Tutorial


Related Posts Plugin for WordPress, Blogger...