Error messages logging and copying.

Hi:

How can I copy the error messages when I execute a SSIS package?. The Progress tab or the Execution results tab both dont have the means to copy the results. I would like the errors to be output to a text file under a directory on my drive system (some thing like C:\SSIS\ExecResults.txt). Is this possible?. If so how do I configure my package to output the package execution results to a text file?.

Any help/suggestions/comments highly appreciated.

Thanks

AK

Right click the package control flow and select Logging. Create and configure text log provider to output events that you want to the text file.

Books Online has detailed instructions on this. By the way, we just release July update to BOL, it is worth download time:
http://www.microsoft.com/downloads/details.aspx?FamilyId=BE6A2C5D-00DF-4220-B133-29C1E0B6585F&displaylang=en

Error Message requires explanation please

Hi
I am a basic user and need to know what this error message means
10025 Write to SQL Server faile
The database that I was using (external application has data hosted to SQL Server 2000) was idle at the time. I understand that this could be a network problem. Is it something as simple as a timeout issue, and if so, how do I rectify this
This message was also displayed
Context: SQLOptLockErrPara
dbo.CA
What does this mean? If anyone could give me an example of why this happens I would really appreciate it
Thank
ShnibniHi!
Do please check if the article at
http://support.microsoft.com/default.aspx?scid=kb;en-us;109787 helps you.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Shnibnib" <anonymous@.discussions.microsoft.com> wrote in message
news:52137B66-4562-4EE9-A579-65E6346ED76F@.microsoft.com...
> Hi,
> I am a basic user and need to know what this error message means:
> 10025 Write to SQL Server failed
> The database that I was using (external application has data hosted to SQL
Server 2000) was idle at the time. I understand that this could be a
network problem. Is it something as simple as a timeout issue, and if so,
how do I rectify this?
> This message was also displayed:
> Context: SQLOptLockErrParam
> dbo.CAL
> What does this mean? If anyone could give me an example of why this
happens I would really appreciate it.
> Thanks
> Shnibnib
>