SQL Server 2008 to Sybase Linked Server (x64) -- Provider and permissions issues

Posted by Cory Larson on Server Fault See other posts from Server Fault or by Cory Larson
Published on 2010-04-20T13:40:14Z Indexed on 2010/04/20 13:43 UTC
Read the original article Hit count: 684

Good morning,

We're testing a new SQL Server 2008 setup (64-bit) and one of our requirements was to get a linked server up and talking to a Sybase database.

We've successfully done so using Sybase's 64-bit 15.5 drivers, however I can't expand the catalog list from a remote machine (connecting to the '08 box with SSMS) without having my network account being added as an Administrator on the actual box and then using Windows Authentication to connect to the server instance.

This is going to be problematic when we go live. Has anybody experienced this, or have any input on the permissions in SQL Server 2008 with regards to linked servers?

If I remove my network account from the Administrators group, the big error I'm getting is a 'Msg 7302, Level 16, State 1, Line 41' with a description something like "Cannot create an instance of OLE DB provider "ASEOLEDB" for linked server "", and all research points to permissions issues.

Thoughts? This document talks about DCOM configuration and permissions, but we've tried all of it with no luck.

Thanks

© Server Fault or respective owner

Related posts about windows-server-2003

Related posts about sql-server-2008