sql server reporting services won't start

• Awards Season
• Big Stories
• Pop Culture
• Video Games
• Celebrities

How to Choose the Right Proxy Server for Your Needs

When it comes to online security, a proxy server can be a great way to protect your data and privacy. A proxy server acts as an intermediary between your computer and the internet, allowing you to access websites and services without revealing your identity or location. But with so many different types of proxy servers available, it can be difficult to know which one is right for you. Here are some tips on how to choose the right proxy server for your needs.

Understand Your Needs

The first step in choosing the right proxy server is understanding your needs. What type of activities do you plan on using the proxy server for? Are you looking for a secure connection for online banking or shopping? Or do you need a fast connection for streaming video or gaming? Knowing what type of activities you’ll be using the proxy server for will help narrow down your choices.

Consider Security Features

When selecting a proxy server, it’s important to consider the security features it offers. Look for servers that offer encryption, which will help protect your data from being intercepted by hackers. You should also look for servers that offer additional features such as malware protection and anonymous browsing. These features can help keep your data safe from malicious actors.

Evaluate Speed and Reliability

In addition to security features, it’s important to consider the speed and reliability of the proxy server you’re considering. If you’re using the server for streaming video or gaming, then speed is essential. Make sure that the server has enough bandwidth and is reliable enough to handle large amounts of traffic without slowing down or crashing.

Choosing the right proxy server can be a daunting task, but with these tips in mind, you should be able to find one that meets your needs and provides a secure connection. Be sure to research different servers before making a decision and make sure that they offer all of the features and security measures that are important to you.

This text was generated using a large language model, and select text has been reviewed and moderated for purposes such as readability.

MORE FROM ASK.COM

SQLGeeksPro

SQL Server DBA – Tips to Make it easier.

SQL Server Reporting Services Not Starting

This article is about troubleshooting SQL Server Reporting services not starting issue. It was a nice weekend until I got a call saying SSRS is not working. First thing I asked the on shift DBA if the services online and he says “No”. Of-course the DBA tried to bring it up and it failed saying “ The service did not respond   to the start or control request in a  timely fashion ‘.

Further he informed that Windows Team performed maintenance activity and as part of that they rebooted the server. After reboot all services came online except SSRS service.

Not to mention, you must have already guessed the situation. It required deeper troubleshooting and I am going to explain the steps in the following section.

The SQL Server version: SQL 2012 (SP4-GDR), Standard Edition.

Troubleshooting SQL Server Reporting Services Not Starting

First thing I tried to start the service from Services.msc to check if I get a different error. And It threw the following generic error:

The above error was of not much help but it will log the error at the top (mostly) in application event log. This is what I could find in the event log:

Log Name: Application Source: Report Server Date: 3/27/2020 6:40:30 AM Event ID: 133 Task Category: (4) Level: Error Keywords: Classic User: N/A Computer: <<ServerName>> Description: The description for Event ID 133 from source Report Server cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer\RSReportServer.config

The error image shows as follows:

The very first thing comes to mind after seeing the error is the SSRS service got corrupted and needs to be repaired/reinstalled. But that should always be the last resort. Continue to read to find the solution without reinstall. Next Page>>

SAP Business One Helpdesk

How can we help you today, windows could not start the sql server reporting services service on local computer print.

Modified on: Mon, 2 Aug, 2021 at 6:03 PM

SQL Server reporting service failed to start from Task Manager with below error message:

Below error message shown when starting from Reporting Service Configuration Manager.

Solution: 

Replace the attached web.config in below.

     C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\ReportServer

Start the SSRS Service from the Reporting Service Configuration Manager or Task Manager.

Did you find it helpful? Yes No

Related Articles

This browser is no longer supported.

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

Troubleshoot a Reporting Services installation

• 12 contributors

If you cannot install Reporting Services because of errors that occur during setup, use the instructions in this article to address the conditions that are most likely to cause installation errors.

