Error executing xp_cmdshell from within a SQL task in a DTS package...

Hello

I am trying to execute xp_cmdshell' from within a DTS package that
was created by another person. When I try to execute that SQL Task'
selectively from within the package, I get the following error
message:

Error Title: Package Error
Error Details:
Error Source: Microsoft OLE DB Provider for SQL Server
Error Description: xpsql.cpp: Error 87 from GetProxyAccount on line
604

Why is this error message popping up? When I create a new package
(myself) and create an exact same SQL task as above and run it, the
SQL task runs fine.

Appreciate any help / feedback.

Thanks in Advance
Jagannathan SanthanamWhen a sysadmin role member executes xp_cmdshell, it runs under the
security context of the SQL Server service account. However, when a
non-sysadmin user executes the proc, it runs under the SQL Agent proxy
account.

It looks like there is an issue with your configuration of the proxy
account and/or SQL Server service account security. Enterprise Manager
automatically assigns the necessary rights to these accounts when these
are specified or changed via the GUI. Alternatively, you can manually
assign the following Windows rights to the accounts.

<Excerpt
href="http://support.microsoft.com/default.aspx?scid=kb;en-us;264155"
MSSQLServer and SQLServerAgent Services
- Act as part of the Operating System.
- Increase Quotas.
- Replace a process level token.
- Log on as a batch job.
SQLAgentCmdExec Account
- Log on as a batch job.

NOTE: You must restart the entire server, not just the SQL Services, in
order for any changes made to user rights permissions to take effect.

</Excerpt
--
Hope this helps.

Dan Guzman
SQL Server MVP

--------
SQL FAQ links (courtesy Neil Pike):

http://www.ntfaq.com/Articles/Index...epartmentID=800
http://www.sqlserverfaq.com
http://www.mssqlserver.com/faq
--------

"Jagannathan Santhanam" <jags_32@.yahoo.com> wrote in message
news:605df08e.0311170307.39d9b1f1@.posting.google.c om...
> Hello
> I am trying to execute 'xp_cmdshell' from within a DTS package that
> was created by another person. When I try to execute that 'SQL Task'
> selectively from within the package, I get the following error
> message:
> Error Title: Package Error
> Error Details:
> Error Source: Microsoft OLE DB Provider for SQL Server
> Error Description: xpsql.cpp: Error 87 from GetProxyAccount on line
> 604
>
> Why is this error message popping up? When I create a new package
> (myself) and create an exact same SQL task as above and run it, the
> SQL task runs fine.
> Appreciate any help / feedback.
> Thanks in Advance
> Jagannathan Santhanam

Error Executing Parallel SQL Tasks

I have three SQL tasks executing in parallel in an Integration Services package.

+-B-+
A-+-C-+-E
+-D-+

It starts with task A; then B, C, and D all execute in parallel; and finally task E runs after BCD are done.

B, C, and D are all Execute SQL tasks, all with the same connection manager. Here is their code:

B) SELECT CASE WHEN COUNT(*) = 0 THEN 0 ELSE 1 END AS Process
FROM temp_B

C) SELECT CASE WHEN COUNT(*) = 0 THEN 0 ELSE 1 END AS Process
FROM temp_C

D) SELECT CASE WHEN COUNT(*) = 0 THEN 0 ELSE 1 END AS Process
FROM temp_D

Each one is setting a binary value to a package variable (using Result Set settings) based on the count of records from different tables.

This works with no problems when I run it against one server (development). But when I switch to the production server, task B and D both fail. I'v checked to make sure all of the temp tables exist in the database for that connection manager and that all three have the same connection manager - all is okay.

Here's the trickier part. When I'm still pointing to the production server and I run these tasks individually, they are all successful. It is only when they are attempting to run in parallel that they fail.

Here is the Output error:
Error: 0xC002F210 at Process Med?, Execute SQL Task: Executing the query "SELECT CASE WHEN COUNT(*) = 0 THEN 0 ELSE 1 END AS Process FROM temp_B" failed with the following error: "Invalid object name 'temp_B'.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

What could be causing this? I'm at a loss.

Why do they fail? Do you have an error message?

-Jamie

|||Sorry Jamie - I neglected to put in the error message at first. It's now in the original post.|||

perhaps the error message is a red herring. Can you use Profiler to check that everything is OK when the tasks get fired.

