Walter Hofstädtler
Walter Hofstädtler
Hi, I see the same issue with current 64 bit version. Works with any Linux based mail server but will not work with Exchange 2013 or Exchange 2016. Any ideas...
Hi, I am not a compiler guy, so I search for a solution without compiling. Walter
@danwos, thank you, this solved the issue.
Daniel, The output is in the file as requested. Let me know if you need more information. [nmap.txt](https://github.com/user-attachments/files/20665940/nmap.txt)
As requested the attachments, the Powershell command does not generate any output. [nmap_info.txt](https://github.com/user-attachments/files/20940107/nmap_info.txt) [nmap.exe.11332.dmp](https://github.com/user-attachments/files/20940108/nmap.exe.11332.dmp) [nmap.exe.27552.dmp](https://github.com/user-attachments/files/20940109/nmap.exe.27552.dmp)
No, "direct write" is *not* enabled.
It's just strange that these messages appeared after updating to 2.7.10, but not since yesterday. I'll keep watching and let you know if there's any news.
Today I see the issue again. The database is on an SMB share on a Debian Samba server.
I only added about 30 characters to an existing record.
I am sorry, but there are no warnings or errors in the Windows event log at the time I see the error.