For information about other errors and issues related to Reporting Services, see Troubleshoot SSRS issues and errors.

Review the Online release notes in case the issue you encounter is described in the release notes.

Check setup logs

Setup errors are recorded in log files in the C:\Program Files\Microsoft SQL Server\ nnn \Setup Bootstrap\Log folder. A subfolder is created each time you run Setup. The subfolder name is the time and date you ran Setup. For instructions on how to view the Setup log files, see View and Read SQL Server Setup Log Files .

The log files include a collection of files.

Open the *_summary.txt file to view product, component, and instance information.

Open the *_errorlog.txt file to view error information generated during Setup.

Open the *_RS_*_ComponentUpdateSetup.log to view Reporting Services setup information.

Check prerequisites

Setup checks prerequisites automatically. However, if you are troubleshooting setup problems, it is helpful to know which requirements Setup is checking for.

Account requirements for running Setup include membership in the local Administrators group. Setup must have permission to add files, registry settings, create local security groups, and set permissions. If you are installing a default configuration, Setup must have permission to create a report server database on the SQL Server instance on which you are installing.

Operating System must support HTTP.SYS 1.1.

HTTP service must be enabled and running.

Distributed Transaction Coordinator (DTC) must be running if you are also installing SQL Server Agent service.

Authz.dll must be present in the System32 folder.

Setup no longer checks for Internet Information Services (IIS) or ASP.NET. Reporting Services requires MDAC 2.0 and the Microsoft .NET Framework version 2.0; Setup will install these, if they are not already installed.

Troubleshoot problems with SharePoint mode installations

Report Server Configuration Manager Does not start

You do not see the SQL Server Reporting Services service in SharePoint Central Administration after installing SQL Server 2016 SSRS in SharePoint mode

Reporting services powershell cmdlets are not available and commands are not recognized, you see an error message indicating the url is not configured, setup fails on a computer with sharepoint installed but it is not configured, sharepoint central administration page is blank, you see an error message when you try to create a new report builder report, you see an error message that rs_shp is not supported with prepareimage, report server configuration manager does not start.

Description: This issue is by design in SQL Server 2012 and later. Reporting Services is architected for the SharePoint service architecture. The Configuration Manager is no longer needed to configure and administer Reporting Services in SharePoint mode.

Workaround: Use SharePoint Central Administration to configure a report server in SharePoint mode. For more information, see Manage a Reporting Services SharePoint Service Application

Description: If after successfully installing SQL Server 2016 Reporting Services in SharePoint mode and the SQL Server 2016 Reporting Services Add-in for SharePoint 2013/2016, you do not see "SQL Server Reporting Services" in the following two menus, then the Reporting Services service has not been registered:

SharePoint 2013/2016 Central Administration -> "Application Management" -> "Manage Services on Server" page

SharePoint 2013/2016 Central Administration -> "Application Management" -> "Manage Service Applications" -> "New" menu

Workaround: To register and start the Reporting Services SharePoint Services, complete the following steps:

On the computer that runs SharePoint 2013/2016 Central Administration

Open the SharePoint 2013/2016 Management Shell with administrator privileges. Right-click the icon and click Run As Administrator . Run the following three cmdlets from the shell:

• Install-SPRSService
• Install-SPRSServiceProxy
• Get-SPServiceInstance -all |where {$_.TypeName -like "SQL Server Reporting*"} | Start-SPServiceInstance

Verify the Reporting Services Service shows status as " Started " on the page: SharePoint 2013/2016 Central Administration -> " Application Management " -> " Manage Services on Server "

Description: When you try to run a Reporting Services PowerShell cmdlet, you see an error message similar to this one:

• The term 'Install-SPRSServiceInstall-SPRSService' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:39+ Install-SPRSServiceInstall-SPRSService <<<< + CategoryInfo : ObjectNotFound: (Install-SPRSServiceInstall-SPRSService:String) [], CommandNotFoundExcep

