October 7, 2016 at 10:59 am
Here's the error I'm getting on one SQL 2012 server, that isn't taking place on another SQL 2012 server:
Error: 2016-10-07 11:21:53.92
Code: 0xC0047062
Source: Load Configuration Flow Task Load Values Script [2]
Description: The component metedata is out of sync with the compiled script. Recompile the script using the Script Component Editor.
End Error
The SSIS package is run by a batch controller product, and it runs fine via the same batch controller product with the appropriate parameters on one server, but for whatever reason, errors out with this problem on a different server. The parameters being used are values being supplied to the package as part of the Script Task that is failing. It started failing this way after I added 3 package variables to the Script Task's list of Read/Write variables that you can examine right after choosing to edit the Script Task. I also modified the Script Task's C# code to just handle the additional incoming parameters from the flat file. I know this could be better accomplished by using Package Configuration, but I'm working on an existing package that it would take a rather long time to go back and re-configure everything to use that instead of this existing methodology. What drives me nuts is that you can go edit this script, and then do a Build on it, and then save the script and then save the package and then copy that file to the folders on each of the servers, and the one server it runs fine, and the other it gives the above error. I'm hoping someone can point me in the right direction on how to fix the problem.
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
October 7, 2016 at 12:08 pm
Well, I've now discovered that the versions of SQL Server are just slightly different. Here are the version details:
Microsoft SQL Server 2012 - 11.0.2100.60 (X64)
Feb 10 2012 19:39:15
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)
Microsoft SQL Server 2012 (SP3) (KB3072779) - 11.0.6020.0 (X64)
Oct 20 2015 15:36:27
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)
The latter version is the one where the failure occurs. Further troubleshooting, by going into VS on the box where the failure occurs, showed a problem with the configuration file reading data flow, so I went into the script task and did a build, and saved it from that machine, and now it gets past the original error, but finds itself in a position where the connection string that uses one of these variables isn't getting any value from that variable. As it's the user id portion of the connection string, that's a problem. Any ideas? I thought that updating a package variable associated with a Connection Manager's expression for connection string would have full effect. Would delayed validation help in any way?
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
October 7, 2016 at 1:08 pm
Finally got past the version difference by editing the package on the server where it was failing, and then after a couple other quick edits, it worked okay. As this is a bit of a one-off, I don't have too much more to worry about, save any other packages that may fail for similar version difference issues, but it would be nice to know WHY there is such a difference in functionality between updates of the same version of SQL Server 2012 Integration Services. This could be potentially painful.
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
October 7, 2016 at 2:08 pm
sgmunson (10/7/2016)
Finally got past the version difference by editing the package on the server where it was failing, and then after a couple other quick edits, it worked okay. As this is a bit of a one-off, I don't have too much more to worry about, save any other packages that may fail for similar version difference issues, but it would be nice to know WHY there is such a difference in functionality between updates of the same version of SQL Server 2012 Integration Services. This could be potentially painful.
Thanks for posting back everything - very helpful when others find the same issues.
I would guess the Why on this is likely due to changes in the metadata, even if minor, that you probably hit.
The beginning of this article explains the error a bit more:
Sue
October 7, 2016 at 7:47 pm
Sue_H (10/7/2016)
sgmunson (10/7/2016)
Finally got past the version difference by editing the package on the server where it was failing, and then after a couple other quick edits, it worked okay. As this is a bit of a one-off, I don't have too much more to worry about, save any other packages that may fail for similar version difference issues, but it would be nice to know WHY there is such a difference in functionality between updates of the same version of SQL Server 2012 Integration Services. This could be potentially painful.Thanks for posting back everything - very helpful when others find the same issues.
I would guess the Why on this is likely due to changes in the metadata, even if minor, that you probably hit.
The beginning of this article explains the error a bit more:
Sue
Thanks for the link. I did see it in my research on this, but because at the time I saw it, it was 1) a repeat of a solution process I had already tried, and 2) I had yet to discover the difference in service pack level. Once I found that difference, I was more than a little concerned that continuing to use the development server for any further SSIS dev would be dangerous. That kind of problem cropping up when there's no genuine need for it to exist is just crazy. It's hard to reconcile that a fix to software now requires that packages developed prior to that fix level now break when they used to work just fine... Oh well... enough of my soap box. Sure was annoying and time-consuming.
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply