Skip to main content
Version: Latest (4.54.0)

FAQ

How can I clean the temporary folders in Xill4?​

To clean the temporary folders in Xill4, you can follow these steps:

  • Delete the contents of the %temp%/xill4/ folder.
  • Delete the contents of the %temp%/xill4-databases/ folder.

What should I do if I encounter certificate issues when connecting to repositories in Xill4?​

If you encounter certificate issues when connecting to repositories in Xill4, try the following solutions:

  • Add a new environment variable called XILL4_TLS_ALLOW_INVALID_CERTIFICATES. Set the value of XILL4_TLS_ALLOW_INVALID_CERTIFICATES to true. This will disable certificate validation.

  • If you are working with the HTTP Request 2 component, the Content Store components or the Mongo Query component, similar settings can be configured in the component itself.

What does the "Component Missing" pop-up mean in Xill4?​

The "Component Missing" pop-up in Xill4 indicates that you are in one of the following scenarios:

  • You are trying to open a flow that was created in a newer version of Xill4 than the one you are currently using. The flow references new components that are not available in your version.
  • You are trying to open a flow that was created in an older version of Xill4 than the one you are currently using. The flow references components that have been deprecated.

How can I identify which components are missing when I encounter the "Component Missing" pop-up in Xill4?​

To identify the missing components when you encounter the "Component Missing" pop-up in Xill4, you can do the following: Open the Xill4 logs and search for messages containing the text "<component> is missing". These messages will indicate the components that are missing.

What can I do to fix the "Component Missing" issue in Xill4?​

To fix the "Component Missing" issue in Xill4, you have two options:

First: Update Xill4 to the latest version. If you are opening a flow based on a flow file, you can find the version used to create it at the end of the file under the xill4_version section. Note that it is not currently possible to determine the version of project files. Then:

  • If the missing component is not directly used by the flow, you can remove it from the flow by editing the project/flow file in a text editor and removing the component from the components key(s).
  • If the component is used in the flow, you also need to remove its instances. You can do this by editing the project/flow file in a text editor and removing the component from the design key(s). Keep in mind that removing the component and its instances will break the flow, and you will need to redesign it.

What does the "Path not allowed" error message mean in Xill4?​

The "Path not allowed" error message in Xill4 indicates that you are trying to access a path that is not allowed. This typically occurs when the path you are trying to access is not configured in the XILL4_WORKDIRS environment variable.

Does running the File source connector in Xill4 alter the last accessed date of a file?​

No, running the File source connector in Xill4 does not alter the last accessed date of a file. The connector is designed to only crawl for file and folder metadata without making any modifications to the file system. However, it is important to note that if you utilize certain accelerators, such as the Calculate Hash accelerator, which calculates a hash based on file contents, the last accessed date may be altered. This behavior is applicable only if the file share has enabled the tracking of last access dates.

How can I access network drives in Xill4?​

To access network drives in Xill4, follow these steps:

  1. Ensure the network drive is accessible from the machine where Xill4 is installed.
  2. Map the network drive in File Explorer:
    • Navigate to Computer > Map network drive in the navigation toolbar.
    • Fill in the Drive and Folder fields accordingly.
    • Ensure that the checkbox for Reconnect at sign-in is checked.
  3. Add the root directory path of the network drive to the XILL4_WORKDIRS environment variable. This variable specifies the directories Xill4 can access.

If you still encounter the "Path not allowed" error message after completing these steps, it may be because the network drives were not mapped with administrator privileges. To map the drives with admin rights, follow these steps:

  1. Open Command Prompt as an administrator.
  2. Run the following command:
  • net use [drive]: "[root directory path]" /USER: "[domain/user]" /PERSISTENT:yes
  • Example:
    • net use Y: "\xillio123\root\directory\EXPORT" /USER: "xillio/test_xillio1" /PERSISTENT:yes
note

That using mapped network drives is not recommended, as they are not always accessible from the Xill4 service. This is due a limitation of how Windows handles mapped network drives for services. Use the UNC path instead.

I am getting a "Error while creating collection: An existing index has the same name as the requested index." error message in Xill4. What should I do?​

This usually occurs after upgrading Xill4 to a newer version. To fix this issue, drop the index that is causing the error and restart Xill4. The index will be recreated automatically.

Windows Defender is blocking Xill4. What should I do?​

This can occur when ASR (Attack Surface Reduction) is enabled in Windows Defender. To fix this issue, you can add Xill4 to the list of exclusions of the ASR by adding it's certificate as an indicator. For more information please refer to this article.