Share via

Step by step video on how to fix the SharePoint Workflow issue caused by .NET patch

  • Article

This post is a continuation of this previous post. It is also an extension of KB4465015. The video assumes you read the previous post and/or KB.

The page to the scripts mentioned in the video can be found here: https://gist.github.com/joerodgers/2302b394796c865818839d843bae2dad

 

[embed]https://www.youtube.com/watch?v=l25Gp08egC0[/embed]

Comments

  • Anonymous
    October 12, 2018
    Video killed the radio star. Nice media to explain how to fix the .Net issue.
    • Anonymous
      January 16, 2019
      (The content was deleted per user request)
    • Anonymous
      January 16, 2019
      Rodney, Sean loves you and so do I :)
  • Anonymous
    October 13, 2018
    Worked perfectly as shown in the video, THANK YOU!
  • Anonymous
    October 16, 2018
    The solution worked perfectly. THANKS A LOT
  • Anonymous
    October 16, 2018
    Video no longer available? :(
    • Anonymous
      October 17, 2018
      I just test it and it is working. Maybe there is some firewall blocking for you.
  • Anonymous
    October 17, 2018
    Thank's a lot.Very clear, simple and usefull.
  • Anonymous
    October 23, 2018
    Worked a treat, fantastic video, thank you
  • Anonymous
    October 24, 2018
    We are encountering the below error while executing the script Add-CodeDomAuthorizedTypeToOWSTimerConfig.ps1VERBOSE: Processing server: DE08W3825Get-WmiObject : The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)At C:\Add-CodeDomAuthorizedTypeToOWSTimerConfig.ps1:371 char:52+ $timerServiceConfigPath = Get-WmiObject <<<< -Query "SELECT * FROM Win32_Service WHERE name = 'SPTimerV4'" -ComputerName $computer | SELECT @{Name="PathName"; Expression={$_.PathName.Trim('"')}} + CategoryInfo : InvalidOperation: (:) [Get-WmiObject], COMException + FullyQualifiedErrorId : GetWMICOMException,Microsoft.PowerShell.Commands.GetWmiObjectCommandVERBOSE: Processing server: DE08W3826New-Object : Exception calling ".ctor" with "1" argument(s): "The UNC path should be of the form \server\share."At C:\Add-CodeDomAuthorizedTypeToOWSTimerConfig.ps1:378 char:29+ $fi = New-Object <<<< System.IO.FileInfo( $uncPath ) + CategoryInfo : InvalidOperation: (:) [New-Object], MethodInvocationException + FullyQualifiedErrorId : ConstructorInvokedThrowException,Microsoft.PowerShell.Commands.NewObjectCommandSet-Content : Logon Failure: The target account name is incorrect.At C:\Add-CodeDomAuthorizedTypeToOWSTimerConfig.ps1:401 char:53+ $defaultXml.ToString() | Set-Content <<<< -Path $uncPath + CategoryInfo : WriteError: (\DE08W3826.CONFIG:String) [Set-Content], IOException + FullyQualifiedErrorId : GetContentWriterIOError,Microsoft.PowerShell.Commands.SetContentCommandGet-Content : Cannot find path '\DE08W3826.CONFIG' because it does not exist.At C:\Add-CodeDomAuthorizedTypeToOWSTimerConfig.ps1:405 char:24+ Get-Content <<<< -Path $uncPath | Set-Content -Path "$($uncPath)backup$(Get-Date -Format 'yyyy_MM_dd_hh.mm.ss').config" + CategoryInfo : ObjectNotFound: (\DE08W3826.CONFIG:String) [Get-Content], ItemNotFoundException + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetContentCommand
    • Anonymous
      October 24, 2018
      Make sure SP Timer Service is running on server DE08W3826 and run the script again
  • Anonymous
    October 28, 2018
    Hi Rodney,Can you please confirm that the scripts are ok to run before the application of the .Net Security updates(s)?Thanks.
    • Anonymous
      October 29, 2018
      Yes, you can run the scripts before applying the .NET updates.
      • Anonymous
        October 29, 2018
        Thankyou
  • Anonymous
    November 01, 2018
    Thanks! Worked Perfect!
  • Anonymous
    November 09, 2018
    Your solution worked perfectly on all our servers. The Collect Signatures Workflow SharePoint 2010 "Fail on Start" issue has gone! Thanks a lot!
  • Anonymous
    November 19, 2018
    The comment has been removed
    • Anonymous
      November 20, 2018
      You may have forgotten the closing '}'
  • Anonymous
    November 28, 2018
    I encountered this in our Dev Env and followed steps and worked great...any harm in running these scripts and changing those .CONFIGS before running the same updates on our Production Servers?
    • Anonymous
      November 28, 2018
      Oops sorry, just saw one of the comments above stating that it was ok. My apologies. Thanks again!
    • Anonymous
      November 29, 2018
      It should not bring any problems
  • Anonymous
    December 01, 2018
    We applied all of the windows updates and after applied the scripts. The issue is still not resolved. Any script using an if statement is still having the same issue. Should we have applied the scripts before applying the updates?
    • Anonymous
      December 03, 2018
      Any order should work. You may need to open a support case.