That's just an idea for diagnosis. I'm at a a loss as to what the problem might be!

-Jamie

|||

Problem solved.

Sorry about the errant post - it was actually not a parallel issue.

One of the previous steps changed the conenction manager's database setting and was doing it incorrectly. The tasks were hitting a false database. Not sure why task C didn't fail - but it's moot.

Thanks for your help.

Error during incremental processing of dimension

I have an integration services package that includes a data flow transformation that does an incremental processing for a dimension. The task executes successfully with a small amount of records in the data source query. However, when I attempt to process the large set, I get the following errors:

[Dimension Processing [1192]] Error: Parser: An error occurred during pipeline processing.
[Dimension Processing [1192]] Error: Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation.
[Dimension Processing [1192]] Error: Errors in the OLAP storage engine: An error occurred while the 'Last Name' attribute of the 'Consumer' dimension from the 'DataWarehouseOLAP' database was being processed.
[Dimension Processing [1192]] Error: File system error: The record ID is incorrect. Physical file: . Logical file: .
[Dimension Processing [1192]] Error: Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation.
[Dimension Processing [1192]] Error: Errors in the OLAP storage engine: An error occurred while the 'Email Address' attribute of the 'Consumer' dimension from the 'DataWarehouseOLAP' database was being processed.
[Dimension Processing [1192]] Error: File system error: The record ID is incorrect. Physical file: . Logical file: .
[DTS.Pipeline] Error: The ProcessInput method on component "Dimension Processing" (1192) failed with error code 0x80004005. The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running.
[DTS.Pipeline] Error: Thread "WorkThread0" has exited with error code 0x80004005.
-

I am trying to figure out more information about these errors, but cannot figure out what the problem is. Can someone point me in the right direction?

Clayton

We just encountered the same error. Did you figure out what it was?|||No I did not. I am still stuck on it. I will let you know if I do.|||

Please log your situation in http://connect.microsoft.com/sql. If you willing to share your data to troubleshoot, make sure you provide your contact information.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Hi,

I am facing the same issue. Can you please let me know if there is a solution for resloving this ?

Regards,

Dinesh Reddy N Y

|||

Sounds like you're exceeding the 4 GB limit for string stores. Do you have an attribute with a string key?

Error Deleteing Remote File

I am trying to delete a remote file as part of an SSIS package. The FTP Task I have to retrieve the file works fine. I use the same remote path variable and connection manager for both tasks. However, when the delete step executes I receive the error:

Error: 0xC002918E at FTP Task, FTP Task: Unable to delete remote files using "FTP Connection Manager 1".

Sounds like a permission issue.|||This is a known problem with the FTP task in SSIS trying to delete a file on a non-Windows FTP servers.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1074276&SiteID=1

I do not know if SP2 fixes this problem or not.
|||I can delete the files from the FTP command line. I have a DTS package that uses a .bat file to do this, I just want to put it into SSIS. Thanks for the info.|||Is there a way to tell if the server is not Windows?|||HAs this issue been aknowledge by Microsoft? [Microsoft follow-up]|||

I don't understand your question. Your the closest thing to Microsoft that I have seen involved in any discussion in this area, anywhere I've looked.

Tim

|||Yes, it is still an active bug report, reported over 1 year ago.

See: https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=126207
|||No, you would have to know ahead of time what kind of server you are talking too.

However, there is a workaround on the thread I gave in the previous message. Basically, don't use the FTP task, use a script task and code it by hand.

|||We are aware of this bug and it will be fixed in the coming major release. Please contact CSS if you need a hotifx. Thanks

Error code: 0x80004005

I created a package that refreshes tables on one SQL Server to another SQL Server. First, I use an ExecuteSQL task to truncate the tables. Then I use a Data Flow task to copy the tables from one server to the other. Finally I update a log table. It was working fine with four tables. I added another table to the refresh and now I get these error messages:

[Source - RbcAcctSegment [1096]] Error: An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Unspecified error". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure".

[Source - RbcAcctSegment [1096]] Error: Opening a rowset for "[dbo].[RbcAcctSegment]" failed. Check that the object exists in the database.

[DTS.Pipeline] Error: component "Source - RbcAcctSegment" (1096) failed the pre-execute phase and returned error code 0xC02020E8.

