Showing posts with label deployed. Show all posts
Showing posts with label deployed. Show all posts

Friday, March 30, 2012

Report doesn't work when deployed

I have a report that works perfectly in the development enviroment but when I
deploy it and run it in the report server I get this message:
"An error has occurred during report processing. (rsProcessingAborted)
Obtener ayuda en línea
Query execution failed for data set 'All_TTs'. (rsErrorExecutingCommand)
Obtener ayuda en línea
Object reference not set to an instance of an object. "
I tried recreating the data set bu it was worthless.
--
Pato Connonensure your datasource is pointing to the correct location, and that the
report uses the correct datasource. also ensure your datasource has the
correct connection information
"Pato Connon" wrote:
> I have a report that works perfectly in the development enviroment but when I
> deploy it and run it in the report server I get this message:
> "An error has occurred during report processing. (rsProcessingAborted)
> Obtener ayuda en línea
> Query execution failed for data set 'All_TTs'. (rsErrorExecutingCommand)
> Obtener ayuda en línea
> Object reference not set to an instance of an object. "
> I tried recreating the data set bu it was worthless.
> --
> Pato Connon|||If you are using an ODBC datasource, you might have to create the
datasource on the SSRS server as well. When you run the report in the
designer, it is looking for the ODBC connection on your computer, but
when it runs on the server, it is looking on the server.
-Josh
Pato Connon wrote:
> I have a report that works perfectly in the development enviroment but wh=en I
> deploy it and run it in the report server I get this message:
> "An error has occurred during report processing. (rsProcessingAborted)
> Obtener ayuda en l=EDnea
> Query execution failed for data set 'All_TTs'. (rsErrorExecutingCommand)
> Obtener ayuda en l=EDnea
> Object reference not set to an instance of an object. "
> I tried recreating the data set bu it was worthless.
> -- > Pato Connon

Report Designer vs. Report Builder

Is it possible to associate a VS Report Designer report with a VS Report
Modeler model? In other words make a report that is deployed from Visual
Studio editable using Report Builder, or even the other way around.
--
Tom GarthTom,
It is been my experience that you can't. I have tried a number of different
things with no luck.
"Tom Garth" wrote:
> Is it possible to associate a VS Report Designer report with a VS Report
> Modeler model? In other words make a report that is deployed from Visual
> Studio editable using Report Builder, or even the other way around.
> --
> Tom Garth|||you can't
you can open an RDL created in report builder into VS
you can can create a new report in VS based on a report builder model
but you can't allow a user to edit a report created into VS with report
builder.
"Tom Garth" <TomGarth@.discussions.microsoft.com> wrote in message
news:2930040A-8541-49F0-B6C4-174C47AF8DED@.microsoft.com...
> Is it possible to associate a VS Report Designer report with a VS Report
> Modeler model? In other words make a report that is deployed from Visual
> Studio editable using Report Builder, or even the other way around.
> --
> Tom Garth|||Thanks to you both. You have confirmed cause my frustation. It is very
unfortunate that this is so, but... oh well.
--
Tom Garth
"Tom Garth" wrote:
> Is it possible to associate a VS Report Designer report with a VS Report
> Modeler model? In other words make a report that is deployed from Visual
> Studio editable using Report Builder, or even the other way around.
> --
> Tom Garthsql

Wednesday, March 21, 2012

Report Builder Processing Error

Hi all,

Am having a problem processing reports using Report Builder. Have created the Data Source, DSV and Report Model and deployed them (following Report Builder walkthrough instructions in BOL). Building the report through the Report Builder app is also no problem. However when I try and process the report I always get the same error:

Report Execution Error
The Report might not be valid or the server could not process the data

Keyword not supported: 'provider'.
-
Cannot create a connection to data source 'dataSource'. (rsErrorOpeningConnection)
-
An error has occurred during report processing. (rsProcessingAborted)


Have tried building reports using several different models off several different DBs with the same results. Has anyone else seen the same?

I know that in the April CTP Report Builder was not fully functional. Just want to know if this is just a CTP glitch or something I am missing. Either way I am very impressed with what RB is going to offer the ad-hoc reporting world. Really happy that MS will be including it with Standard as well as Enterprise.

Cheers,Please ignore - my fault! Error was being thrown because I used '.' as the server name (lazy way of saying localhost) in my data source.

Everything worked as soon as I typed the full name of the server and redeployed all objects.

Apologies for time wasting.

Cheers,sql

Tuesday, March 20, 2012

Report Builder logon failed

