ILA: Issue while installing Workspace ONE Access Content Pack

[Ashwini-Ravi]

Code of Conduct

• I have read and agree to the Code of Conduct.
• Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

VMware Cloud Foundation

5.1

Module Version

2.9.0.1047

PowerShell Version

7.3.6

PowerCLI Version

13.1.0.21624340

PowerVCF Version

2.4.1.1000

Guest Operating System

windows server 2019

Environment Details

No response

Description

Issue while running Invoke-ILAdeployment at step Install Workspace ONE Access Content Pack�

Error or Debug Output

[INFO] Install Workspace ONE Access Content Pack�

[INFO] Error at Script Line 15391�[0m

[INFO] Relevant Command: $response = Invoke-RestMethod -Method 'GET' -Uri $Uri -Headers $ghHeaders

[INFO] Error Message: Cannot validate argument on parameter 'Uri'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again.�

[ERROR] Exception calling "FromBase64String" with "1" argument(s): "The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters."�

Expected Behavior

There should not any errors while running Invoke-ILAdeployment

Actual Behavior

Error while installing Workspace ONE Access Content Pack�

Steps to Reproduce

Run Invoke-ILAdeployment and it will fail at step Install Workspace ONE Access Content Pack�

Log Fragments and Files

No response

Screenshots

No response

References

No response

[tenthirtyam]

Can you test the function to install the content pack directly to see if it fails?

[github-actions]

I'm going to lock this issue because it has been closed for 30 days. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.