SQL error number: "4818". SQL error message: "Login failed for user

  • 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!

  • 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

  • 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."

  • Yes the SQL Agent is installed.  We currently do not use it because we just upgraded to SBS 2003 premium and it was included.  I work for an accounting firm and alot of the new software coming out will have the compatability with SQL.  This problem started somewhere out of the blue. It was working fine and all of a sudden it started on one server.  A couple days later it started on the other server.  I looked to see if veritas had any updates but they didn't.  I checked all the login passwords and they were all correct.  I did not change anything to the server and these errors started.  I want to get this problem solved so I can start to impliment SQL Server and have good backups.  They backups are configured to go to disk first, then backed up to tape using Veritas.  I think the reason I am getting these errors is because it is backing up to disk at the same time Veritas is trying to back up the files.  Is there a way to schedule the backup to disks for an earlier time?

  • Ahhhh, more information. Yes, you will have problems if Backup Exec is trying to copy the files while SQL Server is backing up to those files. Both can not use them at the same time.

    To reschedule the SQL Server backup job, first you need to figure out how you originally scheduled the job. Are you using a maintenance plan? Or did you write the backup job?

    Either way, the first place to look is in Enterprise Manager. Drill down to Management, then Jobs. Find the backup job, right click on it, select properties, go to the Schedule tab. Make your changes there. (I don't use a maintenance plan, so you might have to redo yours if that's what you are using).

    -SQLBill

  • I have the same error reported in Veritas for SBS 2003 running on SBS 2003 using the SQL agent.  I installed Act! 2006.  I do not have Enterprise Manager installed on this server, only the SQL presence installed by ACT!  2006.  I am not copying my DB's to disk first because SQL is not installed.  Any ideas?

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply