Product

Kodak^® InSite^™ Creative Workflow, Asset Library, and Variable Data Print, all versions

Platform

Mac or PC

Operating system

Apple^® Mac OS^® X or Microsoft^® Windows^®

Symptoms

There are two possible symptoms.

First, the transfer progress window displays the following message after bytes are transferred:
A fatal error occurred during the file transfer.

Second, in a Web browser, the transfer progress window indicates that files were transferred and lists the number of bytes sent, and the Close button appears. However, when you click Close and the server processing status window opens, the progress bar never goes beyond 0%. The transfer may or may not time out. No elements appear in the upload location. Upload history indicates that the upload failed.

Cause

Upload automation rules may be failing to execute.

On a Windows 2000 system (InSite Creative 3.0.3 or earlier), you can verify whether automation rules are the problem by performing the following procedure.

The verification steps cannot be used on a Windows 2003 system (InSite Creative 3.0.4 or later). If you are on a Windows 2003 system, there is no easy way to verify that automation rules are the problem. In this case, we suggest that you skip the verification steps in the Cause section and go directly to the solution in the Solution section below to see if that solves the problem.

To verify whether automation rules are the problem (Windows 2000 systems only):

1. Ensure that the TwEm service is running (or at least AutomationApp.exe).
2. On the server (or another computer from which you can access the server), open a Web browser window and go to http://<servername>:61235/AutomationStatus/
   ActiveRules.aspx

If the automation rules are okay, the Web page looks something like:

However, there is a problem with the automation rules if the Web page does not list any of the rule sets, or the page looks something like:

If the automation rules are okay, then this is not the cause of the upload problem. Check the other Creative Workflow/Asset Library/Variable Data Print troubleshooting items for other possible causes.

Solution

Once you have verified that the automation rules are the cause of the problem (or you were unable to verify the cause because you are on a Windows 2003 system), complete the following procedure to fix the problem. The procedure is fairly complex, so you may want to contact product development for assistance in completing it.

1. On the server, open a command prompt window.
2. Stop the TwAm and W3src services by typing the following:
   net stop twam & net stop w3svc
3. Ensure that the AutomationApp.exe process is not running. (It shouldn't be if the TwEm service is stopped.) If it is running, end the process from Task Manager.
4. Delete the contents of the automation tables by typing the following:
   sqlplus prinergy/araxi
    -- Empty all AUT tables except for AUT_RULESETFOLDER --
    delete from AUT_PERSISTEDACTION;
    delete from AUT_PERSISTEDEVENT;
    delete from AUT_RULE;
    delete from AUT_RULESETACTIVATION;
    delete from AUT_RULESET;
    commit;
5. Change the default location to the location of the rulesets by typing the following:
   cd \creo\twam\data\RuleSets
6. Run the following executable from the default location in step 5 by typing:
   \Creo\twam\Automation\bin\RuleUtility.exe
7. When the utility starts, type the following at the utility command prompts:
   list (no rules should be present)
   import * (rules should import)
   list (rules should now be listed)
   quit
8. Open a new command prompt window and type the following commands, one at a time, to reactivate the rule set:
1. cd \creo\twam\setup\config\sql\insite\tw\
   RuleEngineSqlScripts
2. sqlplus prinergy/araxi
3. @TW_RuleSetActivation.sql
9. Restart the TwEm service, wait for AutomationApp.exe to start, and check that the rule sets are active (following the procedure described in the Cause section above).

Technical contact

Brian Laberge

Submitted by

Brian Laberge

Date submitted

03 Apr 2008