Skip to main content

Report Viewer - Unable to generate Module Productivity Report "Database logon failed" for Oracle Database

Article # 3035228 - Page views: 266


When customer with an Oracle 12c Database are unable to retrieve any standard Kofax Reports via Report Viewer.

Error message found in the ERR_YYMM.txt logs are similar to TFS 55533 which was for SQL Server (Fixed in KC

2021-09-28 16:34:22, 0x00000018, 0x00000000, 0x00000069, 0x80131500, 0x00000000, C:\Kofax\CaptureSS\ServLib\Bin, ReportViewer, PRIMARY:Sess 2, 11.0.646.0, ShowReportError at offset 157 in file:line:column <filename unknown>:0:0
, 0, Unable to generate System Status Report.CrystalDecisions.CrystalReports.Engine.LogOnException: Database logon failed. ---> System.Runtime.InteropServices.COMException: Database logon failed.   at CrystalDecisions.ReportAppServer.Controllers.ReportSourceClass.GetLastPageNumber(RequestContext pRequestContext)   at CrystalDecisions.ReportSource.EromReportSourceBase.GetLastPageNumber(ReportPageRequestContext reqContext)   --- End of inner exception stack trace ---   at Kofax.AscentCapture.ReportViewer.ReportViewerForm.ShowReport(), ,


This is a known TFS Bug 1102650 which was fixed in KC

Add the following tag to ACConfig.xml to enable ReportViewer to use Ole DB Provider for Oracle
      instead of ODBC Provider:
          <ReportViewer UseOleDbForOracle="1"/>
 The default value of UseOleDbForOracle is "0".

Level of Complexity 



Applies to  

Product Version Build Environment Hardware
KC 11.0 11.0      


Add any references to other internal or external articles


Article # 3035228