Comments
Sort by recent activity
I didn't even realize how many log files had "piled" up on my box. There really needs to be a way to delete old logs. I had over 13000 of them!! / comments
I didn't even realize how many log files had "piled" up on my box. There really needs to be a way to delete old logs. I had over 13000 of them!!
No virus checkers doing anything. This has to do purely with GotoMyPC and terminal services. / comments
No virus checkers doing anything. This has to do purely with GotoMyPC and terminal services.
I am using Windows 2000 with all the service packs and updates (according to Windows Update). @version results this:
I am using Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Developer Edition on Windows NT 5.0 (Build 2195: Service Pack 4) / comments
I am using Windows 2000 with all the service packs and updates (according to Windows Update).@version results this:
I am using Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:...
see PM / comments
see PM
I can pretty much repeat this on demand now. / comments
I can pretty much repeat this on demand now.
Yes along those lines. I haven't done it again since I want it to backup [image]
I have a couple hundred DB's that backup. It does some of them, I log into it, open Explorer and Enterprise Manager. Close everything, log off the machine. Then I get the error in email. / comments
Yes along those lines. I haven't done it again since I want it to backup
I have a couple hundred DB's that backup. It does some of them, I log into it, open Explorer and Enterprise Manager. Clo...
Here is the VDI log:
2005/04/25 22:06:53 pid(1060) tid(1292)
Error on SQLBACKUP_191761517
Error at TriggerAbort: invoked
2005/04/25 22:06:53 pid(300) tid(484)
Error on SQLBACKUP_191761517
Error at CVD::GetCommand: AbortDetected
2005/04/25 22:06:53 pid(1060) tid(1292)
Error on SQLBACKUP_191761517
Error at TriggerAbort: invoked
2005/04/25 22:06:53 pid(300) tid(484)
Error on SQLBACKUP_191761517
Error at TriggerAbort: invoked
2005/04/25 22:06:53 pid(1060) tid(1292)
Error on SQLBACKUP_191761517
Error at SVDS::CloseDevice: Abort detected
2005/04/25 22:06:53 pid(300) tid(2324)
Error on SQLBACKUP_191761517
Error at TriggerAbort: invoked
2005/04/25 22:06:53 pid(1060) tid(1292)
Error on SQLBACKUP_191761517
Error at TriggerAbort: invoked
2005/04/25 22:06:53 pid(1060) tid(1596)
Error on SQLBACKUP_191761517
Error at TriggerAbort: invoked
2005/04/27 22:24:52 pid(1060) tid(1292)
Error on SQLBACKUP_88112141
Error at TriggerAbort: invoked
2005/04/27 22:24:52 pid(1060) tid(1292)
Error on SQLBACKUP_88112141
Error at TriggerAbort: invoked
2005/04/27 22:24:52 pid(1060) tid(1292)
Error on SQLBACKUP_88112141
Error at TriggerAbort: invoked
2005/04/27 22:24:52 pid(516) tid(2784)
Error on SQLBACKUP_88112141
Error at TriggerAbort: invoked
2005/04/27 22:24:52 pid(1060) tid(1292)
Error on SQLBACKUP_88112141
Error at SVDS::CloseDevice: Abort detected
2005/04/27 22:24:52 pid(516) tid(3644)
Error on SQLBACKUP_88112141
Error at TriggerAbort: invoked
2005/04/27 22:24:52 pid(1060) tid(1292)
Error on SQLBACKUP_88112141
Error at TriggerAbort: invoked
2005/04/27 22:24:53 pid(1060) tid(1500)
Error on SQLBACKUP_88112141
Error at TriggerAbort: invoked / comments
Here is the VDI log:
2005/04/25 22:06:53 pid(1060) tid(1292)
Error on SQLBACKUP_191761517
Error at TriggerAbort: invoked
2005/04/25 22:06:53 pid(300) tid(484)
Error on SQLBACKUP_191761517
Error at ...
Nope - the only thing that makes this happen is if I am logged into the machine remotely while the RG SQL Backup is running, open the EM, close it, log off the computer. / comments
Nope - the only thing that makes this happen is if I am logged into the machine remotely while the RG SQL Backup is running, open the EM, close it, log off the computer.