Workaround: Complete one of the following actions:

Run the Reporting Services add-in for SharePoint products. rssharepoint.msi .

Install Reporting Services SharePoint mode from the SQL Server installation media.

If the SharePoint 2013/2016 Management Shell is open when you complete one of the workarounds, close and reopen the management shell.

For more information, see the following articles:

Where to find the Reporting Services add-in for SharePoint Products

Install the first Report Server in SharePoint mode

Description: You see an error message similar to this one:

This SQL Server Reporting Services (SSRS) functionality is not supported. Use Central Administration to verify and fix one or more of the following issues:

A report server URL is not configured. Use the SSRS Integration page to set it.

The SSRS service application proxy is not configured. Use the SSRS service application pages to configure the proxy.

The SSRS service application is not mapped to this web application. Use the SSRS service application pages to associate the SSRS service application proxy to the Application Proxy Group for this web application.

Workaround: The error message contains three suggested steps to correct this issue. The first suggestion in the message 'A report server URL is not configured.' is relevant when integrating with report server version previous to SQL Server 2012 (11.x). SharePoint Configuration for the previous report server versions is completed on the General Application Settings page, using the SQL Server Reporting Services (2008 and 2008 R2) ..

More Information: You will see this error message when attempting to use any of the Reporting Services functionality that requires a connection to the Reporting Services service. This includes:

Opening SQL Server Report Builder from a SharePoint document library.

Manage Subscriptions.

Manage a service application.

Description: If you select to install Reporting Services SharePoint Mode on a computer that has SharePoint installed but SharePoint is not configured, you will see a message similar to the following and setup will stop:

SQL Server Setup has stopped working

Workaround: Configure SharePoint and then run SQL Server Installation.

More Information: When installing Reporting Services into and existing SharePoint installation, setup attempts to install and start the Reporting Services SharePoint service. If SharePoint is not configured, the service installation fails, causing setup to fail.

Description: You were able to successfully install SharePoint 2013/2016, with no installation errors. However when you browse to Central Administration, you only see a blank page:

Workaround: This issue is not specific to Reporting Services but is related to the configuration of permissions in your overall SharePoint installation. Here are some suggestions:

Review the SharePoint article on development environments. Set up a general development environment for SharePoint

Review the forum post: Central Administration returns blank page after installation on Windows 7

The Service account you are using for SharePoint services such as the SharePoint 2013/2016 Central Administration Service, should have administrative privileges in the local operating system.

Description: You see an error message similar to the following when you attempt to create a Report Builder report inside a document library:

This functionality is not supported because a SQL Server Reporting Services service application does not exist or a report server URL has not been configured in Central Administration.

Workaround: Verify you have an Reporting Services service application and it is correctly configured. For more information, see Install the first Report Server in SharePoint mode .

Description: When you try to run PREPAREIMAGE for Reporting Services you see an error message similar to this one:

"The specified feature 'RS_SHP' is not supported when running the PREPAREIMAGE action, since it does not support SysPrep. Remove the features that are not compatible with SysPrep and run setup again."

Workaround: There is no work-around. Reporting Services does not support SYSPREP (PREPAREIMAGE). Reporting Services Native mode does support SYSPREP.

Troubleshoot problems with the native mode installations

Performance counters are not visible after upgrading to windows vista or windows server 2008.

If you upgrade the operating system to Windows Vista or Windows Server 2008 on a computer that runs Reporting Services, Reporting Services performance counters will not be set after the upgrade.

To reinstate Reporting Services performance counters

Delete the following registry keys:

HKLM\SYSTEM\CurrentControlSet\Services\MSRS 2016 Web Service

HKLM\SYSTEM\CurrentControlSet\Services\MSRS 2016 Windows Service

Open a command window and type the following command at the prompt:

run < .NET 4.0 Framework directory >\InstallUtil.exe < Report Server Bin directory >\ReportingServicesLibrary.dll

