Troubleshooting tips

Problem description	Solution
The component does not generate an output file. Status Monitor displays the following message: Worldox failed to initialize API. Error: Operation failed.	The component service may not have connection to WORLDOX system. If you used the Specify user code connection method in the General tab, the entered user code may be incorrect. Check it and enter correct user code. Click the Reconnect button to make sure that the connection was successful. If you used the System user method, your system login name may not belong to a Worldox user codes list. Contact your WORLDOX administrator or try another connection method.
Status monitor displays the correct operation of the component but there are no files in the output directory.	Maybe data validation has failed and output file has been rejected. The field length of some profile field may be incorrect. Check if the profile field values in the Document Profile settings have a proper length.
"Parent-child" relations are not set when you use the option.	The specified number of the parent document may be out-of-bounds. It means that its absolute value exceeds the number of input documents. Enter the correct parent document number.
"Parent-child" relations are not set when you use the Set another document as parent option on the Document Relations tab.	The parent file is the same as the child file. Use another file as a parent. If the Set relation only if parent exists option is off, and the selected file does not exist in the specified folder, place the selected file into the specified folder, and the component will set relationship. If the Set relation only if parent exists option is on, and the selected file does not exist in the specified folder, the relation cannot be set. Use an existing file in the folder as a parent.
The document profile parameters determined with the use of RRTs are empty or not replaced.	Maybe you used profile group specific RRTs for document profile parameters determination and the Profile group specified on the General tab was determined with the For output folder method. You may use these RRTs for document profile settings only if the Profile group is determined by the Specify identifier method. Change the profile group determination method or do not use these RRTs inside the settings on the Document Profile tab.
Add as new version option on the General tab is on, but the new version of the output file does not occur in the output folder.	Probably there are already 15 versions in the output folder; thus WORLDOX limitation has been exceeded. Specify another output file name.
No file is placed into the output directory. Status monitor displays the following message: Worldox failed to copy file name to ... Error returned: destination file already exists, where name is output file name with the path.	Maybe the file with the same name already exists in output directory and neither the Replace existing file, nor the Add as new version options on the General tab is selected. Select one of the options.
When you send files to WORLDOX, the Status Monitor shows the following message: Worldox failed to set document profile. Error returned: Cannot get first item in the list. The file is rejected.	There are two possible causes of this problem: You try to send files with a .tmp extension. This extension is related to the internal WORLDOX file format; therefore, files with this extension cannot be processed correctly. Try to change the file extension. You don't have write permission for directory. For example, if you try to send a file with the XNAMEIDX.CRS name, then you will get this error, because this is a system file and you don't have permissions for overwriting the existing XNAMEIDX.CRS file.
When you try to send files to the server, the Status Monitor shows the following error message: Error WORLDOX eConnector: Worldox failed to copy file path to ... Error returned: The file is secured from being checked-out or not checked-out to be checked-id.	The possible reason of this error is that you do not have rights for the current directory or the root directory. To fix the problem, try to run the workflow server (batch.exe) as a local administrator account or as a user that has sufficient rights on the server.
~WRC::ProfileFolder~ RRT fails to be generated or is generated incorrectly. For example, if ~WRC::BaseFolder~ is Y:\ and the profile has two subdirectory fields: FLD13 and FLD23, then the ~WRC::ProfileFolder~ is replaced with Y:\ instead of Y:\FLD13\FLD23\. This behavior has irregular nature and depends on background programs running, set of input files, and so on.	This problem is connected with WORLDOX API software instability. To improve stability of WORLDOX API it is recommended to make sure that there are no viruses in the system and remove all background file scanners; that is, indexing services, real time virus scanner, and so on. However in some situations this does not help. To avoid this problem do not use ~WRC::ProfileFolder~ RRT in the Output folder field on the General tab. Instead this field should contain manually-formed output path. For example, if the selected profile contains two subfolder fields FLD13 and FLD23, then the output folder should contain ~WRC::BaseFolder~FLD13\FLD23. Although this will not prevent warnings about ~WRC::ProfileFolder~ RRT, all documents will be processed correctly.
Sometimes, when the component configuration dialog opens, the component service window hides under another window.	This problem is not critical and is related to the RRT window that is displayed before the component configuration dialog. The problem can be resolved by minimizing another window.
When network connection to the WORLDOX GX server is broken during processing, after restoration the component refuses to process files and writes error messages into the log. Windows displays error messages about failure of WAAPI.EXE or Worldox API Controller.	The problem is related to the WORLDOX GX API unstable work in case of network connection failures. Depending on the operating system and workflow environment, one of the following workarounds can be used to avoid this issue: The Workflow service is running while the user logs on the machine. In this case it is recommended to permanently have WORLDOX client software running on the machine. This approach does not necessarily resolve the issue if the Workflow service is running on Windows 2000. The Workflow service is running while there are no users logged on the machine. If the operating system on the workflow machine is Windows XP or Windows 2003, it is recommended to disable error reporting and notifications about critical errors (on the Control Panel->System->Advanced tab->Error Reporting dialog). No recommendations can be given in case of Windows 2000, though the correct processing is usually restored after 5-10 minutes.
When you use the Auto name option on the General tab, the file is not placed into the output directory and the Status Monitor shows the following message: Worldox failed to produce automatic file name for the output directory path. Error returned: Operation failed, where path is the output folder path.	WORLDOX software may be configured incorrectly to produce auto name for the routed file. Apply to WORLDOX administrator or use the Rename file option instead of the Auto name option.
Status monitor shows the following message: Worldox failed to copy file name to ... Error returned: Operation failed. The file is not placed to output folder or placed with incorrect profile.	There may be a problem with the output folder, for example, the place limit may be exhausted. If the file size is rather big, the reason may be in WORLDOX API feature that concerns copying files of a size about 600Mb and larger. In this case the file profile is not created correctly even if the file is correctly copied. Try to decrease the size of the file.