[РЕШЕНО]: 1С ошибка 1053 служба не ответила на запрос своевременно | ragent has stopped working" (APPCRASH) | Прекращена работа программы 1C | ragent rserver exception code c0000005

В моём случае причиной ошибки был антивирус. Дальше разбирайтесь с антивирусом (отключайте/лечите/добавляйте исключения).

Проверьте журнал системы (Event Viewer -> Windows Logs -> System):

"Microsoft Antimalware has detected malware or other potentially unwanted  software." (Source: Microsoft Antimalware, Event ID: 1116)

Microsoft Antimalware has detected malware or other potentially unwanted software.
 For more information please see the following:
http://go.microsoft.com/fwlink/?linkid=37020&name=PUA:Win32/Packunwan&threatid=298189&enterprise=1
     Name: PUA:Win32/Packunwan
     ID: 298189
     Severity: Severe
     Category: Potentially Unwanted Software
     Path: file:_C:\Program Files\1cv8\8.3.12.1529\bin\x ;file:_C:\Program Files\1cv8\8.3.9.2309\bin\x
     Detection Origin: Local machine
     Detection Type: Concrete
     Detection Source: Real-Time Protection
     User:      Process Name: C:\Program Files\1cv8\8.3.12.1529\bin\rphost.exe
     Signature Version: AV: 1.421.263.0, AS: 1.421.263.0, NIS: 0.0.0.0
     Engine Version: AM: 1.1.24090.11, NIS: 0.0.0.0

P.S. Если запустить службу как процесс в командной строке
(Пуск - cmd с правами администора - "C:\Program Files\1cv8\8.3.9.2309\bin\ragent.exe" -srvc -agent -regport 1741 -port 1740 -range 1760:1791 -d E:\1c_log\1cv82\srvinfo\ -debug)
То вы увидите "ragent has stopped working" (APPCRASH), в русской версии Windows это скорее всего переводится как "Прекращена работа программы"

 

ragent rserver exception code c0000005

#1C #1С

 

[SOLVED] HKLM:\SOFTWARE\Policies\Microsoft\Windows Defender' Exclusion Path. Reg file. Windows Server 2016

Reg file exported from Windows Server 2016 after applying "Add-MpPreference -ExclusionPath "C:\Program Files\XYZ" command.

I've tested importing that reg file on Windows 2012 R2, but "exclusion path" did not work (was not applied) (however I did not test reboot, since that was a production server, so possibly reboot will work for you)

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Defender\Exclusions]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Defender\Exclusions\Extensions]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Defender\Exclusions\Paths]
"C:\\Program Files\\XYZ\\"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Defender\Exclusions\Processes]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Defender\Exclusions\TemporaryPaths]

[SOLVED by workaround]: Windows Server 2012 R2 + Add exclusion for Windows Defender (Microsoft Antimalware). Add-MpPreference: The term 'Add-MpPreference' is not recognized as a name of a cmdlet, function, script file, or executable program.

 So I found in EventLogs (Event Viewer -> Windows Logs -> System) following error:

"Microsoft Antimalware has detected malware or other potentially unwanted  software." (Source: Microsoft Antimalware, Event ID: 1116)

Then I decided to add one particular file to the exclusion list of Windows Defender.
Brief googling showed basic approaches how I can do it:

• Via Domain Group Policies
  
• Via Local Group Policies
• Via Powershell (using Add-MpPreference and/or Set-MpPreference)
• Via Registry customization 
• UPDATE: Via Defender for Endpoint package
• Via System Center Endpoint Protection / SCCM
  

On Windows Server 2012R2 I was unable to do it:

Add-MpPreference: The term 'Add-MpPreference' is not recognized as a name of a cmdlet, function, script file, or executable program.

And beside that Microsoft claims that Powershell 4.0 (which was my version of Powershell on Windows Server 2012R2) should have this functions working, it turned out that it doesn't. (I've checked it on two different systems).

What I've done - I've used Powershell's Add-MpPreference on Windows Server 2016 (I was able to launch it successfully just on Windows 2016), and then exported settings from HKLM:\SOFTWARE\Policies\Microsoft\Windows Defender' from Windows 2016, and then imported reg file into Windows 2012R2, but it did not work (there still was the same unwanted blocking behaviour of some executables).

So my solution was: to move my file (which was blocked by Windows Defender) to Windows Server 2016 and then add exclusion with Powershell by running "Add-MpPreference -ExclusionPath "C:\Program Files\XYZ".
Yes, it's quick and dirty solution, but I did not have enough time for more experiments.

For those who still want too add exclusion to Microsoft Defender exactly on Windows Server 2012R2, I could recommend to explore Group Policy method more thoroughly.
(you can also try to reboot your server after mentioned above registry changes, I was unable to test it on my production server however).

UPDATE (found on microsoft forum) :

"The Defender PowerShell module isn't available in Server 2012, but you can install it and run it in Passive mode.

Is the Defender for Endpoint package installed?"

