Hi All,
I am getting Orthanc errors in my windows eventlog. When these errors happen othanc hangs. Orthanc is running on Server 2019.
I am using the latest Windows version of Orthanc with a Postgresql 14 DB for the indexing.
If you need any more information please let me know.
With kind regards,
Martin
------------Eventlog---------------------
Log Name: Application
Source: Windows Error Reporting
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: computer
Description:
Fault bucket , type 0
Event Name: BEX
Response: Not available
Cab Id: 0
Problem signature:
P1: OrthancService.exe
P2: 0.0.0.0
P3: 00000000
P4: StackHash_2beb
P5: 0.0.0.0
P6: 00000000
P7: PCH_FE_FROM_ntdll+0x0007031C
P8: c0000005
P9: 00000008
P10:
Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB277.tmp.WERInternalMetadata.xml
These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_OrthancService.e_df8533bfe28ef39efd18fb09f23d6498a81c7a3_672e4850_40be343c
Analysis symbol:
Rechecking for solution: 0
Report Id: f7e9fce7-fb83-4cea-8ba9-e0389e5d1c79
Report Status: 100
Hashed bucket:
Cab Guid: 0
Event Xml:
Hello,
Please carefully read the documentation about how to ask support:
https://book.orthanc-server.com/users/support.html
In particular, you should at least provide the Orthanc logs in “–verbose” mode:
https://book.orthanc-server.com/faq/log.html
Regards,
Sébastien-
Hi Sébastien,
I installed the very latest release of Orthanc
I have run Orthanc in verbose mode and no errors appear in the logfile. The errors also stopped in the eventlog after running Orthanc from the commandline. Therefor my assumption is that the problem is between the Orthancservice.exe file and Windows.
In the worst case senario I can always use a scheduledtask to start orthanc after a reboot.
The slowness of Orthanc was another problem altogether and got resolved when I disabled IPV6 on the nic.
With kind regards,
Martin
Hello Martin,
I don’t have enough information to provide any further guidance.
Please provide us with a way to reproduce your issue (“minimal working example”), otherwise nobody will be able to help you.
Sébastien-
Hi Sébastien,
This problem happens automatically even when nobody is interacting with Orthanc. I understand that you cannot do anything if you cannot reproduce the error 
Do you know if Orthanc will run correctly on a Server 2022 installation? If this is possible I can try upgrading the server and see if this resolves the problem.
Martin
I have never seen anybody reporting an incompatibility of Orthanc with Microsoft Server.
As far as I’m concerned, I only test Orthanc on an old Microsoft Windows XP SP2 32bit virtual machine. Choosing such an old operating system is explained by the fact that Microsoft ensures backward compatibility in its line of products. Obviously, I cannot test Orthanc on each and every flavor of Microsoft Windows.
Regarding your issue, I would bet on a bad configuration file or a permission error. This is why I suggested you to collect the logs out of the “OrthancService.exe” system, by running “Orthanc.exe” manually in “–verbose” mode, as explained in the Orthanc Book:
https://book.orthanc-server.com/faq/log.html#under-windows
Sébastien-
Hi
A few years ago, when I started using Orthanc, I did it with Windows Server 2012 R2, it worked fine but it needed a lot of server resources for it to work. I currently have Orthanc installed on the same computer but with Windows 7 64 bits and it works better, much faster and requires much less resources on the computer.
I think that in our work, the most powerful thing should be Orthanc, not the operating system on which it works. Sometimes simpler is better.
William
Hi William and Sébastien,
Windows 7 is not an option for because the rules of my IT department are that we can only use supported software and Windows 7 is no longer supported.
Can you explain the purpose of the orthancservice.exe and why is this file 32bits in the 64 bits installation?
I’ve tried the following things
Removed Windows defender virusscanner
Updated Windows.
Turned of DEP.
Tried the default Orthanc configuration.
Tried running orthanc from the commandline (“C:\Orthanc Server\Orthanc.exe” --verbose “C:\Orthanc Server\Configuration” > e:\Temp\Orthanc.log 2<&1)
Even when I run orthanc from the commandline I still get the errors in the eventlog
As Bex is a Buffer Overflow Exceptions I included a Screenshot of the memory consumption of the orthanc server.
Attached in the zip file are the evenlogs, orthanc log and the orthanc.json file.
With kind regards,
Martin
files.zip (547 KB)
Hello,
“OrthancService.exe” is the source code of the Windows service that is responsible for starting/stopping the “Orthanc.exe” command line. You can find its source code at the following location:
https://github.com/orthanc-server/orthanc-builder/tree/master/WindowsInstaller/Configuration
“OrthancService.exe” is a 32bit file for compatibility with both 32bit and 64bit distributions of Windows. “Orthanc.exe” is either 32bit or 64bit, depending on the installer you decided to download.
From what I see in the “Orthanc.log” logs you provided, “Orthanc.exe” works just fine, so this is not a misconfiguration issue.
If the “OrthancService.exe” doesn’t work for you, please get in touch with a professional assistance to track down your issue (you can most probably afford this assistance if you have an IT department):
https://book.orthanc-server.com/users/support.html#finding-professional-assistance
An alternative is simply to launch “Orthanc.exe” at the startup of your Windows server. Many tutorials on Internet explain how to do so (make a search about e.g. “launch exe at startup of windows 10” on your favorite Internet search engine, or ask your IT department to help you).
Regards,
Sébastien-