Error 4818 Sql
Contents |
Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 7,2000 » Backups » SQL error number: "4818". SQL error sql error 4818 backup exec message:... SQL error number: "4818". SQL error message: "Login failed for user Rate Topic
Sql Error 18456
Display Mode Topic Options Author Message marko-272611marko-272611 Posted Wednesday, October 26, 2005 11:15 AM Forum Newbie Group: General Forum Members Last Login: sql error number 4818 Monday, October 31, 2005 7:24 AM Points: 2, Visits: 1 This is the error I am getting when using Veritas Backup. I checked all users and all passwords and they are correct. Any ideas of how to fix this problem?Thank you! Post #232613 SQLBillSQLBill Posted Wednesday, October 26, 2005 11:29 AM Hall of Fame Group: General Forum Members Last Login: 2 days ago @ 1:55 PM Points: 3,408, Visits: 979 ARGHHHH! Veritas Backup Exec!!!! First, do you have the Agent for SQL Server installed? If not, then it won't backup SQL Server. If so, check the Backup Exec Job Agent service login. This login must have permissions on the database.I highly suggest you replanning your backup strategy. I backup to disk using SQL Server commands and then use Backup Exec to copy the backup file to tape.-SQLBill Post #232627 Rudyx - the DoctorRudyx - the Doctor Posted Thursday, October 27, 2005 10:20 AM Hall of Fame Group: General Forum Members Last Login: Saturday, September 24, 2016 9:57 AM Points: 3,243, Visits: 2,465 I agree with SQLBill. Backup your databases to disk, then have Veritas pick up the files. It's actually more a efficient strategy because all of your SQL Server can backup to disk at te same time of day and then Veritas is free to roam and pick up the files on it's own schedule. No waiting for available tape drives, etc. Also, the more importnt thing is that I've always been able to have a 50+% FAILURE rate on 'agent' type restores - choose a vendor. Besides, a DBA is only as good as their last 'restore' ! RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus." Post #233016 marko-272611marko-272611 Posted Thursday, October 27, 2005 10:32 AM Forum Newbie Group: General Forum Members Last Login: Monday, October 31, 2005 7:24 AM Points: 2, Visits: 1 Yes the SQL Agent is installed. We currently do not use
DriverDoc WinSweeper SupersonicPC FileViewPro About Support Contact Errors Troubleshooting › Runtime Errors › Symantec › Backup Exec › Error 4818 How To Fix Backup Exec Error 4818 Error http://www.solvusoft.com/en/errors/runtime-errors/symantec/backup-exec/4818-sql-error-number-4818/ Number: Error 4818 Error Name:"SQL error number: ""4818""" Error Description: "An error occurred while attempting to log in to the following server: ""ServerName"". SQL error number: ""4818"". SQL error message: ""Login failed for user 'DOMAIN\BackupExec Service Account'"". BackupExec causes 4818 SQL Login Event Log Error." Developer:Symantec Software:Backup Exec Applies to:Windows XP, Vista, 7, 8 Download sql error NowWinThruster 2015 - Scan your PC for computer errors. Compatible with Windows 10, 8, 7, Vista, XP and 2000 Symptoms of Error 4818 "Error 4818" appears and crashes the active program window. Your PC frequently crashes with Error 4818 when running the same program. “"SQL error number: ""4818"""” is displayed. Windows runs sluggishly and responds slowly error 4818 sql to mouse or keyboard input. Your computer periodically “freezes” for a few seconds at a time. These 4818 error messages can appear during program installation, while a Symantec-related software program (eg. Backup Exec) is running, during Windows startup or shutdown, or even during the installation of the Windows operating system. Keeping track of when and where your 4818 error occurs is a critical piece of information in troubleshooting the problem. Causes of Error 4818 Corrupt download or incomplete installation of Backup Exec software. Corruption in Windows registry from a recent Backup Exec-related software change (install or uninstall). Virus or malware infection that has corrupted Windows system files or Backup Exec-related program files. Another program maliciously or mistakenly deleted Backup Exec-related files. Runtime Errors such as “Error 4818” can be caused by a variety of factors, so it is important that you troubleshoot each of the possible causes to prevent it from recurring. Runtime Errors Knowledgebase Article ID: 130090 Article Author: Jay Geater Last Up