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

Keepasshttp plugin compilation fails with keepass 2.34 #293

Open
bennodepenno opened this issue Nov 4, 2016 · 7 comments
Open

Keepasshttp plugin compilation fails with keepass 2.34 #293

bennodepenno opened this issue Nov 4, 2016 · 7 comments

Comments

@bennodepenno
Copy link

Hi,

On my archlinux machine, I'm running into a plugin compile error when launching keepass 2.34. I've started keepass with --debug parameter which shows
screenshot from 2016-11-04 11-00-44

My mono version: Mono JIT compiler version 4.6.1 (Stable 4.6.1.3/abb06f1 Mon Oct 3 07:51:42 UTC 2016)
My kernel: Linux winecup 4.7.6-1-ARCH #1 SMP PREEMPT Fri Sep 30 19:28:42 CEST 2016 x86_64 GNU/Linux

I've tried the clear cache option in keepass, removing ~/.local/share/KeePass/PluginCache/* and I've verified that the files KeePassHttp.dll and Newtonsoft.Json.dll on my system are exactly the same as in github's mono directory.

Any help would be appreciated in solving this problem. Thank you in advance.

Regards,

Ben

@Suvidu
Copy link

Suvidu commented Dec 6, 2016

I have the same problem with Windows (10). After copying the file into the appropriate folder, KeePass tells me after starting that this plugin is incompatible with this version of KeePass.

@craigchandler
Copy link

Here is the windows 10 dialog

[Window Title]
KeePass

[Content]
The following plugin is incompatible with the current KeePass version:
C:\Users\Me\AppData\Local\KeePass\PluginCache\Dd4geUqZK9CXILcfL28z\KeePassHttp.dll

Have a look at the plugin's website for an appropriate version.

[Expanded Information]
Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
System
at System.Net.UnsafeNclNativeMethods.SetFileCompletionNotificationModes(CriticalHandle handle, FileCompletionNotificationModes modes)
at System.Net.HttpListener.CreateRequestQueueHandle()
at System.Net.HttpListener.Start()
at KeePassHttp.KeePassHttpExt.Initialize(IPluginHost host)
at KeePass.Plugins.PluginManager.LoadPlugins(List`1 lFiles, String strTypeName, String strDisplayFilePath, Boolean bSkipCacheFiles)
Boolean SetFileCompletionNotificationModes(System.Runtime.InteropServices.CriticalHandle, FileCompletionNotificationModes)

[^] Details [OK]

@pfn
Copy link
Owner

pfn commented Dec 13, 2016

This should hopefully resolve itself when I get around to merging #289

@craigchandler
Copy link

Thanks for the heads up, I can confirm the linked fork is working for me here on windows 10

@penascimento
Copy link

Hurray!!! this fork is working for my windows 10 also!!! thanks a lot!

@pdbogen
Copy link

pdbogen commented Dec 20, 2016

Incidentally, on Linux, I observed this proximate problem (that the plugin didn't work after an upgrade); but I found that it was because there was a residual Mono process running that was holding open port 45531.

@theob88
Copy link

theob88 commented Jan 5, 2017

I can confirm the following worked to fix my installation on a Windows 10 machine. Quoted from the following thread: #275

"I had the exact same problem with Windows 10 x64. I did some research with the exception message and found another thread that had a problem with "SetFileCompletionNotificationModes". In this case the culprit was a buggy uninstalling of a Lavasoft software (Ad-Aware) which left the LavasoftTcpService64.dll in the System32 directory."

"Simply reset the Winsock Catalog from the command prompt as an admin:

netsh winsock reset

Then, restart your PC and delete the buggy files from:

C:\WINDOWS\system32\LavasoftTcpService64.dll
C:\WINDOWS\SysWOW64\LavasoftTcpService.dll"

I've read elsewhere that some people only had to do the winsock reset but I deleted the lavasoft files anyway since I don't have Ad Aware installed anymore. Hope this helps!

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

No branches or pull requests

7 participants