Comments
Sort by recent activity
You were asking about how to re-enable Feature Usage (not Error Reporting)? Are you all-set now? / comments
You were asking about how to re-enable Feature Usage (not Error Reporting)? Are you all-set now?
Yes / comments
Yes
Apologies for this. It's a new bug (reference SA-1387. Please downgrade to version 6.2 which you can get here: http://downloads.red-gate.com/checkforu ... .2.215.exe / comments
Apologies for this. It's a new bug (reference SA-1387. Please downgrade to version 6.2 which you can get here:http://downloads.red-gate.com/checkforu ... .2.215.exe
Are all the fixes in 6.5.2.18 included in the new V 7?
Yes. As a general rule, Red Gate has a 'linear' approach to developing software- we hardly ever create branches.
Hope this helps [image] / comments
Are all the fixes in 6.5.2.18 included in the new V 7?
Yes. As a general rule, Red Gate has a 'linear' approach to developing software- we hardly ever create branches.
Hope this helps
This appears similar to an issue that some other users experienced. In those cases, we provided a patch, which resolved the issue.
The patch is available using this link: ftp://support.red-gate.com/patches/sql_ ... 5_2_18.zip
The zip 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. SQL Backup should now error out correctly and not become unresponsive.
Let me know if the error still occurs after applying the patch. / comments
This appears similar to an issue that some other users experienced. In those cases, we provided a patch, which resolved the issue.
The patch is available using this link:ftp://support.red-gate.com...
OK, thanks. Can you send to us (support@red-gate.com)
- Windows application event log (shows pertinent .Net errors)
- ANTS log (Help->Open log folder) / comments
OK, thanks. Can you send to us (support@red-gate.com)
- Windows application event log (shows pertinent .Net errors)
- ANTS log (Help->Open log folder)
Try the same but withholding the ASP.NET account details / comments
Try the same but withholding the ASP.NET account details
Quickest thing to try first: run _explicitly_ as administrator (right click on the ANTSGUI.exe). This kills 50% of bugs. / comments
Quickest thing to try first: run _explicitly_ as administrator (right click on the ANTSGUI.exe). This kills 50% of bugs.
Thanks for your observations. I shall pass them on to our product development team / comments
Thanks for your observations. I shall pass them on to our product development team
Yes, the process is identical whether you initiate 'manual' SA exceptions or not - select the feature in the UI/command line and let SA do it's thang. / comments
Yes, the process is identical whether you initiate 'manual' SA exceptions or not - select the feature in the UI/command line and let SA do it's thang.