After Applying 24.1 Monthly Update Siebel Asynch Migration Failing At Unpackage Step With Errors "Could not unpackage the zip file due to Access is denied due to invalid credentials or insufficient privilege"
(Doc ID 3020336.1)
Last updated on MAY 01, 2024
Applies to:
Siebel CRM - Version 24.1 and laterInformation in this document applies to any platform.
Symptoms
Siebel Asynch Migration failed after applying 24.1 at the UnPackage step and the following errors are observed on the mentioned log files located under $SAI_HOME/applicationcontainer_external/logs
- migration.log
[DEBUG] 2024-04-24 15:40:41.422 [https-jsse-nio-444-exec-9] Migration - com.siebel.migration.server.MigrationUtility:InvokeRestCall Response received from RST URL: https://AIHost:444/siebel/v1.0/service/ExecutionDataService/Delete
[DEBUG] 2024-04-24 15:40:41.422 [https-jsse-nio-444-exec-9] Migration - com.siebel.migration.server.MigrationUtility:InvokeRestCall Response from Server: {"SiebelMessage":{"IntObjectFormat":"Siebel Hierarchical","MessageId":"","IntObjectName":"Transaction","MessageType":"Integration Object","Transaction":{"status":"Running","Id":"1-22ZQ37L","mgPlanName":"AJSTAGERRFull-POC","mgPlanId":"1-1QU3LEA","TransactionResource":{"seq_num":"6","Id":"1-22ZQ37O","resName":"Migration Application Workspace Data Service","status":"Not Started","endTime":"","loglocation":"https:\/\/ajtmstgwvsai51.cvp.cs:444\/siebel\/v1.0","txnId":"1-22ZQ37L","stDate":"","operationName":"SeedCopyImport","resType":"DB Util","trackingId":"","resId":"1-1QU3LED"}}}}
[TRACE] 2024-04-24 15:40:41.422 [https-jsse-nio-444-exec-9] Migration - com.siebel.migration.server.MigrationServer:doPost Output message: {"status":"error","msg":"Could not unpackage the zip file due to Access is denied due to invalid credentials or insufficient privilege."}
- commonlogger.log
The issue can be reproduced at will with the following steps:
1. Login to Migration Application
2. Navigate to Execution tab and select migration plan and click execute
3. Provide the package zip file(Export zip file copied from Source environment) name and click ok.
4. Unpackage failed with above reported errors
Changes
Applied 24.1 monthly update on top of 22.12
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |