SQL Server - SSRS Report prompting for login credentials

Hi ,

I developed a SSRS report and deployed that report to my staging server.

When I try to access the report it is always prompting for the login details. I noticed that the prompt is for the login information of datasource and not the report server.

My database server is different from the reportserver. Are there any configuration changes that need to be made to avoid the prompt ,as I have already mentioned those details in the datasource.

This is the screen shot 1-9-2025 5-04-45 PM.zip

Can you anyone please help me in this.

Thanks in advance

you can go through the below link


Solving the Reporting Services Login issue in the  of SQL Server 2008:

 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

I am assuming the prompt is for the username / password for the domain. Internally you are likely getting through the AD authentication check in your application as you will have permissions to deliver the report (you can test that premise with Firefox or other browser that doesnt handle AD authentication like IE does.

I think you may have setup for basic authorisation to view the report RSReportServer.config rather than web.config is that what you have done? (see this to see example

http://msdn.microsoft.com/en-us/library/cc281309.aspx.

If you are trying to get full anonymous access then you are in for some fun; luckily one of the RS team blogged a way to achieve it; I wouldn't advocate doing it straight onto a production box though.

you can check this blog also

http://blogs.msdn.com/b/jameswu/archive/2008/07/15/anonymous-access-in-sql-rs-2008.aspx

The following Code describes how to pass the logon information like Server Name , database Name , User Name and password dynamically to the Crystal Reports from C# applications.Use this code-
using System;
using System.Windows.Forms;
using CrystalDecisions.CrystalReports.Engine;
using CrystalDecisions.Shared;

namespace WindowsApplication1
{
public partial class Form1 : Form
{
public Form1()
{
InitializeComponent();
}

private void button1_Click(object sender, EventArgs e)
{
ReportDocument cryRpt = new ReportDocument();
TableLogOnInfos crtableLogoninfos = new TableLogOnInfos();
TableLogOnInfo crtableLogoninfo = new TableLogOnInfo();
ConnectionInfo crConnectionInfo = new ConnectionInfo();
Tables CrTables ;

cryRpt.Load("PUT CRYSTAL REPORT PATH HERE\CrystalReport1.rpt");

crConnectionInfo.ServerName = "YOUR SERVER NAME";
crConnectionInfo.DatabaseName = "YOUR DATABASE NAME";
crConnectionInfo.UserID = "YOUR DATABASE USERNAME";
crConnectionInfo.Password = "YOUR DATABASE PASSWORD";

CrTables = cryRpt.Database.Tables ;
foreach (CrystalDecisions.CrystalReports.Engine.Table CrTable in CrTables)
{
crtableLogoninfo = CrTable.LogOnInfo;
crtableLogoninfo.ConnectionInfo = crConnectionInfo;
CrTable.ApplyLogOnInfo(crtableLogoninfo);
}

crystalReportViewer1.ReportSource = cryRpt;
crystalReportViewer1.Refresh();
}
}
} Try this code and let me know.

Hello,

 

have you checked the properties of the data source once its been deployed to the report server? For comparison, on the report server, I have the following set up for a typical datasource:

- "Name" : name of datasource
- "enable this data source": is checked
- "connection type": MS SQL Server
- "connection string": Data Source= name of SQL server
Catalog = name of database
- "Credentials stored securely in the report server" (radio button):
User name = SQL Username or 'sa'
Password = password for the above

everything else is blank / not filled in / not checked

I don't use windows authentication when setting up the data source, I usually create a SQL Login/user with db_datareader permission on the database. This user is created specifically for running reports on the database. Alternatively, try using 'sa'

:)

 

Hope this is helpful !

Thanks

 

 

 

 

 

hi,

http://msdn.microsoft.com/en-us/library/ms160330.aspx
:%20http://blogs.msdn.com/b/lukaszp/archive/2008/03/26/solving-the-reporting-services-login-issue-in-the-february-ctp-of-sql-server-2008.aspx