cancel
Showing results for 
Search instead for 
Did you mean: 

Logon failed.Error in File XXX.rpt Unable to connect: incorrect log on para

Former Member
0 Kudos

HI

I have had crystal reports running on our small business server 2003 server now for over 12 months with no problems, this is with creating crystal reports in visual studio testing them locally then deploying to the server - all fine.

The past week we upgraded the server from small business server 2003 to small business server 2008.

I use Sql server 2008 on both servers.

Now I get the error message:

Logon failed.Error in File temp_e54ff288-3e6b-436d-aa03-442e72399e02 {66B9B0F2-C6B4-4CCD-B21F-759CF546E68D}.rpt:

Unable to connect: incorrect log on parameters.

The database login parameters are held in the web.config file, I have changed these accordingly i.e (i have removed the actual details out)

<add key="CRServerName" value="server"></add>

<add key="CRDatabaseName" value="database"></add>

<add key="CRUserID" value="usename"></add>

<add key="CRPassword" value="password"></add>

The code remains unchanged for 2 years, that is:

#region Set Crystal Reports database

CrystalDecisions.Shared.ConnectionInfo conn = new CrystalDecisions.Shared.ConnectionInfo();

conn.ServerName = ConfigurationManager.AppSettings["CRServerName"].ToString();

conn.DatabaseName = ConfigurationManager.AppSettings["CRDatabaseName"].ToString();

conn.UserID = ConfigurationManager.AppSettings["CRUserID"].ToString();

conn.Password = ConfigurationManager.AppSettings["CRPassword"].ToString();

CrystalDecisions.CrystalReports.Engine.Tables tables = crptReport.Database.Tables;

CrystalDecisions.Shared.TableLogOnInfos tablelogininfos;

CrystalDecisions.Shared.TableLogOnInfo tablelogininfo;

foreach (CrystalDecisions.CrystalReports.Engine.Table table in tables)

{

tablelogininfo = table.LogOnInfo;

tablelogininfo.ConnectionInfo = conn;

table.ApplyLogOnInfo(tablelogininfo);

table.Location = conn.DatabaseName + ".dbo." + table.Location.Substring(table.Location.LastIndexOf(".") + 1);

#endregion

So the only difference is the server from 2003 small business server has been upgraded to 2008 small business server.

Does, has anyone had some experience here? I changed the web.config details to use the sa database password, no difference.

Is this a permissions thing? Our new server is called 'sql' would this make a difference (that is is a keyword in sql).

Any help is appreciated!

Best

Matt

Accepted Solutions (1)

Accepted Solutions (1)

former_member188030
Active Contributor
0 Kudos

Hello,

Please provide,

Version of crystal reports with detailed patch level.

Visual Studio version.

Is the Win 2008 server running on 32 bit or 64 bit mode?

Thanks,

Bhushan.

Former Member
0 Kudos

Hi

I am using Visual Studio 2010, set to use the .net framework 3.5.

I am using cr2008sp2 (Crystal Reports 2008 runtime service pack 2).

Please let me know if you need anymore information and thank you for your help so far.

Best

Matt

Former Member
0 Kudos

Hi ,

Sorry the website through the application pool is running in 32 mode, this is the only 32 mode I know about.

Best

Matt

former_member183750
Active Contributor
0 Kudos

See if the article [Troubleshooting Guide to Database Connectivity Issues with Crystal Reports in Visual Studio .NET Applications|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b0225775-88c4-2c10-bd80-8298769293de] will help in troubleshooting this issue.

Ludek

Follow us on Twitter http://twitter.com/SAPCRNetSup

Former Member
0 Kudos

Solved.

On the 2003 server I had Crystal Reports 2008 (full product) installed and I had Crystal Reports basic for visual studio 2008.

This worked on the 2003 small business server.

On the 2008 business server I installed Crystal Reports 2008 (full product) and the 2008 Crystal Reports runtime service pack 2 ( Crystal Reports basic for visual studio 2008 will not install on the 2008 small business server).

This didnu2019t work.

It only works if you uninstall the full edition and just put the runtime (service pack 2) onu2026.

Weird.

Matt

Answers (0)