Skip to content

Windows Server 2016: "Operating system call CryptAcquireContext failed. Error code 127" [CORE5437] #5709

Open
@firebird-automations

Description

@firebird-automations

Submitted by: F.D.Castel (fdcastel)

Firebird 3.0.1 SuperServer installs and runs fine in Windows Server 2016 (service starts ok).

However, when trying to CONNECT the server returns the following error message:

-----
Error occurred during login, please check server firebird.log for details.
-----

The client application and the server are in the same computer.

Looking at firebird.log (oddly found at... \SysWOW64 folder? is this right?) shows me:

-----
APP11 Fri Jan 06 02:12:28 2017
Operating system call CryptAcquireContext failed. Error code 127

APP11 Fri Jan 06 02:12:28 2017
Authentication, client plugin:
operating system directive CryptAcquireContext failed
The specified procedure could not be found.
-----

Firebird was installed with CopyFbClientToSysTask,CopyFbClientAsGds32Task,EnableLegacyClientAuth installer tasks.

This same installation process *WORKS* in Windows 10. This problem occurs *ONLY* in Windows Server 2016.

Also, I can attest the 'advapi32.dll' is the same in both operating systems.

System32\advapi32.dll v10.0.14393.0 (637KB)
SysWOW64\advapi32.dll v10.0.14393.0 (471KB)

I did even check the .DLL with Dependency Walker to ensure that the function exists. It *IS* there!! (CryptAcquireContextW and CryptAcquireContextA)

I'm completely at a loss here. Anyone did test Firebird 3.0.1 in Windows Server 2016?

More info:

https://msdn.microsoft.com/en-us/library/windows/desktop/aa379886(v=vs.85).aspx

Firebird::system_call_failed::raise("CryptAcquireContext");
}
}
else
{
Firebird::system_call_failed::raise("CryptAcquireContext");

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions