sql server reporting services: Sybase ODBC Problem -- sql server reporting services

Sybase ODBC Problem

Dave S
3/18/2005 8:21:06 AM

sql server reporting services:

In attempting to connect to a Sybase 12.5 DB using ODBC I get the following
error when I go to run a report via the Report Manager:

An error has occurred during report processing. (rsProcessingAborted) Get
Online Help
Cannot create a connection to data source 'DataSource1'.
(rsErrorOpeningConnection) Get Online Help
ERROR [HY000] [MERANT][ODBC Sybase ASE driver]Unable to load communication
module. NetLib Driver has not been correctly installed. ERROR [HY000]
[MERANT][ODBC Sybase ASE driver]Unable to load communication module. NetLib
Driver has not been correctly installed.

Is something missing? Or is some permission of path not set correctly. The
ODBC datasource itself can connect successfully to the database. And the
report runs fine within the preview on visual studio. But when I deploy the
report and attempt to execute it, the above error appears.

We just started assessing reporting services and as most of our databases
are Sybase, its critical that we overcome this issue. Any suggestions would

Re: Sybase ODBC Problem

Bruce L-C [MVP]
3/18/2005 7:26:09 PM

I have been going against Sybase extensively since it was released (really,
before it was released since I started with the beta). ODBC is the best way
to go (versus OleDB). You say it works in preview but not deployed. Is this
the same machine? What should work is to have a machine DSN. Check your data
source in Reporting Services and go to the credentials tab and make sure you
have a valid user. Go to the machine you have deployed the report on and
open up the query tool (I just spaced on the name of Sybase query tool) and
make sure you can query the database. When using this log in using the
username that you are using from Reporting Services to connect to the
database. What I do is have a user that is a readonly user that I use only
for reporting.

Based on your error it sure seems like something is not installed correctly.
That is why I suggest making sure you can connect with the query tool.

--
Bruce Loehle-Conger
MVP SQL Server Reporting Services

[quoted text, click to view]