Service suddenly stopped working

[djockheck]

This is the only message I got after I started my Veeam Agent Backup (free version). In the eventlog I saw that something happed to sqlservr.exe but the mentioned logs are not usefull to me.
<cut>
Fehlerbucket , Typ 0
Ereignisname: SQLException64
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: sqlservr.exe
P2: 2011.110.7001.0
P3: 0000000059936D60
P4: sqlDK.dll
P5: 2011.110.7001.0
P6: 00000000599371C6
P7: -1073741819
P8: 0000000099999999
P9: 0000000007547F25
P10:

Angefügte Dateien:
C:\\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\VeeamEndPoint\SQLDump0011.mdmp
C:\\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\VeeamEndPoint\SQLDump0011.txt
C:\\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\VeeamEndPoint\SQLDump0011.log

Diese Dateien befinden sich möglicherweise hier:


Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 1a9fa8c1-12c6-11eb-adfb-0002b3ca386c
Berichtstatus: 0
</cut>

[djockheck]

I tried the mentioned steps from kb1959 but this did'nt solve the issue.

[Egor Yakovlev]

Hi Detlef,

make sure to share opened support case ID when opening a technical issue thread on Veeam Community Forums.
Something is interfering with SQL server on your server it seems, and it is best to troubleshoot with Veeam Support rather than catching wild guesses on the forum.

/Thanks!

[djockheck]

Solved: In my case it was an interference with traps from palo alto.

[Egor Yakovlev]

Thanks for update. Glad it sorted out.

/Cheers!

[sash]

Hi djockheck,
may I ask how you solved that with traps? Have you excluded directories in traps? If yes, which?

[Egor Yakovlev]

We have a general recommended Agent Antivirus Exclusions list, unless there were some specific edits to PA.
/Cheers!

[sash]

Hi, we have already excluded the folders from article KB2034 in Paloalto Cortex, but the problem still persists. What else was being done here?

[shagedorn]

Also having the same issue with service suddenly stopped working. We have added the folders to the Palo Alto Cortex/Traps whitelist but it is still occuring.

[nitramd]

@sash & @shagedorn,

Have a look at my post in this thread: veeam-agent-for-windows-f33/veeam-agent ... ml#p392772

Please be aware that there could be a minor side effect implementing this solution but I brought it up in the post.

Can you post back your results?

Hope this helps.

[sash]

we had the same situation as in the thread by @nitramd that we only had the problem on some systems and not on all systems. It must be related to how the update from the last Paloalto Traps to the new Cortex version took place. It looks like that the clients with which the update was carried out via the Cortex WebConsole have the problem and the problem does not exist with a manual update directly on the client. I have uninstalled and reinstalled Cortex on clients with the problem (manually on the client). The problem with the Veeam Agent did not appear after that.

I hope this works for you too. Please try it and give it a reply!!