Comments
Sort by recent activity
The service did not respond gracefully to the restart request, and wound up hung in the "stopping" state. I killed the process via TaskMgr and restarted the service, and I'll now perform all tests using the 6.3 GUI only. / comments
The service did not respond gracefully to the restart request, and wound up hung in the "stopping" state. I killed the process via TaskMgr and restarted the service, and I'll now perform all tests...
Nothing in the Event log to indicate that the service stopped / comments
Nothing in the Event log to indicate that the service stopped
The last time this happened, I'm not sure the service crashed at all - there's nothing in the event logs to indicate a crash. It's just that the GUI isn't able to communicate with the service. I just restarted the 6.4 GUI and it reports:
SQB service did not acknowledge receipt of data. (WAIT_TIMEOUT
I'll download the 6.3 GUI and see if it can connect to the service as-is. / comments
The last time this happened, I'm not sure the service crashed at all - there's nothing in the event logs to indicate a crash. It's just that the GUI isn't able to communicate with the service. I ...
I loaded the 6.3 GUI onto another machine - same as 6.4, it fails to connect to the service that's still running on my server (same error message that 6.4 gives, too).
I'll restart the SQL Backup Agent service, and schedule more tests after-hours this evening, using only the 6.3 GUI / comments
I loaded the 6.3 GUI onto another machine - same as 6.4, it fails to connect to the service that's still running on my server (same error message that 6.4 gives, too).
I'll restart the SQL Backup A...
I'm seeing the same behavior (my server is running Windows 2003 SP2)
I've got it running in -sqbdebug mode in hopes of capturing some helpful diagnostic data. / comments
I'm seeing the same behavior (my server is running Windows 2003 SP2)
I've got it running in -sqbdebug mode in hopes of capturing some helpful diagnostic data.
I thought maybe it'd stop if I deleted that server from the group.
Good news:
Yes, that stops a job in progress.
Bad news:
It also caused SQL Backup I/F to crash (invalid object reference)
and the SQL Backup Agent on that server stopped.
Not quite the solution I was looking for... :oops: / comments
I thought maybe it'd stop if I deleted that server from the group.
Good news:
Yes, that stops a job in progress.
Bad news:
It also caused SQL Backup I/F to crash (invalid object reference)
and the ...
FYI: I found a work-around that will suffice for at least simple scripts. It relies on the "On Error:" behavior "Stop executing on database with error" option.
Using a two script approach, script 1 serves to "pre-qualify" the database. I created a simple pass/fail query: "select count(*) from ConfigDistrict" - that's a table guaranteed to exist in each of the databases I'm looking to reach, and equally guaranteed NOT to exist in any of the databases I don't want to reach.
If script 1 fails (i.e. table not found), then script 2 isn't run for that database, but MultiScript forges on to the next database. If script 1 succeeds, then script 2 is invoked for that database.
Suitable only for the simplest, single-script tasks, but it's a start. I do still have to build a Distribution List of "all databases on all servers" every time I've got a task to run (since that list is a moving target), but at least it's a fairly swift "select all, Add>" process.
:idea: It would still be nice if an upcoming release gave Distribution Lists some kind of selection criteria or filtering option! [image] / comments
FYI: I found a work-around that will suffice for at least simple scripts. It relies on the "On Error:" behavior "Stop executing on database with error" option.
Using a two script approach, script...
I'm getting this error (and I didn't even want the license distribution file to start with!) / comments
I'm getting this error (and I didn't even want the license distribution file to start with!)
Let me second brsato's motion: :!: It'd be REALLY nice actually if we could use the backup history of one server and have it restore to another server. / comments
Let me second brsato's motion: :!: It'd be REALLY nice actually if we could use the backup history of one server and have it restore to another server.