Troubleshooting

Listed below are some of the more common issues that you may encounter during your Studio installation.

When Problem Possible cause Corrective action
Installation Cannot install Studio. When you click the msi file, you see a message saying that the system administrator has set policies to prevent installation. User performing the installation does not belong to the Administrator group on the machine. Add user to the Administrator group on that machine.
Configuration Unable to configure the Database using the Studio Database Configuration application. User does not have the necessary privileges. Refer to Creating the Studio database or Changing the database access account in this document.
Connecting to SAP Unable to create a connection to SAP. SAP .net Connector 3.0 DLLs are missing from the Studio installation folder
  • Ensure that your SAP connector is the same bit version as your Studio installation.
  • Studio must be installed as an administrator.
  • Verify that sapnco.dll and sapnco_utils.dll exist at [Install Path]\Infor Risk & Compliance Studio. If not, copy these dll’s from SAP installed folder on your Studio machine to [Install Path]\Infor Risk & Compliance Studio.
  • Right click studio.exe at [Install Path]\Infor Risk & Compliance Studio and select Run as administrator
Connecting to an Oracle Database. Unable to create a connection to an Oracle Database. Missing or wrong client software or configuration settings. Verify that Oracle 11g client R2 is installed and that it is the same bit version as your Studio.

Verify that your tnsnames.ora file has the necessary database definition in place.

Connecting to a DB2 Database.

Unable to create a connection to a DB2 Database.

Missing or wrong client software. Verify that the DB2 Client is installed and that it is the same bit version as your Studio.
Publishing Insight on split servers as well as single server. Application displays an error message - Unable to retrieve the CDM tables for this project Lack of permission on the logged in user folder Share the logged in user folder (C:\user\logged in user) and provide read and write permission to the folder.

Users publishing Insights must have permission to Infor Risk & Compliance and Studio install path. After providing the permissions, the Application Server is authenticated successfully.

Publishing Process Insight on a single server Application displays an error message - 'Infor Risk & Compliance studio was unable to determine if there is enough disk space to publish to the Application server. Please verify this user has Administrator access to the application server'. The webserver name on the PI_CONFIG table in the IRC database is without FQN. Run this query to identify the same.

select * FROM PI_CONFIG WHERE [DESCRIPTION] = 'WebServer'

Update the webserver name with the FQN.

Sample query UPDATE PI_CONFIG SET STRING_VALUE =[webserver name with FQN] WHERE [DESCRIPTION] = 'WebServer'

Publishing Insight on the IRC server Insight publish fails with an error message - Publish failed - Root element is missing. Global search name for an object is selected in the Destination Table Detail but the Full Text is not selected for any column of the same object. Full Text for an object column must be selected if the Global search name is selected in the Destination Table Detail.
Republishing Lawson Payroll Insight , from an earlier version, on the IRC server Republishing fails with an error message - Error processing Global Search ... Modification of the Insight column length for the Infor_Payroll_ Law10_ EMACHDEPST table. Drop the full text index on the same table before republishing.
Process Insight publish task, from Studio, is in progress and you are logging into Infor Risk & Compliance. The Infor Risk & Compliance log-in page displays the maintenance screen. Studio application closed through Task Manager. Remove the file app_offline.htm from Infor Risk & Compliance [Install Path]\BizRightsPresentation folder.
Creating Package

Error encountered while merging the SAP specific code into the Insight package

Permission not provided to the user Ensure full permission is provided to the user. Once the permissions are updated, re-create the package. For details on providing permissions, see Creating the Studio database.
Uninstall Studio. Displays a message that the database should be deleted manually Database is not accessible. Remove database manually.