ReportDebug.txt Error Table Could Not Be Found

ReportDebug.txt Error Table Could Not Be Found

In Fusion Servicing Director, you will receive the following error if your Customer Self-Service web applications is denied access to the table or view listed in the error:
After GetReportLoc Before load 
After load 
C:\inetpub\wwwroot\ILSWebBus\rpt\Periodic_Statement.rpt
After GetReportLoc 
Before export CrystalDecisions.CrystalReports.Engine.DataSourceException: The table 'R_<view name here>' could not be found.

Workaround:

Reset the SQL logins using the Customer Self-Service specific W_FixRights SQL procedure, which will grant the required access. Review the related article for more information.

ArticleNumber:

000044565

    • Related Articles

    • Servicing Director Posting.txt File For UltraData Warning Error

      warning duplicate G/L posting .txt file ! do you wish to continue ? 'Y/N' Root Cause: You have created a Servicing Director Posting.txt file, uploaded it to your UltraData host server, and when using UltraFis to run CU437 and import the file, you get ...

    • Servicing Director Customer Self-Service ReportDebug.txt Error: "...UFL 'u2lserv.dll' that implements this function is missing..."

      fter GetReportLoc Before load After load C:\inetpub\wwwroot\ILSWebBus\rpt\<YourDocument>.rpt After GetReportLoc Before export CrystalDecisions.CrystalReports.Engine.FormulaException: UFL 'u2lserv.dll' that implements this function is missing. Error ...

    • Runtime Error 53 File Not Found

      During an update, you received the following error: Runtime Error 53 File Not Found Root Cause: During the update process the file names for EZTELLERENT.EXE OR EZSUPERENT.EXE changed to EZTELL~.EXE or EZSUP~.EXE. Fusion EZTeller cannot read the ...

    • Error BOServer: File Not Found

      BOServer: File note found (C:\Program Files (x86)\D+H\Servicing Director\BussObj\[file name].cbo Root Cause: This message appears when you are opening a custom add-on to your Fusion Servicing Director system and your computer does not have the ...

    • Application Error 1706 No Valid Source Could Be Found

      Error 1706. No valid source could be found for product Fusion Servicing Director Application. The Windows Installer cannot continue. The feature you are trying to use is on a network resource that is unavailable. Root Cause: This error can be caused ...