Comments for Stefan Goßner

Hi Islam,
from the KB article:
As part of SharePoint database upgrade, the members of the db_owner role are deleted from the role, except for the “dbo” user and the user who is performing the upgrade. This is done for enhanced security to make sure that an errant account isn’t inadvertently left having the db_owner role privileges. However, there may be situations in which this behavior is not desirable. For example, RBS may be broken every time that an upgrade is run. In this situation, a registry key is added to bypass this behavior.

With other words: this is not mandatory – this is optional and only applies to certain specific situations.

Cheers,
Stefan

Hi,

do i have to set the SideBySiteToken onto 16.0.4600.1002 or 16.0.4600.1000

i would say 16.0.4600.1002
(our sharepoint is english with a german languagepack)

Technet:
$webapp.WebService.SideBySideToken =

Hi Stefan,

After installing these SharePoint 2013 server PU, do we need to run the configuration wizard?

Thank You
Sajid

Hi Stefan,

my post is 100% in the wrong category, even it’s the same product. Did you recognize any problems with SharePoint 2013 (version doesn’t matter) after that patch day?
I got issues when I navigated in the Central Administration on “Create new SiteCollection”.
The error I got is:
“Sorry, something went wrong
Common Language Runtime detected an invalid program.”
With SharePoint 2010, this issue is not coming up, so i guess it could have something to do with .NET.
Thanks in advance for your answer.
Cheers,
Michael

Hi Stefan,

I’m working through applying the October Cumulative updates for SharePoint and in both my SharePoint Farms I am seeing bizarre issues. On one I am consistently receiving the error below, I’ve tried a bunch of the suggestion on the web with no luck. Any thoughts on this, I’ve never had an issue like this applying updates.

An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown. Additional exception information:
Upgrade [SPContentDatabase Name=SP2013DEV_CONTENT] failed. (EventID:ajxnm)

Exception: Object reference not set to an instance of an object. (EventID:ajxnm)

(EventID:ajxnm)

Upgrade Timer job is exiting due to exception: System.NullReferenceException: Object reference not set to an instance of an object.
… (EventID:aj0ur)

Hi Brad,
if you need assistance to analyze the issue ensure to open a ticket with Microsoft Support.
Cheers,
Stefan

Hi Michael,
haven’t seen this. The error indicates that there is a dll with corrupted content.
Would be important to isolate which dll this is.
Cheers,
Stefan

Hi Sajid,
as there is not a single SharePoint fix which would not require the config wizard.
So: yes.
Cheers,
Stefan

Hi Tobias,
you always have to pick the highest applied build number.
With other words: 16.0.4600.1002
Cheers,
Stefan

.NET Framework 4.7.1 has been released.

I did try SharePoint 2013 installation with preinstalled .NET 4.7.1 on Windows Server 2012 R2. No issues.
Just make sure you have this special svrsetup.dll in the “Updates” Folder as described here:
https://blogs.technet.microsoft.com/stefan_gossner/2016/09/14/sharepoint-2013-installer-now-supports-net-framework-4-6-and-above/

I also tried SharePoint 2016 installation with preinstalled .NET 4.7.1 on Windows Server 2016 with SQL Server 2017. No issues.

Hi, I was wondering if you would be able to help me.
I’m trying to make a PS script to run an executable in memory, from a base64 string. Powershell keeps giving the following error:

Exception calling “Run” with “0” argument(s): “Parameter count mismatch.”
At C:\Users\user\directory\script.ps1:21 char:1
+ [Runner.MainXT]::Run()
+ ~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : TargetParameterCountException

My PS code is as follows:

$Source = @”
using System;
using System.Reflection;
namespace Runner
{
public static class MainXT
{ public static string b64 = “”;
public static void Run()
{
byte[] bin = Convert.FromBase64String(b64);
Assembly a = Assembly.Load(bin);
MethodInfo method = a.EntryPoint;
object o = a.CreateInstance(method.Name);
method.Invoke(o, null);
}
}
}
“@
Add-Type -TypeDefinition $Source -Language CSharp
[Runner.MainXT]::Run()

Hi Brad,

starting the following services at “configurationtask 8” of “SharePoint Products Configuration Wizard” solved the problem for me.

$foo = get-service “SPTimerV4”
$foo.start()
$bar = get-service “IISSVCS”
$bar.start()

Hi Matt,
did you have a previous version of the csharp script with parameter in the same powershell window?
You need to close the powershell window to ensure that the csharp code gets recompiled.
Cheers,
Stefan

Hi Stefan, which Sharepoint 2013 CU will support SP4 for SQL 2012?

Hi Stefan,
I installed the September 2017 CU (from your link above) in our farm, run the psconfig, all OK. Except, the Configuration db version number after the install is now 15.0.4957.1000. I checked Todd Klindt’s list of build numbers and this number does not exist anywhere. There is it referenced that for the September CU the build number should be 15.0.4963.1000. Which is the correct build number?
Many thanks

Hi Andreas,

Yep that’s what did it for me after many hours of reading. Thanks for the tip.

In the command line example, the parameter “-install” is listed twice. Is that by design?

The first is to install applicationcontent, the second is to install services.
Each segments starts with “-cmd”

Cheers,
Stefan

There is no specific CU required.

Comment on October 2017 CU for SharePoint Server 2016 is available for download by Stefan Goßner

Comment on October 2017 CU for SharePoint Server 2016 is available for download by TobiasMa

Comment on SharePoint security fixes released with October 2017 PU and offered through Microsoft Update by Sajid Ali

Comment on SharePoint security fixes released with October 2017 PU and offered through Microsoft Update by Michael Heuer

Comment on October 2017 CU for SharePoint 2013 product family is available for download by Brad

Comment on October 2017 CU for SharePoint 2013 product family is available for download by Stefan Goßner

Comment on SharePoint security fixes released with October 2017 PU and offered through Microsoft Update by Stefan Goßner

Comment on SharePoint security fixes released with October 2017 PU and offered through Microsoft Update by Stefan Goßner

Comment on October 2017 CU for SharePoint Server 2016 is available for download by Stefan Goßner

Comment on SharePoint 2013/2016 and .NET framework 4.7 by 859

Comment on Using CSharp (C#) code in Powershell scripts by Matt

Comment on October 2017 CU for SharePoint 2013 product family is available for download by Andreas

Comment on Using CSharp (C#) code in Powershell scripts by Stefan Goßner

Comment on October 2017 CU for SharePoint 2013 product family is available for download by iamgeorgem

Comment on September 2017 CU for SharePoint 2013 product family is available for download by Giorgos A

Comment on October 2017 CU for SharePoint 2013 product family is available for download by Brad

Comment on Why I prefer PSCONFIGUI.EXE over PSCONFIG.EXE by David

Comment on Why I prefer PSCONFIGUI.EXE over PSCONFIG.EXE by Stefan Goßner

Comment on October 2017 CU for SharePoint 2013 product family is available for download by Stefan Goßner

Comment on September 2017 CU for SharePoint 2013 product family is available for download by Stefan Goßner