empty cellset issue with mdx in reporting services 2005

Hi all,
I am using reporting services 2005 based on analysis services 2005 cubes
datasource. I use oledb provider and connect to analysis services 9.0. I am
writing an expression in dataset which will evaluate to mdx query during
runtime. Now the issue is if the generated dynamic query cannot product even
a single row because of slicer, then I get an ugly error message.
If in a sql statement, the where clause we include make the query return
zero rows, then you wont see any data for your report, but you dont see an
error. But here in RS with mdx, you are getting error. How to avoid this? Is
there any work around available to solve this issue while creating datasets.
Thanks.Hello,
Thank you for your post in MSDN newsgroup!
To understand the issue better, I'd like to know the following information:
1. What is the exact error message you encountered? Is is saying there are
multiple measures in the WHERE clause even though there is only one
measure? If so, this shall be known issue in AS 2005.
2. Does the issue occur if you run the MDX directly on SSMS? If you use
"Microsoft SQL Server Analysis Services" instead of OlEDB provider for
Analysis Service, does the issue still occur?
3. If the error message is different from that mentioned above, will you
provide us a simple sample project by using Adventure works sample
database, so that we may be able to reproduce the issue on our side? YOu
could send it to me at petery@.microsoft.com.
If you have other related information, please also let's know.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
=====================================================
Microsoft Online Community Support
==================================================Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi,
Just want to check in if you have further questions on the issue. Please
feel free to post back if need any help.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================