[https://learn.microsoft.com/en-us/microsoft-365/security/defender-endpoint/configure-server-endpoints?view=o365-worldwide#windows-server-2012-r2-and-windows-server-2016

[SOLVED] "Fatal error: Uncaught Error: Call to undefined function xdebug_info()"

 "Fatal error: Uncaught Error: Call to undefined function xdebug_info()"

This error could happen if xdebug.ini was not included (as configuration) properly.
In my case xdebug.ini was in "mods-available", but not in "conf.d" directory.

Try this:
ln -s /etc/php/7.4/mods-available/99-xdebug.ini /etc/php/7.4/apache2/conf.d/99-xdebug.ini

And then reload your apache/php-fpm service

[SOLVED]: "Unknown mode: 117". Error creating empty image subvolume. UrBackup

Solution: UrBackup Server Web-Interface - Settings - Clients - your_buggy_client - Image Backups - Image backup file format - Change it!

In my case it turned out that I was using "Raw copy-on-write file" option with Windows client which is most likely not supported on Windows. I've set it to "Compressed VHDX (Compressed non-standard Virtual HardDisk v2) (beta)" and this made it work!

Example of logs:

(Server side, Web-Interface - Logs)

    Errors
    10/21/24 16:43
    Error creating empty image subvolume. "Unknown mode: 117"
    Errors
    10/21/24 16:43
    Error creating image backup destination.
    Errors
    10/21/24 16:43
    Backup failed

(Client side, C:\Program files\UrBackup\debug.log)

    0-1729518191-Basing image backup on last incremental or full image backup
    1-1729518191-Error retrieving last image backup. Doing full image backup instead.
    2-1729518191-Error creating empty image subvolume. "Unknown mode: 117"
    2-1729518191-Error creating image backup destination.
    0-1729518191-Time taken for backing up client buggy_client_hostname: 246ms
    2-1729518191-Backup failed

[SOLVED]: DPM Error (0x800423F4) or DPM (ID 3114) or DPM (ID 30111) VssError:The writer experienced a non-transient error. Or Backup Exec: 0xe000943f - Database s failed to freeze for backup. This can be caused if the database is in a state that does not support backup; such as offline, standby, or recovering.

I got my server backed up by DPM and Backup Exec, thus I had warnings from both backup solutions (error codes/IDs listed below).

At first check output of the command "VSSadmin List writers" 

if you'll see output like this: "Writer name: 'SqlServerWriter' State: [8] Failed Last error: Non-retryable error"

then just reboot your SQL server OS which is used for database in your SharePoint setup.

 

Symptoms :

DPM 2016 (Data Protection manager)

            Recovery point creation jobs for Microsoft Hyper-V xxxyyzz on xxxyyzz have been failing. The number of failed recovery point creation jobs = 1.

            If the data source protected has some dependent data sources (like a SharePoint Farm), then click on the Error Details to view the list of dependent data sources for which recovery point creation failed. (ID 3114)

           

             The VSS application writer or the VSS provider is in a bad state. Either it was already in a bad state or it entered a bad state during the current operation. (ID 30111 Details: VssError:The writer experienced a non-transient error.  If the backup process is retried,

            the error is likely to reoccur.

            (0x800423F4))

           

             Please check that the Event Service, the VSS service and the shadow copy provider service is running, and check for errors associated with these services in the Application Event Log on the server xxyyzz. Please allow 10 minutes for VSS to repair itself and then retry the operation.

            For more information on this error, go to http://go.microsoft.com/fwlink/?LinkId=132612.

 

Backup Exec

            Backup- ConfigurationV5-DB (xxyyzz\xx\SharePoint_Config)V-79-57344-37951 - Database SharePoint_Config has failed to freeze for the snapshot backup.

 

            Job Completion Status

            Job ended: 13 марта 2024 г. at 19:52:20

            Completed status: Failed

            Final error: 0xe000943f - Database s failed to freeze for backup.  This can be caused if the database is in a state that does not support backup; such as offline, standby, or recovering.  

            Final error category: Other Errors

 

            For additional information regarding this error refer to link V-79-57344-37951

[SOLVED]: How to fix DPM 40003 error (Data Protection Manager 2016)

Summary: DPM fails with error 40003 complaining either on DPM agent's or DPM server's storage.
It seems the real reason (in my case) behind this error was that the last backup taken was corrupted!
(Furthermore, in my case it turned out that RAID array was in the degraded state on DPM server's storage side. So it's better for you to CHECK YOUR DISK SUBSYSTEM and RAID STATUS!!! of both client and server). 

To fix it you need to delete last (possibly corrupted) backup (or Recovery Point in terms of DPM).
However you can't do it via GUI, only from Powershell.
Basic concept to do it is as follows:
* Determine Protection group of that RecoveryPoint
* Determine Datasource of that RecoveryPoint
* Determine the last RecoveryPoint available for that Datasource
* Delete it.
This helped me a lot of times (even with degraded RAID!).

Don't forget to launch Powershell with elevated/administrator privileges.

$pg = Get-ProtectionGroup -DPMServerName your_DPM_server | where {$_.Name -eq "MSSQL System Databases" }

Get-Datasource -ProtectionGroup $pg | where {$_.Computer -like "*computer_with_DPM_agent*"  } |where {$_.Name -eq "msdb" }

$ds = Get-Datasource -ProtectionGroup $pg | where {$_.Computer -like "*computer_with_DPM_agent*"  } |where {$_.Name -eq "msdb" }

Get-RecoveryPoint -Datasource $ds |Sort-Object -property BackupTime

Get-RecoveryPoint -Datasource $ds |Sort-Object -property BackupTime |select-object -last 1

$rp = Get-RecoveryPoint -Datasource $ds |Sort-Object -property BackupTime |select-object -last 1

echo $rp

Remove-RecoveryPoint -RecoveryPoint $rp 

Update: I noticed that after rebooting DPM server this error almost gone (while still running with degraded RAID 5!). I guess it's because of hard swapping issues and hence slow disk subsystem due to degraded RAID - it was partially solved by reboot.
So simple reboot of DPM server may also help you!

Original idea taken from here:
[1] https://social.technet.microsoft.com/Forums/en-US/30f8ef3f-1d20-42ae-bffb-dab49fdea0fc/quoterror-40003-the-storage-involving-the-current-operation-could-not-be-read-from-or-written?forum=dataprotectionmanager
[2] https://www.jfe.cloud/how-to-delete-a-specific-recovery-point-in-dpm/