RbcAcctSegment is the new table that I added. The errors occur in the Data Flow task. We have tried running this on a different workstation with the same results.

What would cause this?

Fred

Try changing the connection propery 'Retain Same Connection' to FALSE.|||The 'Retain Same Connection' property is already set to FALSE for both Source and Destination Connection Managers.|||

I believe I found the problem.

I made a few changes in the Data Flow task. In the Properties of the Destination components I changed the OpenRowset property to include the database name beside the table name. Not all the Destination components had the database name.

Before it was [dbo].[TableName] and I changed it to [DatabaseName].[dbo].[TableName].

Fred

|||

It wasn't the problem. It worked one time.

Is there a limit on how many tables you can copy in one DataFlow task?

Fred

|||Now that you mention, I do remember we did have a similar error when we had around 20 in a data flow and then we moved some of them out to a new data flow and it worked fine. I had to put a precedence between the two.

Error code: 0x80004005

I created a package that refreshes tables on one SQL Server to another SQL Server. First, I use an ExecuteSQL task to truncate the tables. Then I use a Data Flow task to copy the tables from one server to the other. Finally I update a log table. It was working fine with four tables. I added another table to the refresh and now I get these error messages:

[Source - RbcAcctSegment [1096]] Error: An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Unspecified error". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure".

[Source - RbcAcctSegment [1096]] Error: Opening a rowset for "[dbo].[RbcAcctSegment]" failed. Check that the object exists in the database.

[DTS.Pipeline] Error: component "Source - RbcAcctSegment" (1096) failed the pre-execute phase and returned error code 0xC02020E8.

RbcAcctSegment is the new table that I added. The errors occur in the Data Flow task. We have tried running this on a different workstation with the same results.

What would cause this?

Fred

Try changing the connection propery 'Retain Same Connection' to FALSE.|||The 'Retain Same Connection' property is already set to FALSE for both Source and Destination Connection Managers.|||

I believe I found the problem.

I made a few changes in the Data Flow task. In the Properties of the Destination components I changed the OpenRowset property to include the database name beside the table name. Not all the Destination components had the database name.

Before it was [dbo].[TableName] and I changed it to [DatabaseName].[dbo].[TableName].

Fred

|||

It wasn't the problem. It worked one time.

Is there a limit on how many tables you can copy in one DataFlow task?

Fred

|||Now that you mention, I do remember we did have a similar error when we had around 20 in a data flow and then we moved some of them out to a new data flow and it worked fine. I had to put a precedence between the two.

error code from DTEXEC not 0 nor 1

I would like to send back to MS-DOS (ERRORLEVEL) an error code 2 ( different from 0 and 1) via a scripting Task.

Our package are started with the DTEXEC Utility.

In general, how can i send back a flag saying "There were warnings" during the execution of a Package

Warnings can happen with successful package executions, and for that matter, so can errors.

There are a numerous ways to figure out there were warnings though, such that a shell caller is aware of that fact.

One, capture the console output from dtexec and look through the captured text for the warning event.

Two, create a console utility which calls Package.Execute() and iterates through the .Warnings collection. If the count > 0, return what you want as the process exit code.

Three, use logging. Configure the package to use the native SSIS logging facilities to write log entires. Read the produced log provider for warning events.

