March 17, 2014 at 10:28 am
ok, SSIS gurus. This is our first time setting up a SSIS package. I created a simple straight forward package that has one 'Data Flow Task'. Within that Data Flow Task I have 'OLE DB Source' which then outputs data to a text file. I have two Connections one for the test server and one for the Flatfile. Everything works fine in BIDS. It runs, turns green and outputs a file.
Now I have set the deployment to True. Copied the BIN folder to our Test server. Ran the install wizard to install in the file system. I have two issues now.
1. When i log into Integration Services on the Test server I do not see the package under the File System node.
2. I get this Validation error during the install
"ERROR: SSIS Error Code DTS_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Test Server" failed with error code 0xC0202009.
3. I also see this error as well:
"ERROR: SSIS Error Code DTS_E_OLDEBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult 0x80040E4D Description "Login failed for user "
Just in case you need this info my laptop is Windows 7 64 bit and our Test server is also 64 bit. I am using Sql Server 2008 R2.
Any help would be greatly appreciated. Thanks.
March 17, 2014 at 8:52 pm
OK, issue 1 is resolved i placed the file in the wrong location. I thought it was C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Packages when it actually was C:\Program Files\Microsoft SQL Server\100\DTS\Packages.
Any one that can help with number 2 and 3 ??? I still get that error when double clicking on the package and running it.
Thanks.
March 18, 2014 at 10:38 am
I was able to resolve issue.
Thanks.
March 18, 2014 at 2:25 pm
elee1969 (3/18/2014)
I was able to resolve issue.Thanks.
What did you do to resolve it?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 18, 2014 at 2:54 pm
Jeff Moden (3/18/2014)
elee1969 (3/18/2014)
I was able to resolve issue.Thanks.
What did you do to resolve it?
Change the protectlevel to DoNotSave and created the config file to store the password.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply