May 17, 2011 at 6:38 am
I have some SIS packages that I start building on my local machine and then to run them I move them over to another machine.
I've setup the Data Sources the same but whenever I try to open the package on another machine it hangs up on the Validating portion.
Is there a way to turn this off so I can move these packages between computers and use them without rebuilding them every time.
Thanks in Advance
May 17, 2011 at 8:22 am
Wayne,
I'm a little fuzzy on how you are moving them can you clarify? When you say you setup the data sources the same, please clarify.
Also, verification can only be delayed, it cannot be turned off.
CEWII
May 17, 2011 at 9:27 am
The main SIS package that I am having a problem with is one that pulls information from a Progress database and dumps the data into SQL. It uses a Progress Driver to access the database.
Before we upgraded our servers to 2008 it worked fine, now it errors out when trying to run it on a 2008 server.
What I have done is I run the SIS package from a desktop that has 2005 on it. When I opened the file to reconfigure the location of the Data source the first time after moving the Solution to the desktop is when it hung up on the Validating.
I had to recreate the entire package with 14 containers before I could get it to work correctly.
Now I've gotten another notebook and was trying to open the package on there to work on it and am having the same issues.
Hope this helps some.
Thanks
May 17, 2011 at 9:58 am
Ok, I'm actually guessing you didn't wait long enough on validation. I have seen some obscene validation times on a couple packages.
So you had a 2005 package that you got errors on in 2008, what were the errors?
Now you are trying to run that same package on a 2005 machine again? The package wasn't opened in BIDS 2008 was it? If so I think you are screwed.
I would try to open the package and just let it sit for a while, it will likely eventually finish validation.
Also was 2005 32-bit and 2008 64-bit?
CEWII
May 17, 2011 at 10:07 am
I have also seen some very long validation times (up to 30mins) on Progress databases, especially if it has to go across the network.
May 17, 2011 at 11:24 am
Actually just because of this I've got a 2005 version and a 2008 version.
When I started to put it on my Server 2008 box I copied it over to VS 2008 and then upgraded that version to 2008 and left the 2005 in place just in case.
When I had posted it to the server and was trying to run it is when I found out that 2008 does not store the Passwords to pass to the Progress Data source. I've put the User Name and Password in a file on the server and it still will not work.
I've opened up the 2005 version on a new machine and have had it validating for up to 2 days and it still has never validated.
Now when I just tried to pull it up on my new machine this time using the 2005 version and pulling it up in 2005 I get the message about DTS: Password "Key not valid for use in specified state" and tells me to verify the correct key is available.
Of course since I can't do anything with it I can't make any changes.
Thanks
May 17, 2011 at 11:53 am
Both 2005 and 2008 handle passwords the same way if the protection level is set the same, so I don't think that is the basis for the problem. However, you said you put the password in a file for it to use, may I assume you are using package configurations? If so, did you setup the package to use it or are you passing in the name at run-time?
What is protection level of the 2005 version? And if you can get it the 2008 version?
The most common reason to get the key not valid message is when the package is set to the protection level od Encrypt Sensitive With User Key and the user opening the package was NOT the last one to save it with the correct keys. Keep in mind the user is the AD domain or user account. So this begs the question, is the user who wrote this the same user opening it? If so were they ALWAYS logged in with the same username?
CEWII
May 17, 2011 at 12:26 pm
That helped quite a bit. I went into the Package on the original machine that it was built on and turned the Encryption off and at least don't have the error with the DTS password now.
Yes, I'm the one that created the package on the original machine and I'm logging in with the same user name that I had previously.
I'll see how long the validation takes this time .
Thanks
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply