Crystal Reports - Database Login failed only on production machine

Hello,

I am developing a web app that has reports created on VS 2019 and run fine from developer mode, but when I publish the website I get "Database logon failed" Error. Database server is on different server that development and production machine.
The error is throwing in line

cryRpt.ExportToStream(CrystalDecisions.Shared.ExportFormatType.PortableDocFormat)

Note that I have the same version of crystal reports installed to developer and production machine and aspnet_client folder is on wwwroot and 32-bit Application is enabled on Application Pool.
I also changed Identity to Administrator (Application Pool --> Advance Settings) and back to ApplicationPoolIdentity, since it didn't work.
I try connecting from IIS Server to database server using the reports credentials to check if I have access and there is access.

Development machine: Windows 10, Visual Studio 2019, Crystal Reports v4.0.30319
Production machine: Windows Server 2012 R2, Crystal Reports v4.0.30319

What could be causing this? Thank you in advance.

This is my code:

public void sendEmail(int id)
{
ReportDocument cryRpt = new ReportDocument();
TableLogOnInfos crtableLogoninfos = new TableLogOnInfos();
TableLogOnInfo crtableLogoninfo = new TableLogOnInfo();
ConnectionInfo crConnectionInfo = new ConnectionInfo();
Tables CrTables;
cryRpt.Load(@"C:\temp\rep1.rpt");
crConnectionInfo.ServerName = "server";
crConnectionInfo.DatabaseName = "db";
crConnectionInfo.UserID = "username";
crConnectionInfo.Password = "pass";
CrTables = cryRpt.Database.Tables;
foreach (CrystalDecisions.CrystalReports.Engine.Table CrTable in CrTables)
{
crtableLogoninfo = CrTable.LogOnInfo;
crtableLogoninfo.ConnectionInfo = crConnectionInfo;
CrTable.ApplyLogOnInfo(crtableLogoninfo);
}
cryRpt.SetParameterValue("@ID", id);
emailCreator(from, to, subject, body, "Attachment.pdf", cryRpt.ExportToStream(CrystalDecisions.Shared.ExportFormatType.PortableDocFormat));
}

4 Replies

Know the answer? Post it — somebody with the same question will find it here.

Dealy5y ago
I am using SQL Native 11 which I installed on production server as well, but I still get the same error.
Sachin Singh5y ago
If the connection is via ODBC, make sure you are using a 64 bit ODBC datasource.
This being MS SQL the following client installs are important:
MS SQL 2005 - OLE DB Provider
MS SQL 2008 - SQL Native 10
MS SQL 2012 - SQL Native 11
MS SQL 2013 - SQL Native 11
Dealy5y ago
The information is correct, I used the same servername,databasename,credentials to connect to database from the production machine through Sql Server Management Studio and is connecting.
Jignesh Kumar5y ago
Hi,

Your connection information which are going in production may be wrong. check at this area. Connection information is going correct in production.
crConnectionInfo.ServerName = "server";
crConnectionInfo.DatabaseName = "db";
crConnectionInfo.UserID = "username";
crConnectionInfo.Password = "pass";