problem with srever 2005 and Oracle

I am creating report model witch have connection to Oracle database. I was
created the connection and data source view, but then I want to create
Report model with wizard I am geting the error: ORA-02179: valid options:
ISOLATION LEVEL {SERIAZABLE | READ COMMITTED}.
how to change isolation level to valid oracle connection isolation level.It is my understanding that the model part of RS in 2005 is not yet
compatible with Oracle. I am tied to find where I read that on technet
but I can't. Maybe someone else can elaborate.
Thanks!|||Work-around for Report Builder:
1. Create linked server connection to Oracle database using the
OraOLEDB.Oracle provider(more up-to-date than Microsoft's).
2. Create a Data Source using the native SQL provider to the SQL Server
where you created in step 1.
3. Create a data source view; do not select objects.
4. Right-click in the DSV designer pane and create a New Named Query. Build
your query against the linked server (i.e. use 4-part names: select * from
linkedservername..schema.object). Repeat step 4 for each object you wish to
add to your model.
5. Add logical keys where applicable.
6. Build your model.
7. Deploy & build reports using Report Builder :-)
X

Problem with Report Model.

Hi,

I am using report model as my data source and when I preview my report, I got the following error message:

An error has occurred during report processing. (rsProcessingAborted)
Cannot create command for data source 'xxxx'. (rsErrorCreatingCommand)
An attempt has been made to use a data extension 'SQL' that is not registered for this report server. (rsSemanticQueryExtensionNotFound)

Anyone has any idea how to fix it?

Many Thanks,

UT

A couple questions:

What Version & Edition of SQL Server do you have installed?
Do you see this same error when you publish and render the report from Report Manager?
Is the Data Source local to your Report Server?

- Jason Tremper

|||

Hi Jason,

Thx for your reply and I am sorry for not replying earlier.

I am using SQL 2005 with the SP1 + hotfix.

Yes, same error message occur when I view it from Report Manager.

The data source is local to Report Server

Thanks,

UT

|||I have the same problem. Have you found a solution ?|||The problem solved by SP2.

Thanks and Regards,
UT

Problem with Report Model.

Hi,

I am using report model as my data source and when I preview my report, I got the following error message:

An error has occurred during report processing. (rsProcessingAborted)
Cannot create command for data source 'xxxx'. (rsErrorCreatingCommand)
An attempt has been made to use a data extension 'SQL' that is not registered for this report server. (rsSemanticQueryExtensionNotFound)

Anyone has any idea how to fix it?

Many Thanks,

UT

A couple questions:

What Version & Edition of SQL Server do you have installed?
Do you see this same error when you publish and render the report from Report Manager?
Is the Data Source local to your Report Server?

- Jason Tremper

|||

Hi Jason,

Thx for your reply and I am sorry for not replying earlier.

I am using SQL 2005 with the SP1 + hotfix.

Yes, same error message occur when I view it from Report Manager.

The data source is local to Report Server

Thanks,

UT

|||I have the same problem. Have you found a solution ?|||The problem solved by SP2.

Thanks and Regards,
UT

Problem with Report Builder reporting from a remote database

Hi All,
I had the same problem with an earlier build of SQL Server.
The data for my report model is located on a different server than SQL Server 2005. On the SQL Server 2005 server I can use the Report Builder and it works just fine.
When I try to run the Report Builder on my desktop I get the following error:

For more information about this error navigate to the report server on the local server machine, or enable remote errors
-
Cannot create a connection to data source 'dataSource1'.
-
An error has occurred during report processing.

What needs to be in order for users to build reports whose data is located on a different server than SQL Server 2005?

Thanks for your help,
RoyMy guess is you are using Windows Integrated Authentication for connection to both the model and its data source. This won't work if you have two "hops". The typical practice is to store credentials for a user with read-only access to the database on the datasource, and use integrated authentication on the model.

Problem with regenerated report model.

Hi,

I regenerated a report model (just added a new field) and now the existing reports created using Report Builder no longer run. I get the following error:

An error has occurred during report processing.
Semantic query compilation failed: e EmptySemanticQuery The SemanticQuery does not contain any Groupings or MeasureGroups. SemanticQuery must contain at least one of these elements. (SemanticQuery '').

When I try to open the report in Repoprt Builder, it does not see any of the entities in the model. Instead, it displays "Unknown Entity".

How can I get the reports to be usable again?

Thanks,

Rocco M.

Hi Rocco,

I am also facing the same issue. Did you find the resolution ?

Thanks

Ashutosh

|||

It sounds like you used the Regenerate Model button in Report Manager, which will delete elements of the model if the underlying schema element is no longer present. The Generate command in a VS Report Model project does not do this -- it is only additive.

It appears model regeneration was unable to discover any tables/columns in the underlying database. I don't know why this might have been the case (messed up connection string?), but unfortunately the model is gone now, and it will be very tedious to resuscitate your reports. If you have a recent backup of your report server database, you are in much better shape, however.

Server-based model generation is for quick-and-dirty scenarios. If you are serious about developing and deploying reports based on a report model, you should create one in Visual Studio (or create an empty project, download the generated one from the server, and add it to the project). You will have much finer control over the evolution of the model over time, and it will be much easier to maintain backups and/or old versions as needed.

|||

Hi Ashutosh,

I did not find a resolution to this problem. All of the reports created with Report Builder needed to be re-created. This was not a good situation.

All of the changes made to the report model were done using Visual Studio.

To prevent this situation from happening again, I have created a duplicate "development" version of the report model. All proposed changes are first done to this development version and some reports created specifically against this development version are used to verify proper operation. If the verification is successful, the changs are then made to the production version of the report model using the exact same steps performed on the development version.

Regards,

Rocco

Problem with regenerated report model.

Hi,

I regenerated a report model (just added a new field) and now the existing reports created using Report Builder no longer run. I get the following error:

An error has occurred during report processing.
Semantic query compilation failed: e EmptySemanticQuery The SemanticQuery does not contain any Groupings or MeasureGroups. SemanticQuery must contain at least one of these elements. (SemanticQuery '').

When I try to open the report in Repoprt Builder, it does not see any of the entities in the model. Instead, it displays "Unknown Entity".

How can I get the reports to be usable again?

Thanks,

Rocco M.

Hi Rocco,

I am also facing the same issue. Did you find the resolution ?

Thanks

Ashutosh

|||

It sounds like you used the Regenerate Model button in Report Manager, which will delete elements of the model if the underlying schema element is no longer present. The Generate command in a VS Report Model project does not do this -- it is only additive.

It appears model regeneration was unable to discover any tables/columns in the underlying database. I don't know why this might have been the case (messed up connection string?), but unfortunately the model is gone now, and it will be very tedious to resuscitate your reports. If you have a recent backup of your report server database, you are in much better shape, however.

Server-based model generation is for quick-and-dirty scenarios. If you are serious about developing and deploying reports based on a report model, you should create one in Visual Studio (or create an empty project, download the generated one from the server, and add it to the project). You will have much finer control over the evolution of the model over time, and it will be much easier to maintain backups and/or old versions as needed.

|||

Hi Ashutosh,

I did not find a resolution to this problem. All of the reports created with Report Builder needed to be re-created. This was not a good situation.

All of the changes made to the report model were done using Visual Studio.

To prevent this situation from happening again, I have created a duplicate "development" version of the report model. All proposed changes are first done to this development version and some reports created specifically against this development version are used to verify proper operation. If the verification is successful, the changs are then made to the production version of the report model using the exact same steps performed on the development version.

Regards,

Rocco