Home > Error Event > Error Event 57860

Error Event 57860


All the other services that have anything to do with SQL (such as MSSQL$BKUPEXEC) has veritas_sa as the log on account. SQL error number: "0011"" is seen when backing up a server with SQL installed. No Yes May I suggest that you look at some of these http://www.google.com.au/search?source=ig&hl=en&rlz=&=&q=SQL+error+number%3A+%220011%22.+SQL+error+message%3A+&aq=f&aqi=&aql=&oq=Jeff Wharton MSysDev (C.Sturt), MDbDsgnMgt (C.Sturt) MCT, MCPD, MCITP, MCDBA, MCSD, MCAD Tuesday, May 17, 2011 11:42 PM Reply | Quote click site

you can assign this by going : Right click -->properties --> Security-->if you do not see the user add it and give it full control In my case there was That said, I quick search in Google which produced a number of reasons why this error occurs. Select Storage from the tabs along the ribbon bar as the top: Ensure the proper storage devi… Storage Software Windows Server 2008 Native Backup on Windows 7 Video by: Thomas The 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 https://www.veritas.com/support/en_US/article.TECH29539

Error Event 57860

Don't have a SymAccount? You either need the SQL agent to do this, or Go to Solution 6 Comments LVL 23 Overall: Level 23 Windows Server 2003 20 Storage Software 3 Message Active 5 CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical Restart the Backup Exec services on the media server.5.

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 - The sa password is null. For more information, click the following link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml

Aug 13, 2010 Während der Anmeldung an folgendem Server trat ein Fehler auf: "WHTSBAAN01". 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

Join Now For immediate help use Live now! It is possible that updates have been made to the original version after this document was translated and published. Wednesday, May 18, 2011 4:25 AM Reply | Quote 0 Sign in to vote No problem. x 5 Private comment: Subscribers only.

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 If SQL is installed on the media server (i.e. If the Agent cannot connect to a SQL instance, this error message will be present. You’ll be auto redirected in 1 second.

Recommend Us Quick Tip Connect to EventID.Net directly from the Microsoft Event Viewer!Instructions Customer services Contact usSupportTerms of Use Help & FAQ Sales FAQEventID.Net FAQ Advertise with us Articles Managing logsRecommended check over here Join the IT Network or Login. Error Event 57860 SQL-Fehlermeldung: "Login failed for user 'PROJECTINA\svcbackup'. ". Has this happened to anyone?

Get 1:1 Help Now Advertise Here Enjoyed your answer? http://invictanetworks.net/error-event/error-event-15000.html Email Reset Password Cancel Need to recover your Spiceworks IT Desktop password? The data field contains the error numberNext Next post: How to completely disable DEP in Windows Server 2003 Proudly powered by WordPress Developer Network Developer Network Developer :CreateViewProfileText: Sign in MSDN Start the Backup Exec servicesIf the SQL/MSDE is installed on a Remote Server:1.

  1. It is not a major issue but we do have a lot of SQL servers and it would be nice not to be bombarded with alert mails every morning.Thanks.Mike Cracknell Labels:
  2. Thank You!
  3. If SQL is installed on the media server (i.e.
  4. Veritas_sa has been granted access to the BKUPEXEC database.
  5. 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
  6. SQL error number: "0011".
  7. Per Symantec's instructions, we removed the disabled instance name from the InstalledInstances key in the registry (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server) and the error was resolved.
  8. The user is not associated with a trusted SQL Server connection" - See Event ID 18452 from source MSSQLSERVER.

Workaround: Perform the following to resolve this issue: 1. All rights reserved. No Yes Did this article save you the trouble of contacting technical support? navigate to this website Covered by US Patent.

SQL error number: "0011"" is seen when backing up a server with SQL installed. Login here! On the SQL server, stop the Backup Exec Remote Agent Service from Windows Control Panel > Services. 2.

Stats Reported 7 years ago 1 Comment 3,868 Views Others from Backup Exec 34113 57755 33152 33808 33919 58068 57476 34114 See More IT's easier with help Join millions of IT

United States Products Threat Protection Information Protection Cyber Security Services Website Security Small Business CustomerOne Products A-Z Services Business Critical Services Consulting Services Customer Success Services Cyber Security Services Education Services Re-Start the Backup Exec services on the media server. 5. Access the Backup and Restore options: Click on the windows 7 start ball in the lower left corner of the scree… Windows 7 PCs Storage Software Advertise Here 810 members asked If you choose to participate, the online survey will be presented to you when you leave the Msdn Web site.Would you like to participate?

Start the Backup Exec services If the SQL/MSDE is installed on a Remote Server: 1. SQL error message: "". Third party tools should also be used. my review here I uninstalled it and everything started working again.

Email Address (Optional) Your feedback has been submitted successfully! Here is what I did so far: MS SQL server is NOT installed. Add Cancel × Insert code Language Apache AppleScript Awk BASH Batchfile C C++ C# CSS ERB HTML Java JavaScript Lua ObjectiveC PHP Perl Text Powershell Python R Ruby Sass Scala SQL About Advertising Privacy Terms Help Sitemap × Join millions of IT pros like you Log in to Spiceworks Reset community password Agree to Terms of Service Connect with Or Sign up

CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical 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 Submit a Threat Submit a suspected infected fileto Symantec. Weitere Informationen finden Sie unter dem folgenden Link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml

May 28, 2012 Comments Mace Mar 1, 2011 Denis Kelley Engineering, 1-50 Employees I had an old sql instance that was disabled

SQL error number: "0011"" is seen when backing up a server with SQL installed. SQL error number: "0011". Rename the bedssql2.dll file to bedssql2.old on the remote server.3. x 4 Matthew C.

We do not, however, use it to backup our MS SQL2000 databases on line. Try these resources. It is event id 57860 from Backup Exec: An error occured while attempting to log into the following server "DC-Dur\BACKUPEXEC" SQL error number: "4814" SQL error message:"Login failed for user 'veritas_sa'. Suggested Solutions Title # Comments Views Activity NTVDM encountered a hard error on Windows Server 2003 SP2 7 39 47d Allowing users to save certain file extesions using FSRM on a