Four, use a package level OnWarning event handler. Inside the event handler, set something external to the package (file, db, message queue, doesn't matter) which is readable post-execution.

error code 0xC0202025

i need to export the contents of a sql server 2005 table to excel in ssis. there are two nvarchar(max) colums in my table. the data flow task in my package fails unless i remove these two columns from the table, then it works fine. the error code being returned is 0xC0202025. HELP!http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=412859&SiteID=1|||no luck converting the columns to nvarchar(4000) either.|||Did you recreate the metadata in the Excel Destination?|||yes.

Error at Transfer Objects Task: The source server can not be the same as the destination server.

SQL Server 2005 - June CTP

Error at Transfer Objects Task [Transfer Objects Task]: The source server can not be the same as the destination server.

Why not? I'm trying to transfer a set of tables from one database to another. Both databases happen to be on the same server. I understand that the source *database* cannot be the same as the destination *database*. But why can't I use the Transfer Objects task to transfer objects from one database to another on the same server?

Thanks for your help!

I can easily reproduce this. I would agree with Joseph, moving between databases on the same server is a legitamate requirement.

-Jamie|||I bumped into this problem several weeks ago and was only told "there are known problems with the transfer objects task"

My work around is to use an execute sql task that uses a fully qualified Insert statement to insert records into database 2 from database 1

Insert database2.dbo.tableA select * from database1.dbo.tableA

While it is a royal pain to have to have a line per table (250+ tables..changing on a regular basis) it does work and I get my records from the staging DB to the production

Paul Pisarek|||Paul,

Sorry about the curt response. Please reactivate the bug and follow through until you're satisfied with either the explaination or the resolution.

thanks,
ash|||

Dear Sharma,

Could you please update everyone whether the bug is resolved or yet to be resolved as we are facing a lot of issues in this task even after installing Service Pack Sp1.

Thanks,

Pradeep

+91 99451 20960

Pradeep.au@.gmail.com

|||

As far as I can see, with the production release of VS 2005, the original bug which I reported 'the source server cannot be the same as the destination server' has been corrected. I just used the Transfer SQL Server Objects task to transfer all objects (i.e. Tables, Views, Data, Indexes, etc.) from one database to another on the same server.

What 'issues' specifically are you encountering?

- Joe Geretz -

Error at Transfer Objects Task: The source server can not be the same as the destination ser

SQL Server 2005 - June CTP

Error at Transfer Objects Task [Transfer Objects Task]: The source server can not be the same as the destination server.

Why not? I'm trying to transfer a set of tables from one database to another. Both databases happen to be on the same server. I understand that the source *database* cannot be the same as the destination *database*. But why can't I use the Transfer Objects task to transfer objects from one database to another on the same server?

Thanks for your help!

I can easily reproduce this. I would agree with Joseph, moving between databases on the same server is a legitamate requirement.

-Jamie|||I bumped into this problem several weeks ago and was only told "there are known problems with the transfer objects task"

My work around is to use an execute sql task that uses a fully qualified Insert statement to insert records into database 2 from database 1

Insert database2.dbo.tableA select * from database1.dbo.tableA

While it is a royal pain to have to have a line per table (250+ tables..changing on a regular basis) it does work and I get my records from the staging DB to the production

Paul Pisarek|||Paul,

Sorry about the curt response. Please reactivate the bug and follow through until you're satisfied with either the explaination or the resolution.

thanks,
ash|||

Dear Sharma,

Could you please update everyone whether the bug is resolved or yet to be resolved as we are facing a lot of issues in this task even after installing Service Pack Sp1.

Thanks,

Pradeep

+91 99451 20960

Pradeep.au@.gmail.com

|||

As far as I can see, with the production release of VS 2005, the original bug which I reported 'the source server cannot be the same as the destination server' has been corrected. I just used the Transfer SQL Server Objects task to transfer all objects (i.e. Tables, Views, Data, Indexes, etc.) from one database to another on the same server.

What 'issues' specifically are you encountering?

- Joe Geretz -

Error at parse query

Hello

I have the following:

One data flow task in the control flow
In this data flow task I have an OLE DB Source with the following sql command

'.... where cc = ?'

Then I click on the Parameters button and I map the ? to the right Parameter

Parameter0 = User::var_cc

When I click on parse query I get the following message :

"Parameter Information cannot be derived from SQL statements. Set parameter information before preparing command."

Anyone has an idea?
ThxThis is a known issue. Parse Query does not know how to use the parameters you mapped.

If you do not get any error after clicking OK, your query should be fine and you can safely ignore the error from Parse Query.

ERROR AT DATA FLOW TASK

HI, I HAVE A NEW PROBLEM...HOPE SOMEONE KNOWS WHAT THE $#%#$ IS HAPPENING. HERE IT′S THE THING: I′M USING A DATA FLOW TASK TO READ DATA FROM AN ORACLE SERVER AND TRANSFER THE INFO TO MY SQL 2005 SERVER, THE SOURCE IS AVAILABLE AND THE CONNECTION IS WORKING, I'M USING A DATA READER SOURCE TO CONNECT AND EXTRACT. I′VE PUT THIS DTS IN A JOB AND IT WAS OK, IT HAD BEEN RUNNING OK FOR ALMOST A MONTH BUT SUDDENLY HIS MORNING IT FAILED WITH THE FOLLOWING ERROR:

SSIS package "SAZSIE_CargaVentasSeguros (1).dtsx" starting.

Information: 0x4004300A at Extrae SAZ_GranoO_New, DTS.Pipeline: Validation phase is beginning.

Information: 0x4004300A at Extrae SAZ_GranoO_New, DTS.Pipeline: Validation phase is beginning.

Information: 0x40043006 at Extrae SAZ_GranoO_New, DTS.Pipeline: Prepare for Execute phase is beginning.

Information: 0x40043007 at Extrae SAZ_GranoO_New, DTS.Pipeline: Pre-Execute phase is beginning.

Information: 0x4004300C at Extrae SAZ_GranoO_New, DTS.Pipeline: Execute phase is beginning.

Error: 0xC0047062 at Extrae SAZ_GranoO_New, SAZ_GranoONew [421]: System.NullReferenceException: Object reference not set to an instance of an object.

at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.PrimeOutput(Int32 outputs, Int32[] outputIDs, PipelineBuffer[] buffers)

at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostPrimeOutput(IDTSManagedComponentWrapper90 wrapper, Int32 outputs, Int32[] outputIDs, IDTSBuffer90[] buffers, IntPtr ppBufferWirePacket)

Error: 0xC0047038 at Extrae SAZ_GranoO_New, DTS.Pipeline: The PrimeOutput method on component "SAZ_GranoONew" (421) returned error code 0x80004003. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing.

Error: 0xC0047021 at Extrae SAZ_GranoO_New, DTS.Pipeline: Thread "SourceThread0" has exited with error code 0xC0047038.

Information: 0x402090DF at Extrae SAZ_GranoO_New, OLE DB Destination [1022]: The final commit for the data insertion has started.

Information: 0x402090E0 at Extrae SAZ_GranoO_New, OLE DB Destination [1022]: The final commit for the data insertion has ended.

Information: 0x40043008 at Extrae SAZ_GranoO_New, DTS.Pipeline: Post Execute phase is beginning.

Information: 0x40043009 at Extrae SAZ_GranoO_New, DTS.Pipeline: Cleanup phase is beginning.

Information: 0x4004300B at Extrae SAZ_GranoO_New, DTS.Pipeline: "component "OLE DB Destination" (1022)" wrote 19522 rows.

Task failed: Extrae SAZ_GranoO_New

Warning: 0x80019002 at SAZSIE_CargaVentasSeguros: The Execution method succeeded, but the number of errors raised (3) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.

SSIS package "SAZSIE_CargaVentasSeguros (1).dtsx" finished: Failure.

THE DATA HAS BEEN COPIED INTO MY DESTINATION TABLE, BUT THE PACKAGE ENDS IN AN ERROR, WHAT IS THE PROBLEM WITH THIS?

PLASE SOMEONE !!!!

THANKS!!!!!!!

the problem was that those idiots changed the source by adding a new field in their table and my package wasn′t updated with the new definition of it... thanks anyway...|||take it easy|||

ruk_walled wrote:

the problem was that those idiots changed the source by adding a new field in their table and my package wasn′t updated with the new definition of it... thanks anyway...

Hence you should always use a SQL statement rather than referencing a table by name!

-Jamie

|||

it′s exactly what i did... after the error of course ;)