Replace < .NET 4.0 Framework directory > with the physical path of the .NET Framework 4.0 files and replace < Report Server Bin directory > with the physical path of the report server bin files.

Restart the Reporting Services service.

To verify that the steps worked, open a Web browser and navigate to the web portal URL or the Report Server URL. Then open Performance Monitor to verify that the counters are working.

To add the performance registry keys again by using Registry Editor

Open the Registry Editor:

Click Start , and click Run .

In the Run dialog box, in the Open box, type regedit .

In Registry Editor, select the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSRS 2016 Web Service\Performance

Right-click the Performance node, point to New , and click Multi-String Value .

Type Counter Names and then press ENTER.

Repeat to add the Counter Types registry key in this node.

Navigate to the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSRS 2016 Web Service\Performance

After you repair the 64-bit instance or add the registry keys again manually, you can use Performance Monitor to configure the Reporting Services performance objects that you want to monitor.

ReportServerExternalURL and PassThroughCookies configuration properties are not configured after an upgrade from SQL Server 2005

When you upgrade from SQL Server 2005 (9.x) to SQL Server 2016 Reporting Services or later (SSRS), the ReportServerExternalURL and PassThroughCookies configuration properties are not configured by the upgrade process. ReportServerExternalURL is an optional property, and it should be set only if you are using SharePoint 2.0 Web Parts and you want users to be able to retrieve a report and open it in a new browser window. For more information about ReportServerExternalURL , see URLs in Configuration Files (Report Server Configuration Manager) . PassThroughCookies is required only when using Custom authentication method. For more information about PassThroughCookies , see Configure the Web Portal to Pass Custom Authentication Cookies .

When you use Custom authentication, it is recommended that you migrate your installation rather than performing an upgrade. For more information about migrating Reporting Services, see Migrate a Reporting Services Installation (Native Mode) .

By default, these properties do not exist in the SQL Server 2016 Reporting Services or later (SSRS) configuration. If you configured these properties in SQL Server 2005 (9.x) and you continue to require the functionality that they provide, you must manually add them to the RSReportServer.config file following the upgrade process. For more information, see Modify a Reporting Services Configuration File (RSreportserver.config) .

401-Unauthorized error when using Windows authentication after an upgrade from SQL Server 2005 to SQL Server 2016

If you upgrade from SQL Server 2005 (9.x) Reporting Services to SQL Server 2016 Reporting Services or later (SSRS), and you use NTLM authentication with a built-in account for the Report Server service account, you might encounter a 401-Unauthorized error when you access the report server or the web portal after the upgrade.

You see this message because of a change in the default SQL Server 2016 Reporting Services or later (SSRS) configuration for Windows authentication. Negotiate is configured when the Report Server service account is either Network Service or Local System. NTLM is configured when the Report Server service account is not one of those built-in accounts. To fix this issue after you upgrade, you can edit the RSReportServer.config file and configure the AuthenticationType to be RSWindowsNTLM . For more information, see Configure Windows Authentication on the Report Server .

Uninstalling 32-bit instance of SQL Server 2016 Reporting Services in side-by-side deployment with a 64-bit instance breaks the 64-bit instance

When you install a 32-bit instance and a 64-bit instance of SQL Server 2016 Reporting Services or later (SSRS) side by side on a computer, and you uninstall the 32-bit instance, four Reporting Services registry keys are removed. Removing the keys breaks the 64-bit instance of Reporting Services. The Reporting Services registry keys that are removed when you uninstall the 32-bit instance are:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSRS 2016 Web Service\Performance:Counter Names HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSRS 2016 Windows Service\Performance:Counter Names HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSRS 2016 Web Service\Performance:Counter Types HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSRS 2016 Windows Service\Performance:Counter Types

To fix this issue, you can repair the 64-bit instance. Although it is recommended to use repair, you can add the registry keys again manually by using Registry Editor.

