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?
Related
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
I have a SQL Server Express database on my desktop that I use to test an old classic asp program. I need to change the authentication method from Windows authentication to password authentication. I have changed the server from windows auth to SQL Server and Windows auth mode and restarted the server. I went into security and added a new login for the database set the name and login and the default db to the db I need to be able to use password to login to. When I attempt to log in using SQL Authentication I get the error message
CANNOT OPEN USER DEFAULT DATABASE. LOGIN FAILED. LOGIN FAILED FOR USER ERROR 4064
I open the connection properties and changed the connect to db to the db for the password login and got the same message. I have searched the internet and tried ever solution I could find to no avail. What am doing wrong?
First of all see if the sql server was configured to received SQL Server Autentication (Mix Mode)
right clink at server at the management-> porperties -> security
choose the option below and restar the service
other commum problem to some connection it that the user was create with a wrong default database
open the security folder at the management-> Logins
Choose your the login and open the properties like this below
Tell me if it's works
I am using SQL Server 2016 on Windows Server 2012.
Also I am using SQL Server in a workgroup.
What I did is
installed AD DC (SQL server was installed before i install AD DC)
Removed AD DC to go back to workgroup and get local administrator user
After I did this, I cannot login to SQL Server using Windows Auth anymore
When I try to login with Windows authentication, I got this error
Login failed for user 'domain\username'. (Microsoft SQL Server, Error: 18456)
and I checked error log for the error state, the error state was 5.
But when I connect using sa user and checked login folder in Security folder, I see the correct user with the same name as my local user name. See the screenshot below
My local admin username is WIN-2NEKEGJF11Q\Administrator
Please, help me
-see the red line
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
When I try to create a Pover View report over my .bism connection I get following error:
Original XML
rsCannotRetrieveModel400An error
occurred while loading the model for the item or data source
'http://localhost/rpl/model.bism'. Verify that the connection
information is correct and that you have permissions to access the
data source.http://go.microsoft.com/fwlink/?LinkId=20476&EvtSrc=Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings&EvtID=rsCannotRetrieveModel&ProdName=Microsoft%20SQL%20Server%20Reporting%20Services&ProdVer=11.0.2100.60Microsoft SQL
Server Reporting Services11.0.2100.60127OsIndependent1033ReportingServicesLibraryAn error
occurred while loading the model for the item or data source
'http://localhost/rpl/Model.bism'. Verify that the connection
information is correct and that you have permissions to access the
data
source.Microsoft.ReportingServices.ProcessingCoreCannot
impersonate user for data source
'TemporaryDataSource'.Microsoft.ReportingServices.ServiceRuntimeCannot
convert claims identity to windows
token.Microsoft.SharePointCould
not retrieve a valid Windows
identity.mscorlibAccess
is
denied.
Readable version
rsCannotRetrieveModel400An error occurred while loading the model for the item or data source 'http://localhost/rpl/model.bism'.
Verify that the connection information is correct and that you have permissions to access the data source.http://go.microsoft.com/fwlink/?LinkId=20476&EvtSrc=Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings&EvtID=rsCannotRetrieveModel&ProdName=Microsoft%20SQL%20Server%20Reporting%20Services&ProdVer=11.0.2100.60
Microsoft SQL Server Reporting Services11.0.2100.60127OsIndependent1033ReportingServicesLibrary
An error occurred while loading the model for the item or data source 'http://localhost/rpl/Model.bism'.
Verify that the connection information is correct and that you have permissions to access the data source.Microsoft.ReportingServices.
ProcessingCoreCannot impersonate user for data source 'TemporaryDataSource'.
Microsoft.ReportingServices.
ServiceRuntimeCannot convert claims identity to windows token.Microsoft.SharePointCould not retrieve a valid Windows identity.mscorlib
Access is denied
Microsoft SQL Server Reporting Services11.0.2100.60127OsIndependent1033ReportingServicesLibrary
An error occurred while loading the model for the item or data source 'http://localhost/rpl/Model.bism'.
Verify that the connection information is correct and that you have permissions to access the data source.Microsoft.ReportingServices.
ProcessingCoreCannot impersonate user for data source 'TemporaryDataSource'.
Microsoft.ReportingServices.
ServiceRuntimeCannot convert claims identity to windows token.Microsoft.SharePointCould not retrieve a valid Windows identity.mscorlib
Access is denied
I am using SQL Server 2012 RTM, Sharepoint 2010, Windows Server 2008 R2 Enterprise with service pack 1. All SQL, Analysis Services and Sharepoint windows services run with the same domain account which is also administrator in local machine. That domain account is god in both SQL and Analysis Services. It also farm admin in sharepoint and all sharepoint services uses that account. IIS aplication pools run with that account too. I can connect by any other client like SQL Management Studio. What is wrong with Power View connection? Please help!
In SharePoint central administration, Navigate to Application Management -> Manage Services on the Server. Stop the service "Claims to Windows Token Service" and restart IIS. Should fix your problem.