Latest Contributions by JeremyWright

Blair, When my developer emailed Dov Isaacs from Adobe about it his reply was just to say "No updates, sorry!". I've asked with our CTO and PM staff about avenues to escalate the issue within Adobe, and my developer has pledged to review the issue once more to explore any potential experimental workarounds that might help us mitigate this. But unfortunately we are no further now than we were when we made initial contact. Regards, Jeremy W. ... View more

I just checked with my developer and he has not heard anything out of them. Additionally he said the estimate from Dov Isaacs was that we would not hear anything until end of year.  My developer will attempt to contact Dov again to get any update ... View more

andy, It actually looks like the poly is still transparent, but a) In your exported PDF (I assume at higher DPI than display) you're getting a different LOD of the hillshade in the basemap, which doesn't actually include the hillshade.  Topo and other basemaps do this content change and higher LODs which trips us up all the time :/.   b)  Your layout may be set to be CMYK, which means the colors would appear darker/muddier due to different gamut.  you can check this in Layout properties dialog. Jeremy W. ... View more

Hello Everyone, Esri's patch that resolves this issue in Desktop, Engine, and Server/Enterprise is now posted at https://support.esri.com/en/download/7726 The patch needs to be applied to Server/Enterprise and Desktop installations depending on what type of service you're publishing from ArcMap. Lastly, be aware that a patch for runtime local server is forthcoming. Regards, Jeremy W. ... View more

Ming, The patch is already built for all Desktop/Server/Engine versions we plan to patch, and testing is almost complete on those patches across all affected versions.  Thus, we expect to have it available soon. FYI, the ArcGIS Runtime team is also testing their version of the patch (for the local server in Runtime versions affected) but it will be released a bit behind the Desktop/Server/Engine patches. Regards, Jeremy W. ... View more

Sorry for the delay Brett - just to let you know this was demo'd at the Road Ahead for ArcGIS Pro session at Esri UC 2019.  So it's well in progress for the next release. ... View more

Hi Andrew can you send us your logo file (I assume it is an EMF?) via Esri Support?  We'd like to take a look. ... View more

Yes at this time we also plan to patch runtime local server. ... View more

UPDATE 7.10.2019: We've posted a KB article at https://support.esri.com/Technical-Article/000021401 that describes the problem and many different workarounds that can be applied to resolve this issue. A general patch for affected supported versions has been tested and is working its way through the patch creation process.  I'll update this thread when the Esri-side fixes are available.  In the meantime the technical article linked contains several workarounds that can be applied. ... View more

Randy, thanks for your feedback. 1. The help for creating new marker symbols (including a description of the types available) is here: http://desktop.arcgis.com/en/arcmap/10.3/map/styles-and-symbols/creating-marker-symbols.htm 2.  Publishing from Pro doesn't use this codepath, unless you're using an older (2.0/2.1) version of Pro.   So if you're experiencing issues after republishing the service from Pro, I would recommend updating Pro to a more current version.  The most recent public version is 2.4.   3.  You will note that the "roll back the security updates" options do say "...and opt out of updates until the resolution is available".  An article which enumerates several ways to opt out of windows updates is linked here for Win10, similar info is available online for other versions: https://www.windowscentral.com/how-stop-updates-installing-automatically-windows-10 The full Kb article is copy-edited and we're pushing it to the web presently. Regards, Jeremy W. ... View more

yes we found all windows versions that were updated in this way are affected by this security update. ... View more

UPDATE: We worked over the weekend with Microsoft on this issue and found the root cause was the security patch, BUT we discovered a fix we can do on our end.  The fix has been tested and the QFE team has begun the process of porting the fix back to the relevant versions. We're also publishing a KB article with all known details on the issue and all of the known workarounds for those that need fixes right now.   I'll update the thread with the KB article as soon as it is copy edited and posted, in the meantime here's the draft of the workarounds section: Workarounds: There are several workarounds that can be used until general patches are available.  Choose one of the following strategies:   Switch the character-marker based symbols to use simple markers instead, and republish the map.  Simple markers are not affected by this issue as they do not use the affected Windows GDI method to be published. Republish the map from ArcGIS Pro instead of publishing from ArcGIS Desktop.  This can be done by importing the MXD into Pro and sharing via a portal connection or to server directly.  ArcGIS Pro publishing uses a different code path that’s not dependent on the faulting GDI function. Roll back the security updates temporarily on either client or server machines: If publishing a map or feature service to ArcGIS Server directly or ArcGIS Enterprise: The machine on which ArcGIS Server is installed must be rolled back to before the June security patches for Microsoft Windows (KB4503286 or KB4503276) and opted out of updates until a resolution is available, and the affected services must be restarted. If publishing a hosted service to ArcGIS Enterprise or ArcGIS Online: The machine on which ArcGIS Desktop is installed must be rolled back to before the June security patches for Microsoft Windows (KB4503286 or KB4503276) and opted out of updates until a resolution is available, and then the affected services must be republished from the rolled-back machine.  ... View more

Just to update the thread: Our developer Rajeev Pahuja who was in contact with Adobe analyst Dov Isaacs did receive a reply from Dov - the delay was because he's out of the office right now.  In his reply Dov acknowledged that they were able to reproduce the issue and "the problem is actively being investigated".  His reply also indicated that Dov is not certain on the timeline of an update or fix but indicated it will likely be closer to the end of this year. We've additionally asked for an incident or error report number so we can refer to the issue in the future, I will update the thread when we hear back from them. Regards, Jeremy W. ... View more

Oh I get it Randy - I'll definitely express to Microsoft the need for urgency in resolving this issue.  Thanks for the versions - I'll check with the folks who are in charge of Explorer on that working at previous releases.  ... View more