I'm trying to figure out which credentials I should be storing to enable use of Reporting Services' Data-Driven Subscriptions. Nothing I type in seems to work. It's all happening on localhost under XP-Pro SP3.
A little background:
I'm able to connect to the localhost server as a Database Engine in SQL Server Management Studio, using either Windows Authentication or the username 'sa' and a given password. However, trying to connect to localhost as a Reporting Services server using those same credentials fails with this error:
Cannot connect to localhost.
Additional information:
Unable to connect to the remote server (Microsoft.SqlServer.Management.UI.RSClient)
No connection could be made because the target machine actively refused it [IP]:80
In Reporting Services Configuration Manager, Windows Service Identity is set up like this:
Service Name: ReportServer
Service Account: LocalSystem
Built-in Account: Local System
Web Service Identity is set up like this:
ASP .NET Service Account: [Machine]\ASPNET
Database Connection:
Server Name: [Machine]
Database Name: ReportServer
Database Version: C.0.8.54
Server Mode: Native
Credentials Type: Service Credentials
The Service Status page is green and running.
The Report Server webpage is available and accessible; I can view and generate reports manually. However, I want to create a Data-Driven Subscription so that I can create multiple reports in one go. This is where I'm running into problems. When I click "Subscriptions", it refuses to let me set one up because
Data-driven subscriptions cannot be created because the credentials used to run the report are not stored, the report is using user-defined parameters values, or if a linked report, the link is no longer valid.
Fair enough, I haven't stored credentials. So I went to the "Properties" section and clicked "Data Sources". By default, the report uses "A shared data source". Switching to "A custom data source" requires me to select credential types. Nothing I enter into this seems to produce a result that will allow me to get past the "Data-driven subscriptions cannot be created..." message and create the subscription.
Anyone know how I can fix this?
That error with subscriptions implies that at least one of the data sources you're using (either for your report or for the subscription data) doesn't have stored credentials.
For example, normally I might be using Windows Integrated Security to connect to a data source, but if I want to store the credentials, I will enter MyDomain\SomeAccount and its Windows password in the box on the Data Source screen, and tick the checkbox to indicate it's Windows security.
If this is done for all the data sources, then you should be able to create a subscription. You don't need to use a custom data source if you're happy to store credentials in the shared data source.
I think you need to store credentials for the data source as well as for the execution account in the SSRS Configuration tool, especially if you're using Local System. Rob is correct about how to set the credentials for the data source, just modify the shared data source directly.
Related
I'm new to SQL Server. I was a postgres user before. I installed the default SQL Server on my local machine and I'm trying to get an old react with node js application of mine working with a SQL Server. When ever my frontend makes more than 1 call to the backend, if my SQL Server has admin privileges it throws
Error: 17810: Could not connect because the maximum number of '1' dedicated administrator connections already exists.
If not, it throws:
Error 18451: Only administrators may connect at this time.
I checked my database configs and it's set to MULTI_USERS, so I don't understand why I can't login without admin privileges. Can someone help me with this? I wasn't able to find anything online.
My NodeJS backend is using TypeORM to connect to the database
The dedicated administrator connection is a different kind of connection. It's not just "a connection being made by someone with administrative access". You would use the DAC when the SQL instance is having some kind problem, and you can't connect at all because resources are all tied up. SQL will reserve some resources especially for the DAC connection to make sure you can still connect.
A DAC connection can be made by specifying ADMIN: as part of your connection string, which will connect to the assigned DAC port.
You shouldn't use this for "routine" admin work. Just connect using a login with the required administrative server roles (eg, sysadmin). You definitely shouldn't use this as part of a regular application's connection string. You shouldn't be using a SQL Server sysadmin login either. Create a user with the appropriate permissions for your application, and don't use the admin connection.
Regarding your second issue: Make sure the instance wasn't set to start in single user or minimum configuration mode using startup flags. Note that this is for the whole instance, it's not the same as the configuration for an individual database.
I’m trying to find a way on using web based SSRS Report Builder outside of Active Directory environment or using RDP.
Currently I use the ananymous solution. Following is the detail.
In the Data Source Server Type selection, I‘m choosing “Analysis Service” (Anonymous Authentication is embed in the IIS Server)
The user access is set by default to Anonymous Authentication.
This is how I provide the connection detail in SQL Server Management Studio.
And the following is the connection string configuration in SSRS
Only by choosing the “current Windows User” (without filling any user authentication) the Datasource access in the report builder can be accessed.
By this solution, I have deep concern about the security of the data source, as the data source become accessible without any authentication.
Is there any other settings or solution to enable me design report in SSRS Report Builder from outside from the server in a more secure way?
You probably don't want to do this. Set up a VPN instead, then they can be accessed as though they are on the local lan but maintaining security.
I am following http://msdn.microsoft.com/en-us/library/ff647294.aspx to add authentication to a WCF. My SQL Server is on a different machine than the development server. In Step 1, I am not using SQLExpress but using SQL Server 2012. When I get to the Step 8: Create a User in the User Store, under Security Tab of ASP.net Web Site Administration Tool I see the following message:
There is a problem with your selected data store. This can be caused by an invalid server name or credentials, or by insufficient permission. It can also be caused by the role manager feature not being enabled. Click the button below to be redirected to a page where you can choose a new data store.
The following message may help in diagnosing the problem: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.
So looks like setting Windows Authentication is the problem. I am not sure what in the multi-step process I have to modify to add authentication to my WCF. Any help will be appreciated.
The example in Your link Access to SQL server is given to a local user NetworkService. This is the default Identity for the Application pool.
In Your case you cannot use a local user account, since the SQL Server is on a different machine.
You need to:
Create a domain account
Grant Access to SQL server to that domain account
Change the Identity for Your Application pool to that of the domain accout
I have one web server & one DB server (running SQL SERVER 2008). Both the servers are in different domains. The web server is allowed to communicate(the communication takes place internally without the intervention of firewall) directly with the DB server, it is given Admin privileges & the DB access through SQL is going on without any problems.But whenever the web server tries to access the Reporting Server & its services, its asking for a separate authentication(Local system account authentication has been configured for SQL Server). I want to know whether is there any way to get rid of this separate authentication for Reporting Services
If you are being prompted for credentials when running a report, then your data source is configured to prompt at run time. You'll need to change the DS to use a SQL login if you don't want this to happen. Your windows credentials cannot be passed from one server to another.
If you are being prompted to log on to the RS site - I've only experienced that on firefox but fixed with a firefox config setting to save the cred for the domain.
I have an analysis services cube in SQL server 2005 which I'm connecting to via an excel front end.
When I connect via one user its fine, but when I log on to the same machine as another user I get an error in my excel spreadhseet - "user...does not have access to the [Cube name] database"
Obviously the first user has the correct permissions, but how do I set up analysis services to allow other users to join the party?
Login to the machine with an account that is an administrator (Domain\CubeAdmin) on the cube. Connect to the cube in BIDS (run devenv.exe and open Analysis Services Database).
Under Roles, create a reader role and in the Membership tab, add the user account (Domain\NewUser).
All this will only work if the SSAS Server Administrator gives the Domain\NewUser access to the server.
The Windows user accounts that you are trying to access SQL Analysis Services with need to be added to the Roles in the Cube that would allow the permissions you want.
If you are connecting over HTTP using msmdpump.dll through IIS you need to turn on Authentication for that site and allow the Windows user account to access the site.
If the IIS site using msmdpump is on another machine and you aren't using a domain then the accounts would need to exist on both servers with the same password.
I know this is old but for other's reference, I had to repair the MS Office install to resolve a connectivity issue with SSAS. The user was added to the role, but the error "Cannot connect to server" was displayed when connecting.
Raj has already answered the initial question... You need users to be set up with at least read access to your SSAS instance.
However, the error "Cannot connect to server" does not necessarily mean it's an authentication issue, it actually doesn't mean much. I've seen this error on Excel 2007 on various occasions, where the underlying error could be anything, this is just a generic error from Excel.
Several aspects that caused problems on my end were (things to check):
User has access to the web site (if not using anonymous auth)
ADOMD and OLEDB for Analysis Services are installed locally (correct version)
User propagated to SSAS has read access to instance (are you using ApplicationPoolIdentity?)
Handler mapping (script mapping for *.dll) is set up
For a complete guide of how to set up HTTP access for SSAS check:
Microsoft - Configure HTTP Access to SSAS via IIS
Cheers