A dollar to anyone with a working solution...

Hello everyone, there are 101+ posts regarding the login exception but
I think mine may be different as I have read through all the posts and
couldn't find a single reference to my issue.

Setup:
I've built a class that exposes a public method which returns a
datatable. I have created a report and set up it's data connection to
point to this compiled class. The report runs great and without issue.

However, I would like to access this report from a web page and so
using the ReportDocument I load the report and try to export it I get
the following error. I am trying to build Reports classes that I can
use for all my reports and have the reports bind to the .dll.

Like I said, the report generates properly when I run just the report,
however, when I try to call the report from a webpage I get this issue.
I'm confused because the .dll should be managing all the login
credentials and simply send back a datatable. I don't understand why
Crystal is trying to play with the login.

Any thoughts? It seems like everyone else is adding the report to the
project. I don't want to do that. I don't want the reports to be part
of the project at all.

Thanks.




CrystalDecisions.CrystalReports.Engine.LogOnException: Logon failed.
Details: mscorlib : File or assembly name AUS.Common.Reports.dll, or
one of its dependencies, was not found. Failed to open a rowset. Error
in File C:\WINNT\TEMP\{8188BFC4-0624-4BF0-9BFC-E7725B25BE0F}.rpt:
Unable to connect: incorrect log on parameters. --->
System.Runtime.InteropServices.COMException (0x8004100F): Logon failed.
Details: mscorlib : File or assembly name AUS.Common.Reports.dll, or
one of its dependencies, was not found. Failed to open a rowset. Error
in File C:\WINNT\TEMP\{8188BFC4-0624-4BF0-9BFC-E7725B25BE0F}.rpt:
Unable to connect: incorrect log on parameters. at
CrystalDecisions.ReportAppServer.Controllers.ReportSourceClass.Export(ExportOptions
pExportOptions, RequestContext pRequestContext) at
CrystalDecisions.ReportSource.EromReportSourceBase.ExportToStream(ExportRequestContext
reqContext) --- End of inner exception stack trace --- at
CrystalDecisions.ReportAppServer.ConvertDotNetToErom.ThrowDotNetException(Exception
e) at
CrystalDecisions.ReportSource.EromReportSourceBase.ExportToStream(ExportRequestContext
reqContext) at
CrystalDecisions.CrystalReports.Engine.FormatEngine.ExportToStream(ExportRequestContext
reqContext) at
CrystalDecisions.CrystalReports.Engine.ReportDocument.y(ExportOptions
1) at
CrystalDecisions.CrystalReports.Engine.ReportDocument.ExportToHttpResponse(ExportOptions
options, HttpResponse response, Boolean asAttachment, String
attachmentName) at
CrystalDecisions.CrystalReports.Engine.ReportDocument.ExportToHttpResponse(ExportFormatType
formatType, HttpResponse response, Boolean asAttachment, String
attachmentName) at WebApplication3.WebForm1.test1() in
c:\inetpub\wwwroot\webapplication3\webform1.aspx.cs:line 55

Hi Stephan,

How does your crystal report bind it's data source? Could
you give more detail info?

Elton Wang
(E-Mail Removed)

>-----Original Message-----
>A dollar to anyone with a working solution...
>
>Hello everyone, there are 101+ posts regarding the login
exception but
>I think mine may be different as I have read through all
the posts and
>couldn't find a single reference to my issue.
>
>Setup:
>I've built a class that exposes a public method which
returns a
>datatable. I have created a report and set up it's data
connection to
>point to this compiled class. The report runs great and
without issue.
>
>However, I would like to access this report from a web
page and so
>using the ReportDocument I load the report and try to
export it I get
>the following error. I am trying to build Reports
classes that I can
>use for all my reports and have the reports bind to
the .dll.
>
>Like I said, the report generates properly when I run
just the report,
>however, when I try to call the report from a webpage I
get this issue.
>I'm confused because the .dll should be managing all the
login
>credentials and simply send back a datatable. I don't
understand why
>Crystal is trying to play with the login.
>
>Any thoughts? It seems like everyone else is adding the
report to the
>project. I don't want to do that. I don't want the
reports to be part
>of the project at all.
>
>Thanks.
>
>
>
>
>CrystalDecisions.CrystalReports.Engine.LogOnException:
Logon failed.
>Details: mscorlib : File or assembly name
AUS.Common.Reports.dll, or
>one of its dependencies, was not found. Failed to open a
rowset. Error
>in File C:\WINNT\TEMP\{8188BFC4-0624-4BF0-9BFC-
E7725B25BE0F}.rpt:
>Unable to connect: incorrect log on parameters. --->
>System.Runtime.InteropServices.COMException (0x8004100F):
Logon failed.
>Details: mscorlib : File or assembly name
AUS.Common.Reports.dll, or
>one of its dependencies, was not found. Failed to open a
rowset. Error
>in File C:\WINNT\TEMP\{8188BFC4-0624-4BF0-9BFC-
E7725B25BE0F}.rpt:
>Unable to connect: incorrect log on parameters. at
>CrystalDecisions.ReportAppServer.Controllers.ReportSourceC
lass.Export(ExportOptions
>pExportOptions, RequestContext pRequestContext) at
>CrystalDecisions.ReportSource.EromReportSourceBase.ExportT
oStream(ExportRequestContext
>reqContext) --- End of inner exception stack trace --- at
>CrystalDecisions.ReportAppServer.ConvertDotNetToErom.Throw
DotNetException(Exception
>e) at
>CrystalDecisions.ReportSource.EromReportSourceBase.ExportT
oStream(ExportRequestContext
>reqContext) at
>CrystalDecisions.CrystalReports.Engine.FormatEngine.Export
ToStream(ExportRequestContext
>reqContext) at
>CrystalDecisions.CrystalReports.Engine.ReportDocument.y
(ExportOptions
>1) at
>CrystalDecisions.CrystalReports.Engine.ReportDocument.Expo
rtToHttpResponse(ExportOptions
>options, HttpResponse response, Boolean asAttachment,
String
>attachmentName) at
>CrystalDecisions.CrystalReports.Engine.ReportDocument.Expo
rtToHttpResponse(ExportFormatType
>formatType, HttpResponse response, Boolean asAttachment,
String
>attachmentName) at WebApplication3.WebForm1.test1() in
>c:\inetpub\wwwroot\webapplication3\webform1.aspx.cs:line
55
>
>.
>