SharePoint Snippets

Living a SharePoint life

Tuesday, August 9, 2016

August 2016 Office Update Release

The August 2016 Public Update releases for Office are now available!

Note: In August, we are following a revised schedule for the release of non-security updates for the MSI (Windows Installer) version of Office and related client products. Non-security updates (those with the Critical or Definition update classification) were available on the Download Center on August 2 and will be available on Microsoft Update/WSUS on August 16.

This change will only be in effect for August. After that, we’ll resume the normal first Tuesday monthly release for non-security updates on both the Download Center and MU/WSUS.

This month, there are 28 security updates (3 bulletin) and 40 non-security updates.

Security bulletins:

All of the security and non-security updates for August are listed in KB article 3181038

A new version of Office 2013 Click-To-Run is available: 15.0.4849.1003

A new version of Office 2010 Click-To-Run is available: 14.0.7172.5001

For information on Office 365 Click-To-Run updates, see Office 365 client update branch releases.

Content from: Office Updates http://bit.ly/2aJnTvc

Wednesday, August 3, 2016

Bug hunter: Could not create the site from the context

Today a colleague approached with an interesting problem. The SharePoint farm consist of two server, which both serve as a web frontend server. One of the two acts as the application server. When he opens a specific site collection, the first SharePoint node returns the page as expected, the other node however just returns a 404.

This post is

Tuesday, August 2, 2016

August 2016 Non-Security Office Update Release

Listed below are the non-security updates we released on the Download Center today. See the linked KB articles for more information.

In August, we’ll be following a revised schedule for the release of non-security updates for the MSI (Windows Installer) version of Office and related client products. Non-security updates (those with the Critical or Definition update classification) will be available on the Download Center on August 2 and on Microsoft Update/WSUS on August 16.

This change will only be in effect for August. After that, we’ll resume the normal first Tuesday monthly release for non-security updates on both the Download Center and MU/WSUS.

Security updates will release on the second Tuesday of August as usual.

Office 2007

Update for Microsoft Office Outlook 2007 Junk Email Filter (KB3115461)

Office 2010

Definition Update for Microsoft Office 2010 (KB3115475)

Office 2013

Definition Update for Microsoft Office 2013 (KB3115404)

Update for Microsoft Office 2013 (KB3101491)

Update for Microsoft Office 2013 (KB3115425)

Update for Microsoft PowerPoint 2013 (KB3115444)

Update for Microsoft Project 2013 (KB3115434)

Update for Microsoft SharePoint Designer 2013 (KB3114721)

Update for Microsoft SharePoint Server 2013 Client Components SDK (KB3115430)

Update for Microsoft OneDrive for Business (KB3115433)

Office 2016

Definition Update for Microsoft Office 2016 (KB3115407)

Update for Microsoft Access 2016 (KB3115142)

Update for Microsoft Office 2016 (KB3115141)

Update for Microsoft Office 2016 (KB3115270)

Update for Microsoft Office 2016 (KB3115406)

Update for Microsoft Office 2016 (KB3115410)

Update for Microsoft Office 2016 (KB3115411)

Update for Microsoft Office 2016 (KB3115413)

Update for Microsoft Office 2016 (KB3115416)

Update for Microsoft Office 2016 (KB3115417)

Update for Microsoft Office 2016 (KB3115421)

Update for Microsoft Office 2016 Language Interface Pack (KB3115414)

Update for Microsoft PowerPoint 2016 (KB3115409)

Update for Microsoft Project 2016 (KB3115424)

Update for Microsoft Visio 2016 (KB3115405)

Update for Microsoft OneDrive for Business (KB3115423)

 

Content from: Office Updates http://bit.ly/2ajdDnm

Thursday, July 28, 2016

Revised August schedule for non-security Office updates

In August, we’ll be following a revised schedule for the release of non-security updates for the MSI (Windows Installer) version of Office and related client products. Non-security updates (those with the Critical or Definition update classification) will be available on the Download Center on August 2 and on Microsoft Update/WSUS on August 16.

This change will only be in effect for August. After that, we’ll resume the normal first Tuesday monthly release for non-security updates on both the Download Center and MU/WSUS.

Security updates will release on the second Tuesday of August as usual.

 

Content from: Office Updates http://bit.ly/2ahSVHK

Tuesday, March 22, 2016

SharePoint HRESULT: 0x80131904 list error

Recently a customer of mine had a problem creating new entries in SharePoint lists. Everytime he tried to add a new entry to a list, SharePoint returned an error with HRESULT: 0x80131904

After some research in the windows logs, it became quite clear that the SQL server transaction logs have exhausted the entire disk space on the SQL server. So we cleared the transactions by backup, shrunk the size afterwards and the errors were gone.

Thursday, October 29, 2015

Latest release of the SPBestWarmUp Script available

I finished the updates on the latest version of the SPBestWarmUp script and we’re heading version 2.0 (Stockholm). You can get it here on Codeplex.

SPBestWarmUp is a PowerShell script that will load all of your SharePoint web sites. By doing so it helps to populate the IIS and the asp.net caches. This will speed up accessing your server and give your users a better overall experience.

Change log:
  • Removed the Internet Explorer to fetch webpages and switched instead to the Invoke-WebRequest Cmdlet. IE will be deprecated in the future anyway.
  • Collecting all relevant Urls prior fetching them from the server.
  • Temporarily removed the ability to use own Urls. Will be added in the future as a parameter and/or as a file. However, if you look at the code, you’ll find it isn’t hard to write your own little patch if you need to.
The code is marked as beta. To use it, collect a copy from the source repository.

Feedback is welcome. If you find any issue, please use the issues panel on the Codeplex project site.

Wednesday, October 21, 2015

Change the SQL recovery model in bulk with the PowerShell

Sometimes you need to configure settings on your SQL server in bulk, like e.g. the recovery model. In my case, we needed to change all databases to the Full recovery model, due to the usage of Always-On. Scince SQL 2012 there is a great way to do this with the PowerShell.

First open a Powershell and see if the SQL PowerShell module is loaded.
Get-Module SQLPS
If it isn't loaded, do so by using
Import-Module SQLPS
For scripts you should check if the module is loaded before you import it like this:

if ((Get-Module "SQLPS" -ea silentlycontinue) -eq $null)
{
    Import-Module SQLPS -DisableNameChecking
}
Now you can change to the SQL server by simply entering SQLSERVER:

Use ls or dir to see what options you have

Change the 'directory' with cd SQL. This way you go to the SQL server configuration. Do so as well for the servers host name and the SQL server instance, until you you enter the databases directory. Here you'll find all the databases hosted by the SQl server instance you choose. Now we can run the following script to change the recovery model in bulk.
foreach ($db in ls) {
  if ($db.RecoveryModel -ne "Full") {
    $db.RecoveryModel = "Full"
    $db.Alter()
  }
}

Monday, September 14, 2015

Trickshots: Testing a SQL connection quick and easy

Did you ever need to test a SQL connection? As a SharePoint Pro you probably have. I found a nice little trick on Steve Rachui's Blog today I’d like to share with you.

Create a new text file on the desktop of the machine you will try to connect to the SQL server. Name the file whatever you like, but rename the file into UDL. Double click on the file and a dialog pops up with SQL connection settings. Enter your connection settings and use the Test Connection button in the lower end of the dialog.

If you need to test a different SQL server port (not 1433), simply create a SQL alias on the machine and test against the alias.