Skip to main content

​
Troubleshooting

​
Workflow Deployment Error

If there were any errors during the workflow deployment process, the Ingestion Pipeline Entity will still be created, but no workflow will be present in the Ingestion container.
  • You can then Edit the Ingestion Pipeline and Deploy it again.
  • From the Connection tab, you can also Edit the Service if needed.

​
Connector Debug Troubleshooting

This section provides instructions to help resolve common issues encountered during connector setup and metadata ingestion in Collate. Below are some of the most frequently observed troubleshooting scenarios.

​
How to Enable Debug Logging for Any Ingestion

To enable debug logging for any ingestion workflow in Collate:
  1. Navigate to Services Go to Settings > Services > Service Type (e.g., Database) in the Collate UI.
  2. Select a Service Choose the specific service for which you want to enable debug logging.
  3. Access Agents Tab Go to the Agents tab and click the three-dot menu on the right-hand side of the ingestion type, and select Edit.
  4. Enable Debug Logging In the configuration dialog, enable the Debug Log option and click Next.
  5. Schedule and Submit Configure the schedule if needed and click Submit to apply the changes.

​
Permission Issues

If you encounter permission-related errors during connector setup or metadata ingestion, ensure that all the prerequisites and access configurations specified for each connector are properly implemented. Refer to the connector-specific documentation to verify the required permissions.

​
SSIS Connector Issues

Learn how to resolve the most common problems in the SSIS connector.

​
No Pipelines Are Ingested

The connector finds no packages in the configured location. The ingestion logs show No .dtsx packages found in the packageConnection storage. Check the following:
  • The bucket, container, or folder in the connection contains .dtsx files. Files inside Visual Studio obj folders are skipped.
  • For S3, the packages are in the first bucket of Bucket Names. The connector reads only that bucket.
  • The packages are not saved with the EncryptAllWithPassword or EncryptAllWithUserKey protection level.

​
Pipelines Are Ingested Without Run History

The SSISDB login can connect but cannot see the catalog objects. Grant the permissions in Requirements > SSISDB Permissions on the SSIS connector page, and run the verification query as the connector’s login.

​
Azure: AuthorizationPermissionMismatch

The App Registration can sign in but has no data role on the container. Assign it Storage Blob Data Reader on the container, as described in Requirements > Azure Blob Storage on the SSIS connector page. The Reader role is not enough. A new role assignment can take up to 10 minutes to take effect.

​
Azure: AuthorizationFailure

The storage account firewall blocks the network that the ingestion runs from. In the storage account, go to Networking > Firewalls and virtual networks and allow that network.

​
Azure: Account Name Is Required to Create Blob Service Client

The Storage Account Name field is empty. Enter the storage account name, without the https:// prefix or the .blob.core.windows.net suffix.

​
Azure: SSIS Azure Blob packageConnection Requires a containerName

The Container Name field is empty. Enter the name of the container that holds the packages.

​
The Ingestion Fails While Listing the Packages

The whole run fails when the connector cannot list the bucket, container, or folder. Common causes are an expired secret or a removed permission. This is deliberate: a run that read nothing would mark every SSIS pipeline ingested before as deleted. Fix the access, then run the ingestion again. A single package file that cannot be read or parsed does not fail the run: it is reported as a failure in the run summary and skipped.

​
A Package Is Skipped as Already Parsed

The logs show Skipping ...: package ... was already parsed from another file. The same package (the same DTSID) exists in more than one place in the location. The connector ingests the first copy in path order. Remove the extra copies if the wrong one is ingested.