Current setup: We have an SSRS component to generate reports using: Report Server: Microsoft Windows Server 2003 R2, Standard Edition, SP2DB Server: Microsoft SQL Server 2005 Currently, Reporting Services application based on the Web service is using the rsutility (RS.exe), the Reporting Services script environment. Our reporting service script is written in Visual Basic .NET and uses the Mgmt2000 endpoint to access the various operations of Report Server Web Service. The Report Server is configured to Native mode. Current script attached (RunReportFromXML.rss). Going-to-be Setup: We have upgraded our Report Server and DB Server to the following versions of Windows and SQL Server: Report Server: Windows Server 2008 R2 Enterprise, SP1DB Server: Windows Server 2008 R2 Enterprise, SP1; Microsoft SQL Server 2012 Now, after upgrading the Report Server and DB Server the Reporting Services VB script is failing at the rs.exe command. Here is the analysis and the steps that we have done so far to troubleshoot this issue: Ran the SSRS component using the endpoint Mgmt2000 and got the error: Invalid Endpoint, so we changed it to Mgmt2005 per http://msdn.microsoft.com/en-us/library/ms162839.aspx. After changing the endpoint when we execute the package we are getting the following error: error BC30456: 'Render' is not a member of 'Microsoft.SqlServer.ReportingServices2005.ReportingService2005'.Updated the Management Endpoint to Mgmt2010 since this endpoint merges the functionalities of the endpoints Mgmt2005 and Mgmt2006 perhttp://msdn.microsoft.com/en-us/library/ms155398.aspx. After changing the endpoint when we execute the SSRS component we are getting the errors like: error BC30451: Name 'ExecutionSettingEnum' is not declared, rs.SetExecutionOptions(reportPath, ExecutionSettingEnum.Snapshot, definition) error BC30456: 'Render' is not a member of 'Microsoft.SqlServer.ReportingServices2010.ReportingService2010'. results = rs.Render(reportPath, format, _ etc. etc. After going through the ReportingService2010 Class Properties and Methods we realized that some of the methods that we were referring in our Reporting Service Script are obsolete. For e.g. GetReportParameters in ReportingService2005 class is changed to GetItemParameters in ReportingService2010. This way we are able to resolve all the errors except BC30456: 'Render' is not a member of 'Microsoft.SqlServer.ReportingServices2005.ReportingService2005'. It seems that this Render method which is a part of ReportExecutionService is not exposed by ReportService2010 endpoint since it is a method which is exposed by an Execution Endpoint and not by a Management Endpoint.So, in order to access Render method through ReportExecutionService we ran the SSRS component using the endpoint Exec2005 and got the list of errors like: error BC30456: 'SetExecutionOptions' is not a member of 'Microsoft.SqlServer.ReportingServices2005.Execution.ReportExecutionService'.rs.SetExecutionOptions(reportPath, ExecutionSettingEnum.Live, Nothing) error BC30456: 'GetReportParameters' is not a member of 'Microsoft.SqlServer.ReportingServices2005.Execution.ReportExecutionService'.reportParameters = rs.GetReportParameters(reportPath, historyID, forRendering, parameters, Nothing) etc.etc. In this case we are getting errors corresponding to all those methods which are not exposed by this endpoint but by ReportService2010, for e.g., GetReportParameters etc. as can be seen in the attached error log file. Now here are the questions / issues: What is the easiest & Microsoft Recommended way to upgrade SSRS (from 2005) when some the options/components/methods are obsolete in SSRS 2012?How can we use the methods exposed by both ReportService2010 and ReportExecutionService using a single end point using the aforementioned Report Server and DB Server configuration? We tried to use the endpoints Mgmt2005 and Mgmt2010 but failed to access the methods exposed by Exec2005. When we use the endpoint Exec2005 we fail to access the methods exposed by the Management End Points (Mgmt 2005 and Mgmt2010).If the answer to #1 is NO, then, what are our options to execute the existing SSRS Package with the aforementioned Report Server and DB Server configuration?

Hello AbhinavV, First of all, I am sorry to say that Mgmt2000 end point is deprecated in reporting service 2005, though we can use it in 2005. The end point is used for old version of reporting service, RS 2000. If the script was based on other end point at that time, we would be much easier to upgrade the script to latest version. For more information about the end point of rs utility, please refer to the MSDN page, http://msdn.microsoft.com/en-us/library/ms162839(v=sql.90).aspx, for RS 2005. For the current scenario, we suggest that we can use the latest endpoint to rewrite the whole script. As I know, it will be a tough task, but I consider it will save much work in the future upgrade. For the second question, I am afraid that we cannot use both end point in the same time. Based on my knowledge, Mgmt2010 is to manage the report server, and Exec2005 is to run or to navigate the report. They are different on the goal of the execution. It is by design for the authorization. As we know, if the account has only browser permission, it cannot manage the reporting service. If we separate the permission to different service, then we can guarantee that the browser account has no way to access the manage functions. It will provide securer way to the reporting service. In addition, from the operation, the report management and execution is unrelated. Therefore, if we separate the execution and management into two end points, it will not bother the operation. For the mentioned scenario, I consider that we can separate the operations into two script. One is for reporting service management and the other is for execution. We wrote an extra batch file to invoke the rs utility twice to run the two scripts. If you have any questions, we are very pleased to help you. Regards, EdwardEdward Zhu TechNet Community Support