Comments
Sort by recent activity
Should be fixed for release now. / comments
Should be fixed for release now.
Fantastic!
That'll do it Dan - Thanks [image] / comments
Fantastic!
That'll do it Dan - Thanks
Hi Dan,
Could you maybe dig out the latest log file if it happens again please?
These will be in your Local Application Data (Under Red Gate\Logs\SQL backup).
e.g. on Vista mine is "C:\Users\nigel.morse\AppData\Local\Red Gate\Logs"
And i'll see if there's anything interesting in there as to where it's comming from.
Thanks,
Nigel / comments
Hi Dan,
Could you maybe dig out the latest log file if it happens again please?
These will be in your Local Application Data (Under Red Gate\Logs\SQL backup).
e.g. on Vista mine is "C:\Users\nigel....
Thanks. We managed to reproduce it, but only by having a user called <> - and this then broke the HTML used to put the username in bold.
not quite sure why it broke in your case, but I've put some proper HTML encoding round the username which hopefull should fix it for you as well for final release. / comments
Thanks. We managed to reproduce it, but only by having a user called <> - and this then broke the HTML used to put the username in bold.
not quite sure why it broke in your case, but I've put some...
Hi Andy,
What was the username you were using to log in to this server, and did it (as RBA suggests) have characters like < or > in the name?
Thanks
Nigel / comments
Hi Andy,
What was the username you were using to log in to this server, and did it (as RBA suggests) have characters like < or > in the name?
Thanks
Nigel
Hi Bill,
Sorry you're having problems still.
Were you originally using windows authentication to connect the service to sql server?
I think the best thing to is to make sure the server components are fully uninstalled before reinstalling and that should allow to re-enter the accounts and get the setup straightened out
First remove the SQL Backup 5 (server components) for the instance you're interested in (or the only one if you have only one instance). However make sure you choose No on the dialog asking if you want to remove all the activity history or you'll lose all the data of previous backups
Then check the binn directory of the instance (e.g. mine is C:\Program Files\Microsoft SQL Server\MSSQL\Binn ) and make sure xp_sqlbackup.dll has been removed
Then re-run the server components setup and it should ask for users to run the service as, and next which type of authentication to use.
If all this fails I suggest we ask one of our support guys to help out and see if they can fix it. / comments
Hi Bill,
Sorry you're having problems still.
Were you originally using windows authentication to connect the service to sql server?
I think the best thing to is to make sure the server components a...
Hi,
The 5.3 and 5.4 clients will both work with the 5.3 and 5.4 server components so there's no specific order needed to upgrade. You can upgrade servers and clients however you wish. / comments
Hi,
The 5.3 and 5.4 clients will both work with the 5.3 and 5.4 server components so there's no specific order needed to upgrade. You can upgrade servers and clients however you wish.
Hi,
Sorry you've had this problem. We've done some digging into the VDI and we think we found a way to fix this. We're locking down version 5.5 in a few days time and so if it works we will put this in before then. / comments
Hi,
Sorry you've had this problem. We've done some digging into the VDI and we think we found a way to fix this. We're locking down version 5.5 in a few days time and so if it works we will put th...
jason.williams14 wrote:
So for the SQL Backup piece, since we have a team of DBA's, what is the best way to set this up, so all of us can manage Backup Pro? That is where I am a little fuzzy.
Each DBA can install the client locally and then add the machines they want to look at. From there they can install the server components if they've not been done by one of the other DBAs for that instance.
Note the licensing is by server machine and so once a DBA has licensed an instance all instances on that box can be viewed by all DBAs / comments
jason.williams14 wrote:
So for the SQL Backup piece, since we have a team of DBA's, what is the best way to set this up, so all of us can manage Backup Pro? That is where I am a little fuzzy.
...
Hi,
SQL Backup and SQL Response currently use different deployment models.
SQL Backup has a small component that gets installed on each SQL Server instance, you then add those servers to each client so no central server needed.
SQL Response on the other had does use a central server. You install the Alert Repository on this central server and then each client will connect to that. / comments
Hi,
SQL Backup and SQL Response currently use different deployment models.
SQL Backup has a small component that gets installed on each SQL Server instance, you then add those servers to each clien...