December 29, 2010 at 7:46 am
I have an issue that has just recently should up in the last month. I don't know what else to do or check. But here is the issue and what I've done to date.
We have several packages that require us to add a header row in the flat file. We normally create a variable as a string and assign it a value. This could be a static value or a dynamic value.
We then assign the variable to the header property under the expressions property on the data flow.
This has been working fine for several years. untill this month and something has changed. Now the no longer works with the following error.
Executed as user: ebe\hbuckner. ...rsion 9.00.4035.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 9:20:48 AM Error: 2010-12-29 09:20:49.44 Code: 0xC0010018 Source: {9C1741CD-F447-48A4-B68C-4D6DC35A345D} Description: Error loading value "<DTS:PropertyExpression xmlns:DTS="www.microsoft.com/SqlServer/Dts" DTS:Name="[Flat File Destination].[Header]">@[User::var_HeaderString]</DTS:PropertyExpression>" from node "DTS:PropertyExpression". End Error Error: 2010-12-29 09:20:49.44 Code: 0xC0010018 Source: {9C1741CD-F447-48A4-B68C-4D6DC35A345D} Description: Error loading a task. The contact information for the task is "Performs high-performance data extraction, transformation and loading;Microsoft Corporation; Microsoft SQL Server v9; (C) 2004 Microsoft Corporation; All Rights Reserved;http://www.microsoft.com/sql/support/default.asp;1". This happens when loading a task fails. End Error Error: 2010-12-2... Process Exit Code 5. The step failed.
So to get the prodution packages running again, I ended up not assigning the variables to the header property in the dataflow and just put the static information in the header property of the Flat file destination. This worked fine for the static information but not for the dynamic vaules.
We have to rework those to create two dataflows, one to write the header info and then the second to append the details. Which is a work around for the problem but not a solution.
I've been trying to replicate the issue on other machines but have not been able to do it. Our current environment is a active\active cluster running Windows Server Enterprise 2003 SP2 with 15 instances of SQL server 2005 X64 bit balenced across both nodes. The SSIS service is x32 bit and runs on both nodes.
The last hotfix that was applied right before this issues, I applied 9.0.4226 on three SQL instances that was not part of the SSIS environement.
I created a test environement set up with Windows 2003 SP2 and installed a 2005 sp3 64bit engine and 32 bit SSIS sp3 and the package worked as planned. I then took the engine up to 9.0.4226 and it still worked as planned.
I have not been able to replicat the issue on any other machine I tested and am at a loss what to try. My only solution is to rework the package to work around the issue. Lucky there are not many of them.
I don't know what else to try and if someone has a suggestion, I'll be listening.
Thanks
February 9, 2011 at 8:04 am
In our case, we have the error:
Message
Executed as user: ...... ...ion 9.00.4035.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 16:01:26 Error: 2011-02-08 16:01:33.08 Code: 0xC0010018 Source: {1FD8BAE0-9DF2-4A28-B091-798215802BD6} Description: Error loading value "<DTS:PropertyExpression xmlns:DTS="www.microsoft.com/SqlServer/Dts" DTS:Name="[DataReader Source].[SqlCommand]">@[User::strSQL]</DTS:PropertyExpression>" from node "DTS:PropertyExpression". End Error Error: 2011-02-08 16:01:33.08 Code: 0xC0010018 Source: {1FD8BAE0-9DF2-4A28-B091-798215802BD6} Description: Error loading a task. The contact information for the task is "Performs high-performance data extraction, transformation and loading;Microsoft Corporation; Microsoft SQL Server v9; (C) 2004 Microsoft Corporation; All Rights Reserved;http://www.microsoft.com/sql/support/default.asp;1". This happens when loading a task fails. End Error Error: 2011-02-08 16:01:33.0... Process Exit Code 5. The step failed.
and we check the registry entries:
for the DTSPipeline.dll 32 and 64 Bit.
The entry for the 32 Bit dll was absend.
%windir%\syswow64\regsvr32 "C:\Program Files (x86)\90\DTS\Binn\DTSPipeline.dll"
Has fix the problem!
Klaus Müller
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply