Windows Error Reporting: Difference between revisions

From support-works
Jump to navigation Jump to search
No edit summary
No edit summary
Line 4: Line 4:


<pre>
<pre>
click on LocalDumps > New > Key > enter ServerService.exe
click on HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps > New > Key > enter ServerService.exe
click on ServerService.exe > new > DWORD(32-bit) Value > enter text and hexadecimal value as shown
click on ServerService.exe > new > DWORD(32-bit) Value > enter text and hexadecimal value as shown
click on ServerService.exe > new > Expandible string Value > Enter text as shown with your path as per your Hornbill directory
click on ServerService.exe > new > Expandible string Value > Enter text as shown with your path as per your Hornbill directory

Revision as of 15:43, 16 February 2018

Applicable To = Supportworks ESP

Normally Supportworks runs without issues but in the unlikely event that the Swserver service fails, to assist with determining the root cause the Support team would need to obtain crash dump files that are stored locally on the server. It is far better to have Windows Error Reporting enabled in advance so that in the event of a failure the crash dumps can be investigated immediately. In order to do this, set up the following registry configurations on the server:

click on HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps > New > Key > enter ServerService.exe
click on ServerService.exe > new > DWORD(32-bit) Value > enter text and hexadecimal value as shown
click on ServerService.exe > new > Expandible string Value > Enter text as shown with your path as per your Hornbill directory
click on ServerService.exe > new > DWORD(32-bit) Value > enter hexadecimal value as shown

WER.png