Uninstalling Reporting Services 2005 instance

Hi,
I'm trying to uninstall an old instance of SQL 2005 Reporting Services (x86) on a WS2008 vm but for some reason the uninstall crashes.
I am using programs and features to uninstall the SQL 2005 Reporting Services named instance. I get a message saying 'setup is preparing to make the requested configuration changes' and the setup then closes without any warning or error message.
Has anyone else had similar problems and does anyone have any ideas how to remove this instance of RS? If it's any help the corresponding SQL instance has been uninstalled so maybe thats confusing the setup program?
Many Thanks,
Phil

Hi phil,
Both the Installation Wizard and command line setup can be used to remove or modify an existing installation. Refer to How to: Uninstall an Instance of Reporting Services:
http://msdn.microsoft.com/en-us/library/ms143518(v=SQL.90).aspx.
In addition, I think you need to uninstall SQL Server 2005 manually. Follow steps:
http://support.microsoft.com/kb/909967.
BUG: You cannot repair or uninstall SQL Server 2005 Reporting Services after you uninstall and then reinstall Internet Information Services 6.0:
http://support.microsoft.com/kb/910544.
Hope this helps.
Maggie Luo
TechNet Community Support

Similar Messages

Run Reporting services 2005 with databases housed on SQL Server 2012?

Hi, I have a RS 2005 install in which the ReportServer and ReportServerTempDB databases reside on a different SQL Server 2005 server. I am planning to upgrade DB server to 2012 and would like to keep SSRS as 2005.As a second phase I will upgrade SSRS2005
to SSRS 2008. So I would be running something like this:
Server A: SQL 2005 Reporting Services
Server B: SQL 2012 database engine - housing ReportServer and ReportServerTempDB
Is this configuration supported?

Hello,
According to the
BOL, Report Server service checks the database version at startup. If the report server is connected to a database that is an earlier version, the report server will update the database during startup.If you have a newer report server database, you
cannot use it with an earlier version of a report server instances.
In that case, the earlier versions of SQL Server Database Engine that can be used to host the SSRS report server databases. For example, In SQL Server 2005 Reporting Services, we can use either SQL Server 2000 or SQL Server 2005 to host the databases, for
SSRS 2012, we can use SQL Server 2012,2008 R2,2008,2005.
Based on my test, In the Reporting Services 2005 Configure Manager, we can create a new database on a remote SQL Server 2012 database engine and the Initialization is successful.
In this way, the databases are created from the script file which installed with the Reporting Services instance, you can find the Catalog.sql and CatalogTempDB.sql under folder C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer.
However, when upgrade the existing ReportServer database and ReportServerTempDB database on the SQL Server 2012 by restore from a backup, we cannot use this existing database for Reporting Services 2005 and get the following message:
The database version (162) does not match your reporting serivces installation.And the initialization failed.
In your case, you can host the ReportServer database and ReportServerTempDB database of SSRS 2005 on SQL Server 2012 database enginer by create a new database from Reporting Services 2005 Configure Manager. But you cannot use the existing
database which upgrade to SQL Server 2012.
Regards,
Fanny Liu
If you have any feedback on our support, please click here.
Fanny Liu
TechNet Community Support

Urgent: System.OutOfMemoryException in SQL Reporting Services 2005 Web Service

