Comments
Sort by recent activity
Thanks for the reply Petey. This is now resolved. It turns out the encrypted password for the SMTP account in the registry at HKLM\Software\Red Gate\SQL Backup\BackupSettingsGlobal\<instance name> in the SMTPPassword node was incorrect. It did not work through the GUI when I tried to correct it there but after stopping the SQL Backup agent service and correcting it at that registry node and restarting the service, it did work and the settings information are correctly retained in the GUI. / comments
Thanks for the reply Petey. This is now resolved. It turns out the encrypted password for the SMTP account in the registry at HKLM\Software\Red Gate\SQL Backup\BackupSettingsGlobal\<instance name> ...
Yes, the patch fixed my issue too. Thanks Neil. / comments
Yes, the patch fixed my issue too. Thanks Neil.
FYI, this is their email response:
"This is a known issue. We have identified the problem and aim to release a fix next week. Week commencing 21st May 2012. We apologise for any inconvenience caused by this issue." / comments
FYI, this is their email response:
"This is a known issue. We have identified the problem and aim to release a fix next week. Week commencing 21st May 2012. We apologise for any inconvenience cause...
I see this same issue too with the exact same error message as above. It is incredibly annoying to get this popup message inside SSMS 2008. At first, I thought this was an issue with SQL Data Compare 10 which was where I posted this issue first on that forum. Now I think this is an issue with SQL Compare 10.2.0.696. Here are my client specs:
Microsoft SQL Server Management Studio 10.0.5500.0
Microsoft Analysis Services Client Tools 10.0.5500.0
Microsoft Data Access Components (MDAC) 6.1.7601.17514
Microsoft MSXML 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 9.0.8112.16421
Microsoft .NET Framework 2.0.50727.5456
Operating System 6.1.7601 (Windows 7 Professional 64bit SP1) / comments
I see this same issue too with the exact same error message as above. It is incredibly annoying to get this popup message inside SSMS 2008. At first, I thought this was an issue with SQL Data Compa...
This is resolved. The patch release for SQL Compare 10.2.0.777 fixed this issue for me. Thanks. / comments
This is resolved. The patch release for SQL Compare 10.2.0.777 fixed this issue for me. Thanks.
It looks like this may not be an issue with SQL Data Compare but it may be an issue with SQL Compare 10.2.0.696. Looking over at that forum, I see someone else has a similar issue to mine. / comments
It looks like this may not be an issue with SQL Data Compare but it may be an issue with SQL Compare 10.2.0.696. Looking over at that forum, I see someone else has a similar issue to mine.
I checked "%programdata%\Microsoft\SQL Server Management Studio\11.0\Addins" and the only add-in in there is "RedGate.SQLPrompt.SSMSUI.2011.AddIn" in mine. I'm hesitant to remove it unless RedGate recommends it - I'll wait for their reply. / comments
I checked "%programdata%\Microsoft\SQL Server Management Studio\11.0\Addins" and the only add-in in there is "RedGate.SQLPrompt.SSMSUI.2011.AddIn" in mine. I'm hesitant to remove it unless RedGate ...
Eddie, here is the info you requested:
Microsoft SQL Server Management Studio 10.0.5500.0
Microsoft Analysis Services Client Tools 10.0.5500.0
Microsoft Data Access Components (MDAC) 6.1.7601.17514
Microsoft MSXML 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 9.0.8112.16421
Microsoft .NET Framework 2.0.50727.5456
Operating System 6.1.7601 (Windows 7 Professional 64bit SP1) / comments
Eddie, here is the info you requested:
Microsoft SQL Server Management Studio 10.0.5500.0
Microsoft Analysis Services Client Tools 10.0.5500.0
Microsoft Data Access Components (MDAC) 6.1.7601.17514...
Not a bug - I was missing something obvious.
The source environment had its DDL trigger disabled as well which was probably why the destination environment failed to show the sql statement to re-enable the DDL trigger. After re-enabling the DDL trigger in the source, the destination sync script did produce the re-enable DDL trigger sql statement. Sorry - false alarm. [image] / comments
Not a bug - I was missing something obvious.
The source environment had its DDL trigger disabled as well which was probably why the destination environment failed to show the sql statement to re-en...
Thanks for your input petey. I'll try that suggestion. I suspect it might be the network throughput between the 2 servers and not the load on the restore server itself. / comments
Thanks for your input petey. I'll try that suggestion. I suspect it might be the network throughput between the 2 servers and not the load on the restore server itself.