POST
|
I did some additional MMPK troubleshooting last week with the help of an Esri support rep from the Navigator team. I had stripped out all relationships classes in my source fgdb as well as the geometric network. We isolated a specific polygon feature class as the problem layer and saw that it had some suspect geometries.....polygon slivers with an area less than a square foot. I deleted the bad features out of the dataset and the MMPK built with no errors. I've been able to consistently rebuild it with no errors ever since. Now I'm gradually adding back relationship classes and rebuilding to see if I bump into the error again. The odd thing was that I would get the "path already exists" error when the problem feature class was in a map with other layers, but would get a generic 999999 "function failed to execute" error when it was in a map by itself.
... View more
07-24-2017
07:44 AM
|
0
|
0
|
556
|
POST
|
Did you ever get any news on the bug you described? I am still having that same issue at Pro 2.0.
... View more
07-13-2017
11:04 AM
|
0
|
2
|
556
|
POST
|
Glad that helped! I burned a week on it last week...was almost at the point of rebuilding the whole config until I decided to review the IIS SSL settings since someone else had done the initial setup.
... View more
02-04-2015
02:54 PM
|
0
|
1
|
832
|
POST
|
Hi Kelly - Our issue ended up being that IIS had been inadvertently set to accept client certificates in the SSL settings. Once we set it back to ignore client certificates, everything worked as expected. Thanks!
... View more
02-03-2015
03:23 PM
|
2
|
3
|
832
|
POST
|
Alex - Did you find any resolution to the 502 bad gateway issue? I currently have the same problem on a production server install although my development and test environments are working fine with the same configuration. My secured services can be added directly to a web map with no issues, but can't be used to create a service item with stored credentials.
... View more
01-28-2015
07:53 PM
|
0
|
5
|
832
|
POST
|
Yes, unfortunately this error is caused by the Federal Shutdown. We are working on a KB article to help users address this issue during the shutdown. If you'd like further in, please contact Esri Support Services. Scott - Are you guys close to posting a workaround? We're getting calls on this, but didn't want to spend a lot of time if you had a fix.
... View more
10-08-2013
07:42 AM
|
0
|
0
|
216
|
Title | Kudos | Posted |
---|---|---|
2 | 02-03-2015 03:23 PM |
Online Status |
Offline
|
Date Last Visited |
12-18-2023
07:00 AM
|