Hi All,
On a production server box with 8GB of RAM, we are running a windows service which retrieves image format bytes of a particular report which results in pages ranging from 10 to 300 using Reporting Services 2005 Web Service.
Problem is when image bytes are being retrieved by using Render method for a report with more than around 30-40 pages,
Report Web Service throws an exception of type System.OutOfMemoryException. This does not happen with reports with smaller pages. Please note that we are retrieving high DPI image and we have no option but to do so.
Since the production server has 8 GB of RAM and we have even enabled the 3GB switch in boot.ini of Windows Server 2003, This problem still exists.
I have already read the contents of the article http://support.microsoft.com/kb/909678 but as i mentioned even the large physical memory does not seem to help and shortening the report is not an option.
Also note that large number of records is also not a problem as our application works fine when we generate excel files instead of images.
Follwing is the detailed exception that we receive.
System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
   at System.String.GetStringForStringBuilder(String value, Int32 startIndex, Int32 length, Int32 capacity)
   at System.Text.StringBuilder.set_Capacity(Int32 value)
   at System.Xml.BufferBuilder.ToString()
   at System.Xml.XmlTextReaderImpl.ParseText()
   at System.Xml.XmlTextReaderImpl.ParseElementContent()
   at System.Xml.XmlTextReaderImpl.Read()
   at System.Xml.XmlTextReader.Read()
   at System.Xml.XmlTextReaderImpl.InitReadElementContentAsBinary()
   at System.Xml.XmlTextReaderImpl.ReadElementContentAsBase64(Byte[] buffer, Int32 index, Int32 count)
   at System.Xml.XmlTextReader.ReadElementContentAsBase64(Byte[] buffer, Int32 index, Int32 count)
   at System.Xml.Serialization.XmlSerializationReader.ReadByteArray(Boolean isBase64)
   at System.Xml.Serialization.XmlSerializationReader.ToByteArrayBase64(Boolean isNull)
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderReportExecutionService.Read34_RenderResponse()
   at Microsoft.Xml.Serialization.GeneratedAssembly.ArrayOfObjectSerializer25.Deserialize(XmlSerializationReader reader)
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at ReportExecution2005.ReportExecutionService.Render(String Format, String DeviceInfo, String& Extension, String& MimeType, String& Encoding, Warning[]& Warnings, String[]& StreamIds)

Hi Hameer,
This error might be caused by the memory limit. There are two settings that will affect the memory configuration.
When you render a report through the Reporting Services Web service, the Reporting Services Web service obtains the "MemoryLimit" setting from the Machine.config file.
A scheduled report is rendered by the Report Server Windows service. The Report Server Windows service obtains the "MemoryLimit" setting from the RSReportServer.config file.
These values represent a percentage of physical memory. You can adjust them to change the memory limit.
If there are any more questions, please let me know.
Thanks.

EPSI Dashboard problem after moving from reporting services 2005 to 2012

I have created a Dashboard with Allscripts EPSI with a Reporting Services Report. After we changed from Micrsosoft Reporting Services 2005 to 2012, the report now gets cut in half. I turned a ticket in to Allscripts and they said that it had
nothing to do with their software, that it had something to do with a setting on our Reporting Services server. Please point me into the right direction.

Hi Jason,
Based on my understanding, after you move the report from Reporting Services 2005 to Reporting Services 2012, the report can’t display well.
In Reporting Services, upgrading a report definition in SQL Server Data Tools is the only way to upgrade the .rdl file. In your scenario, if the .rdl file isn’t upgraded in the new environment, it’s expected that the report won’t display well. So please
open an .rdl file in Report Designer in SQL Server Data Tools (SSDT) within the new environment, then the Report Designer will automatically create a backup file and upgrades the report to the current namespace. After a report is upgraded, you might notice
additional errors, warnings, and messages. This is the result of changes to the internal report object model and processing components, which cause messages to appear when underlying problems in the report are detected.
Reference:
Upgrade Reports
If you have any question, please feel free to ask.
Best regards,
Qiuyun Yu
Qiuyun Yu
TechNet Community Support

Is the Export Quality for PDFs in Reporting Services 2005 only 96DPI?

I have been fighting with Reporting Services all day, and despite setting the PDF output quality to 300DPI, I have noticed that the image quality appears to be only 96DPI. I've noticed this because images with a size set for 300DPI are too large for the page, and images set for 96DPI fit just right.
Could someone please tell me if this is a limitation of Reporting Services 2005, or am I just doing something wrong?
I need to know this because I am up against a deadline with this project. I had ran several tests with Reporting Services but had never had assumed there would be problems with image quality.
Is there any other product that offers similar features to Microsoft Reporting Services that you could recommend?
My luck has not been very good with this project, and I'm assuming the response is going to be 96DPI is all that is supported...

OK, I have managed to get higher quality images from the PDF renderer. Here is what I have found:
1) The PDF renderer in Reporting Services 2005 will size all images that it is given at 96 DPI no matter what DPI the image is when you pass it to the renderer. That means that a 300 DPI image or even a 600 DPI image will be sized in the PDF as if it is only 96 DPI. That means your high DPI image will render much larger than you expect.
So you might expect a 300 DPI image that is 6.5 inches wide to render properly at 1950 pixels. Yet, the PDF renderer will size it as it were 96 DPI which would make the image 20.3 inches long!
2) There is good news though. Despite sizing the images as if they were 96 DPI, the PDF renderer appears to render higher DPI images at a higher quality than 96 DPI. So despite the sizing being wrong, the image actually is rendering at a higher quality.
This means that you should size the image to the proper number of inches based on 96 DPI calculations. Then you can use Bitmap.SetResolution to set your images to at least 300 DPI. That should give you a higher quality image that is the proper number of pixels to fit properly in your report.
I am able to do all of this sizing dynamically because I am using objects as my data sources, but I am sure there are VB functions you could use in the report itself to accomplish the same task.
It is late, and I've been at this project all day long, so forgive me if I have explained anything poorly or gotten any concepts long. Yet, at this late hour, I believe this is what the renderer is doing.
I hope this helps someone else in the future, or at least points them in the right direction.

