nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ArcGIS Data Pipelines- Stored Credential Layer Error Out

Amanda.Huber@threeriversparks.org_trpd

Hello,

When trying to access a ArcGIS Online Hosted Stored Credential Layer we're seeing errors. This layer is fully accessible everywhere else in ArcGIS Online. I tested to see if it was an ownership issue, it is not.

Can someone please advise?

Thank you,

Amanda Huber

Find more posts tagged with

Accepted answers

MaxPayson

Hi @Amanda__Huber , I'd recommend opening a tech support case here to investigate the issue.

In general, the error implies that the feature layer queries made by Data Pipelines are failing. Given that it is working in other apps, my hunch is that the layer server does not have enough resources to respond to the queries, especially if the layer has many features with complex geometries. This may not happen in other apps because they only need to query subsets of the data. For example, Map Viewer has optimizations to only query the data for the current map extent with features simplified for the current scale, while Data Pipelines processes the entire layer with full resolution geometries.

That said, it'd be good to work with support to troubleshoot the specifics. I would also try adding a tool like Select fields - if the fields show up in the form, this verifies that Data Pipelines can at least access the layer and it is related to the underlying feature queries.

All comments

MaxPayson

Nice that's great! Glad it is working

Amanda.Huber@threeriversparks.org_trpd

HI @MaxPayson,

Thanks so much for your response! Good idea, I tested your workflow with the "Select Fields" tool and I was successfully able to view the fields with no server error (which is promising):

That being said, when trying to preview the output in the pipeline, this server error popped up, it appears our "The ArcSOC process for this service may not have enough memory allocated to it." so that was great insight you provided. We've updated the javaHeapSize and it appears to be working correctly in Pipelines now 🎉

Thanks so much for your assistance, we appreciate it!
Amanda Huber

MaxPayson

Hi @Amanda__Huber , I'd recommend opening a tech support case here to investigate the issue.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.