Microsoft help! Trying to send reports via email using RS2000

I keep getting these errorrs. I am using RS 2000. What does this mean and
how do I fix this issue?
2007-09-25 11:00:25 - + [000] Schedule 143 has already been cached by job
0xF155CEC465AE154F8A73A19FB303190D
2007-09-25 11:01:02 - + [162] Internal request (from SetJobNextRunDate
[reason: schedule will not run again]) to deactivate schedule 143
2007-09-25 11:01:02 - + [163] 1 operations applied (0 remaining)
2007-09-25 11:03:32 - + [000] Schedule 144 has already been cached by job
0xEA305CE0F980DA49B68D71B6CC693AA9
2007-09-25 11:04:01 - + [162] Internal request (from SetJobNextRunDate
[reason: schedule will not run again]) to deactivate schedule 144
2007-09-25 11:04:01 - + [163] 1 operations applied (0 remaining)On Sep 25, 10:24 am, OriginalStealth
<OriginalStea...@.discussions.microsoft.com> wrote:
> I keep getting these errorrs. I am using RS 2000. What does this mean and
> how do I fix this issue?
> 2007-09-25 11:00:25 - + [000] Schedule 143 has already been cached by job
> 0xF155CEC465AE154F8A73A19FB303190D
> 2007-09-25 11:01:02 - + [162] Internal request (from SetJobNextRunDate
> [reason: schedule will not run again]) to deactivate schedule 143
> 2007-09-25 11:01:02 - + [163] 1 operations applied (0 remaining)
> 2007-09-25 11:03:32 - + [000] Schedule 144 has already been cached by job
> 0xEA305CE0F980DA49B68D71B6CC693AA9
> 2007-09-25 11:04:01 - + [162] Internal request (from SetJobNextRunDate
> [reason: schedule will not run again]) to deactivate schedule 144
> 2007-09-25 11:04:01 - + [163] 1 operations applied (0 remaining)
This link might be helpful.
http://support.microsoft.com/kb/295378
Regards,
Enrique Martinez
Sr. Software Consultant

mgmnt studio express won't shrink .ldf files

I'm attempting to truncate/shrink a db (mdf & ldf) to be able to zip it and email it. From Object Explorer I select the db->tasks->shrink->files->filetype->log->release unused spage or reorganize->shrink file to (0mb). This action does not change the size of the .ldf file. Shrinking the mdf works just like SQL 2000 - as expected. Why don't the actions taken do what they imply for the .ldf file? If this is not what the selections mean, what do they mean?

thanks, jack

If you want the LDF to skrink to 0mb then you need to truncate the log because SQL Server in shrink mode reserves what was active log now called virtual log before releasing space to the OS. You can run DBCC Shrinkfile and see what error you get because 2005 now logs the error in the error log. Run a search for DBCC Shrinkfile and Truncate log in the BOL. Hope this helps.

|||Caddre, your response led me to information that explains the 'reality' of dealing with the logfile. In my case since I 'want' an empty db to distribute,I found that I could just detach the db, then delete the .ldf file. When I re-attach a 'new' empty log file is created. -- thanks, jack