Table of Contents
PC running slow?
If you see event ID 57860, this guide should help.
Item: 100016185
Last Published: 05.12.2017
Votes: 0 0
Problem
PC running slow?
ASR Pro is the ultimate solution for your PC repair needs! Not only does it swiftly and safely diagnose and repair various Windows issues, but it also increases system performance, optimizes memory, improves security and fine tunes your PC for maximum reliability. So why wait? Get started today!
Event ID: 57860 “An error occurred while connecting to the following website … SQL error number:” 0011 “” appears when backing up a server with SQL installed.
Error Message
Event ID: 57860 Source: Backup Exec Type: Error Description: An error occurred while trying to log on to save the server “SERVER NAME”. SQL error number: “0011”. SQL error message: “[DBNETLIB] [ConnectionOpen (Connect ()).] SQL No device or access denied.
The following issue and related error has also been seen in some versions of Exec Backup:
Quick backup with error “V-79-57344-3844 – The media server could not connect to the remote agent on the computer.” Error executable file Beremote.Application in module bedql2.dll
V-79-57344-3844 – The media server was unable to connect to the remote agent on the computer.
The multimedia forum uses an attempt A local agent to complete the operation. You cannot initialize the remote agent.
Event ID: 57860 “An error occurred while trying to connect to some of the following servers // XXXX. Number of SQL errors: “0011” “appears when backing up a solid state server with SQL installed.
Reason
Another corrupted SQL database on the remote computer.
Solution
This error also requires Microsoft SQL Server Desktop Engine (MSDE) when performing any type of backup from a server that is running Microsoft SQL Server, sometimes even while performing a SQL Agent backup. Bedql2.dll is always initialized and loaded on every server running the Backup Exec Remote Agent Service, regardless of whether a SQL and Real Estate Agent license is installed.
1. On the SQL Server, stop the Backup Exec Remote Agent service using the Windows Control Panel n Services.
2. When SQL is created on a media server (that is, when SQL is on the same computer as Backup Exec), it is often found using Windows Explorer to findand the default Backup Exec installation directory this:
If SQL is installed on a remote server, go to the installation directory of the remote agent:
four. Rename this bedql2.dll File bedql2.old
4. Start Backup Exec Services.
If this SQL / MSDE is installed on the remote server:
1. Stop the Remote Agent service on the remote server.
2. Rename this Bedql2.dll also bedql2.old for a remote server.
3. Start the new Remote Service Agent.
4. Typically, restart the Backup Exec services on the secondary computer.
5. Save the task and continue checking the result.
Warning: rename Bedsql2.Dll will efficiently and safely disable the SQL agent on the device it is renamed to. If the SQL agent is obtained while it is still alive, the problem with corrupted databases should always be resolved first and by backing up the SQL servers on which Bedsql2.dll has been modified – desired The content of bedql2.old MUST be renamed to bedql2.dll.
Improve the speed of your computer today by downloading this software - it will fix your PC problems.
Como Resolver O Incidente ID 57860
Как разрешить идентификатор объекта 57860
Comment Sur Le Marché Résoudre L’ID D’événement 57860
Cómo Resolver El ID De Evento 57860
Come Eliminarsi ID Evento 57860
Jak Rozwiązać Zdarzenie O Identyfikatorze 57860
Wie In Bezug Auf Das Auflösen Der Ereignis-ID 57860
Hur Man Löser Dag -ID 57860
이벤트 ID 57860 해결 방법
Activiteits-ID 57860 Oplossen
