KB Articles

KB Article # 10023

Topic/Category: Advanced Reporting

Ephesoft Version: 4x

Issue: Reporting: Logi Debugger Trace Report : Invalid Object Name Not Working

2015-09-24

Analysis:

Installation most likely not performed properly. Issue may be fixed by dropping Report table and recreating.

 

Solution:
1.  Backup than when ready, Drop Report table.

 

2.  Recreate the databases with the following queries depending if you are using a mssql or mysql server. Check the queries to insure the database names are appropriate to step 1. The queries also have a credentials creation and association step. Depending on the db admins policies, you may or may not want to use these lines. The query will error out on these lines if the user credentials already exist on the system – this is ok if you understand this. Once the databases have been verified as created, verify that the previous credentials noted in step 1 are reassociated and/or recreated.

{path}\Ephesoft\Dependencies\MsSQLSetup\ephesoft-mssql-config.sql
{path}\Ephesoft\Dependencies\MySQLSetup\ephesoft-mysql-config.sql

 

3.  Rename the serialized (*.ser) files so that database setup procedures can be performed{path}\Ephesoft\SharedFolders\database-update

 

BatchClassUpdate.ser-executed to BatchClassUpdate.ser
DependencyUpdate.ser-executed to DependencyUpdate.ser
PluginConfigUpdate.ser-executed to PluginConfigUpdate.ser
PluginUpdate.ser-executed to PluginUpdate.ser
ScannerConfigUpdate.ser-executed to ScannerConfigUpdate.ser

 

4.  Change configuration flags so that database setup procedures can be performed

 

{path}\Ephesoft\Application\WEB-INF\classes\META-INF\dcma-data-access\dcma-db.properties
upgradePatch.enable=true

{path}\Ephesoft\Application\WEB-INF\classes\META-INF\dcma-workflows\dcma-workflows.properties
workflow.deploy=true

 

 

 5.  Start Server

 

< Back|KB Main Page | Next KB Article >

Was this article helpful to you?

Walter Lee