Product

• Kodak^® InSite^™ Creative Worklow and Kodak InSite Asset Library 3.0
• Kodak TeamWorks and Kodak EyeMedia 2.1.x

Platform

PC

Operating system

Symptoms

After a Kodak Prinergy^® 4.0 upgrade in an integrated system that includes Kodak InSite/Kodak InSite Prepress Portal and Creative Workflow/Asset Library (or Teamworks/EyeMedia), the Creative Workflow/TeamWorks server can no longer connect to the Prinergy database to sync up the customer and user database. This is evident in that no users created in Prinergy or InSite/Prepress Portal are available in Creative Workflow/Asset Library (or TeamWorks/EyeMedia).

Cause

The server needs an entry in its tnsnames.ora file so that it can connect to the Prinergy database through a database link. The SERVICE_NAME for the Prinergy database as identified in this file changed from CreoDb in Prinergy 3.x to AraxiDb in Prinergy 4.0. So, if a customer has upgraded to Prinergy 4.0, the Creative Workflow/TeamWorks server needs to know to connect to the Prinergy database using the new SERVICE_NAME.

Solution

To verify that this is indeed the problem, run the following two SQL commands in a command prompt window on the Creative Workflow/TeamWorks server:

sqlplus prinergy/araxi
SQL> select count(*) from dbcs_remoteuser@prinergydbserver;

If the following error is reported,

select count(*) from dbcs_remoteuser@prinergydbserver
*
ERROR at line 1:
ORA-12514: TNS:listener could not resolve SERVICE_NAME given in connect descriptor

then you have confirmed that this is the problem.

There are two ways to fix the problem:

1. Rerun the Creative Workflow/TeamWorks installer with any build later than 2.1.1.930. The installer will check the Prinergy server registry, detect the presence of Prinergy 4.0, and adjust the SERVICE_NAME entry accordingly.
2. Rerun the Configure Server Utility (the utility used to integrate a Prinergy, InSite/Prepress Portal and Creative Workflow/TeamWorks server together). You can find this utility in Programs > Kodak Twem > Teamworks Config App > Configure Server. Rerunning this utility will check the Prinergy server registry, detect the presence of Prinergy 4.0, and adjust the SERVICE_NAME entry accordingly.

Technical contact

Brian Laberge

Submitted by

Brian Laberge

Date submitted

12 Feb 2007