SQL Server 2005 Crystal Report is unable to connect: Incorrect log on parameters

Posted on 2014-01-30
Last Modified: 2014-02-02
Hey guys,

I have about 10 crystal reports that I created in VS 2008 C# version of Crystal Reports.  I have a code snippet attached that I run 5 reports by only changing the report name.  They use the same stored procedure and the same code except for the report name.  Two of the reports give the error:  Unable to connect: Incorrect log on parameters.

There must be something wrong with the reports but they work perfectly when run in the Main Report Preview.
Question by:JDL129
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 2
LVL 100

Assisted Solution

mlmcc earned 250 total points
ID: 39823252
What version of Crystal?
By the code I am guessing it is CR9

Do the 2 reports that fail have a subreport?


Author Comment

ID: 39824316
mlmcc!!!  Thanks for the post!!

They were all built with whatever CR comes with VS2008 C#.
No subreport on any of the 5 reports.  I can just change the report name in the code and three will run correctly and two of them won't.  They all have the same data source which is a stored procedure in sql server 2005.

LVL 100

Accepted Solution

mlmcc earned 250 total points
ID: 39824392
Can you open the reports in the designer and try a VERIFY DATABASE?

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!


Author Comment

ID: 39824579

Yes, and it shows all the data when I run it in the designer mode.  I am creating a new stored procedure.  Maybe I just missed a field in the one I am currently using.

Thanks for your assistance!!!!!!!!!!  Keep thinking!!!!


Author Comment

ID: 39824681

I created a new stored procedure and created a new label but am still getting the same error.
I changed the name of the report to one that works and it still does.  The only thing different in the procedure is the report name.  :-(

Keep Thinking!!!


Author Closing Comment

ID: 39827813

What I did to create the report was to replace the fields on a report that was working with the new ones I needed.  I haven't a clue why that would work and the new ones wouldn't.
Thanks for the assist!!!

Featured Post

Revamp Your Training Process

Drastically shorten your training time with WalkMe's advanced online training solution that Guides your trainees to action.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article introduced a TextBox that supports transparent background.   Introduction TextBox is the most widely used control component in GUI design. Most GUI controls do not support transparent background and more or less do not have the…
Calculating holidays and working days is a function that is often needed yet it is not one found within the Framework. This article presents one approach to building a working-day calculator for use in .NET.
I've attached the XLSM Excel spreadsheet I used in the video and also text files containing the macros used below.…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

710 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question