RS.SetItemDataSources fails in 2008

  • I have a script that deploys reports using rs utility that works fine in 2005. Switched over to 2008 and everything works except RS.SetItemDataSources. I have also used Jasper Smith's RSScripter and it doesn't work either so it is not the script.

    I have found the issue but haven't figured out a 'good' fix. I have thousands of reports to deploy and all fail except for a couple. So I started looking at the differences between the working and non... The ones that work have been created with a datasource with the same name that I am using on the report server. The ones that don't work use a datasource with a different name. In 2005 the name made no difference, using RS.SetItemDataSources would set the datasource to the one I create on the report server. In 2008 this fails with 'Error : rsDataSourceNotFound (The data source 'BLAH' cannot be found.)' even though it is clearly there and works on the reports that were created with a datasource named BLAH.

    The only way I can get this to work so far is:

    a) Use same name datasource on report server as what was used in developing the .RDL file. (can't as every dev seems to use something different)

    b) Edit every .RDL files datasource to be named as the one I want to use in the various deployment environments at deployment time.

    c)...

    Please help me with C as A and B are lacking.

    Thx,

    Gork

  • Hello

    Have you found a fix for the rsDataSourceNotFound issue... I have the same exact problem and so far had no luck.. Thanks.

  • I'm having the exact same problem. Since I'm not the one developing every report, I can't expect the developer to design the .rdl file with the exact datasource name that is being used in production. I need my script to be able to mass deploy reports but having the SetItemDataSource fail every time because of a completely irrelevant name is killing me. Hopefully someone can get this to work and share with us!

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

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