Thursday, April 12, 2012

Batch aborts with message Error! Setting State.XML / Couldn't initiate log file: Access is denied. in IBM Datacap Taskmaster Capture


Batch aborts with message Error!


Setting State.XML / Couldn't initiate log file: Access is


denied. in IBM Datacap Taskmaster Capture


Abstract


Batch aborts with message "Error! Setting State.XML / Couldn't initiate log file: Access is denied." in IBM Datacap Taskmaster Capture

Symptom




When running Taskmaster Client or Taskmaster Client Service, the task log contains the following or similar error message:

Error! Setting State.XML

Couldn't initiate log file: Access is denied.


Cause




This is caused by IBM DatacapTaskmaster Capture attempting to create the interbatch or "WRRS" log. Either the destination folder was momentarily unavailable, or the account running the rules does not have proper permissions to it.


Resolving the problem




Check network security permissions for the account running rules or disable interbatch or "WRRS" logging as noted in the IBM Document::







Suppressing interbatch or WRRS logs in IBM Datacap Taskmaster Capture


http://www-01.ibm.com/support/docview.wss?uid=swg21578728

  • In Taskmaster 8.0.0 and later the location for WRRS logs defaults to the local \Datacap\RRS\Logs folder, but this path can be adjusted through the system registry.
      See registry key HKEY_LOCAL_MACHINE\SOFTWARE\Datacap\RRS\Locations (REG_SZ) RRS for the root RRS folder location; the folder in which WRRS logs are created will be specified by the secondary registry key (REG_SZ) Logs, which defaults to be relative to the RRS folder.


  • In Taskmaster 7.6 and earlier the location for WRRS logs usually points to the \Datacap\RRS folder on the Taskmaster Server in a distributed environment.
      See registry key HKEY_LOCAL_MACHINE\SOFTWARE\Datacap\RRS\Locations (REG_SZ) RRS for the WRRS folder location. This path cannot be adjusted without also altering the location of application rules to be loaded by the client machine; in distributed environments it is not practical to maintain multiple copies of application rules.



Note: Reprocessing the batch may succeed if the abort is caused by intermittent network connectivity problems.


 


No comments:

Post a Comment