Issue Details (XML | Word | Printable)

Key: CORE-5437
Type: Bug Bug
Status: Open Open
Priority: Blocker Blocker
Assignee: Unassigned
Reporter: F.D.Castel
Votes: 0
Watchers: 6

If you were logged in you would be able to see more operations.
Firebird Core

Windows Server 2016: "Operating system call CryptAcquireContext failed. Error code 127"

Created: 06/Jan/17 04:40 AM   Updated: 09/Oct/19 04:52 PM
Component/s: Security
Affects Version/s: 3.0.1
Fix Version/s: None

Environment: Windows Server 2016 Standard

QA Status: No test

 Description  « Hide
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:

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Jose Zaragoza added a comment - 09/Oct/19 04:52 PM
F.D.Castel how did you solve this issue?

Best Regards

Jose Zaragoza