locked
ASP.NET 4 :: An exception of type 'CrystalDecisions.CrystalReports.Engine.LogOnException' occurred and was caught. RRS feed

  • Question

  • User-1301396245 posted

    Hi,

    We've just deployed crystal reports on our qa environment and whenever we try to run the reports it gives following error.

    Timestamp: 4/16/2013 6:09:48 PM
    Message: HandlingInstanceID: 85c297c5-4076-4b29-b8b2-0e289c5ca983
    An exception of type 'CrystalDecisions.CrystalReports.Engine.LogOnException' occurred and was caught.
    -----------------------------------------------------------------------------------------------------
    04/16/2013 18:09:48
    Type : CrystalDecisions.CrystalReports.Engine.LogOnException, CrystalDecisions.Shared, Version=13.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304
    Message : Database logon failed.
    Source : CrystalDecisions.ReportAppServer.DataSetConversion
    Help link :
    ErrorID : LogOnFailed
    Data : System.Collections.ListDictionaryInternal
    TargetSite : Boolean ThrowDotNetException(System.Exception)
    HResult : -2147215360
    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.ExportToStream(ExportOptions options)
    at CrystalDecisions.CrystalReports.Engine.ReportDocument.ExportToStream(ExportFormatType formatType)

    We tried everything but couldn't fix the issue. Can you please help us?

    Thanks,

    Sachin Pawar

    Tuesday, April 16, 2013 2:31 PM

Answers

  • User-1301396245 posted

    Thanks all! The issues was there because SQL Server 2008 Native Client was not installed on the machine. We had installed only required software the production machine. It did not have SQL Management Studio installed on the server and so the native client.

    After reading various blogs, I could figure out it could be sql native client issue.

    Thanks all again. I appreciate your time. Smile

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Friday, April 19, 2013 4:05 PM

All replies