May 26, 2016 at 3:27 pm
I've been running a simple SSIS package on a 32 bit 2008 R1 server as a daily scheduled job
It uploads an Excel spreadsheet, and pushes the data to a production server running SQL 2005 sp4. The connection to the prod server from uses SQL Authenticaion: "sa".
On the new 2008 64 bit server, I want to get away from "sa", but it fails using "sa" and a lower privilege account.
On the 64 bit 2008 server, when I run it, I get an error "Login failed for user 'sa' or "Login failed for user 'My_SQL_Login'. Inside the SSIS package, I edit the DestinationConnection, re-enter the password, click "save my password", "Test Connection" works. Save the package to file system. Import Package, selecting "Rely on Server Storage & Roles" .....
There's still no problem running it from the old SQL 2008 32 bit server, so the connection to PROD server seems fine.
I used the "Wizard" and created a new package from scratch and that one is working, writing to PROD server, (although I don't have all the data lined up correctly)
Am I missing something about 64 bit that I need to change in the migrated package ?? ??
May 26, 2016 at 5:55 pm
Interesting. Not the problem I would have expected you to have moving from 32-bit to 64-bit. Since this is a job working with Excel files my first thought is the 64-bit runtime having problems with the provider for Excel. Normally you have to specify in the job properties to run in 32-bit mode to work properly.
Joie Andrew
"Since 1982"
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply