Crystal Report: Cannot Connect Incorrect Registration Settings

Question

When printing a report, the user sometimes has the following error:

  CrystalDecisions.CrystalReports.Engine.LogOnException:  
 Error in File C: \ DOCUME ~ 1 \ carolec \ LOCALS ~ 1 \ Temp \ temp_b117cc2e-c184-4556-a493-e04e6d4126fb {388C2B55-114E-4087-A22D-9289902AFDEB} .rpt:  
 Unable to connect: incorrect log on parameters.  ---> System.Runtime.InteropServices.COMException (0x8004100F): 
 Error in File C: \ DOCUME ~ 1 \ carolec \ LOCALS ~ 1 \ Temp \ temp_b117cc2e-c184-4556-a493-e04e6d4126fb {388C2B55-114E-4087-A22D-9289902AFDEB} .rpt:
 Unable to connect: incorrect log on parameters.
    à CrystalDecisions.ReportAppServer.Controllers.ReportSourceClass.GetLastPageNumber (RequestContext pRequestContext)
    à CrystalDecisions.ReportSource.EromReportSourceBase.GetLastPageNumber (ReportPageRequestContext reqContext)
    --- Fin de la trace de la pile d'exception interne ---
    à CrystalDecisions.ReportAppServer.ConvertDotNetToErom.ThrowDotNetException (Exception e)
    à CrystalDecisions.ReportSource.EromReportSourceBase.GetLastPageNumber (ReportPageRequestContext reqContext)
    à CrystalDecisions.CrystalReports.Engine.FormatEngine.PrintToPrinter (Int32 nCopies, Boolean collated, Int32 startPageN, Int32 endPageN)
    à CrystalDecisions.CrystalReports.Engine.ReportDocument.PrintToPrinter (Int32 nCopies, Boolean collated, Int32 startPageN, Int32 endPageN) 

Any ideas for a solution?

Configuration: C # (2008), WinForm, Crystal Report 10, SQL Server 2008 Express (local)

Answer 1

We did not use Crystal Reports for bits, but in general, an error in the “LogOn Exception” lines may have nothing to do with security at all, Crystal Report errors can be a bit random.

Perhaps this could be a memory error.

Or...

This can be a specific report, for example, in the subheading there may be an attempt to enter the system using the credentials stored in the report, and not the credentials that you transmitted to it through the code; You need to skip all the supporting reports, not just the main report that defines the login information.

I remember this error when I used a workaround to set a dynamic logo for a report (which I pulled from a binary field in another database table), except for a small error in which it pulled out logo data for each data series; After a certain number of rows returned, it died, which led to a similar error.

Answer 2

For those who have the same problem, also check if your Datasource provider of your SQL Native Client report is. If so, this will not work on your Production server, which does not have SQL client installed. It must be "SQLOLEDB" because it runs on machines that do not have the SQL client installed.

For this reason, my report worked on my test server (which had a SQL server client) and did not work on my production server

Answer 3

I have the same problem, but it is resolved.

The problem is connecting odbc. Just install your own SQL driver to add the connection to odbc. Download link https://support.fotoware.com/hc/en-us/articles/208664385-Microsoft-SQL-Native-Client-fails-to-download-during-FotoWeb-setup

Answer 4

If you had a report that worked fine, but then suddenly stopped working ... And you are using SQL Server authentication ... check the password expiration date in the login account. :)