Article - CS409589
Writing context to Azure Blob storage using ESIBlobUtility.writeTextToAzureBlob API failed in Windchill Enterprise System Integration
Modified: 24-Jan-2024
Applies To
- Windchill Enterprise Systems Integration 12.1
Description
- Writing context to Azure Blob storage using ESIBlobUtility.writeTextToAzureBlob(containerName, "Hello"); failed an error message that says 'Signature did not match'
- Failed to verify supported API writeTextToAzureBlob, Method Server reports below error:
wt.system.err wcadmin - (wt.fv.fvResource/17) com.ptc.windchill.objectstorage.azureblob.exception.BlobFileCanNotBeStoredException: Cannot save: Folder is probably full or the write permissions are denied wt.system.err wcadmin - Nested exception is: com.azure.storage.blob.models.BlobStorageException: If you are using a StorageSharedKeyCredential, and the server returned an error message that says 'Signature did not match', you can compare the string to sign with the one generated by the SDK. To log the string to sign, pass in the context key value pair 'Azure-Storage-Log-String-To-Sign': true to the appropriate method call. wt.system.err wcadmin - If you are using a SAS token, and the server returned an error message that says 'Signature did not match', you can compare the string to sign with the one generated by the SDK. To log the string to sign, pass in the context key value pair 'Azure-Storage-Log-String-To-Sign': true to the appropriate generateSas method call. wt.system.err wcadmin - Please remember to disable 'Azure-Storage-Log-String-To-Sign' before going to production as this string can potentially contain PII. wt.system.err wcadmin - Status code 403, "<?xml version="1.0" encoding="utf-8"?><Error><Code>AuthorizationPermissionMismatch</Code><Message>This request is not authorized to perform this operation using this permission.
This is a printer-friendly version of Article 409589 and may be out of date. For the latest version click CS409589