thanks for your advice!!!

|||Interesting. I just ran into this same problem, with the same cause - source table structure changed.

However, the query I was using to retrieve from it was of the form "select * from <blah>".

It took deleting and recreating the step to fix the error. Do SSIS packages cache table structures or something?|||

LpAngelRob wrote:

It took deleting and recreating the step to fix the error. Do SSIS packages cache table structures or something?

Any component in a dataflow that acceses something external to the package has something called the ExternalMetadata collection which is information about what that external thing "looks" like. If that external thing doesn't look like what the SSIS package is expecting - you'll get problems.

-Jamie

ERROR AT DATA FLOW TASK

HI, I HAVE A NEW PROBLEM...HOPE SOMEONE KNOWS WHAT THE $#%#$ IS HAPPENING. HERE IT′S THE THING: I′M USING A DATA FLOW TASK TO READ DATA FROM AN ORACLE SERVER AND TRANSFER THE INFO TO MY SQL 2005 SERVER, THE SOURCE IS AVAILABLE AND THE CONNECTION IS WORKING, I'M USING A DATA READER SOURCE TO CONNECT AND EXTRACT. I′VE PUT THIS DTS IN A JOB AND IT WAS OK, IT HAD BEEN RUNNING OK FOR ALMOST A MONTH BUT SUDDENLY HIS MORNING IT FAILED WITH THE FOLLOWING ERROR:

