Windows Server 2022 Error

Nick McGinnis
Nick McGinnis
Sixth Anniversary Kudos 1 Name Dropper Participant
in Blackbaud CRM Developer Discussions

Hello,

I am experimenting with using Windows Server 2022 for our local CRM environments. After installing I am receiving this error: “Thumbprint node not found in WSFederation config file.” There is a Knowledge Base article saying to disable TLS 1.0 and TLS 1.1, which I have done, and am still receiving this error.

Is Windows Server 2022 not supported or is there something I am missing?

Thanks for any assistance in advance!

Nick McGinnis - DAV

Comments

  • Jori Gelbaugh
    Jori Gelbaugh
    Third Anniversary Name Dropper Facilitator 1 June 2023 Monthly Challenge

    @Nick McGinnis I'm not sure about support for Windows Server 2022, but I received a similar error during an upgrade to SP32 and applying the SystemDefaultTlsVersions registry changes that are documented here resolved the error.

  • Nick McGinnis
    Nick McGinnis
    Sixth Anniversary Kudos 1 Name Dropper Participant

    @Jori Gelbaugh

    That fixed it, thank you for the quick response!

  • Simon Watson
    Simon Watson
    Tenth Anniversary Name Dropper Participant Facilitator 1

    @Jori Gelbaugh @Nick McGinnis
    I'm experiencing a similar issue on a new enviornment I am setting up. I've corrected the TLS issue, however the environment does not have internet/outside access. And so I beleive the issue is it cannot ping sts.sky.blackbaud.com/WSFederation/action which is listed in the WSFederation.config file.

    As our security policy does not allow outside/internet access does anyone know a way to remove or change this WSFederation configuration/requirement?

    The KB article says to allow access to sts.sky.blackbaud.com.

  • Nick McGinnis
    Nick McGinnis
    Sixth Anniversary Kudos 1 Name Dropper Participant

    @Simon Watson

    For our local environments I have to disable the condition setting for WSFederation after a refresh from a hosted environment since locally we use Windows Auth instead of BBID, not sure if this will address your issue but it is the only other related thing I can think of. Hope this helps!

    IF EXISTS (SELECT 1 FROM CONDITIONSETTING WHERE NAME='WSFederation')

    BEGIN

    delete from dbo.CONDITIONSETTING where NAME='WSFederation'

    END

  • Simon Watson
    Simon Watson
    Tenth Anniversary Name Dropper Participant Facilitator 1

    Thanks @Nick McGinnis for the suggestion.

    We are just using a sample DB, which I've checked but it doesn't have that WSFederation conditionsetting.

    I've logged the issue with Blackbaud Support so see if they have any suggestions.

    Thanks again.

Categories