I used an sql server logon to create the view and model in designer, I deployed the source and model from desigen, when I go to report builder I get this message:
  • Logon failed.
  • Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E) My server and web service are on the same server and I set up my server security to use mixed mode if that makes a difference.to answer my own question, even though it said it set up the rs service account correctly, it set up a new one with appropriate security and it now works, I just deleted the old id and use the new one.|||

    hi there!

    i encounter the same error... how did u find the id? i am using the domain account.. how can i make the necessary changes?

    if i have to run my report in the client workstation, i got this error msg:

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

    I'm encountering the same error and cannot seem to get the issue resolved. I setup a new report server on my local machine and deployed a model to it and it works fine.

    However, on my 2003 server I get the message

    Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
    -
    Logon failed.

    Can you please explain how exactly to rectify this error?

    Thanks

    |||

    Go to management studio, create a LOGIN give it access to the msdb, reportsever database and reportserver temp database. See

    http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSinstall/htm/gs_installingrs_v1_75k2.asp

    |||Goto Reporting Services Configuration (in Start Menu->Programs->Sql Server->Config Tools. Click on Execution Account Uncheck "Specify an execution account"
  • Report Builder logon failed

    I used an sql server logon to create the view and model in designer, I deployed the source and model from desigen, when I go to report builder I get this message:
  • Logon failed.
  • Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E) My server and web service are on the same server and I set up my server security to use mixed mode if that makes a difference.to answer my own question, even though it said it set up the rs service account correctly, it set up a new one with appropriate security and it now works, I just deleted the old id and use the new one.|||

    hi there!

    i encounter the same error... how did u find the id? i am using the domain account.. how can i make the necessary changes?

    if i have to run my report in the client workstation, i got this error msg:

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

    I'm encountering the same error and cannot seem to get the issue resolved. I setup a new report server on my local machine and deployed a model to it and it works fine.

    However, on my 2003 server I get the message

    Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
    -
    Logon failed.

    Can you please explain how exactly to rectify this error?

    Thanks

    |||

    Go to management studio, create a LOGIN give it access to the msdb, reportsever database and reportserver temp database. See

    http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSinstall/htm/gs_installingrs_v1_75k2.asp

    |||Goto Reporting Services Configuration (in Start Menu->Programs->Sql Server->Config Tools. Click on Execution Account Uncheck "Specify an execution account"
  • Report Builder logon failed

    I used an sql server logon to create the view and model in designer, I deployed the source and model from desigen, when I go to report builder I get this message:
  • Logon failed.
  • Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E) My server and web service are on the same server and I set up my server security to use mixed mode if that makes a difference.to answer my own question, even though it said it set up the rs service account correctly, it set up a new one with appropriate security and it now works, I just deleted the old id and use the new one.|||

    hi there!

    i encounter the same error... how did u find the id? i am using the domain account.. how can i make the necessary changes?

    if i have to run my report in the client workstation, i got this error msg:

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

    I'm encountering the same error and cannot seem to get the issue resolved. I setup a new report server on my local machine and deployed a model to it and it works fine.

    However, on my 2003 server I get the message

    Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
    -
    Logon failed.

    Can you please explain how exactly to rectify this error?

    Thanks

    |||

    Go to management studio, create a LOGIN give it access to the msdb, reportsever database and reportserver temp database. See

    http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSinstall/htm/gs_installingrs_v1_75k2.asp

    |||Goto Reporting Services Configuration (in Start Menu->Programs->Sql Server->Config Tools. Click on Execution Account Uncheck "Specify an execution account"|||Hi CadsKiran

    Thanks for u'r solution.
    it worked for me :) .

    Thanks
    Isuru
  • Friday, March 9, 2012

    Report Builder - unable to open report sample

    I have deployed the AdventureWorks report model to the report server and published the sample reports (RDLs - Customer Purchases, Product Sales by Year, and Sales by Territory). When I attempt to open the RDL in Report Builder, I unable to open the report and the following error is reported "This report cannot be opened in Report Builder." Any ideas?

    Clay BOnly reports that were authored in Report Builder can be opened in Report Builder. All of the sample reports were authored in Report Designer, not Report Builder.

    Report Builder - unable to open report sample

    I have deployed the AdventureWorks report model to the report server and published the sample reports (RDLs - Customer Purchases, Product Sales by Year, and Sales by Territory). When I attempt to open the RDL in Report Builder, I unable to open the report and the following error is reported "This report cannot be opened in Report Builder." Any ideas?

    Clay BOnly reports that were authored in Report Builder can be opened in Report Builder. All of the sample reports were authored in Report Designer, not Report Builder.

    Saturday, February 25, 2012

    Report Authoring Using Report Builder

    We have deployed multiple report builder models and the number 1 user complaint is that every report builder report created can only have 1 table or 1 matrix or 1 chart in per .rdl (or report created). Anyone found any way around this? Is there a fix planned?This was an intentional design constraint for this release. There are no workarounds. We are definitely looking to include this functionality in a future release.