Incorrectly editing the registry can severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.

Additional resources

The following are additional resources you can review to assist you with troubleshooting issues:

TechNet Wiki: Troubleshoot SQL Server Reporting Services (SSRS) in SharePoint 2010 Integrated Mode

Microsoft Q & A: SQL Server Reporting Services

Got feedback or more questions? Share ideas for SQL .

Was this page helpful?

Submit and view feedback for

Nov 2023 Discount: Comprehensive Database Performance Health Check | Testimonials

SQL SERVER – Reporting Services Not Starting After Maintenance Window

I stopped SQL related services without any issue during the maintenance window (let’s call it as a fake maintenance as it as my lab server). Now, while restarting the same all the SQL related servers got started except SSRS service. After restart server, it started.

I checked on the internet to find a way to find the cause. I started checking the SSRS error log file  Reporting Services Log Files and Sources

Here is the information I could see.

• servicecontroller!WindowsService_0!f80!10/22/2018-06:14:04:: e ERROR: Error initializing configuration from the database: Microsoft.ReportingServices.Library.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. —> System.Data.SqlClient.SqlException: Cannot open database “ReportServer” requested by the login. The login failed.Login failed for user ‘sa’.
• resourceutilities!WindowsService_0!f80!10/22/2018-06:14:05:: i INFO: Reporting Services starting SKU: Enterprise
• library!WindowsService_0!fd0!10/22/2018-06:14:05:: e ERROR: Throwing Microsoft.ReportingServices.Library.ReportServerDatabaseUnavailableException: , Microsoft.ReportingServices.Library.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. —> System.Data.SqlClient.SqlException: Cannot open database “ReportServer” requested by the login. The login failed.Login failed for user ‘sa’.
• library!WindowsService_0!fd0!10/22/2018-06:14:05:: e ERROR: ServiceStartThread: Exception caught while starting service. Error: Microsoft.ReportingServices.Library.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. —> System.Data.SqlClient.SqlException: Cannot open database “ReportServer” requested by the login. The login failed. Login failed for user ‘sa’.
• library!WindowsService_0!fd0!10/22/2018-06:14:05:: e ERROR: ServiceStartThread: Attempting to start service again…
• library!WindowsService_1!ff4!10/22/2018-06:14:55:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: , An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database.;
• library!WindowsService_1!fa0!10/22/2018-06:14:55:: w WARN: Transaction rollback was not executed connection is invalid
• library!WindowsService_1!17ac!10/22/2018-06:15:52:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException:, An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database.;
• schedule!WindowsService_1!17ac!10/22/2018-06:15:52:: Unhandled exception caught in Scheduling maintenance thread: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. —> System.Data.SqlClient.SqlException: Database ‘msdb’ is being recovered. Waiting until recovery is finished.

Note that there were no numbers in the log. I have added them to provide more explanation.

WORKAROUND/SOLUTION

If we look at each numbered item, it has some messages. Let me put them below with the interesting piece.

• e ERROR: Error initializing configuration from the database: Microsoft.ReportingServices.Library.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. —> System.Data.SqlClient.SqlException: Cannot open database “ReportServer” requested by the login. The login failed. Login failed for user ‘sa’.
• i INFO: Reporting Services starting SKU: Enterprise
• e ERROR: Throwing Microsoft.ReportingServices.Library.ReportServerDatabaseUnavailableException: , Microsoft.ReportingServices.Library.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. —> System.Data.SqlClient.SqlException: Cannot open database “ReportServer” requested by the login. The login failed. Login failed for user ‘sa’.
• e ERROR: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. —> System.Data.SqlClient.SqlException: Cannot open database “ReportServer” requested by the login. The login failed. Login failed for user ‘sa’.
• e ERROR:Attempting to start service again…
• e ERROR: An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database.;
• w WARN: Transaction rollback was not executed connection is invalid
• e ERROR: An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. —> System.Data.SqlClient.SqlException: Database ‘msdb’ is being recovered. Waiting until recovery is finished.

