Tag Info

Hot answers tagged

6

If you don't have any good reason to expose it, Then you should probably not expose it. By the way you may be interested in this article to decide wether or not you should expose it


5

Check Server Manager -> Roles and verify if you have Web Server (IIS) installed. If yes, make sure you have IIS Management Console installed.


4

SSRS 2008 does (by default) not rely on IIS. You can run them side-by-side if you wish, but it is no longer required. To configure the URLs to access SSRS, you use the Reporting Services Configuration Tool - you probably want the "Advanced" configuration for Report Manager. See the following link for detailed instructions on how to setup URLs in SSRS 2008. ...


3

Some troubleshooting steps: Are you seeing any errors in the Application event log for the OS? Do you see the hits against /reportserver/ in the IIS logs? Have you verified in IIS that the /reportserver/ virtual directory is still present and that it's using the correct application pool (which has the proper identity)?


3

The report redist must also be installed on any application/web servers if the app is using the report viewer .net control. Users also need admin rights to install the activeX in xp. We automate the installation of these component to all users - similar to this: ...


2

To see the status of your subscriptions and when they last executed, you can perform a query: http://feedproxy.google.com/~r/sqlserverpedia/~3/O78C3knsUO0/


2

Yes you can use SQL 2005 backend for SSRS 2008. Quote: You can use an instance of the Database Engine from SQL Server 2005 or SQL Server 2008 to host the databases. In the olden days, you could not host SSRS 2005 databases onto SQL Server 2000.


2

Resolved the issue after reading an MSDN post here: http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/880b77ac-3228-40ce-99dc-12b0ff0eb46a The steps outlined below allowed me to run the msi successfully and then deploy the feature to the farm: Open the commad window (Start>Run type cmd and press enter) Navigate to the path where ...


2

Do the keys become unnaccessible after a reboot, or after a restart of the Reporting service, or after a restart of the support SQL Server service? As a generic guideline, see this article to troubleshoot the issue: Troubleshooting Initialization and Encryption Key Errors. Then use rsconfig and/or rskeymgmt.exe to fix the problem, once you identify the ...


2

I assume you've discussed the impact of the "no activex" policy with whoever is proposing it? You can set the "ie internet zones" appropriately to only allow SSRS ActiveX to be used for certain trusted sites (like internal sites). A workaround would be to use SSRS schedules to create offline copies of the reports to a file share. You'd only get "canned" ...


2

Research into how Kerberos delegation works shows that no, you cannot share SPNs between service accounts on the same box. I solved the problem by provisioning a second IP address for my server and mapping IIS to one IP address and SSRS to the other. I then created two new A records in DNS (don't use C records, they are unreliable with Kerberos delegation) ...


2

Definitely sounds like a double-hop issue. You will need to set your environment to use Kerberos authentication between your clients, the report server, and the data server. For Kerberos to work, you'll need the reporting service and SQL database service to be running as domain accounts rather than local accounts (Local system/Network service), and you'll ...


2

You won't be able to log ship from SQL 2005 to SQL 2008 and be able to read the database. When the database goes into standby mode it can't bring the database online because it can't upgrade the database's physical version.


2

I would first determine if SSRS is indeed only using one processor. This is simple enough using Process Monitor, Task Manager, or Performance Monitor. If it's only using one thread, I would research the documentation and see if there is anyway to scale this out. Unfortunately, I don't know the answer. The other thing I would look at is SQL Server. Use SQL ...


2

I use the principle of least privilege when setting up services and create a specific account for each service. If you are going to use built-in accounts, which one you should select depends if you are using Active Directory or not. If the server is in an AD Domain, you should use Network. Otherwise, I'd suggest Local System. But my first choice would be to ...


2

The solution was two-fold: I exported the certificate from the primary site sever under "Personal\Certificates" the friendly name is "ConfigMgr SQL Server Identification Certificate." I then imported the certificate to my local workstation under "Trusted Root Certificate Authorities\Certificates." This allowed me to connect to SQL server when I choose "Use ...


2

Using ILSpy, I've determined that "ExecutionLogLevel" setting isn't even used by SSRS 2012; it's not a supported setting. There is no code that references that string anywhere. FYI, I can find code that references "EnableExecutionLogging" and "ExecutionLogDaysKept" (complete with the internal constants defining the default values that SSRS uses). The ...


1

type IIS in the search bar it should bring you to the internet services manager, or you can click start, programs, admnistrative tools and the IIS maanger should be listed


1

maybe you can find the answer here: http://www.mssqltips.com/tip.asp?tip=1453


1

The answer to the original question was that on Windows 2008 (due to UAC) you need to run STSADM from an administrative command prompt. See the comments on the question and Greg_the_Ant's updates for further discussion.


1

Most likely you need to re-register the SSRS WMI Namespace and/or the WMI Provider. You can troubleshoot and fix the problem using the following steps. Troubleshoot the problem using the WMI Tester Close all instances of Reporting Services Configuration Manager or SQL Server Management Studio. Open a command prompt and type wbemtest, and then click OK. ...


1

AFAIK (99% sure) the Dundas components that Microsoft licensed for SSRS in SQL Server 2008 are present in all versions of SQL Server 2008, thus if you're already running 2008 then there is nothing to upgrade. Where are you seeing that they are missing? Which do you think you are missing? If you see for example the donut chart then they are there.


1

it would be helpful to have all the versions/builds/service packs of the systems involved. Here's an answer on StackOverflow that seems to have a fix that has been voted up a lot.


1

Copying reports is pretty easy if you have the original RDL/SMDL files; simply redeploy/upload it again, and change its name/location/datasource. If you don't have the original RDL/SMDL files, you'll need to extract these from the report server and redeploy. The easiest way to do this is via an rs.exe script. The following describes how to copy reports ...


1

I finally found the solution to this issue. Basically the build of sql server 2008 reporting services I installed added an RSWindowsNegotiate setting into rsreportserver.config file and I was running the reporting service under an account other than Network Service. I removed the RSWindowsNegotiate setting and just left the RSWindowsNTLM setting and ...


1

The problem could have been caused by changing the 'log on as' account used in the SQL Server Agent Windows service. I think that the SQL Server Agent no longer had permissions to access the encryption keys (used for subscriptions?), and generated the failure message and requiring a restore of the encryption keys. Additional information found here.


1

SSRS exports a web service that allows reports to be downloaded and uploaded programatically (amongst other things). It comes with utility called rs.exe that lets you script this type of process using vb.net. All this really does is top and tail the script and then compile and execute it. IronPython or any .net language can also be used to do this type of ...


1

You didn't indicate what version of SQL Server. Keep in mind SSRS 2005 requires IIS installed on the box as well. SSRS 2008 does not. It uses HTTP.SYS natively. The optimal answer is #3, however, it really depends on the existing load on the physical server as well as the type of reports you would be running. #1/#2 are essentially the same option with ...



Only top voted, non community-wiki answers of a minimum length are eligible