Comments
5 comments
-
Is it possible that you have set up the service app to log in to SQL Server using SQL authentication? Look in the help file, under the topic 'Using SQL Backup', on how to configure the service app to connect using Windows authentication and SQL authentication.
-
I have not used the sqbsetlogin command so to my knowledge I'm using Windows authentication. If a wrong password is put into the service, it does not start so I know it is using Windows authentication and the service starts and is running. The username sqladmin we are using has sa privs on Sql.
I think it may have something to do with the install on the cluster. It is somewhat of a manual process.
John -
Using sqbsetlogin is not the only way to use SQL authentication. During the installation process, there are options to set how the SQL Backup service will log in to SQL Server. This may have been incorrectly set.
To check, see if there is any data in the following registry value:
HKEY_LOCAL_MACHINE\Software\Red Gate\SQL Backup\InstalledInstances\<instance name>\ServiceLogin -
There is some data in that reg key. Is there any way to reset how it logs on without reinstalling?
John -
If you're feeling lucky, delete the ServiceLogin key, otherwise
sp_addextendedproc sqbsetlogin, 'xp_sqlbackup.dll'
exec master..sqbsetlogin '', ''
sp_dropextendedproc sqbsetlogin
Add comment
Please sign in to leave a comment.
Thank you,
John
====================
Job 'test atmon' : Step 1, 'Step 1' : Began Executing 2006-05-31 08:47:10
SQL Backup (DLL v4.1.0.207)
Login failed for user 'usapsys\sqladmin'.
SQL error code: 18456
name value
exitcode 0
sqlerrorcode 18456
filename01 G:\LAVSQLSRV\Backup\<AUTO>
Msg 50000, Sev 16: SQL Backup job failed with exitcode: 0 SQL error code: 18456 [SQLSTATE 42000]