How can we help you today? How can we help you today?
laurencerooks
Activity overview Badges (0) Posts (7) Comments (14)

Comments

Sort by recent activity
Son of a gun. Thanks cgriffin. I think I know why we're having our issues on certain servers and not on others. Laurence / comments
  1. Community
  2. SQL Backup Previous Versions
  3. GUI Job Editing Inconsistency
Son of a gun. Thanks cgriffin. I think I know why we're having our issues on certain servers and not on others. Laurence
0 votes
I agree with cgriffin. I think we need to have the ability to edit the jobs created by SQL Backup. It provides a simple interface that we can create a simple manual off of for when we are on vacation and someone with less experience needs to access the jobs. I love the new GUI, but it does have its shortcomings, such as being able to edit a job after you create it and reboot your workstation. Also, we can install the server components remotely but we can't remove them remotely. Is there a place we can make suggestions? Laurence / comments
  1. Community
  2. SQL Backup Previous Versions
  3. GUI Job Editing Inconsistency
I agree with cgriffin. I think we need to have the ability to edit the jobs created by SQL Backup. It provides a simple interface that we can create a simple manual off of for when we are on vaca...
0 votes
I'm back and I'm still convinced this is a bug and not a security feature. We should be able to edit all jobs all the time through the GUI on a remote master workstation/server because of the following scenarios: 1. I have 13 production servers, 3 of which I am able to edit, 10 of which I am not able to edit. 2. I don't see a difference between servers on the surface that jump out at me pointing to the reason why I can edit Server 1 and not Server 2. 3. This only occurs after you restart the workstation/server the GUI resides on. 4. I have another co-worker at an site in Europe that ran into the same issues of being able to create a job, tinker with it all day long, and unable to mess with it the next day. It would be different story if I wasn't able to edit any server, then I would say it could fall under the security feature aspect. But that's not the case. Can someone please look into this? It has to do with the remote aspect of it because you can edit all day long if the GUI is directly on the SQL Server in question, so it's not a GUI issue. Thanks, Laurence / comments
  1. Community
  2. SQL Backup Previous Versions
  3. GUI Job Editing Inconsistency
