Unable to establish file routing for Azure in AJO
When setting up file routing for delivery management (DM) output files from ÃÛ¶¹ÊÓƵ Journey Optimizer (AJO) to Azure, an error occurs due to incorrect configuration of the Azure connection string and container.
Description description
Environment
ÃÛ¶¹ÊÓƵ Journey Optimizer (AJO)
Issue/Symptoms
Attempts to produce an output file result in errors.
You may receive an error message like this, indicating a misconfiguration in the container and filename fields:
An error has occurred when exporting data to the destination. The data export with the flowId=AJO-XXXXX-762d-XXXX-aa15-ca34aa576721 segmentId=xxxx:9b7df1b7-dc0d-xxxx-a6e6-ee01fd5364bb flowRunId=not-set parameters was unable to be completed. The error message returned by the wasbs destination is Cannot initialize WASB file system, URI authority not recognized. Please contact customer support if the problem persists.
Resolution resolution
To resolve the issue of establishing file routing from ÃÛ¶¹ÊÓƵ Journey Optimizer to Azure, follow these steps:
-
Ensure you have a valid connection string and container information from your Azure service provider.
-
Verify that the connection string is correctly formatted according to Azure’s specifications. It typically includes:
- Account name
- Account key
- Endpoint suffix
-
Confirm the specified container exists in your Azure storage account and has appropriate permissions set for access.
-
Input the correct connection string into the configuration settings of AJOÂ for DM file routing.
-
Specify the correct container name within AJO settings where output files should be routed. To specify sub-folders, enter the container name only (for example, landing) and prepend
'/subfolder/'in the direct mail Filename field (for example,'/aep/<filename>'). -
Test the configuration by attempting to route a test file from AJO to ensure there are no errors in transmission.