If you encounter issues during or directly after the replication of Perceptive Content from your production environment to the test environment, review this table for the steps to resolve the issue.
| Issue | Cause | Resolution |
|---|---|---|
| Services do not start or you receive a license error. | License issues occur after the production database is copied to test. | In the Perceptive Content database, delete all IN_LIC files. Then, apply the test environment licenses. |
| Services start but stop after 60 minutes. | The ODBC DSN and inow.ini are not configured to point to the test
database. The PERCEPTIVE CONTENT database was copied from the production environment to the test environment without creating the inuser account in the external DBMS. |
In the [ODBC] section of inserver/etc/inow.ini, change the odbc.dsn
setting to point to the test server database. Follow the instructions in this document to make a copy of your PERCEPTIVE CONTENT database and verify the inuser account. |
| Users cannot connect to the test environment. | A firewall is blocking port 6000. | Open port 6000 on the firewall for the test server. |
| iScripts are not working. | iScript files point to an incorrect location after being copied to test | Edit all iScripts referencing a drive letter. |
| A Scheduled Task was not created correctly after being copied to test. | Create Windows Scheduled Tasks to initiate BAT files. | |
| BAT files point to incorrect location after being copied to test | Edit all BAT files to point to correct script location. | |
| Images do not open. | OSM pointers are not synchronous with file structure during the copy from production to test. | Verify that the location of your OSM is correct. |
| Verify that the location of your OSM is correct. | Possible issues include: Perceptive Manager account did not exist in test database. Port 6000 is not enabled for test server. User is applying licenses with an account other than Perceptive Manager. inserver service is not running on the test server. |
To resolve the issue complete the following steps.
|
| Services not functioning properly | DEP is not set on Windows 2003 test server. | Refer to the “Change the DEP setting” section of this document. |
| Perceptive Content Client works against production server, but not the test server. | A different version of the Perceptive Content Server is installed in the test environment compared to the version in production. | Re-run the server installation on the test server and then verify that the test environment has the same version of Perceptive Content agents and extensions as well. |
| The Perceptive Content Server service is unable to log in to the database on the test server. | Inuser does not have sufficient privileges on the test PERCEPTIVE CONTENT database. | Grant inuser the dbo role for PERCEPTIVE CONTENT database. |
| Search or workflow performance is slow. | The database timestamp parameters are not set correctly for Oracle. | Apply the correct timestamp parameters on the Oracle test database instance as listed in the Perceptive Content Installation Guide. |
| Users cannot log in to Perceptive Content Client against test server. | Perceptive Content users must have the following Windows user rights on test server: Allow log on locally Access this computer from the network | Grant those Windows user rights within Local Security Policy or at the Windows Group Policy level. |