Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
firebird-automations opened this issue Jan 6, 2017 · 2 comments

Comments

@firebird-automations
Copy link
Collaborator

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");

@firebird-automations
Copy link
Collaborator Author

Modified by: Sean Leyne (seanleyne)

description: 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");

=>

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");

@firebird-automations
Copy link
Collaborator Author

Commented by: Jose Zaragoza (pepe_itd_hotmail.com)

F\.D\.Castel how did you solve this issue?

Best Regards

Jose Zaragoza

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant