Estou usando o leitor Esri Geodatabase (ArcSDE) e o escritor safe.esri-AGOL.ArcGISFEATURESERVICE para publicar em nosso ArcGIS Portal (Portal [11.3], ArcGIS Pro [3.5.1]). O serviço de feição é criado, mas está sempre vazio. A classe de feição fonte tem cerca de 56.764 registros, mas o log do escritor mostra este erro: ArcGISFeatureServiceWriter: erro ao anexar: Falha no trabalho de escrita: 'Ocorreu um erro.' ArcGISFeatureServiceWriter: 0 feições escritas com sucesso em 'aaSiteAddressPointDEV2', mas o servidor rejeitou as 56765 feições na última solicitação devido a erros. Exceção Python : FMEException... Alguém já passou por isso? Algum conselho sobre o que geralmente causa a "rejeição da gravação em lote" ao usar o escritor ArcGISFeatureService para o Portal? Obrigado!

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; } } }

O escritor ArcGISFeatureService cria o serviço, mas nenhum recurso é escrito

JuneAcosta

Estou usando o leitor Esri Geodatabase (ArcSDE)<\/STRONG> e o escritor safe.esri-AGOL.ArcGISFEATURESERVICE<\/STRONG> para publicar em nosso ArcGIS Portal (Portal [11.3], ArcGIS Pro [3.5.1]). O serviço de feição é criado, mas está sempre vazio.<\/P>A classe de feição fonte tem cerca de 56.764 registros, mas o log do escritor mostra este erro:<\/P>ArcGISFeatureServiceWriter: erro ao anexar: Falha no trabalho de escrita: 'Ocorreu um erro.'<\/EM><\/FONT>
ArcGISFeatureServiceWriter: 0 feições escritas com sucesso em 'aaSiteAddressPointDEV2',<\/EM><\/FONT>
mas o servidor rejeitou as 56765 feições na última solicitação devido a erros.<\/EM><\/FONT>
Exceção Python <RejectedBatchWrite>: FMEException...<\/EM><\/FONT><\/P>Alguém já passou por isso? Algum conselho sobre o que geralmente causa a "rejeição da gravação em lote" ao usar o escritor ArcGISFeatureService para o Portal?<\/P>Obrigado!<\/P>

Encontre mais publicações marcadas com

Accepted answers

RenatoSalvaleon3

Yes, its in the writer parameters.

All comments

RenatoSalvaleon3

The new ESRI ArcGIS Feature Service is backwards compatible down to Portal 11.3, however, it will not hurt if you replace it the ArcGIS Portal Feature Service writer and check if you get the same error.

For the error message itself. At what point in the translation did the writer logged a rejection? Was there a long pause after the first feature entered the writer feature type? Some possible scenarios can be date fields, attribute names, attribute types, coordinate system (although unlikely with CS since the log will return an error). What's your source SDE dbms? The data store for Enterprise hosted feature layers is Postgres so case matters with field names. A BulkAttributeRenamer can be neccesary sometimes. Cpnvert dates to strings for troubleshooting purposes as well.

You can also file a support case if the above can be too daunting to troubleshoot.

bharold

Another possibility is the wrong geometry type is in the data, for example it is OK if the data has null geometry but not if it has line or polygon geometry when you're trying to write to a point feature layer. Also, it is always a good idea when reading and writing between different storage platforms to define your writer by importing the schema definition from the source dataset. Both sides of your equation are Esri technology so this will be reliable.

JuneAcosta

Thanks for responding! I’ve been working on this on and off for a couple of weeks with no luck. We’re testing branch versioning in our stage environment, and I’m trying to use FME to load ~300 layers from our EGDB into Portal. FME still feels like the easiest path, but I’m running into issues.

Our source egdb is MSSQL. Per your suggestion, could you clarify exactly how to “define the writer by importing the schema from the source dataset” in FME? I’m not sure which dialog/step you mean (Add Writer vs. Import Feature Types vs. Feature Type Definition).

I’ve attached the log, and a screenshot of my workbench.

I’ll also test with the ArcGIS Portal Feature Service writer again to see if I get the same results. I think that’s where I originally started, but Safe recommended I use the new writer—so I’ll try it one more time just to compare.

gisdata2Portal.log

bharold

Hi June

When adding a writer you have the option to import its definition from an existing dataset, see outlined in red here:

I'll look at your log shortly.

bharold

Hello again, I see you're reading in state plane and writing out web mercator. In this situation the data is supposed to be automatically reprojected but it's possible something is not working at this step, so you could add an EsriReprojector (or plain Reprojector) in your workspace to see if that helps.

I also see you're using OneDrive as a shared file location, we have not tested this and it's possible it can be an issue.

If problems remain after importing the write definition and reprojecting your data please open a support call.

JuneAcosta

Thanks for responding! I've been working on this on and off for a couple of weeks with no luck. We're testing branch versioning in our stage environment, and I'm trying to use FME to load ~300 layers from our EGDB into Portal. FME still feels like the easiest path, but I'm running into issues.

Per your suggestion, could you clarify exactly how to "define the writer by importing the schema from the source dataset" in FME? I'm not sure which dialog/step you mean (Add Writer vs. Import Feature Types vs. Feature Type Definition).

I've attached the log, and a screenshot of my workbench.

I'll also test with the ArcGIS Portal Feature Service writer again to see if I get the same results. I think that's where I originally started, but Safe recommended I use the new writer-so I'll try it one more time just to compare.

[cid:image001.png@01DC3440.F488CE70]

bharold

Hi, the screen shot didn't make it ;-(

bharold

Another thing, try reducing the batch size being written from the default 1000 to 500 (and less if necessary), if your data is very point rich it might be a problem.

JuneAcosta

Yes, I reduced it to a "max feature per request: 5oo" but still did not work.

RenatoSalvaleon3

I confrm that I can write an Enterprise 11.3 feature layer with the new ESRI ArcGIS Feature Service (3.12.4)

I initially got an error when my Append is configured with Feature Collection (the log showed this error). I switched it to GEOJSON. Before running again, I deleted the feature service in Enterprise created from the first failed run. Once its deleted I ran my workspace again and successfully added features on the layer.

My error message when on my first failed run is similar to yours.

What other error message appeared in your log before this python message? Mine is below,

JuneAcosta

"switched it to GEOJSON" Is this setting in the writer? Could you send me a screenshot of the writer with your configuration?

RenatoSalvaleon3

Yes, its in the writer parameters.

JuneAcosta

Do my other parameters look correct for creating a new feature service?

RenatoSalvaleon3

Can we take this offline? Here's my email, rsalvaleon@esri.com.

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

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