Unsolved

July 2018 Microsoft Security Patches break G/Net Viewer (from GTech ver. 10.1 SP3 )

Comments: 1 - Last Comment by teichel on Jul 25, 2018   Comment Filter:
Posted on Jul 12, 2018
 
 

This is Tina Eichele, with SMUD and we've had some major issues with the MS Server Patches for July 2018 for G/Net Viewr and our 2008 R2 Web Server.   The two KB's that appear to be root of issue are KB430556 and KB4340004.    The issue is as follows:

Launch G/Net Viewer after patches installed on web server.    Client G/Net viewer comes up as seen in attachment.    Nothing we could find or do allowed it to be reset correctly.   We checked all the files (including those mentioned in the snapshot - udb, ccm) as well as the registry and nothing showed changed.   Yet it's coming up referencing Mobile Viewer (not G/Net Viewer).     

Next we removed the KBs and get different KB.    "... I go to uninstall it and that KB number is diffderent the KB I installed is coming up as KB4338612 (instead of the KB430004 uninstalled).

Anyone else having issues with this month's MS Server Patching?

thanks for any help provided Tina Eichele, tina.eichlee@smud.org

patching_issue_July2018.pdf
YOUR USE OF DOWNLOADED MATERIALS PROVIDED THROUGH THIS SITE IS ENTIRELY AT YOUR OWN RISK.
See the Disclaimers section in Terms of Use.
Point your RSS reader here for a feed of the latest messages in this topic
RE: July 2018 Microsoft Security Patches break G/Net Viewer (from GTech ver. 10.1 SP3 )
Posted on Jul 25, 2018 in response to: teichel
 
   
 

Just a follow up to this note i posted.    We didn't take the two patches 

2018-07 Security and Quality Rollup for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 for Windows 7 and Server 2008 R2 for x64 (KB4340556)

4340556

2018-07 Security Only Update for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 for Windows 7 and Server 2008 R2 for x64 (KB4340004)

4340004

which caused the problems with our G/Net Viewer use, but we did take the others.    Monday (day after the patching was done on production) our Web Server service didn't restart after 3 am task (start/stop) ran.    The automation to do this task has worked for 8+ years.   In looking deeper at the patches taken, the App Admin found issue.    We believe the new patches released this week will fix this issue.

  New “bad” one is  KB4338818 and the fix is ....

When an administrator tries to stop the World Wide Web Publishing Service (W3SVC), the W3SVC remains in a "stopping" state, but cannot fully stop or be restarted.

This issue is resolved in KB4345459.

 

SMUD is on ... G/Technology 10.1 Sp3 and Windows 2008 Server R2. with this issue.    Good Luck everyone


Add a Comment

Please sign in on the right menu to comment.  If you do not have an account, please Join now.