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

SOE is &amp;quot;not a valid extension type for MapServer&amp;quot;

KirkKuykendall

I'm able to publish another soe to the basemap_wells mapservice, but LegendCullerSOE give me problems ... here's what the log says:

Unable to read the service '{0}' from the configuration store. {1} basemap_wells.MapServer 'LegendCullerSOE' is not a valid extension type for 'MapServer'.

http://localhost:6080/arcgis/admin/services/Basemap/basemap_wells.MapServer shows that the SOE is enabled and that it supports Rest.

In my constructor LegendCullerSOE(), I log a message, but that never shows in the log file.

The soe file is present in config-store/extns/LegendCullerSOE.soe.

Any suggestions, or even wild guesses, are appreciated.

Encuentra más publicaciones etiquetadas con

Accepted answers

RichardWatson

It appears that things are out of sync. Why, I haven't a clue.

What I would do is to delete (or at least stop) all map services using the extension
Delete the extension (using ArcGIS Server Manager)
Upload the extension
Try to start the map services

All comments

RichardWatson

KirkKuykendall

Thanks Richard, that did the trick, after several tries.

I wonder if things got messed up earilier when I restarted the ArcGIS Server windows service from the Windows Services manager (bypassing arcgis server). I haven't seen any documentation saying not to do that, but I can't help but think it could cause problems on a multimachine site, which is what I'm testing on.

RichardWatson

I have used Windows Services to start and stop the server service many times. I don't know of any other way to accomplish this. Sometimes I need for server to just stop so that it will release locks on various custom DLLs and using the service is just easier than trying to accomplish the same for each server service.

10.1 was a radical change for ArcGIS Server so I am not surprised to see some bugs with regards consistency issues like this. If you can stumble across the exact set of steps then filing an issue with ESRI would be nice so the rest of us can benefit from your pain:)

I would definitely think that multiple machine sites add complexity here. For example, what happens when a machine is temporarily unreachable? Does the operation fail or does ArcGIS Server make it whole when it can reach it?

I would be interested in whatever insights you gain with regards to mutiple machine deployments.

AjitDharmik

Were you able to resolve this? If so, could you share what ended being the issue?

Thanks!
Ajit

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

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