SSIS package "SAZSIE_CargaVentasSeguros (1).dtsx" starting.

Information: 0x4004300A at Extrae SAZ_GranoO_New, DTS.Pipeline: Validation phase is beginning.

Information: 0x4004300A at Extrae SAZ_GranoO_New, DTS.Pipeline: Validation phase is beginning.

Information: 0x40043006 at Extrae SAZ_GranoO_New, DTS.Pipeline: Prepare for Execute phase is beginning.

Information: 0x40043007 at Extrae SAZ_GranoO_New, DTS.Pipeline: Pre-Execute phase is beginning.

Information: 0x4004300C at Extrae SAZ_GranoO_New, DTS.Pipeline: Execute phase is beginning.

Error: 0xC0047062 at Extrae SAZ_GranoO_New, SAZ_GranoONew [421]: System.NullReferenceException: Object reference not set to an instance of an object.

at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.PrimeOutput(Int32 outputs, Int32[] outputIDs, PipelineBuffer[] buffers)

at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostPrimeOutput(IDTSManagedComponentWrapper90 wrapper, Int32 outputs, Int32[] outputIDs, IDTSBuffer90[] buffers, IntPtr ppBufferWirePacket)

Error: 0xC0047038 at Extrae SAZ_GranoO_New, DTS.Pipeline: The PrimeOutput method on component "SAZ_GranoONew" (421) returned error code 0x80004003. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing.

Error: 0xC0047021 at Extrae SAZ_GranoO_New, DTS.Pipeline: Thread "SourceThread0" has exited with error code 0xC0047038.

Information: 0x402090DF at Extrae SAZ_GranoO_New, OLE DB Destination [1022]: The final commit for the data insertion has started.

Information: 0x402090E0 at Extrae SAZ_GranoO_New, OLE DB Destination [1022]: The final commit for the data insertion has ended.

Information: 0x40043008 at Extrae SAZ_GranoO_New, DTS.Pipeline: Post Execute phase is beginning.

Information: 0x40043009 at Extrae SAZ_GranoO_New, DTS.Pipeline: Cleanup phase is beginning.

Information: 0x4004300B at Extrae SAZ_GranoO_New, DTS.Pipeline: "component "OLE DB Destination" (1022)" wrote 19522 rows.

Task failed: Extrae SAZ_GranoO_New

Warning: 0x80019002 at SAZSIE_CargaVentasSeguros: The Execution method succeeded, but the number of errors raised (3) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.

SSIS package "SAZSIE_CargaVentasSeguros (1).dtsx" finished: Failure.

THE DATA HAS BEEN COPIED INTO MY DESTINATION TABLE, BUT THE PACKAGE ENDS IN AN ERROR, WHAT IS THE PROBLEM WITH THIS?

PLASE SOMEONE !!!!

THANKS!!!!!!!

the problem was that those idiots changed the source by adding a new field in their table and my package wasn′t updated with the new definition of it... thanks anyway...|||take it easy|||

ruk_walled wrote:

the problem was that those idiots changed the source by adding a new field in their table and my package wasn′t updated with the new definition of it... thanks anyway...

Hence you should always use a SQL statement rather than referencing a table by name!

-Jamie

|||

it′s exactly what i did... after the error of course ;)

thanks for your advice!!!

|||Interesting. I just ran into this same problem, with the same cause - source table structure changed.

However, the query I was using to retrieve from it was of the form "select * from <blah>".

It took deleting and recreating the step to fix the error. Do SSIS packages cache table structures or something?|||

LpAngelRob wrote:

It took deleting and recreating the step to fix the error. Do SSIS packages cache table structures or something?

Any component in a dataflow that acceses something external to the package has something called the ExternalMetadata collection which is information about what that external thing "looks" like. If that external thing doesn't look like what the SSIS package is expecting - you'll get problems.

-Jamie