Can Reporting Services 2005 report on SQL Server 2012 database?

We would like to upgrade our SQL Server from Standard 2005 to Enterprise/Standard 2012. Unfortunately, we also have a lot of reports based on Reporting Services 2005. If possible we would like avoid upgrading them at this time.
Is it possible to run Reporting Services 2005 of SQL Server 2012? If yes then is there pre-requiste like drivers or dll or any other to connect SSRS 2005 to SQL server 2012?
If we run Reporting Services 2005 of SQL Server 2012 then do we will face performance lag issue due to version difference of SSRS 2005 and SQL server 2012?

Moderators,
Can anyone merge this -
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/2c44351c-35b4-4208-a2b7-88fc810d53ff/can-reporting-services-2005-report-on-sql-server-2012-database?forum=sqlreportingservices
sathya - www.allaboutmssql.com ** Mark as answered if my post solved your problem and Vote as helpful if my post was useful **.

How to uninstall Reporting Services on SQL 2008 R2?

Hi folks,
Does anyone know how to uninstall (and intall) Reporting Services without uninstalling SQL server. I have a reporting Services Instance that has gone wrong (Virtual Directories do not exist in IIS) and the RS Configuration tool will not
let me create a new set of directories (Option remains greyed out).
The SQL Server Repair option did not work when I tried that.

Hi AndyW2007,
From SQL Server Reporting Services(SSRS) 2008, the SSRS is Internet Information Server(IIS) independence. This means there is no directory for Reporting Services under IIS.
In this case, please make sure the SSRS service is running, otherwise, we are not able to configure the Web Service URL and the Report Manager URL(means configuring the virtual directories).
Anyway, in order to uninstall SQL Server Reporting Services without uninstalling other SQL Server components, please follow this guide:
In Add/Remove programs
Click the 'Uninstall/Change' button for "SQL Server 2008 R2"
In the coming dialog, click 'Remove'
Click 'OK'
In the 'Select Instance' dialog, select the appropriate instance, and then click 'Next'
In the 'Select Features' dialog, please only select 'Reporting Services'
Then click 'Next' and 'Next' till the uninstalling process starting
If you have any more questions, please feel free to ask.
Thanks,
Jin Chen
Jin Chen - MSFT

Reporting Services 2005; No Administator Access

Hello forum
I have recently started working for another company and I am in the middle of performing Audits (first time ever for this company). I have come across a SQL Server RS 2005 installation that does have some Reports but it does not appear to have any
Administrators; the BUILTIN\Administrators group is present when I look at the Users Table; however we have tried three separate accounts that should have Administrator rights and none of these do not have admin rights within Reporting Services.
Does anyone have a script to hand which will identify individuals who are set up as Administrators?
Is there a way to either add myself as an Administrator; without using the intranet interface; or is there a way to reset the permissions of BUILTIN|Administrators to make this group an Administrator within Reporting Services?
Many thanks
Please click "Mark As Answer" if my post helped. Tony C.

Hi Tony,
Per my understanding that you some permission issue in the report manager, the users in the default "BUILTIN|Administrators" group don't have the related admin rights, right?
By default, Reporting Services has assigned both System Administrator roles (System-level) and the Content Manager role (Item-level) to the BUILTIN\Administrators group and the users that are in the local administrators group is in this group.
Please check beloe details information to make sure you have done the proper setting of the user permission:
Check the local Users and Groups to see if the user is in the Administrators group, the user should in this group:(If you want to add new user as the content manager you can add this user to the Administrator group)
Click the connect under the "Object Explorer" (Microsoft SQL Server Management Studio) and select to connect "Report services", expand the role folder under the Security
folder and click the properties of "Content Manager" to make it have the permission as below:
Details information about the role assignments for your reference:
Grant User Access to a Report Server (Report Manager)
If your problem still exists, please try to provide more details information about the permission the user currently have.
Any other question, please feel free to ask.
Regards
Vicky Liu
Vicky Liu
TechNet Community Support

