How to Manage Errors with one file

Hi,

I am pretty new in SSIS 2005, and I have some problems... I want to add logging and error management in my package. I found how to made logging. But for errors managing i have some difficulties.

In my package I have only a flat file source and an ole db destination. I want add errors management for both of them. So I create a connection manager for errors on a file. For both element i add redirect row for all available error type and then i add 2 flat file destination. I branch red arrows of flat file source and ole db destination to the flat file destination.

When i run packge i have an error which indicate me that file error is already take by another process... I don't understand why. And i don't want to create on file for each element on package. Have you any idea on why i have this error? Or how can i made what i want do?

Krest

Before going too far - could you checj if your redirect destination do not point to the same file as primary error file? What happens if you turn off package logging?

|||

Hi,

Thanks for you help.

So, i use the same file for the two flat file destination, because i want all my error in the same file. I i turn off logging (SSISmenu->logging and all checkboxes are not checked.

I have the same error as before. here is the exact error message [Flat File Destination 1 [806]] Warning: The process cannot access the file because it is being used by another process.

krest

How to log disconnects?

Check the app logs first, are they logging query/conection
errors,timeouts,etc?
And look for specific errors (ADO,OLE-DB,etc)
Will wrote:
> I need to log user disconnects for a specific DB. I do not know how to
> do this relabily. The application owner is under the impression that
> our SQL cluster is disconnecting their users. Which I am fairly
> confident is not the case.
> Any ideas on how to do this? Specifically disconnects that are not
> 'requested' but either forced or lost.
> Thanks!That kind of logging 'should' happen on the client. For a limited time span,
you may wish to use Profiler.
Application timeout is the first thing to explore. Check the ADO connection
timeout (I think the default is 60 seconds -but I don't remember with
certainty.)
--
Arnie Rowland, YACE*
"To be successful, your heart must accompany your knowledge."
*Yet Another certification Exam
"Will" <wfj5444@.gmail.com> wrote in message
news:1151588003.074757.326780@.m73g2000cwd.googlegroups.com...
>I need to log user disconnects for a specific DB. I do not know how to
> do this relabily. The application owner is under the impression that
> our SQL cluster is disconnecting their users. Which I am fairly
> confident is not the case.
> Any ideas on how to do this? Specifically disconnects that are not
> 'requested' but either forced or lost.
> Thanks!
>|||I need to log user disconnects for a specific DB. I do not know how to
do this relabily. The application owner is under the impression that
our SQL cluster is disconnecting their users. Which I am fairly
confident is not the case.
Any ideas on how to do this? Specifically disconnects that are not
'requested' but either forced or lost.
Thanks!|||Check the app logs first, are they logging query/conection
errors,timeouts,etc?
And look for specific errors (ADO,OLE-DB,etc)
Will wrote:
> I need to log user disconnects for a specific DB. I do not know how to
> do this relabily. The application owner is under the impression that
> our SQL cluster is disconnecting their users. Which I am fairly
> confident is not the case.
> Any ideas on how to do this? Specifically disconnects that are not
> 'requested' but either forced or lost.
> Thanks!|||That kind of logging 'should' happen on the client. For a limited time span,
you may wish to use Profiler.
Application timeout is the first thing to explore. Check the ADO connection
timeout (I think the default is 60 seconds -but I don't remember with
certainty.)
--
Arnie Rowland, YACE*
"To be successful, your heart must accompany your knowledge."
*Yet Another certification Exam
"Will" <wfj5444@.gmail.com> wrote in message
news:1151588003.074757.326780@.m73g2000cwd.googlegroups.com...
>I need to log user disconnects for a specific DB. I do not know how to
> do this relabily. The application owner is under the impression that
> our SQL cluster is disconnecting their users. Which I am fairly
> confident is not the case.
> Any ideas on how to do this? Specifically disconnects that are not
> 'requested' but either forced or lost.
> Thanks!
>|||Right,
That is the issue only one application out of many is seeing the issue.
It does not sound like an SQL Server issue. They are seeing the
disconnects on their side. We have no other users reporting any other
issues or symptoms.
Thanks,
Will
Arnie Rowland wrote:[vbcol=seagreen]
> That kind of logging 'should' happen on the client. For a limited time spa
n,
> you may wish to use Profiler.
> Application timeout is the first thing to explore. Check the ADO connectio
n
> timeout (I think the default is 60 seconds -but I don't remember with
> certainty.)
> --
> Arnie Rowland, YACE*
> "To be successful, your heart must accompany your knowledge."
> *Yet Another certification Exam
>
> "Will" <wfj5444@.gmail.com> wrote in message
> news:1151588003.074757.326780@.m73g2000cwd.googlegroups.com...|||Right,
That is the issue only one application out of many is seeing the issue.
It does not sound like an SQL Server issue. They are seeing the
disconnects on their side. We have no other users reporting any other
issues or symptoms.
Thanks,
Will
Arnie Rowland wrote:[vbcol=seagreen]
> That kind of logging 'should' happen on the client. For a limited time spa
n,
> you may wish to use Profiler.
> Application timeout is the first thing to explore. Check the ADO connectio
n
> timeout (I think the default is 60 seconds -but I don't remember with
> certainty.)
> --
> Arnie Rowland, YACE*
> "To be successful, your heart must accompany your knowledge."
> *Yet Another certification Exam
>
> "Will" <wfj5444@.gmail.com> wrote in message
> news:1151588003.074757.326780@.m73g2000cwd.googlegroups.com...

how to link executionid of sysdtslog90

I have enabled logging using database.

When I try to query the sysdtslog90 table using System::ExecutionInstanceGUID to link executionid - it is not matching.

Any resolution?

Thanks

The variable System::ExecutionInstanceGUID always matches the sysdtslog90.executionid column when I try it.

Are the times matching up? Are you looking in the right table? Try using a Script Task to fire an event with the ExecutionInstanceGUID in the description text, so that it is logged and you can compare the two values in the same row.

|||

It worked when I pass the System::ExecutionInstanceGUID as VARCHAR parameter instead of GUID in SQL Task parameter mapping. And when the stored procedure recieves the same parameter as uniqueidentifier

sorry for my late response.

Thanks

how to link executionid of sysdtslog90

I have enabled logging using database.

When I try to query the sysdtslog90 table using System::ExecutionInstanceGUID to link executionid - it is not matching.

Any resolution?

Thanks

The variable System::ExecutionInstanceGUID always matches the sysdtslog90.executionid column when I try it.

Are the times matching up? Are you looking in the right table? Try using a Script Task to fire an event with the ExecutionInstanceGUID in the description text, so that it is logged and you can compare the two values in the same row.

|||

It worked when I pass the System::ExecutionInstanceGUID as VARCHAR parameter instead of GUID in SQL Task parameter mapping. And when the stored procedure recieves the same parameter as uniqueidentifier

sorry for my late response.

Thanks

|||

I just ran into the same issue. I noticed that all of a sudden the executionid's between sysdtslog90 and the logging table modeled from project real (audit.executionlog) were not matching. I changed the execute sql task that calls the audit.usp_OnBeginPackageEvent stored procedure to use the System::ExecutionInstanceGUID variable as a varchar instead of GUID and now all of sudden they match. Anyone have any idea why this is happening? I know it used to work, and on the service pack sp2.

|||I don't know why it's happening, but I've encountered the same thing a few times.

how to link executionid of sysdtslog90

I have enabled logging using database.

When I try to query the sysdtslog90 table using System::ExecutionInstanceGUID to link executionid - it is not matching.

Any resolution?

Thanks

The variable System::ExecutionInstanceGUID always matches the sysdtslog90.executionid column when I try it.

Are the times matching up? Are you looking in the right table? Try using a Script Task to fire an event with the ExecutionInstanceGUID in the description text, so that it is logged and you can compare the two values in the same row.

|||

It worked when I pass the System::ExecutionInstanceGUID as VARCHAR parameter instead of GUID in SQL Task parameter mapping. And when the stored procedure recieves the same parameter as uniqueidentifier

sorry for my late response.

Thanks

|||

I just ran into the same issue. I noticed that all of a sudden the executionid's between sysdtslog90 and the logging table modeled from project real (audit.executionlog) were not matching. I changed the execute sql task that calls the audit.usp_OnBeginPackageEvent stored procedure to use the System::ExecutionInstanceGUID variable as a varchar instead of GUID and now all of sudden they match. Anyone have any idea why this is happening? I know it used to work, and on the service pack sp2.

|||I don't know why it's happening, but I've encountered the same thing a few times.