There are three kinds of tags we can see above, i-INFO, e-ERROR, and w-WARN. If you read them again, it would start making sense. As we can see that there may be a connection failure, timeout or low disk condition within the report server database.  Also, the system database ‘msdb’ was being recovered and its recovery was not finished. Due to this SSRS service did not start immediately.

When I checked SQL ERRORLOG, I found that MSDB database recovery has taken time to come online and hence SSRS was not able to connect to it. Now, this explained everything and it was a nice experience to do “detective” work to find the root cause.

Reference:  Pinal Dave ( https://blog.sqlauthority.com )

Related Posts

Sql server – 2016 fix: install – rule “oracle jre 7 update 51 (64-bit) or higher is required” failed.

SQL SERVER – Installation Error: System.ArgumentNullException – Value Cannot be Null

SQL SERVER – Identify and Filter In-Memory Optimized Tables – SQL in Sixty Seconds #079

Leave a reply cancel reply.

Pinal Dave is an SQL Server Performance Tuning Expert and independent consultant with over 22 years of hands-on experience. He holds a Masters of Science degree and numerous database certifications.

Pinal has authored 13 SQL Server database books and 56 Pluralsight courses. To freely share his knowledge and help others build their expertise, Pinal has also written more than 5,700 database tech articles on his blog at https://blog.sqlauthority.com .

Pinal is an experienced and dedicated professional with a deep commitment to flawless customer service. If you need help with any SQL Server Performance Tuning Issues , please feel free to reach out at [email protected] .

Pinal is also a CrossFit Level 1 Trainer (CF-L1) and CrossFit Level 2 Trainer (CF-L2) .

Nupur Dave is a social media enthusiast and an independent consultant. She primarily focuses on the database domain, helping clients build short and long-term multi-channel campaigns to drive leads for their sales pipeline.

Is your SQL Server running slow and you want to speed it up without sharing server credentials? In my Comprehensive Database Performance Health Check , we can work together remotely and resolve your biggest performance troublemakers in less than 4 hours .

Once you learn my business secrets, you will fix the majority of problems in the future.

Have you ever opened any PowerPoint deck when you face SQL Server Performance Tuning emergencies? SQL Server Performance Tuning Practical Workshop is my MOST popular training with no PowerPoint presentations and 100% practical demonstrations .

Essentially I share my business secrets to optimize SQL Server performance.

SQL SSRS suddenly stopped working.

About 10 days ago our SQL Server Reporting Services stopped working.  When trying to start the service manually, I get this error message: "windows could not start sql server reporting services error 1053"

I have tried extending the time out period as suggested but that did not help.

Whether I uninstall, reinstall, or repair I get an error message at the end telling me to check my setup log files, though I an unable to find an indicator as to what the problem may be.

We own SQL 2019 Standard and it does let me use that key when installing SSRS it after a uninstall but everything results in an a error.  It will not take the key if I try and "upgrade" the version already installed.

I have only been at this job a couple of months and it is possible the last guy installed an evaluation version but I am unable to confirm that.

I noticed that it never creates the  C:\Program Files\Microsoft SQL Server Reporting Services folder during install.

Here is the install error:

I also attached the last log file.

Thanks for your time and help,

Popular Topics in Microsoft SQL Server

I believe there is something wrong with the MSI/installation files or the Windows Installer itself. As you say, it doesn't even try to install the software.

This looks like some garbage. I could be wrong, but my experience says it isn't correct.

Hopefully, you are using virtual machines. The quickest solution is to build a new server with the correct SQL Server version and SSRS, then migrate your databases, SQL Agent jobs and application to the new server. You might get it working at some point without a rebuild, but I wouldn't trust that machine after this.

We don't even know what exact versions of Windows or SQL Server you are on - or trying to update with SSRS. You might be using SQL Server 2019, but what patch level is the machine at.

 Thanks for the reply.  Once I started poking around looking for the SQL log files I realized that SSRS was not installed in the default directory, it is on the D:\ drive.  I uninstalled the app (ending with that same error as above), renamed the SSRS install folder and reinstalled SSRS using our SQL 2019 key and everything went smooth.

 SSRS is backup and running, I just need to get things setup but I still have the old install folder.

 Thanks again for your help!

This topic has been locked by an administrator and is no longer open for commenting.

To continue this discussion, please ask a new question .

Read these next...

Snap! -- Star Formation, Cheese Caves, Landing a Plane, Bigger on the Inside

Your daily dose of tech news, in brief. Welcome to the Snap! Flashback: November 29, 1849: John Ambrose Fleming was born, the inventor of the first vacuum tube. (Read more HERE.) You need to hear this. Council apologizes for telling we...

Is my government job good for growth?

I got a job as a Telecom contractor for the government a few months ago and am approaching roughly 6mos. The most I have done in this job is install VOIP phones and do the BARE minimum of replacing patches cables and messing with ports. Most of my time is...

What password manager would you recommend?

What would be the best password manager be for a small company that uses multiple accounts for one person in a small business (~50 people).

Spark! Pro series - 29th November 2023

Today in History: 1972 Atari Releases PongThe modern video game industry was born on November 29, 1972, in Andy Capp's Tavern in Sunnyvale, California. The game was Pong, a machine recently constructed by Al Alcorn, an engineer working for gaming entrepre...

Snap! -- Pulsar, Spam Calls, Voice Protection, Palm Scanners, Geothermal Plant

Your daily dose of tech news, in brief. Welcome to the Snap! Flashback: November 28, 1948: Polaroid Instant Camera Goes on Sale (Read more HERE.) Bonus Flashback: November 28, 1967: Astronomers Observe the First Pulsar (Read more HERE.) ...

How to fix Reporting Services when it won't start after patching

After server patching you might find that the Reporting Services service will fail to start; not just SQL 2005 but others too. This is described in a Microsoft knowledge base article . The problem is that applying those instructions is a manual and error prone process.

Methods 3 and 4 from the article are the best. I also used Method 2 in previous revisions of this article but it proved less effective. If you want to give it a go I recorded which registry keys the Group Policy tool changes and recorded them below.

I've written the below PowerShell script to automate the process:

• Set the ServicesPipeTimeout (unless it's set equal to or greater than what we were going to). This will fix SSRS after the next reboot.
• Set the recommended registry key, temporarily, then change it back after SSRS has started.

I've used this fairly extensively in production. My registry path creation / removal process is a little dodgy.

• Hacker News

Troubleshooting

N-central   Troubleshooting

Account cannot connect to SQL server reporting services

Last modified.

Wed Nov 11 21:04 GMT 202

Description

• When running the installer for N-able Report Manager you may get the following error message:

Error: Account cannot connect to SQL server reporting services

Environment

• N-able N-central
• N-able Report Manager
• This is because the installer tries to access the reporting services over 127.0.0.1 and localhost .
• Either the site is not setup correctly in reporting services or the account has not been added in reporting services.
• This can also be caused if the reporting services are not running.
• Ensure the SQL Server Reporting Services service is running and set to run logon as local system
• Open SQL Server Reporting Services Configuration Manager.
• Go to Web Service URL .
• Make sure that TCP port is 80 and IP Address is "All Assigned (Recommended)".
• Go to N-able Report Manager URL .
• Make sure that TCP port is 80 and IP Address is "All Assigned".
• Open Http://localhost/reports In any browser window
• Go to folder settings .
• Click New Role Assignment .
• Add the user that are using in the installer and select content manager , and then click Ok .
• Click site settings in the top right corner.
• Click securit y on the left hand side.
• Add the user that you are using in the installer and select system user and then click OK .
• Refer to the Report Manager Installation Guide for more information.