Reporting Services SQL Instance blank

I have looked at all the links and tried the suggestions and I am still having the problem:
SCCM 2012 R2 SQL 2012 SP1 SSRS installed and configured (separate boxes)
When I try to add the reporting services role, it finds the SCCM database and verifies connectivity to it, the SSRS instance drop down is blank.
Using a domain service accout with local admin rights on both machines and sa rights in SQL.
There is a firewall between the Primary Server and the SQL Server and ports 80, 135, 443, 445, 1433 and the high RPC range.
Does anyone know how it is determining the instance? I have read it is via WMI but I am not sure if it is a query or executing a method. I have verified the svc acct has the correct DCOM privs.

Duplicate post of
http://social.technet.microsoft.com/Forums/en-US/5da8e51c-578e-42a8-9419-4a9c02be65e0/reporting-services-install-on-sql-2012-sp1-instance-blank?forum=configmanagergeneral
http://www.enhansoft.com/

Sccm 2012 reporting services server instance blank

Hi guys,
Can anyone provide me tips to install reporting service point on SCCM 2012 server.
P.S: SRS instance configured in SQL server 2008 R2 SP2 and it can accessible (http://<SQLserver>/Reports/) in SCCM 2012 server
Please help me!
Thanks,

If you don't have DNS entry for your Report Service Point (SQL server), the instance field can be blank too.
Can you expand on this as I have never heard of this issue before.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Reporting Services - Multi instance instalation

Hi
I instaled SQL Server standard edition named instance ("DEV1") on a machine with a previous default instance of SQL Express and RS.
I also instaled a new RS instance using this new SQL Server instance using new endpoints, ex:
http://myserver/reports_DEV1
but I get HTTP 404 Not Found.
The previous default instance on http://myserver/reports is still working fine. it opens
http://localhost/Reports/Pages/Folder.aspx
and I noticed that folder.aspx exists only once in the whole file system. Should I have the rs files duplicated on each instance directory?
What can be wrong with my instalation?
Thanks,
DD

Hi DevDiver,
According to your description, the Report Manager URL for your new Report Server instance can be accessed and return 404 error. However the Report Manager URL for the previous instance works fine. Right?
Based on your information, it indicates the issue in the URL configuration. So please go to the Reporting Services Configuration Manager, check the Web Services URL and Report Manager URL. By default, set IP address All assigned, use port 80. However, the
80 port can be shared with other applications, so in this scenario, it might be occupied by another application. From a command prompt, type the following command to return a list of TCP ports that are being used:
netstat –a –n -p tcp
Then used an available port (like 8080 port) for URL of the new Report Server instance. Since the previous instance works fine, there might be some other issue with configuration. For yourself testing, you can trace the hop of http to see some detail
information about the issue. Please refer to the article below:
http://blogs.msdn.com/b/wndp/archive/2007/01/18/event-tracing-in-http-sys-part-1-capturing-a-trace.aspx
Reference:
Configure a URL (SSRS Configuration Manager)
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

Reporting Service 2005 to 2014 migration.

We are in the middle of migrating our SSRS 2005 server to SSRS 2014. So far all the reports are working except our barcode reports.
When we try and upload the barcode reports we get the following message:
"The definition of this report is not valid or supported by this version of Reporting Services. The report definition may have been created with a later version of Reporting Services, or contain content that is not well-formed or not valid based
on Reporting Services schemas. Details: Deserialization failed: The element 'Style' in namespace 'http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition' has invalid child element 'Border' in namespace 'http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition'.
List of possible elements expected: 'BorderColor, BorderStyle, BorderWidth, BackgroundColor, BackgroundGradientType, BackgroundGradientEndColor, BackgroundImage, FontStyle, FontFamily, FontSize, FontWeight, Format, TextDecoration, TextAlign, VerticalAlign,
Color, PaddingLeft, PaddingRight, PaddingTop, PaddingBottom, LineHeight, Direction, WritingMode, Language, UnicodeBiDi, Calendar, NumeralLanguage, NumeralVariant' in namespace 'http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition' as well
as any element in namespace '##other'. Line 664, position 26. (rsInvalidReportDefinition)."
If I change
http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition
With
http://schemas.microsoft.com/sqlserver/reporting/2010/01/reportdefinition
We get the following message:
"The definition of this report is not valid or supported by this version of Reporting Services. The report definition may have been created with a later version of Reporting Services, or contain content that is not formed or not valid based on Reporting
Services schemas. Details: The report definition has an invalid target namespace " which cannot be upgraded. (rsInvalidReportDefinition)"
Here is an example of one of our report files: (too many characters to upload here so I've linked it to my DropBox)
https://www.dropbox.com/s/z5eb9m9cpw6ivrj/Item%20Barcodes%20%28Subassembly%29%20-%20Neodynamic.rdl?dl=0
What needs to be changed for these reports to run on 2014?

Hi Kelvin.uk,
Based on my understanding, you are migrating the content of Report Server 2005 to Report Server 2014, but the barcode reports can’t be uploaded to report server 2014 and error is thrown out.
In Reporting Services, upgrading a report definition in SQL Server Data Tools is the only way to upgrade the .rdl file. In your scenario, since you are migrating the reports to a new environment with a higher Reporting Services version installed, and some
.NET components are referenced when creating the barcode reports, you should upgrade reports definition, then deploy them to report server.
Reference:
Upgrade Reports
If you have any question, please feel free to ask.
Best regards,
Qiuyun Yu
Qiuyun Yu
TechNet Community Support

Cannot consume SQL Reporting Services 2005 webservice

Hello all,
I have seen some other postings on this subject, but no
answers anywhere.
I am trying to run SQL Reporting Services from a CF
application. The wsdl file is at
http://172.XX.XX.XX/reportserver/reportservice.asmx
When I point my browser to that page, I see the XML, so I
know the URL is correct.
When I try to consume the webservice, by either CFINVOKE or
CFSCRIPT , I get the following error:
"Could not generate stub objects for web service invocation"
We are running CF MX on Windows 2003 server.
Any ideas, references, or resources would be greatly
appreciated!
Thanks,
Kathryn

Ken,
Thanks. I do exactly that, ctrl-c to copy, ctrl-v to paste. I
can Preview the message and see the attached code, but when I click
'Reply to Topic' to post the message, I get the "page not found"
error....sigh...Thanks for trying to help....
Kathryn

Coldfusion and SQL reporting service 2005?

Ive been searching google for hours with no clear answer. How
can you use coldfusion to pull in an sql report from reporting
service? Via a web service or wsdl i assume, but how?

Anwar,
It's important to get the terms right here.
SQL Reporting Services is not the same as SQL Server Reporting Services (SSRS).
SQL Reporting Services refers to an Azure service that lets users develop reports in the cloud. However, it is being retired in Oct. 2014, so you'll want to stay away from that.
SQL Server Reporting Services (SSRS) is the reporting module that is part of SQL Server. This is a sophisticated tool that lets developers create and publish reports that users can access through various methods. It has schedule and refresh capabilities,
and can leverage SQL Server Analysis Services (SSAS) and SQL Server Integration Services (SSIS). You'd most likely use SSRS if you're creating sophisticated reports and queries that you don't want your users creating.
SQL Report Builder is a report creation tool designed for users who want to stay in Microsoft Office. It can be used by developers or end users.
http://technet.microsoft.com/en-us/library/dd220460.aspx
Both environments let you create reports that can be shared (published) on a report server or through SharePoint.
So it's really a matter of what you're most comfortable using.
Hope that helps.

SQLServer Reporting Services 2005 Prompts for Credentials for a trusted domain user

Currently the report is running in the domain AAA. Users in the domain AAA are using the report.
Another new domain BBB and an user XXX is now created and BBB\XXX has been given Browser access. Domain AAA and BBB are trusted domains.
After this when the user BBB\XXX logs in and access the report, before loading the report, credentials dialog is prompted, once credentials of BBB\XXX is entered, the report is loaded.
Why the report prompts for this additional credential dialog for the trusted domain user?

Hello,
Did you have get two textboxes in the report parameter panel (in the left side of the "View Report" button)? The issue is occurred when the credential of the datasource is configured with “Prompt for credentials”. Please check if you configured the credential
with "Stored Credential" of the datasource.
Please refer to the following thread to configure the credential.
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/1564cd7a-6b7a-40f1-9f98-5c766ebfc63e/datasource-userid-and-password-being-asked-eachtime-when-report-is-generated?forum=sqlreportingservices
Regards,
Alisa Tang
Alisa Tang
TechNet Community Support

Uninstalling Reporting Services 2005 instance

Similar Messages

Maybe you are looking for