Comments
Sort by recent activity
You have to restart the Windows service on the host.
Interestingly, the client can't even connect to the service by the new IP address until the service is restarted. That's what led us to the answer. / comments
You have to restart the Windows service on the host.
Interestingly, the client can't even connect to the service by the new IP address until the service is restarted. That's what led us to the answer.
I encountered these errors immediately after the upgrade while testing the app from the server console. I was running Internet Explorer there (not sure which version) but run FireFox 11.0 on my desktop. I do not appear to be having JS issues when hitting SQL Monitor from my desktop via FireFox. / comments
I encountered these errors immediately after the upgrade while testing the app from the server console. I was running Internet Explorer there (not sure which version) but run FireFox 11.0 on my des...
In SQL Response there was an alert labeled "Job did not start". I do not see that alert in SQL Monitor and wonder what happened to it. It seems that it was a good compliment to the "Job duration unusual", especially in cases like the one posted above. We had a similar issue where a job hung and we didn't notice it for over a day. In the past with SQL Response, I thought we would've gotten an alert that a scheduled job didn't start.
Or maybe that wouldn't be true if you can only determine that after the previous instance of the job finishes, which in our case didn't happen until we killed it.
Can you explain why the "did not start" alert is no longer part of the product? / comments
In SQL Response there was an alert labeled "Job did not start". I do not see that alert in SQL Monitor and wonder what happened to it. It seems that it was a good compliment to the "Job duration un...
Peter,
That was it. I created a share, changed the path in my job and everything ran as expected, including the deletion of old backup files.
Thanks a bunch.
Jim / comments
Peter,
That was it. I created a share, changed the path in my job and everything ran as expected, including the deletion of old backup files.
Thanks a bunch.
Jim
Yes, the other servers use paths that do not contain spaces. That must be it. So if I change it to use a share name instead of the file path I should be all set? I'll try that.
I've always hated the default installation path and unfortunately inherited this server and didn't get the chance to change it at install. / comments
Yes, the other servers use paths that do not contain spaces. That must be it. So if I change it to use a share name instead of the file path I should be all set? I'll try that.
I've always hated th...
The script from which we call SQL Backup handles various steps - creating a subdirectory (if necessary) for the backup files, backing up the transaction log, doing a RESTORE VERIFYONLY on the backup file, then finally deleting aged files via the sqbutility XP - see syntax in original post. It is only the last step that is failing.
I'm hoping that a Red Gate technician can give me some ideas on what to look at next, as it appears to be a valid call to the XP but I'm not getting the desired result. / comments
The script from which we call SQL Backup handles various steps - creating a subdirectory (if necessary) for the backup files, backing up the transaction log, doing a RESTORE VERIFYONLY on the backu...