[SQL Backup 7]Cannot conduct database backup (exitcode 669)
lamttl
Posts: 3
HI all
I am encountering issue on a flash installed SQL server 2012 on Windows 2012.
The backup of database fail with the following error no matter I use the GUI or using the stored procedure "sqlbackup"
I cannot find the registry specified by the error code.
However, interesting thing is when I browse the registry using Regedit, it is show that the following registry exist:
SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\INSTANCE1
It seems that the path in error message is missing the back slash.
May anyone help to advise how to fix this?
Below please have the software version:
SQL server: Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64)
Windows: Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)
SQL Backup Version: 7.4.0.186
I am encountering issue on a flash installed SQL server 2012 on Windows 2012.
The backup of database fail with the following error no matter I use the GUI or using the stored procedure "sqlbackup"
SQL Backup could not access [HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobalINSTANCE1] running as user [SQLAdmin].
I cannot find the registry specified by the error code.
However, interesting thing is when I browse the registry using Regedit, it is show that the following registry exist:
SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\INSTANCE1
It seems that the path in error message is missing the back slash.
May anyone help to advise how to fix this?
Below please have the software version:
SQL server: Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64)
Windows: Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)
SQL Backup Version: 7.4.0.186
Comments
Thank you for pointing out the typo in the error message. This will be fixed in the next release.
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8
(We through the Domain admin added the domain ID to a domain group that have local administrator privilege, but they actually not.)
I grant the access privilege directly to the domain account that starting SQL backup Agent service and the problem is solved.