Issue when adding column to default accounts view: "An unexpected error has occurred. Retry the latest operation; if the error persists, contact your System Administrator"...anyone know what might be causing this?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Issue when adding column to default accounts view: "An unexpected error has occurred. Retry the latest operation; if the error persists, contact your System Administrator"...anyone know what might be causing this?

L1 Bithead
13 REPLIES 13

L7 Applicator

What is the name of the column you're trying to add? Is it one of the default columns available, or a custom file category you've added to CyberArk?

L1 Bithead

Its 'ItemName' which seems to be a default in the 'Business Website' platform that I have copied...

L1 Bithead

In fact, any change to the 'visible columns' config (e.g. deleting an existing field) seems to error with the same issue.

 

Just tested myself and see the same. So one for CyberArk support!

L1 Bithead

Thanks....ticket raised!

L7 Applicator

usually this indicates you have an error somewhere in your pvconfig as it's unable to save. Did you make any major changes recently?

 

It can be tricky to track down the problem as the error isn't very descriptive.

 

-Matt

L1 Bithead

No changes, I'm guessing its been there a while in that case.

In my example, it's a brand new untouched pcloud instance, so broken out of the box....

What I don't know is what has broken it, as even the docs indicate these changes can be made.

ok, lets try to revert the pvconfig back a version - if possible- and then test. You'll want to backup the current file just in case you need to reload it later.

 

log into your privateark client as an admin and go in to the PVWAConfig Safe - I'm pretty sure this is where the PVconfig lives. First back-up the current PVConfig so you don't lose any wanted changes, and then right click and go to versions - if there is an older versions make this the new version. Then do an IISReset on the PVWA and test again.

 

Note this will kick everyone out of the PVWA, so prob do this outside normal business hours. The idea is that this pvconfig should not contain any of the problems that the current one may contain.

 

-Matt

I'm using the cloud version, not certain I can do this?

ah, then you'll need a Support case to do this kinda thing. I did not notice that tag, my bad!

 

-Matt

L1 Bithead

Support have confirmed this is a bug. Only option right now is for them to update through the back end.

As filecolumns are rarely added, I'm glad they can do it from the back end as it shouldn't be more than a "once in a while thing". But yeah, a nasty bug to have, and I wonder what else in the Configuration is affected by this.

 

Did they give you a bug # ?

  • 274 Views
  • 13 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!