Comments
Sort by recent activity
AaronBertrand wrote:
Hi Chris,
When you do upgrade to 6.1, here is my horror story from the last few days. I actually spent about 6 man hours getting the upgrade from 5 to 6 to take.
1) after deactivating 5.4, I installed 6.1, upgrading (or so I thought) 5.4
2) I activated 6.1 licenses through the new UI
3) backup jobs were failing ("Trial expired." - they were still using 5.x for some reason)
4) contacted support
5) they told me to uninstall 5/6 and reinstall 6 from scratch
6) uninstalled all Red Gate components, restarted SQL Server, rebooted
7) reinstalled 6.1 -- same result
8) I snooped around and found that uninstall had not removed the old SQBCoreService.exe, and for some reason the upgrade was not pointing the service at the *new* version of this exe (after I told support this, they said, "hey maybe there is an old SQBCoreService.exe laying around?" Thanks guys!)
9) after repeating 6) I deleted the exe above as well as its parent path, and removed all instances of "Red Gate", "redgate" etc. from the registry
Finally I was able to install 6.1 and actually make it stick (it was forced to lay down a NEW SQBCoreService.exe and point the service at it correctly).
So, in case mine was not an isolated incident, I recommend jumping straight to 6)/9) above and cleaning the box before upgrade. Support said that "all other upgrades have worked fine" but I can't imagine I did anything to corrupt this experience. <shrug>
This is exactly mine problem at this moment / comments
AaronBertrand wrote:
Hi Chris,
When you do upgrade to 6.1, here is my horror story from the last few days. I actually spent about 6 man hours getting the upgrade from 5 to 6 to take.
1) after de...