Home > Event Id > Event Id 57860 Symantec

Event Id 57860 Symantec

If the Agent cannot connect to a SQL instance, this error message will be present. If you are experiencing a similar issue, please ask a related question Suggested Solutions Title # Comments Views Activity We have EMC Networker and it is taking an image level backup Sorry, we couldn't post your feedback right now, please try again later. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by HomeForumsServer RackBack-up SystemsSymantec: Backup Exec back-up Forum Error 4818 Event http://computerhelpdev.com/event-id/event-id-41008-symantec.php

No Yes Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES Restart the Backup Exec services on the media server.5. Terms of use for this information are found in Legal Notices.

Related Articles Article Languages x Translated Content Please note that this document is a translation from English, and may Marked as answer by Naomi NModerator Monday, May 23, 2011 11:12 PM Edited by Kisha_sp Sunday, May 29, 2011 6:29 PM Monday, May 23, 2011 8:44 PM Reply | Quote 0

Review job log for details. RE: Error 4818 Event ID 57860 sjvapcd (Programmer) 12 Aug 05 13:07 Thanks for posting this issue.We are having same problem,we updated from version 9.x to 10 of Backup Exec. Join the community of 500,000 technology professionals and ask your questions.

SQL error message: "[DBNETLIB] [ConnectionOpen (Connect () ). Also check the rest of your event log 0 Message Author Comment by:buckstaff ID: 207877202008-01-31 Job ended: Friday, January 25, 2008 at 4:57:21 AM Completed status: Canceled The job was Note: This is applied for all SQL versions, SQL 2000, SQL 2005, SQL 2008, SQL 2008 R2.   Terms of use for this information are found in Legal Notices.

Related For more information, click the following link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtmlWe did whatever was in that link above but didn't solve the problem...Thanks RE: Error 4818 Event ID 57860 steveot (IS/IT--Management) 15 Jul 05

x 3 Pavel Dzemyantsau - Error number: 4814, error message: "Login failed for user ". Workaround: Perform the following to resolve this issue: 1. SQL error message: "[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied   Details:   This error will occur when performing any type of backup on a server running Microsoft SQL http://thebackroomtech.com/2009/03/18/fix-event-id-57860-an-error-occurred-while-attempting-to-log-in-to-the-following-server-sql-error-number-0011-is-seen-when-backing-up-a-server-with-sql-installed/ Create/Manage Case QUESTIONS?

The SQL Agent logs this event when it attempts to exclude files from active databases during backup jobs. No Yes Did this article save you the trouble of contacting technical support? SQL error number: "". Log onto the Backup Exec Central Administration Server.

Error Message Event ID: 57860Source: BackupExecEngineType: ErrorDescription: There was a problem backing up or restoring data with a SQL Server.   Cause This error occurs when the credentials used by a SQL error message: "[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. ". Veritas does not guarantee the accuracy regarding the completeness of the translation. Wednesday, May 18, 2011 4:25 AM Reply | Quote 0 Sign in to vote No problem.

If SQL is installed on the media server (i.e. weblink I traced it down to an installation of HP Web Jet Admin ver. 10 which uses a SQL instance. Cancel Red Flag SubmittedThank you for helping keep Tek-Tips Forums free from inappropriate posts.The Tek-Tips staff will check this out and take appropriate action. Join our community for more solutions or to ask questions.

Register now while it's still free! SQL error number: "0011"" is seen when backing up a server with SQL installed. Rename the bedssql2.dll file to bedssql2.old4. navigate here SQL error number: "0011"" is seen when backing up a server with SQL installed.

Solution: This error message is benign and can be safely ignored. Submit a False Positive Report a suspected erroneous detection (false positive).

Information for: Enterprise Small Business Consumer (Norton) Partners Our Offerings: Products Products A-Z Services Solutions Connect with us: Support You may also refer to the English Version of this knowledge base article for up-to-date information.

Here is another post with similar issues.

http://www.experts-exchange.com/Storage/Backup_Restore/Backup_Exec/Q_22728213.html 0 Message Author Comment by:buckstaff ID: 207878072008-01-31 The only thing I found in the Application Event Log was shortly after the backup began to run Event ID: 57860 An See example of private comment Links: Veritas TechNote ID: 264616, Veritas TechNote ID: 246587, Veritas TechNote ID: 274303, Event ID 18452 from source MSSQLSERVER Search: Google - Bing - Microsoft - For more information, click the following link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml The link shows solution but i do not want to diable my SQL server Agent.Does anyone know why it is occurin The Windows event will contain the media server name, the job name, and the name of the user who canceled the job.

It is possible that updates have been made to the original version after this document was translated and published. Article:000026494 Publish: Article URL:http://www.veritas.com/docs/000026494 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in Run the Backup job and check the result.WARNING:  Renaming the bedssql2.dll will effectively disable the SQL agent on the server it is renamed upon.  If the SQL agent is purchased in http://computerhelpdev.com/event-id/event-id-8-crypt32-symantec.php Submit a Threat Submit a suspected infected fileto Symantec.

if SQL is on the same machine as Backup Exec), within Windows Explorer browse to the installation directory for Backup Exec, which by default is:\Program Files\VERITAS\Backup Exec\NT (Figure 1)for 11d and SQL error number: "0011"" is seen when backing up a server with SQL installed. Feedback: Send comments or solutions - Notify me when updated Printer friendly Subscribe Subscribe to EventID.Net now!Already a subscriber? Start the Backup Exec services If the SQL/MSDE is installed on a Remote Server: 1.

Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! SQL error number: "0011". Solution Perform the following to resolve this issue:1. x 4 Matthew C.

Close Box Join Tek-Tips Today! Already a member? Run the Backup job and check the result. Miller If the 0011 error is in reference to the "SBSMONITORING" database on a 2003 Small Business server, this is due to the integrated monitoring not being set up, so the

Translated Content This is machine translated content Login to Subscribe Please login to set up your subscription. SQL error message: "[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. No Yes How can we make this article more helpful? x 3 EventID.Net - Error number: 0011, error message: "SQL Server does not exist or access denied" - See Veritas TechNote ID: 264616.

Close this window and log in. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? No Yes How can we make this article more helpful? Or you are searching for a contact that you erased from your MS Outlook ‘Contacts’ folder and now realized that it was important.

Rename the bedssql2.dll file to bedssql2.old on the remote server. 3. Start the Remote Agent service. 4. Event ID: 57860 "An error occurred while attempting to log in to the following server //XXXX.