After successfully installing SQL Server Express 2012. I am trying to get set up my Report Builder. Unfortunately I am asked for a password when clicking on the Report manager URL or the Web Services URL. It says something like this (connecting to "my_Pc").
As far as I am aware I do not have any password on my PC nor set up one when configuring my SQL Server. Please note that I have not configure SSRS yet and my Service account is still ReportServer$SQLExpress. How do I sort this out please
?
Issue is with how you have created data source for Report.
Data source is created with option "Prompted Credentials" .
It should be created with "Stored Credentials" or "Windows Integrated Security"
Read more
At one point you might have configured the user "sa", have you tried using sa login to access the report page? If you are using machine id to authenticate with sql server, to configure a new user, after you connect to your database, browse down to security > logins > right-click and choose "new login".
One easy solution for this is to check the browser you are using . |I was using internet explorer edge and realise that explorer edge was simply not trusting that site. So if you are on explorer just go on setting and trust the site.
However I was on IE edge which does not trust any site. I changed it for google chrome. Everything is running perfectly fine. just change the browser (Internet Explorer best as Google could pose problem to visualize data when creating reports) and refresh everything should be running just fine.
Related
I just installed SQL 2012 Enterprise on a laptop running windows 10 Pro x64.
When I try to execute my SSRS reports from the report manager, I always get the same error:
An error has occurred during report processing. (rsProcessingAborted)
Cannot impersonate user for data source 'DataSource1'. (rsErrorImpersonatingUser)
Log on failed. Ensure the user name and password are correct. (rsLogonFailed)
The user name or password is incorrect
I am using integrated windows authentication with a domain account.
The domain account can log on through SSMS and can access the databases with no issue and run queries.
I have also tried using a local SQL account and password but with the same result - The username or password is incorrect, yet this account works through SSMS and is able to execute queries and such.
When i click the Test Connection button in SSRS datasource configuration, it states the connection was created successfully. (I have included a shot of what I am talking about in the uploaded image)
After googling, people stated that the account that is being used to connect to the database using windows impersonation had to have log on locally permissions, so I added the account through local security Policy, but it made no difference.
Another blog stated the SSRS Service account had to also be granted log on locally permissions - so I granted it the log on locally permission as well. Still to no avail.
I have also tried disabling the windows firewall and connecting to both the machine name and localhost just in case there was some screwy rules regarding localhost - still with the same result.
Other people suggested the execution account in SSRS manager needed be disabled. I didn't set this up initially - but set the account up just in case it had something to do with it - still with the same error then removed it again still with the same error.
Can anyone offer any other suggestions as to what might be the cause and how I might fix this?
Many thanks and Cheers
Rod.
OK - managed to work out the problem and a workaround. But it doesn't actually solve the problem.
Problem is Chrome and IE11 wont update the Reports web site when managing datasources. Even when launched as administrator, the SSRS management interface site does not appear to save the changes. Edge is just a joke so don't even bother with that one.
Now - I figured Microsoft has broken something which SSRS interface needs in windows 10, so I logged onto a Windows 7 machine and using IE11, was able to navigate to report manager site, update the credentials (windows and SQL Server credentials) and the reports run.
Confirmed this by trying to change the credentials back on windows 10 and it immediately broke the reports again. Set the credentials back in Win 7 and it corrected the reports.
So if you are using windows 10 and are having issues configuring credentials for SSRS reports, try logging in from a windows 7 machine and set through IE on that machine.
EDIT: IE11 works on older windows 10 build (enterprise) , latest build (Pro) seems to be broken.
Cheers
Rod.
If you have specified an unattended execution account, SSRS flip-flops between impersonating it and the identity specified in your data source during the rendering process. If you use an unattended execution account, you’ve got to keep the password up-to-date.
You could also choose not to use the unattended execution account at all, which may also solve your problem. For more detail see http://blogs.msdn.com/b/bimusings/archive/2006/08/16/702490.aspx
Simply,
Go to Report Configuration Manager
Go to Excution Account
Enter Domain\UserAccount [User Account is your windows User]
Enter Password [Windows Password]
Save and you are good to go
I am trying to migrate several SSRS reports from a client's old SQL Server 2008 R2 on Windows Server 2003 R2 to a new SQL Server 2012 on Windows Server 2008 R2.
I have it all set up except that on the new system, when I click on the Report Manager URL from within Reporting Services Configuration Manager, it pops up a login screen. The old system looks identical, but it does not pop up the login screen.
I have tried checking the "remember my credentials" but with no effect.
I have entered this login in the Site Settings -> Security screen and in the Folder Settings -> Security screen with no effect.
The client has the requirement that they never see the login screen. Can anyone tell me what I'm doing wrong or point me to a solution?
Thanks,
dtaylor
Ok, I figured it out and will post here for completeness.
In my case it wasn't the way SSRS was configured at all. I noticed that the login page was for the computer credentials and not database credentials. I further noticed that the ONLY difference between the account on the old server and the account on the new server was that the old server account was just a standard user account but the account I was using on the new server was the built-in Administrator account. At first I dismissed this, but just for grins, I created another user account on the new server and logged back into the server with the new account. Et Voila, I can now link to the reports without incurring a login page.
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.
I configured SSRS 2008 on a remote server.
I can access the report manager from my local machine using http://SERVER_NAME/Reports_INSTANCE_NAME
problem is that when I try to deploy a report from BIDS, I get the "reporting services login" dialog box that asks me for user and password. I try my AD user and it doesnt work.
I already added myself to all possible roles, including System Administrator.
I saw online that the problem maybe with the IIS website that must be configured to allow anonymous access. That's fine, but where can I configure that since SSRS2008 doesn't create the websites on IIS anymore (also read that online) and I don't seem to have this possibility using the Reports Service Configuration Manager
Take a look at the link below...it's in reference to 2008 CTP, but there are still some items to check in your setup...
http://blogs.msdn.com/b/lukaszp/archive/2008/03/26/solving-the-reporting-services-login-issue-in-the-february-ctp-of-sql-server-2008.aspx
Similar issue / resolution here as well...
Repeated Reporting Services Login issue when deploying through BIDS to a remote server
In your report configuration file, try removing the RSWIndowsNegotiate from the Authentication tag:
<Authentication>
<AuthenticationTypes>
<RSWindowsNegotiate />
</AuthenticationTypes>
<EnableAuthPersistence>true</EnableAuthPersistence>
</Authentication>
We have an ASP site using Windows authentication to connect to a SQLServer database. There are three instances of the web site, a Dev environment (located on my Workstation), an UAT environment and a production environment, which are on separate servers.
When I access the Dev site (which uses the same DB as the UAT site) I have no issues, the site connects to the database using my Windows account. However when I connect to the UAT site, it uses a different account (one which belongs to me but is not connected to my default Windows login) which is not permissioned on the DB, so the site returns the following error:
Microsoft OLE DB Provider for SQL
Server error '80004005'
Cannot open database requested in login 'ANAML'. Login fails.
/inc/dbconnect.asp, line 4
The ASP files on the Dev and UAT sites are identical, so can anyone explain why the UAT site might be using the incorrect Windows account? This only affects me, from all workstations, and no other users.
Have rebooted the server and my workstation, and cleared my internet files locally.
I found the answer at this page on ServerFault. Seems the login details for the UAT server had been stored in the Users control panel at some point. Deleting the relevant entry in the control panel restored the correct login when connecting to the website.
Well, my ASP knowledge has mostly faded but I'll see what comes out of my brain. My first thought would be that the Virtual Directory security is configured differently on the server where it is failing. It sounds like you would need it to be set to "Integrated Windows Authentication" only.
If that is set correctly then I'd ask about your connection string. Does your connection string specify Trusted Connection (e.g. it does not specify a username and password)?
Where does the ANAML account come from? Is it a SQL only login or is it a windows account?