Reporting Services Report Model for Sybase DataSource

Question

Post reply

Reporting Services Report Model for Sybase DataSource

Dan Talbert

SSC Veteran

Points: 290
More actions
November 27, 2006 at 10:58 am

#193283

Reporting Services Report Model Question.

I am trying to create a Report Model for users to create their own Adhoc reports. I can do this just fine if the DataSource of the Report Model is a Microsoft SQL Database.

Unfortunately, I need to create a Report Model Based on a Sybase ASE 12.5 Database. I have been browsing the internet for days now and have found very little on this topic.

The problem is not in the Report Model Creation process because I can create it manually if needed. (THIS TAKE FOREVER, BTW. YOU LITERALLY HAVE TO RECREATE EVERY TABLE AND EVERY RELATIONIONSHIP.)

The problem is that once you have gone through the exceedingly long and painful task, the report model wont upload to the report server from Visual Studio 2005 because the DataSource won’t upload.
When I try to deploy the ODBC DataSource, I get the following
Error
“The required field UserName is missing from the input structure.”

The DataSource tests just fine. I can even use the Report Designer to create reports based on this DataSource. They upload and run just fine.

I can use the web based report manager to manually upload both the DataSource and the model. I can even use the Report Model using Report Builder to build and save the report, but the report won’t run. I get the following error.

Error:
An error has occurred during report processing.
Cannot create command for data source 'dataSource1'.
Value does not fall within the expected range.

I am not sure where to go from here. Sybase has both an ODBC & OLEDB type providers and I have tried them both as the DataSource of the Report Model, only resulting in an array of various errors. (Too many to list here).

Can this even be done?

I need to get back to my manager with an answer.

A: This can’t be done. We need to use another Reporting Product and scrap MS Completely.
B. It can be done. Here is how you do it …_____________...

Can anyone fill in the blank for me???
Any help on this issue will be greatly appreciated.
Gary

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Martin N Ten Centuries Points: 1216 More actions · Answer 1

Hope this helps... I've had problem and it's to do with using Windows credentials...

Excerpt from: http://msdn2.microsoft.com/en-US/library/ms190041.aspx

---------------------------------------------------------------

Windows integrated security

Use the Windows credentials of the current user to access the data source. Choose this option when the credentials that are used to access a data source are the same as those used to log on to the network domain.

This option works best when Kerberos authentication is enabled for your domain, or when the data source is on the same computer as the report server. If Kerberos is not enabled, Windows credentials can be passed to one other computer. If additional computer connections are required, you will get an error instead of the data you expect.

Do not use this option to run unattended reports or reports that are available for subscription. The report server initiates the running of unattended reports. The account that the report server runs under cannot be used to access external data sources.

---------------------------------------------------------------

Kindest Regards,

Martin

Dan Talbert SSC Veteran Points: 290 More actions · Answer 2

Martin,

Thanks for the input but I don't belive this is a Security Problem.

I think that I may have figured this out. I am currently in the process of writing a step by step set of instructions as to how to create a Working Report Model and the associated Data Source to get MS SQL Adhoc reporting to work with a Sybase ASE backend.

I will post the complete step by step when I have finished it. It is not high on my work priority list so I will have to wait until I have time.

In any case, I believe I have fixed the Data Source issue of the problem. As it turns out, there are 3 ways to create the Data Source. 1 ODBC driver and 2 OLEDB providers. Only 1 of the 3 works. The other 2 do not, or at lease I could not get them to work. There are 2 OLEDB provider. 1 is listed as a Native OLEDB provider and the other is a .NET OLEDB provider. I have only been successful in getting the .NET OLEDB provider to work. So that is the first part of it, choosing the best provider. The other part is an entry in the “rsreportserver.config” file.

In the <SemanticQuery> section of the file, you need the following entry.

Once you have this entry and you use the .Net provider, any manually created model should work. My future step by step with include instructions on how to get the Report Model Wizard to do the work for you. This will save you weeks of time.

That all for now

Dan