I'm back and I'm still convinced this is a bug and not a security feature. We should be able to edit all jobs all the time through the GUI on a remote master workstation/server because of the foll...
0 votes
I'm not sure if the administrators will allow me to do that since I am using Remote Desktop to connect in and install the software. I did figure out a work around though, which was using the GUI console on my workstation to remotely install the software on the SQL Server. It doesn't provide the server with the software to manage it directly on the server, but it does provide what I need to backup the databases. Laurence / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Error 1327. Invalid Drive:
I'm not sure if the administrators will allow me to do that since I am using Remote Desktop to connect in and install the software. I did figure out a work around though, which was using the GUI c...
0 votes
Petey, We are using SQL Server 2000 Standard Edition with SP4 on Windows Server 2003 with SP2. We are not using SQL Server Compact Edition. I did not receive any warning or error message during the test backup. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Failed to initialize local data store: Invalid class string
Petey, We are using SQL Server 2000 Standard Edition with SP4 on Windows Server 2003 with SP2. We are not using SQL Server Compact Edition. I did not receive any warning or error message during t...
0 votes
I was able to successfully create a SQL Backup of the model database with the command given. Why am I not able to connect via the GUI console so I can activate the license and manage it? Laurence / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Failed to initialize local data store: Invalid class string
I was able to successfully create a SQL Backup of the model database with the command given. Why am I not able to connect via the GUI console so I can activate the license and manage it? Laurence
0 votes
I'm running into the same problem on only one of my servers, which is running SQL 2000 SP4 on Windows 2000 SP4. There aren't any other backup jobs occurring during this time. All SQL Backup type jobs fail, both Transaction and Full. Restarting the SQL Server is the only resolution. This first occurred two weeks after I installed Red Gate on the server for the first time. It then happened two months later. Now it's happening again two weeks later. The difference between the previous level and the latest is the file produced, which doesn't have any LSN information stored in the header to read from, thereby causing restore issues. Native SQL Backup for one server out of many is not an option, nor is restarting the SQL Server on a weekly basis. Any help would be welcomed. Thanks, Laurence The error message before the latest patch level was: 9/17/2007 12:00:00 PM: Backing up model (transaction log) to: 9/17/2007 12:00:00 PM: F:\backup\model\LOG_TXSQL008_model_20070917_120000.sqb 9/17/2007 12:00:00 PM: BACKUP LOG [model] TO DISK = 'F:\backup\<database>\<AUTO>.sqb' WITH NAME = '<AUTO>', DESCRIPTION = '<AUTO>', INIT, VERIFY, ERASEFILES = 23h, MAILTO_ONERROR = 'laurence.rooks@ttiinc.com;sqlstoredprocs@ttiinc.com;isintelserverteam@ttiinc.com', COMPRESSION = 1, THREADCOUNT = 3 9/17/2007 12:00:00 PM: 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.) 9/17/2007 12:00:01 PM: SQL error 3013: BACKUP LOG is terminating abnormally. 9/17/2007 12:00:01 PM: 9/17/2007 12:00:01 PM: Memory profile 9/17/2007 12:00:01 PM: Type Maximum Minimum Average Blk count Total 9/17/2007 12:00:01 PM: 9/17/2007 12:00:01 PM: Commit 769785856 4096 1578030 1140 1798955008 9/17/2007 12:00:01 PM: Reserve 4186112 4096 483656 162 78352384 9/17/2007 12:00:01 PM: Free 16515072 4096 1159273 233 270110720 9/17/2007 12:00:01 PM: Private 769785856 4096 2358098 780 1839316992 9/17/2007 12:00:01 PM: Mapped 1019904 4096 117715 46 5414912 9/17/2007 12:00:01 PM: Image 7581696 4096 68435 476 32575488 9/17/2007 12:00:01 PM: 9/17/2007 12:00:01 PM: Warning 300: Backup failed. Retry attempt: 1 9/17/2007 12:00:03 PM: BACKUP LOG [model] TO DISK = 'F:\backup\model\LOG_TXSQL008_model_20070917_120000.sqb' WITH NAME = 'Database (model), 9/17/2007 12:00:00 PM', DESCRIPTION = 'Backup on 9/17/2007 12:00:00 PM Server: TXSQL008 Database: model', INIT, VERIFY, ERASEFILES = 23h, MAILTO_ONERROR = 'laurence.rooks@ttiinc.com;sqlstoredprocs@ttiinc.com;isintelserverteam@ttiinc.com', COMPRESSION = 1, THREADCOUNT = 3 9/17/2007 12:00:03 PM: 9/17/2007 12:00:03 PM: Warning 300: Backup failed. Retry attempt: 2 9/17/2007 12:00:05 PM: BACKUP LOG [model] TO DISK = 'F:\backup\model\LOG_TXSQL008_model_20070917_120000.sqb' WITH NAME = 'Database (model), 9/17/2007 12:00:00 PM', DESCRIPTION = 'Backup on 9/17/2007 12:00:00 PM Server: TXSQL008 Database: model', INIT, VERIFY, ERASEFILES = 23h, MAILTO_ONERROR = 'laurence.rooks@ttiinc.com;sqlstoredprocs@ttiinc.com;isintelserverteam@ttiinc.com', COMPRESSION = 1, THREADCOUNT = 3 9/17/2007 12:00:05 PM: 9/17/2007 12:00:05 PM: Warning 300: Backup failed. Retry attempt: 3 9/17/2007 12:00:07 PM: BACKUP LOG [model] TO DISK = 'F:\backup\model\LOG_TXSQL008_model_20070917_120000.sqb' WITH NAME = 'Database (model), 9/17/2007 12:00:00 PM', DESCRIPTION = 'Backup on 9/17/2007 12:00:00 PM Server: TXSQL008 Database: model', INIT, VERIFY, ERASEFILES = 23h, MAILTO_ONERROR = 'laurence.rooks@ttiinc.com;sqlstoredprocs@ttiinc.com;isintelserverteam@ttiinc.com', COMPRESSION = 1, THREADCOUNT = 3 9/17/2007 12:00:07 PM: 9/17/2007 12:00:07 PM: Warning 300: Backup failed. Retry attempt: 4 9/17/2007 12:00:09 PM: BACKUP LOG [model] TO DISK = 'F:\backup\model\LOG_TXSQL008_model_20070917_120000.sqb' WITH NAME = 'Database (model), 9/17/2007 12:00:00 PM', DESCRIPTION = 'Backup on 9/17/2007 12:00:00 PM Server: TXSQL008 Database: model', INIT, VERIFY, ERASEFILES = 23h, MAILTO_ONERROR = 'laurence.rooks@ttiinc.com;sqlstoredprocs@ttiinc.com;isintelserverteam@ttiinc.com', COMPRESSION = 1, THREADCOUNT = 3 ======================================= The error message after the latest patch: 9/17/2007 1:16:13 PM: Backing up model (transaction log) to: 9/17/2007 1:16:13 PM: F:\backup\model\LOG_TXSQL008_model_20070917_131613.sqb 9/17/2007 1:16:13 PM: BACKUP LOG [model] TO DISK = 'F:\backup\<database>\<AUTO>.sqb' WITH NAME = '<AUTO>', DESCRIPTION = '<AUTO>', INIT, VERIFY, ERASEFILES = 23h, MAILTO_ONERROR = 'laurence.rooks@ttiinc.com;sqlstoredprocs@ttiinc.com;isintelserverteam@ttiinc.com', COMPRESSION = 1, THREADCOUNT = 3 9/17/2007 1:16:13 PM: 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.) 9/17/2007 1:16:13 PM: SQL error 3013: BACKUP LOG is terminating abnormally. 9/17/2007 1:16:13 PM: 9/17/2007 1:16:14 PM: Memory profile 9/17/2007 1:16:14 PM: Type Maximum Minimum Average Blk count Total 9/17/2007 1:16:14 PM: 9/17/2007 1:16:14 PM: Commit 769785856 4096 1568325 1147 1798868992 9/17/2007 1:16:14 PM: Reserve 4186112 4096 516439 167 86245376 9/17/2007 1:16:14 PM: Free 16515072 4096 1130619 232 262303744 9/17/2007 1:16:14 PM: Private 769785856 4096 2332222 792 1847119872 9/17/2007 1:16:14 PM: Mapped 1019904 4096 117715 46 5414912 9/17/2007 1:16:14 PM: Image 7581696 4096 68444 476 32579584 9/17/2007 1:16:14 PM: 9/17/2007 1:16:14 PM: Warning 300: Backup failed. Retry attempt: 1 9/17/2007 1:16:16 PM: BACKUP LOG [model] TO DISK = 'F:\backup\model\LOG_TXSQL008_model_20070917_131613.sqb' WITH NAME = 'Database (model), 9/17/2007 1:16:13 PM', DESCRIPTION = 'Backup on 9/17/2007 1:16:13 PM Server: TXSQL008 Database: model', INIT, VERIFY, ERASEFILES = 23h, MAILTO_ONERROR = 'laurence.rooks@ttiinc.com;sqlstoredprocs@ttiinc.com;isintelserverteam@ttiinc.com', COMPRESSION = 1, THREADCOUNT = 3 9/17/2007 1:16:17 PM: Backup data size : 1.500 MB 9/17/2007 1:16:17 PM: Compressed data size: 7.500 KB 9/17/2007 1:16:17 PM: Compression rate : 99.51% BACKUP LOG successfully processed 0 pages in 0.020 seconds (0.000 MB/sec). 9/17/2007 1:16:17 PM: 9/17/2007 1:16:17 PM: Validating files: 9/17/2007 1:16:17 PM: F:\backup\model\LOG_TXSQL008_model_20070917_131613.sqb 9/17/2007 1:16:17 PM: 9/17/2007 1:16:17 PM: RESTORE VERIFYONLY FROM DISK = 'F:\backup\model\LOG_TXSQL008_model_20070917_131613.sqb' The backup set is valid. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. log backup failing randomly (dreaded vdi 1010)
I'm running into the same problem on only one of my servers, which is running SQL 2000 SP4 on Windows 2000 SP4. There aren't any other backup jobs occurring during this time. All SQL Backup type ...
0 votes
Brian, Reinstalling the .NET 2.0 Framework worked. Thanks! / comments
  1. Community
  2. SQL Backup Previous Versions
  3. CLR error: 80004005
Brian, Reinstalling the .NET 2.0 Framework worked. Thanks!
0 votes
Brian, There isn't a framework folder within the .Net folder. Could that be my problem? I checked the add/remove programs and .Net 2.0 is listed as installed. Do I need to reinstall .Net 2.0? Or would going to Windows Update solve that problem for me? I'm still on Service Pack 1 for Windows 2003 Server. Should I move to Service Pack 2? / comments
  1. Community
  2. SQL Backup Previous Versions
  3. CLR error: 80004005
Brian, There isn't a framework folder within the .Net folder. Could that be my problem? I checked the add/remove programs and .Net 2.0 is listed as installed. Do I need to reinstall .Net 2.0? O...
0 votes
Brian, I tried uninstalling and reinstalling SQL Backup to no avail. I still get the same error message. This is on a server that I have to give good reason for rebooting. Do you have any other suggestions outside of restarting the server? Thanks. P.S. - There aren't any errors in the event view, either for Application or System. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. CLR error: 80004005
Brian, I tried uninstalling and reinstalling SQL Backup to no avail. I still get the same error message. This is on a server that I have to give good reason for rebooting. Do you have any other ...
0 votes
Total activity
28
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
7