Red Gate forums :: View topic - Error: Rijndael: Invalid key size - 0, red gate
Return to www.red-gate.com RSS Feed Available

Search  | Usergroups |  Profile |  Messages |  Log in  Register 
Go to product documentation
SQL Backup 6
SQL Backup 6 forum

Error: Rijndael: Invalid key size - 0, red gate

Search in SQL Backup 6 forum
Post new topic   Reply to topic
Jump to:  
Author Message
dklein9930



Joined: 02 Mar 2011
Posts: 13

PostPosted: Wed May 01, 2013 8:49 pm    Post subject: Error: Rijndael: Invalid key size - 0, red gate Reply with quote

Error when attempting a restore. Version: 6.4.0.56
Back to top
View user's profile Send private message
petey



Joined: 24 Apr 2005
Posts: 2305

PostPosted: Thu May 02, 2013 9:38 am    Post subject: Reply with quote

Could you please try patch 6.5.2.23?

ftp://support.red-gate.com/patches/sql_backup/SQB_6_5_2_23.zip

The zip file contains two files:

SQBCoreService.exe
SQLBackupC.exe

To apply the patch, please follow the steps below:

1. Close all GUI connections to the SQL Server.
2. Ensure that no SQL Backup jobs are in progress.
3. Stop the SQL Backup Agent Service, or disable the cluster resource if on a cluster.
4. On the SQL Server where the SQL Backup server components are installed, navigate to the installation directory. Defaults are:

32-bit Machines - C:\Program Files\Red Gate\SQL Backup 6\(local) or <SQL Instance Name>
64-bit Machines - C:\Program Files (x86)\Red Gate\SQL Backup 6\(local) or <SQL Instance Name>

5. In the folder you will find an existing SQBCoreService.exe and SQL BackupC.exe. Rename the existing files, for example to OLDSQBCoreService.exe and OLDSQLBackupC.exe.
6. Now copy in the files extracted from the downloaded zip.
7. Restart the SQL Backup agent service/cluster resource, and ensure that it starts successfully.
8. Perform a test backup to ensure that all is OK. Then test to see if the original error occurs.
_________________
Peter Yeoh
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 7
Back to top
View user's profile Send private message Send e-mail
dklein9930



Joined: 02 Mar 2011
Posts: 13

PostPosted: Thu May 02, 2013 8:43 pm    Post subject: Reply with quote

Thanks for the reply Peter. What is this error? We have been using this version for almost 3 years, we have clients who are receiving backups from us in this version. Management is reluctant to make changes. Why did this error happen all of the sudden?

Thanks again,
David
Back to top
View user's profile Send private message
petey



Joined: 24 Apr 2005
Posts: 2305

PostPosted: Fri May 03, 2013 2:15 am    Post subject: Reply with quote

I can't remember the cause, as it's been almost 2 years since 6.5 was released. Was version 6.5 able to restore from your backup file?
_________________
Peter Yeoh
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 7
Back to top
View user's profile Send private message Send e-mail
dklein9930



Joined: 02 Mar 2011
Posts: 13

PostPosted: Mon May 06, 2013 2:46 pm    Post subject: New error Reply with quote

Hey Peter,

I switched out the files and the first transaction log backups came back with this error:


"Executed as user: dbo. SQL Backup failed with exit code: 667 SQL error code: 0 [SQLSTATE 42000] (Error 50000). The step failed."

Thanks,
David
Back to top
View user's profile Send private message
dklein9930



Joined: 02 Mar 2011
Posts: 13

PostPosted: Mon May 06, 2013 2:54 pm    Post subject: More details Reply with quote

Did this occur cause the transaction logs were on a different version than the full backups? Is the first action after the switch to take a full backup?

Thanks,
David
Back to top
View user's profile Send private message
dklein9930



Joined: 02 Mar 2011
Posts: 13

PostPosted: Mon May 06, 2013 5:59 pm    Post subject: I have not represented the problem properly Reply with quote

My apologies Peter,

The server that is taking the backup is running Redgate backup version 5.3.0.178. The server that we are attempting a ‘partial’ restore on is running version 6.4.0.56. How would this change the solution to our problem? What cost/work is involved in upgrading version 5 listed above to the version to sent me 6.5.2.23?

Thanks for your time,
David
Back to top
View user's profile Send private message
petey



Joined: 24 Apr 2005
Posts: 2305

PostPosted: Wed May 08, 2013 4:22 am    Post subject: Reply with quote

Version 6.5.2.23 can restore backups created in 5.3.0.178. The error you are experiencing (667), indicates that the SQL Backup trial period has expired.
_________________
Peter Yeoh
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 7
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Reply to topic All times are GMT + 1 Hour
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group