- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
04-16-2025 06:16 PM
Got this error "PVWA inaccessible - Source array was not long enough" while trying to access the PVWA.
Fixed this issue by following the below article and reverting to older version of Policies.xml
https://community.cyberark.com/s/article/PVWA-inaccessible-Source-array-was-not-long-enough
We did a compare of the versions and looks like only a PSMServer has been changed at the platform level.
But the encoding utf-8 was missing in the non working xml.
This issue happened after a user updated a platform.
Is there any reason why this issue happens?
05-21-2025 05:05 PM
Hi All,
The issue is with the corrupt PVConfig file. Though we couldnt find the rootcause as when we compared the old and new PVConfig there is no difference except the encoding, the workaround is to revert to the previous version of the file .
Regards,
Ferro
04-17-2025 05:10 AM
Hi,
Hard to say what happened exactly, but maybe he did a copy and paste from somewhere and a bad invisible character was copied.
04-17-2025 05:10 AM
Hi,
Hard to say what happened exactly, but maybe he did a copy and paste from somewhere and a bad invisible character was copied.
05-20-2025 11:46 PM
Hi @Froz Abdul Wahab Ameer Ahamed
As it seems Amaral provided an answer for your question, could you kindly share if this solution resolved your issue?
If so, could you please mark the answer as "Select as Best" to help other community members?
If the issue is still relevant, I would advise raising a ticket with our support team for further assistance.
Thank you,
Liad
05-21-2025 06:56 AM
Hi,
I get same issue sometimes, I rollback the PVConfiguration.xml file to older or previous version it works fine.
Best regards.
05-21-2025 06:56 AM
Hi,
I get same issue sometimes, I rollback the PVConfiguration.xml file to older or previous version it works fine.
Best regards.
05-21-2025 05:05 PM
Hi All,
The issue is with the corrupt PVConfig file. Though we couldnt find the rootcause as when we compared the old and new PVConfig there is no difference except the encoding, the workaround is to revert to the previous version of the file .
Regards,
Ferro
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

