SharePoint 2013 Alerts not working...again

There is plenty of resources online about this issue and none suggest doing this first and they really should.

So if you had SharePoint 2013 alerts configured and working and is just stopped working one day with the following symptoms:

• If you register for alerts in a particular list, you get a notification that "You have successfully created an alert for..."
• If you modify any item in the same list as above, no alerts come thru.

You will need to make sure that each SharePoint server ip address (web front, application) in the farm is added as an allowed SMTP sender in Exchange.

Explanation: Any SharePoint server in the farm can be in charge of sending an alert and usually one is in charge of a particular site collection. If you restart Timer Service, it might move that responsibility to another SharePoint server whose IP is not listed as an allowed SMTP sender in Exchange, and as an end result, it might not send alerts.

Hoping this helps someone

Publishing Office Web Apps 2013 in UAG 2010

If you are setting up Office Web Apps 2013 along with SharePoint 2013 and need to publish both in UAG 2010 for external users you should read the following article:

http://technet.microsoft.com/en-us/library/jj204665.aspx

Pay close attention to line 8 as it made a difference for us.

The permissions granted to user ‘domain\username’ are insufficient for performing this operation.

If you are setting up SharePoint 2013 and SQL 2012 with SharePoint Integration Mode please read on. You might be under impression you did everything properly but you get the following error when trying to deploy a report using BIDS or trying to edit a data source:

"The permissions granted to user ‘domain\username’ are insufficient for performing this operation. —> Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions granted to user ‘domain\username’ are insufficient for performing this operation."

To solve this problem you have to grant your SQL Reporting Service Application Pool Account (whatever is running your SQL Service Application, see Central Admin -> Manage Service Application -> SQL Server Reporting Services) Full Control to the web application that report is being deployed to in your particular case.

Or you could just use the powershell command below:

$webApp = Get-SPWebApplication –Identity http://yoursharepointapp
$webApp.GrantAccessToProcessIdentity(“domain\SSRSAccount”)

Source: http://paulliebrand.com/

Attaching SharePoint 2010 content database (Windows/SQL 2008 R2) database to SharePoint 2013 (Windows/SQL 2012)

If you are migrating from SharePoint 2010 to SharePoint 2013 and trying to attach a SharePoint 2010 content database that used to reside in SQL 2008 R2 to SQL 2012 you should know the following.

During the upgrade process of attached database you might get an error message similar to this:

"WARNING The [SharePoint - 25000] web application is configured with claims authentication mode however the content database you are trying to attach is intended to be used against a windows classic authentication mode."

The reason you are getting error message above is because all new Web Applications in SharePoint 2013 are by default created in Claims Authentication Mode.

To get around this, create the new Web Application in SharePoint 2013 using PowerShell command with Windows Classic Authentication Mode:

New-SPWebApplication -Name "Contoso Internet Site" -ApplicationPool "ContosoAppPool" -AuthenticationMethod "Kerberos" -ApplicationPoolAccount (Get-SPManagedAccount "CONTOSO\jdoe") -Port 80 -URL "https://www.contoso.com"

Microsoft: http://technet.microsoft.com/en-us/library/gg276326.aspx

Please be aware that this authentication mode is no longer supported. At this point you can run the upgrade once more and move on.

If you use anything written here, you do it on your own risk!

My very first post! Oy, so excited!!!

Here goes my very first post.

I will blog mostly about SharePoint 2010 and SharePoint 2013. I am no expert, these blogs are just about my daily interactions with SharePoint.

Wish me luck!