SOLVED

ADFS Server Error 352 after installing KB4088787

%3CLINGO-SUB%20id%3D%22lingo-sub-173608%22%20slang%3D%22en-US%22%3EADFS%20Server%20Error%20352%20after%20installing%20KB4088787%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-173608%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20a%202%20server%20ADFS%20Farm%20with%20a%20Windows%20Internal%20Database%20on%20Windows%20Server%202016%20hosted%20in%20azure.%20Yesterday%20after%20ADFS01%20updated%3CSTRONG%3E%26nbsp%3B%3C%2FSTRONG%3E2018-03%20cumulative%20update%20for%20Windows%20Server%202016%20the%20Service%20stopped%20working%20and%20showed%20the%20behavior%20as%20shown%20in%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fhochwald.net%2Fkb4077525-caused-issues-adfs-servers%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fhochwald.net%2Fkb4077525-caused-issues-adfs-servers%3C%2FA%3E%20and%20it%20even%20took%20down%20ADFS02%20which%20had%20already%20installed%20that%20update%20the%20week%20before.%20I%20tried%20restoring%20the%20server%20using%20azure%20backup%20from%20the%20day%20before%20yet%20the%20error%20persisted.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20the%20end%20I%20restored%20to%20a%20point%20in%20time%20were%20even%202018-02%20cumulative%20update%20was%20not%20installed%20and%20everything%20worked%20although%20I%20also%20had%20to%20restore%20ADFS02%20to%20the%20same%20point%20in%20time%20to%20get%20it%20to%20work%2C%20too.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIronically%2C%20the%20update%20I%20installed%20was%20the%20one%20that%20should%20have%20fixed%20an%20ADFS%20error%20caused%20by%202018-02%2C%20which%20didn't%20occur%20in%20my%20environment%20to%20begin%20with.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESince%20I%20am%20using%20update%20management%20in%20azure%20how%20am%20I%20supposed%20to%20get%20to%20a%20current%20build%20without%20destroying%20ADFS%3F%20Should%20I%20wait%20for%20the%20next%20CU%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20am%20afraid%20of%20reapplying%20the%20updates%20since%20I%20fear%20they%20will%20break%20my%20servers%20again%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-173608%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EManagement%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-180632%22%20slang%3D%22en-US%22%3ERe%3A%20ADFS%20Server%20Error%20352%20after%20installing%20KB4088787%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-180632%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20the%20link%20somehow%20the%20march%20cu%20which%20caused%20the%20problem%20for%20me%20didn't%20cause%20any%20issues%20this%20time%20arround%2C%20maybe%20because%20the%20feburary%20cumulative%20update%20was%20not%20installed%20before%20on%20the%20restored%20vm.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-179996%22%20slang%3D%22en-US%22%3ERe%3A%20ADFS%20Server%20Error%20352%20after%20installing%20KB4088787%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-179996%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20one%20may%20sort%20it.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4096309%2Fmarch27-2018kb4096309osbuild14393-2156%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4096309%2Fmarch27-2018kb4096309osbuild14393-2156%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-179636%22%20slang%3D%22en-US%22%3ERe%3A%20ADFS%20Server%20Error%20352%20after%20installing%20KB4088787%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-179636%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Fabio%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ethanks%20for%20the%20information%2C%20I%20will%20try%20to%20install%20that%20patch%20next%20week%20and%20see%20if%20it%20helps.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ERegards%3C%2FP%3E%0A%3CP%3ECarsten%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-176851%22%20slang%3D%22en-US%22%3ERe%3A%20ADFS%20Server%20Error%20352%20after%20installing%20KB4088787%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-176851%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Carsten%2C%3C%2FP%3E%0A%3CP%3Ei%20had%20the%20same%20problem%2C%20i%20have%20resolved%20with%20the%20installation%20of%20patch%20KB4088889.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThank%20You%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFabio%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

I have a 2 server ADFS Farm with a Windows Internal Database on Windows Server 2016 hosted in azure. Yesterday after ADFS01 updated 2018-03 cumulative update for Windows Server 2016 the Service stopped working and showed the behavior as shown in https://hochwald.net/kb4077525-caused-issues-adfs-servers and it even took down ADFS02 which had already installed that update the week before. I tried restoring the server using azure backup from the day before yet the error persisted.

 

In the end I restored to a point in time were even 2018-02 cumulative update was not installed and everything worked although I also had to restore ADFS02 to the same point in time to get it to work, too.

 

Ironically, the update I installed was the one that should have fixed an ADFS error caused by 2018-02, which didn't occur in my environment to begin with.

 

Since I am using update management in azure how am I supposed to get to a current build without destroying ADFS? Should I wait for the next CU?

 

I am afraid of reapplying the updates since I fear they will break my servers again

4 Replies
Highlighted

Hello Carsten,

i had the same problem, i have resolved with the installation of patch KB4088889.

 

Thank You 

 

Fabio 

Highlighted

Hi Fabio,

 

thanks for the information, I will try to install that patch next week and see if it helps.

 

Regards

Carsten

Highlighted
Best Response confirmed by Carsten Stahlberg (Occasional Contributor)
Highlighted

Thanks for the link somehow the march cu which caused the problem for me didn't cause any issues this time arround, maybe because the feburary cumulative update was not installed before on the restored vm.