Post reply

execution failed for data set in reporting service

  • May 15, 2006 at 9:31 pm

    #172561

    HI,

    Can anyone help me?

    I create report and I deploy it to report server.

    When I run it, it works fine BUT when I ask other user to run it.

    they get the error message as below

    ·         An error has occurred during report processing. (rsProcessingAborted)

    ·         Query execution failed for data set 'MyDataset'. (rsErrorExecutingCommand)

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

     

    I suspect it has an issue with user access.

    however I don't kno wwhere I should go or do?

    your help is really appreciated.

    Thanks,

    Susan

  • May 15, 2006 at 10:20 pm

    #638054

    I Found out that there is a work around but I try it and still doesn't solve my problem.

    Has anyone used or known this before?

    There is a workaround for this has been discussed in several threads on this

    newsgroup. The fix is available in SP1.

    In the meantime you need to go to the "Data Options" tab of the "Dataset"

    dialog in report designer. On the Data Options tab you will see that all

    settings contain "Auto" (and report server would therefore try to

    auto-detect the collation settings from the database server).

    Replace the Auto-settings with the following settings (e.g. if your SQL 7.0

    database collation is "SQL_Latin1_General_CP1_CI_AS"):

    Collation = Latin1_General

    Case sensitivity = false

    Kanatype sensitivity = false

    Width sensitivity = false

    Accent sensitivity = true

  • May 17, 2006 at 2:31 pm

    #638558

    I'd say its security related. What credentials are you using to connect to your datasource from the report? Integrated or a generic login account?

    We've found its a good idea to use a generic SQL login that has only data reader access to the database. Keep the password secret and allow password saving in your datasource.

    If you use the same login when developing as the users you'll soon find any problems they are likely to have.

    Hope this helps

    Kindest Regards,

    Martin

  • May 17, 2006 at 7:22 pm

    #638607

    Thanks Martin

    I change to use a generic SQL logins and it works well

    thanks again

     

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

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