Windows 10 AU + WSE 2012 Connector problems

[Quartz-1]

This workstation is running W10 AU and my server is running WSE 2012 (NOT R2) and now the Connector software is reporting a version mismatch.

I'm seeing lots of errors in the System event log about WSE services not starting, and errors in the Application event log as below in the spoiler:

Spoiler

Log Name: Application
Source: Application Error
Date: 06/10/2016 15:08:29
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: QPC.AlbertDen.local
Description:
Faulting application name: WseClientSvc.exe, version: 6.2.9805.10, time stamp: 0x578eac4d
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x80131623
Fault offset: 0x00007ffca88e1015
Faulting process ID: 0x27d4
Faulting application start time: 0x01d21fdb1cec164d
Faulting application path: C:\Program Files\Windows Server\Bin\WseClientSvc.exe
Faulting module path: unknown
Report ID: d1ec2c58-177e-4498-a80e-27ab8fe96103
Faulting package full name:
Faulting package-relative application ID:

Log Name: Application
Source: .NET Runtime
Date: 06/10/2016 15:08:36
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: QPC.AlbertDen.local
Description:
Application: LANConfigSvc.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileLoadException
at Microsoft.WindowsServerSolutions.CoreNetworking.LANConfigSvc.LANConfig.Main(System.String[])

Log Name: Application
Source: Windows Error Reporting
Date: 06/10/2016 15:08:29
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: QPC.AlbertDen.local
Description:
Fault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: WseClientSvc.exe
P2: 6.2.9805.10
P3: 578eac4d
P4: mscorlib
P5: 4.6.1586.0
P6: 575a1530
P7: 3805
P8: 8
P9: System.ArgumentNullException
P10:

Got any suggestions?

 

[bigdogchris]

Is this related? Windows 10 Feature Upgrade breaks client connector for Window Server 2012 R2 Essentials, Windows Server 2012 Essentials and Windows Small Business Server 2011 Essentials

Have you tried removing the connection and reconnecting?

Have you ran Windows Update (and check the box to give updates for other Microsoft updates) on both client and server? They may have deployed compatibility fixes through updates.

 

[Quartz-1]

I have fixed this. The fix in the linked article didn't work. I had to remove both the connector and something else. Unfortunately, I forgot to make a note of it, but I recall it being related.