Comments
Sort by recent activity
Yes, Red-Gate support showed me the Management studio compact and repair option
also agree that the history collection via sql compact edition is not great
in the end I did the following to fix the error permanently (touch wood)
- de-licensed sqlbackup on that server
- completely uninstalled sql backup
- removed the red-gate dirs in prog files and all users
- reinstalled / comments
Yes, Red-Gate support showed me the Management studio compact and repair option
also agree that the history collection via sql compact edition is not great
in the end I did the following to fix the...
OK, managed to fix this by doing the following
1. stop the sqlbackup service
2. delete\rename the data.sdf file
3. restart the sqlbackup service / comments
OK, managed to fix this by doing the following
1. stop the sqlbackup service
2. delete\rename the data.sdf file
3. restart the sqlbackup service
I had a similar issue at another site that I worked at a few years back and got round the issue by doing the following to the defrag\reindex job.
in the agent job for defragging\reindexing
step 1. disable the transaction log backup job
step 2. set the database to BULK-LOGGED
step 3. run the customised reindex script. This script basically cursors through each table on the database and after each table, gets the current system time, and if the time passed is at least the required frequency (5 mins), then it does a transaction log backup, and then goes to the next table.
step 4. set database back to FULL recovery
step 5. enable the transaction log backup job
hope this helps / comments
I had a similar issue at another site that I worked at a few years back and got round the issue by doing the following to the defrag\reindex job.
in the agent job for defragging\reindexing
step 1. ...
some more info
19/07/2007 18:19:09: VDI error 1010: Failed to get configuration from server. Check that the SQL Server instance is running, and that you have the SQL Server Systems Administrator server role. Error code: (-2139684860: An abort request is preventing anything except termination actions.)
19/07/2007 18:19:09: SQL error 3013: BACKUP LOG is terminating abnormally.
19/07/2007 18:19:09:
19/07/2007 18:19:09: Memory profile
19/07/2007 18:19:09: Type Maximum Minimum Average Blk count Total
19/07/2007 18:19:09:
19/07/2007 18:19:09: Commit 208003072 4096 232178 12256 2845577216
19/07/2007 18:19:09: Reserve 14622720 4096 23706 10558 250298368
19/07/2007 18:19:09: Free 4063232 4096 251070 499 125284352
19/07/2007 18:19:09: Private 208003072 4096 136949 22205 3040956416
19/07/2007 18:19:09: Mapped 1060864 4096 105505 62 6541312
19/07/2007 18:19:09: Image 6156288 4096 88442 547 48377856
SQL Backup job failed with exitcode: 1010 SQL error code: 3013 / comments
some more info
19/07/2007 18:19:09: VDI error 1010: Failed to get configuration from server. Check that the SQL Server instance is running, and that you have the SQL Server Systems Administrator s...
Im also now getting this error
I can backup the log normally using the native SQL command
but not using SQLBackup.
has anyone got a solution for this? / comments
Im also now getting this error
I can backup the log normally using the native SQL command
but not using SQLBackup.
has anyone got a solution for this?
I have had the exact same problem since upgrading to version 5.1 (from ver 4.6)
In this case, the server was running with 2 different service accounts for the SQL Server service and the SQL Agent service (reason is that this server also doubles as a repl distributor, so I have the agent running under the repl AD account)
Originally the SQLBackup service account was running under teh same account as the SQL Server service. Note that both these accounts are low privilege domain accounts and are not local admins on the server.
Had the permissions error. as in the messages above. eventually changed the SQLBackup account to run the same as the SQL Agent account.
now got this error
"Warning 402: Failed to open local data store: Access to the database file is not allowed. [File name=C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Data\(LOCAL)\data.sdf]"
So then gave the Service account full security permissions on the folder
"C:\Documents and Settings\All Users\Application Data\Red Gate"
and this fixed it.
hope this helps / comments
I have had the exact same problem since upgrading to version 5.1 (from ver 4.6)
In this case, the server was running with 2 different service accounts for the SQL Server service and the SQL Agent s...
just tried a new install and using serviceaccount@domain works fine / comments
just tried a new install and using serviceaccount@domain works fine
I got the problem doing a clean install of version 5.0
Trying to install on 2003 32-bit and onto sql 2000 sp3
1. My account (Installer) is a domain account (standard user), with local admin on the dB server.
2. Backup, sql server and agent account, is the same domain account, stardard user on domain and local dB server
3. Installer and Backup accounts are different
4. SQL server and Backup are the same account
5. yes, but single default instance that gave the problem
6. sql 2000
I will try a few more installs and see if the result is the same (as we do have 2005 boxes and some x64 versions as well)
I did get around the issue by doing a "local System" install and then changing the service account afterwards / comments
I got the problem doing a clean install of version 5.0
Trying to install on 2003 32-bit and onto sql 2000 sp3
1. My account (Installer) is a domain account (standard user), with local admin on the...
Same problem occurs doing a clean install on
Win 2003 x64
sql server 2005 Enterprise x64 / comments
Same problem occurs doing a clean install on
Win 2003 x64
sql server 2005 Enterprise x64
Ive also had this issue occur this afternoon when upgrading the SQLBackup on one of my x64 cluster instances to version 6.5.0.75
I can start the sqlbackup resource on the cluster, but doing any backups fails with the error unable to initialise data store etc..
I then copied the old data.sdf to the path requested (eg C:...) and this has rectified the backup problem. I have also tried changing the registry to for the data path to the correct path on the shared storage, but this keeps getting reset back to C:\....
clearly this is going to be a problem when I fail the instance over to another node which doesnt have the data.sdf local to C
ideas??? / comments
Ive also had this issue occur this afternoon when upgrading the SQLBackup on one of my x64 cluster instances to version 6.5.0.75
I can start the sqlbackup resource on the cluster, but doing any bac...