I want to deploy a report to a report server (SSRS) from Visual Studio. The (domain) account that's saved in Visual Studio does not have permissions on the report server. How do I change the user credentials to a different user that does have permissions, preferably a SQL Server account? Visual Studio simply fails out without giving me the option to try a different account.
Error rsAccessDenied : The permissions granted to user 'domain\user' are insufficient for performing this operation.
I got stuck with the same error message because I entered the wrong credentials on the first attempted deployment, and Visual Studio saved those for the next attempts. After restarting Visual Studio, I was allowed to enter different credentials.
Set the report connection; provide the connection string in the General tab and select to use the Windows Authentication (Integrated Security) in the Credentials tab.
In SSRS server, create a data source. In the Connect Using section, select 'Credentials stored securely in the report server' and enter in the login info for the service account. Make sure you click the check box for 'Use as Windows credentials when connecting to the data source'.
Deploy the report to SSRS and assign the report to use the new data source.
Make sure the service account has permissions to execute any queries in SQL server
Related
SQL Server 2012 / SSRS. Windows 2008 R2. When trying to access the Report Manager via URL (http://servername/reports), it prompts us for a username and password. When I enter a valid user/pass it works and I can get to the Report Manager site and run reports fine. But we don't want to be prompted, we don't even need Windows Authentication, just to go strait in to the page. Any ideas why its asking for a username and password and how I can allow direct access?
You need to store the credentials in the report.
You can store the credentials used to access an external data source.
Credentials are stored in reversible encryption in the report server
database. You can specify one set of stored credentials for each data
source used in a report. The credentials you provide retrieve the same
data for every user who runs the report.
Stored credentials are
recommended as part of a strategy for accessing remote database
servers. Stored credentials are required if you want to support
subscriptions, or schedule report history generation or report
snapshot refreshes. When a report runs as a background process, the
report server is the agent that executes the report. Because there is
no user context in place, the report server must get credential
information from the report server database in order to connect to a
data source. The user name and password that you specify can be
Windows credentials or a database login. If you specify Windows
credentials, the report server passes the credentials to Windows for
subsequent authentication. Otherwise, the credentials are passed to
the database server for authentication.
https://learn.microsoft.com/en-us/sql/reporting-services/report-data/specify-credential-and-connection-information-for-report-data-sources
You could configure Windows AD and set up NTLM/Kerberos in SSRS. This would help to seamlessly access the resources without an username and password.
I installed SQL Analysis Services. I want to test it via Excel Services on SharePoint.
I created new account with which I can easily login to SQL Server Management Studio: the username and password are demonstrably correct.
After that, I made a new Excel workbook and connected it with the database. I provided the account details created before and everything it works.
Then I tried to upload a workbook to the SharePoint Document Library. Upload is successful, but when i want to refresh the data there I get this error in the SQL log:
"Login failed for user 'Darko'. Reason: Password did not match that
for the login provided."
What password is not matching? I can easily login to SQL Server Management Studio. I tried with the "sa" account but get the same result. I've set "SQL Server and Windows Authentication" in server properties. How do I fix or diagnose this issue?
I have a SQL Server 2008 R2 instance and can log in using the sa user. But I want to define another user (administrator) to log in with SQL Server Management Studio, so I did the following:
Logged in to the server in Management Studio as sa.
Right clicked on the database name.
Clicked on properties.
Then under permission, I select the required username (administrator).
And I grant him all the permission.
But when I tried to log in using administrator, I got the following error:
Login failed for user “administator” Error 18456.
Can anyone advise what might be the problem?
If the server encounters an error that prevents a login from succeeding, the client will display the following error mesage.
Msg 18456, Level 14, State 1, Server <server name>, Line 1
Login failed for user '<user name>'
This usually means that your connection request was successfully received by the server name you specified but the server is not able to grant you access for a number of reasons and throws error: 18456.
This eventID sometimes provides also state 1 which actually isn’t that useful as due to security reasons any error is converted to state 1 unless you can check logging on the server.
Microsoft does not provide very useful message boxes so below are some explanations why you get the error.
Invalid userID: SQL Server is not able to find the specified UserID on the server you are trying to get. The most common cause is that this userID hasn’t been granted access on the server but this could be also a simple typo or you accidentally are trying to connect to different server (Typical if you use more than one server)
Invalid password: Wrong password or just a typo. Remember that this username can have different passwords on different servers.
less common errors: The userID might be disabled on the server. Windows login was provided for SQL Authentication (change to Windows Authentication. If you use SSMS you might have to run as different user to use this option). Password might have expired and probably several other reasons….
18456 state 1 explanations: Usually Microsoft SQL Server will give you error state 1 which actually does not mean anything apart from that you have 18456 error. State 1 is used to hide actual state in order to protect the system, which to me makes sense. Below is a list with all different states and for more information about retrieving accurate states visit Understanding "login failed" (Error 18456) error messages in SQL Server 2005
SQL Authentication not enabled: If you use SQL Login for the first time on SQL Server instance than very often error 18456 occurs because Windows Authentication (only) is set in Server properties (security section).
To Access Server Properties,
- Open SQL Server Management Studio, go to Object Explorer pane (use view if you can’t see it).
- Use the connect button to connect to database engine for your server. Once connected you will see it in object explorer.
- Right click server and click properties. Server Properties window will appear.
See below screenshot that might be causing SQL login to fail
You should set Server Authentication to SQL Server Windows Authentication
To resolve this error follow the steps below on computer with SQL Server 2005.
Create new user with Administrator privilege with same username and password as of SQL Server 2008 in operating system.
On SQL Server database create new user by expanding DatabaseNode >> Security >> Login >> - Create New User and add this new user with Windows Authentication radio button selected. - This user can be only added by selected Windows Authentication it is Operating system’s User Login.
Once above two steps are completed when connected from SQL Server 2008 to SQL Server 2005 using Windows Authentication it will connect successfully.
How to fix? Check this link video SQL Server and Windows Authentication Mode page.
Source
You need to add a server login:
Connect to your SQL Server with SSMS as sa.
Drill into the server's Security folder in SSMS's Object Explorer pane.
Right-click on the server's Security > Logins folder that appears in Object Explorer.
Click on New Login... in the context menu that appears.
Provide details of the new login in the Login - New dialog that opens - particularly its General, Server Roles, and User Mappings pages (along the left). (See the screenshots of each page with sample input at the bottom of the answer.)
You may need to add a database user depending on your needs, but a server login (like your sa login) is necessary to connect to the SQL Server instance using Windows or SQL Server authentication. Mapping the new login to a database user (in the Login - New dialog's User Mappings page) will create a new user in the mapped database if you specify a username that does not already exist; alternatively you can map the new login to an existing database user.
Another SO question speaks to the differences between server logins and database users.
Login - New (General page)
SQL Server authentication
or
Windows authentication
Login - New (Server Roles page)
Login - New (User Mappings page)
SQL Server authentication
or
Windows authentication
So I've been tasked to install DNN onto my system. I am using the Microsoft Web Platform Installer. I am being asked for the password for the 'sa' account. I do not know the password for the account. So when I tried to use the Microsoft SQL Server Management software to change the password I get the following message:
"Change password failed for Login 'sa' (Microsoft.SqlServer.Smo)
Additional Information:
An exception occurred while executing a Transact-SQL or batch. (Microsoft.SqlServer.ConnectionInfo)
Cannot alter the login 'sa', because it does not exist or you do not have permission. (Microsoft SQL Server, Error: 15151)"
How would I obtain permission to change the password? Or am I missing the point entirely and should be doing something else to install the software??
I would assume the issue lies with SQL, what steps should I take to rectify this problem??
SQL Server uses either/both of "Windows authentication" and "SQL Server authentication".
By default, MSSQL installs with ONLY "Windows authentication". "sa" requires MSSQL authentication.
SOLUTION:
http://technet.microsoft.com/en-us/library/ms188670.aspx
1) Go into SQL Server Management Studio Object Explorer, right-click the server, and then click Properties.
2) On the Security page, under Server authentication, select the new server authentication mode, and then click OK.
3) In the SQL Server Management Studio dialog box, click OK to acknowledge the requirement to restart SQL Server.
4) In Object Explorer, right-click your server, and then click Restart.
Are you able to login via Windows Authentication and change it that way? If so, that would be the best way to do it.
If the only account that has admin access is the sa account though, then you can try starting SQL server in single user mode and then resetting the sa password. Note that this method requires local admin access to the server itself.
http://sigkillit.com/2013/01/02/recover-sa-password-on-microsoft-sql-server/
Sounds to me like you could login with the SA account into SQL server, it will likely prompt you to change your password (first time logging in) and then you would be good to go after that.
That being said, I never recommend setting up DNN to connect to SQL server with the SA account. Each DNN database should have its own DB user, that way if one DNN install gets compromised for some reason, they can't reach out into other databases on the same server.
EDIT: a little more info
From http://www.christoc.com/Tutorials/All-Tutorials/aid/1
In SQL Server you should go through and create a new database. I always create a database with the same name as the website, so in this case DNNDEV.ME. Once you have created the database, create a user that can access that database. I always use SQL authentication, turn off the enforce password requirements, and give the user DB Owner and Public access to the DNNDEV.ME database. Remember the username and password you create here as you will need them when you walk through the Installation screen for DotNetNuke.
I have SQL Server 2008 with BIDS, I have installed sql server myself and i am administrator of machine. Now I am able to make reports using BIDS, I am also able to login(windows authentication) to report server using SSMS, but when i try to access report manager URL it asks me for Username/passowrd. I am not sure what to give there as till now from SSMS i could manage with windows authentication for database engine.
SSRS always uses Windows authentication so your user name and password that you're seeing is your Windows login. There is no separate account just for Report Manager. If you're seeing a prompt, you might have UAC enabled and it's prompting you because of that. Or your browser is not enabled for Windows integrated security. You can add the Report Manager URL to trusted sites or Intranet sites if you're using IE.