Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Cannot view/create custom reports with Reporting Wizard RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

     

    After going through the steps for creating a custom report with CRM 4.0 Reporting Wizard.  We receive the following error when trying to view/run the report.

     

     

    An error has occurred during report processing.

    • Query execution failed for data set 'DSMain'.

      • For more information about this error navigate to the report server on the local server machine, or enable remote errors

       

      It states dataset is "DSMain", should this be our CRM instance/organization name?  Do we have to configure some settings on the Reporting Server. 

       

       

      Any help would be appreciated.

       

       

      Thanks,

       

       

      Brian

       

       

    Tuesday, June 3, 2008 8:15 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Open the report in Visual Studio and change the dataset to SQL with the name of the server, etc.  Try running the report in VS and see if it works.  Your consultant will know how to take this action.  Once the report works in VS, upload it to the CRM server.

     

    Monday, October 13, 2008 5:58 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

     

    where id DSMain, see its previledges and data.

     

    Regards,

    Imran

     

    Thursday, June 19, 2008 10:40 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    We are experiencing the same problem.  Have you found a solution yet?  CRM 4.0 SQL 2005 GP 10.0 and Scribe

    Thursday, October 9, 2008 7:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    The name 'dsMain' has no significance - the report wiazard creates a dataset and has to give a name, and it always uses dsMain.

     

    There are certain reports that should be possible with the Report Wizard, but through the error described - one example is if trying to report off opportunities and products. What is the report you are trying to write ?

    Friday, October 10, 2008 8:23 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    I built a simple report to show the last X days of invoices associated with a sales person.  We can run reports but othing created with the wizard.

     

    Friday, October 10, 2008 12:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Do you have the SQL Report Connector installed?  Are you able to run the report from the Report Server?

     

    Monday, October 13, 2008 12:44 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I ran the report from the SQL server and got the same problem.  The Applicaiton Log records

    an error: "Report data set execution failure. Error: The column 'accountid' was specified multiple times for 'invoice0'.".  I am not sure if that is a false lead or not.

     

    Our CRM consultant reinstalled the connector when we started having this problem, thinking it was the issue.  I will verify that the SQL server is the SRS.

    Monday, October 13, 2008 1:07 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Open the report in Visual Studio and change the dataset to SQL with the name of the server, etc.  Try running the report in VS and see if it works.  Your consultant will know how to take this action.  Once the report works in VS, upload it to the CRM server.

     

    Monday, October 13, 2008 5:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi David,

    I'm having the same error "Query execution failed for data set". My report does access Opportunity, account and a few other filtered views. I can run the report from the administrator's login. But I get the error when running it from any other login. I saw quite a few postings on this but doesn't seem to have a resolution. Can you assist? Thanks in adavance.
    Tuesday, March 10, 2009 1:46 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Tony -

    You're seeing a typical example of limited permissions affecting the report execution - is this a custom report (built in VStudios?) -- or was it created from the report wizard?

    If it  is a custom report, check to make sure you're only referencing the filtered views - non-admin users do not neccessarily have rights to query the base or non-filtered views. (depends on several conditions)

    Try granting a non administrative user admin rights long enough to try running the report - if it works, revoke those rights and then test adding/removing rights.

    If temporarily granting admin rights to a user does not allow them to run the report, check your report queries for references to non-filtered views or base tables.

    Scott Sewell CustomerEffective.com
    Tuesday, March 10, 2009 6:13 PM
    Moderator
  • Question
    Sign in to vote
    1
    Sign in to vote
    Scott's recommedation are correct.  One addition is that you want to ensure you have set the report to use Windows Authentication.  You can find this and other report property settings like the datasource by going to your report server and selecting the edit button of the report.  Another test you can try is to actually supply the System Admin login to the report properties, save the change and then see if a user can run the report.  if the user can run the report, then you need to work on the report properties.

    Do you have the SRSS Connector installed on your SQL server?
    Best Regards, Donna
    Wednesday, March 11, 2009 3:46 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks Scott & Donna,

    In my case, it was a user defined function that was causing the problem. It needed the Permission for the CRMReaderRole and ReportGroup. I thought I checked all of the access level but totally forgot about this one function. Your advice encourages me to look through it again and found the culprit. Thanks.
    Thursday, March 12, 2009 11:15 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Tony - Glad to hear your problem is resolved!  permissions can be so tricky to troubleshoot since we all tend to develop and test as 'admins' - even though we all know better! :)
    Scott Sewell | http:\\blog.CustomerEffective.com
    Thursday, March 12, 2009 11:22 PM
    Moderator