October 17, 2008 at 2:16 pm
Hi,
I've created two packages that connect to a Sybase database from a SQL 2005 SP2 server on Windows 2003 64-bit server.
When I log into the Windows server and run the packages they run and are able to complete the steps in the package.
The problem: when someone else (who has the same priveleges that I have) logs in and runs the package, it runs but fails on the connection.
I've even imported these packages into SQL Server so that users and role permissions would apply. It still does not make the connection.
This is the following error my colleagues receive when they run the package:
Executed as user: [domain/username]. ... 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 1:10:08 PM Error: 2008-10-16 13:10:13.63 Code: 0xC0202009 Source: Package Connection manager "[Sybase_connection]" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E19. An OLE DB record is available. Source: "ASEOLEDB" Hresult: 0x80040E19 Description: "[IM002] [Native Code: 30136] [ASEOLEDB]Data source not found and no default driver specified". End Error Error: 2008-10-16 13:10:13.70 Code: 0xC020801C Source: Data Flow Task sybase [1] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "[Sybase_connection]" failed with error code 0xC0202009. There may be error messages posted before this with more information ... The package execution fa... The step failed.
I've setup the package security to encrypt all with a password, and this is used by my co-workers, but still does not work.
any ideas?? Help!!
October 20, 2008 at 2:15 pm
Folks,
I figured it out. My original connection manager setup was flawed. Instead of using the sybase server and port number("[servername],[portnumber]"), I used the data source name setup in the Sybase Data Source Administrator. I did this because this is how I had set this same package up in SQL 2000 as a DTS and it worked okay, but SQL 2005 SSIS must be more strict in it's interpretation of the data connections to sybase and dropped any hand off to the Sybase Data Source Adminstrator to resolve the server name and port number under another user's login. Wow, even the Sybase tech support couldn't figure this out. Ouch!:D
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply