offset=0&limit=100:1 Failed to load resource: the server responded with a status of 500

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

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

offset=0&limit=100:1 Failed to load resource: the server responded with a status of 500

L0 Member

About CyberArk Privileged Access Security

Copyright © 1999-2024 CyberArk Software Ltd. All Rights Reserved.

Version 14.2.4 (14.2.4.193)

 

I am trying to workout if this is a known issue or if there is a fix.

offset=0&limit=100:1

https://cyberarkpvwa.removed.com/PasswordVault/api/ExtendedAccounts?SavedFilter=Regular&sort=Safe&se...

The above code is causing the error

 

Here’s how it works with and without pagination:

🔹 Without Pagination offset=0&limit=100:1

What happens: You only get the first 100 accounts.

Problem: The remaining 150 accounts are not returned unless you make additional requests.

Risk: If your application or UI expects all accounts and doesn’t handle pagination, it may throw errors or behave unexpectedly.

🔹 With Pagination offset=200&limit=100:1

You break the request into multiple calls using the offset parameter:

| Request | Offset | Limit | Accounts Returned |

| 1 | 0 | 100 | Accounts 1–100 |

| 2 | 100 | 100 | Accounts 101–200 |

| 3 | 200 | 100 | Accounts 201–250 |

 

Each call returns a chunk of accounts, and you can combine them in your application or script.

 

Best Practice

  • Always use pagination for large datasets.
  • If you're building a script or integration, loop through the pages until the number of returned accounts is less than the limit (which means you've reached the end).

 

 

Error message:

Something went wrong

Please try again or contact your administrator

OK

 

IE Console message:

/PasswordVault/v10/:1 Unchecked runtime.lastError: The message port closed before a response was received.

main.b275608b832b1912.js:1 positionTop property is deprecated.

main.b275608b832b1912.js:1 Responsive property is deprecated.

main.b275608b832b1912.js:1 Responsive property is deprecated.

main.b275608b832b1912.js:1 Responsive property is deprecated.

main.b275608b832b1912.js:1 Responsive property is deprecated.

main.b275608b832b1912.js:1 Responsive property is deprecated.

main.b275608b832b1912.js:1 Responsive property is deprecated.

main.b275608b832b1912.js:1 AG Grid: As of v27, registering components via grid property frameworkComponents is deprecated. Instead register both JavaScript AND Framework Components via the components property.

(anonymous) @ main.b275608b832b1912.js:1

/PasswordVault/api/ExtendedAccounts?SavedFilter=Regular&sort=Safe&search=sdi21m01&offset=0&limit=100:1  Failed to load resource: the server responded with a status of 500 ()

 

 

1 REPLY 1

L0 Member

Hi everyone,

I’m just an end user of the CyberArk application within my organization. Out of sheer frustration, I created this community account to raise an issue that’s been affecting my experience.

Unfortunately, it feels like no one within my organization or perhaps even at CyberArk is paying attention to the user experience side of things. I’ve tried raising this internally, but it seems to fall on deaf ears.

I’m really hoping someone here either from the community or CyberArk itself might hear me out and offer a solution. Right now, it feels like I’m shouting into the void.

Thanks in advance to anyone who takes the time to listen and help.

  • 125 Views
  • 1 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!