Comments
Sort by recent activity
Thanks guys for your responses and your help by reporting this issue,
It seems this is indeed the issue you are all hitting, we will get it fixed (if possible) for the patch release in a month or two - for now (and for anyone else reading this thread) there are two work arounds:
Install as a Local System and then change the account logon via the services snapin
Use the format <username>@<domain>
Thanks for all your help,
- James / comments
Thanks guys for your responses and your help by reporting this issue,
It seems this is indeed the issue you are all hitting, we will get it fixed (if possible) for the patch release in a month or t...
By any chance are you using the format <DOMAIN>\<Username>? could you try using <Username>@<domain> instead for example:
rather than
EXAMPLE\James
use JAMES@EXAMPLE.COM
I think we might have reproduced it here - I just want to check that it is the same problem as you are having.
Thanks,
- James / comments
By any chance are you using the format <DOMAIN>\<Username>? could you try using <Username>@<domain> instead for example:
rather than
EXAMPLE\James
useJAMES@EXAMPLE.COM
I think we might have repr...
Hi guys,
We have tried reproducing this here and can't get this to happen, could you let me know the answers to the following questions please?
Are you (the installer) a local admin, domain admin or standard user - is it a domain account or a local account?
Similarly for the SQL Backup Agent user, SQL Server user and SQL Agent User?
Are the accounts above the same account (installer, backup agent ...) or different accounts?
Are SQL Server and SQL Backup running as the same account?
Do you have multiple instances per machine?
Are you running SQL 2000, SQL 2005 or both?
Hopefully we can reproduce this here and get this fixed,
Sorry for the problems you are hitting,
- James / comments
Hi guys,
We have tried reproducing this here and can't get this to happen, could you let me know the answers to the following questions please?
Are you (the installer) a local admin, domain admin ...
Hi guys,
Sorry you have hit this problem and I'm glad you found a work around, we will be looking into this today to try and understand what is going wrong.
Thanks for the heads up,
- James / comments
Hi guys,
Sorry you have hit this problem and I'm glad you found a work around, we will be looking into this today to try and understand what is going wrong.
Thanks for the heads up,
- James
Hi,
I'm sorry you have hit this problem however we have now fixed it and it will be available in SQL Backup v5.0 which should be released in the next few days/weeks (We are just doing the final stages of install testing). An announcement will be made in the forum when it is available.
Sorry for any inconvience caused,
- James / comments
Hi,
I'm sorry you have hit this problem however we have now fixed it and it will be available in SQL Backup v5.0 which should be released in the next few days/weeks (We are just doing the final sta...
One workaround to this is to have .NET 1.1 and .NET 2.0 installed at which point this should work - the other option is to copy the dll's out of GAC and put them in Resharpers start up directory so that the .NET framework can find them when loading resharper and it also finds the right one for us.
As Brian said we are working with the vendor to resolve this issue.
- James / comments
One workaround to this is to have .NET 1.1 and .NET 2.0 installed at which point this should work - the other option is to copy the dll's out of GAC and put them in Resharpers start up directory so...
Hi there,
master..sqlbackup takes two out parameters @errorCode and @sqlErrorCode which will return any warning or error codes SQL Backup has (@errorCode) or any SQL Server errors (@sqlErrorCode). These codes are documented in the help file.
- James / comments
Hi there,
master..sqlbackup takes two out parameters @errorCode and @sqlErrorCode which will return any warning or error codes SQL Backup has (@errorCode) or any SQL Server errors (@sqlErrorCode). ...
Which version of SQL backup are you running?
Thanks,
- James / comments
Which version of SQL backup are you running?
Thanks,
- James
Hi Jan,
You might get away with doing a BACKUP using the NORECOVERY option followed by a RESTORE WITH STANDBY - this is not supported in the GUI itself however you can copy the script and run it it SSMS/QA adding NORECOVERY to the script.
If this does not put the database back into a state where logs can be restored to it then you would need to do a full backup of the source database and restore that to the destination database using STANDBY.
It really depends on what SQL Server thinks has happened to the database since it was detached/attached as to wheter it will let you do option 1. Option 2 will ofcourse work regardless of the state of the destination database.
HTH,
- James / comments
Hi Jan,
You might get away with doing a BACKUP using the NORECOVERY option followed by a RESTORE WITH STANDBY - this is not supported in the GUI itself however you can copy the script and run it it...
Hi there,
Do you have a virus scanner running as they will often lock a file and check is causing problems as SQL Compare cannot then access it. Could you temporaraly disable your virus scanner and see if this solves the issue for you.
- James / comments
Hi there,
Do you have a virus scanner running as they will often lock a file and check is causing problems as SQL Compare cannot then access it. Could you temporaraly disable your virus scanner and...