Changing the basemap to a vector tile basemap (such as Navigation) or changing the Current Map Settings to use the Legacy mapping profile will resolve the warning and allow syncing the map correctly. For example, if you're using the Default mapping profile and add the VectorStreetMap layer, this warning will appear. Replace the layer with one that is compatible or change the mapping profile. This could affect the downloaded map if it's synced with the current layer and mapping profile. Layer incompatible with current mapping profile.Ī layer in the Compilation window is not compatible with the currently selected mapping profile. The Illustrator library file specified for the Custom Swatch process contains a patterned swatch, which can't be applied using the process.Īpply pattern swatches in the downloaded map using Adobe Illustrator instead (or use solid swatches when running the Custom Swatch process). Pattern swatches are not supported with this process. Note:Read more on how you can increase the maxRecordCount and the tileMaxRecordCount.įinished with error. The max record count can be increased to support larger queries.
If the number of results from a query exceeds the limit, this error will be shown and the layer will be removed from the map. Map and feature services have a maximum number of records that they will return to a query. Republish the service with the Shape field turned on.įeature layer query exceeded the maxRecordCount or tileMaxRecordCount limit. The Shape field contains geometry information for features in the service and is required for many spatial operations. When the service in question was published, the Shape field was turned off. Increase the max image size on the service or reduce the size of your mapboard or reduce the PPI (or a combination of any of those options).įeature layer has the Shape field turned off. When you add an image service to the Compilation window, it will fail to load if the maximum image height and width in pixels surpasses the required limit. The image output size exceeds the layer's max image height or width. It may no longer exist, or the service URL may have changed.Ĭheck whether the service is still reachable through the REST endpoint, and consult the author of the service.įailed to load image service layer. (You can change the basemap and map projection later in the Compilation window.) Contact your organization administrator if the basemap gallery doesn't include a supported basemap. If your ArcGIS Enterprise organization is configured with a custom basemap gallery, it must include at least one Web Mercator basemap (such as Dark Gray Canvas). In the Mapboard window, click the Select Basemap button and choose another basemap. For ArcGIS Enterprise accounts in a disconnected environment, the basemap selected in the Mapboard window is based on the default basemap configured for your organization. The Mapboard window requires a basemap that uses a Web Mercator projection. There are no features to draw at the current extent of your map.Ĭhange the extent to view features, or add a data source that does contain features at the extent of your map.ĮRROR 24: To create a mapboard, you must select a basemap that uses Web Mercator projection. Notably, the only piece of Adobe’s CC that is optimized for M1 Macs is Lightroom ( Premiere M1 support and more in beta), while the rest of the suite gaining official support is still in the works.You've selected a projection that the current basemap does not support.Ĭhoose a vector basemap (Vector Street Map, Natural Earth) or change the map's projection to match the basemap.
You can check if you’ve gotten the update on your Mac by opening the Creative Cloud Mac app > click Creative Cloud in the menu bar > About Creative Cloud. Adobe employee Mariia confirmed CCXProcess 4.1.3 is the update that includes the Creative Cloud bug fix. Last week Adobe tracked down the problem and today a new update has a resolution. Users noticed it was the CCXProcess and CCLibrary background processes that were causing the problem by checking out Activity Monitor.
Read on for details and how to get this Creative Cloud bug fix.Īfter updating to macOS Big Sur, some Mac users – seemingly more with the 16-inch MacBook Pro – saw a problem where Creative Cloud background processes were using almost 100% of the CPU and affected machines’ fans would run at full tilt.
Adobe is out with a software update for its Creative Cloud apps that solves a serious issue that some Mac users were seeing after upgrading to macOS Big Sur – CPU usage around 100%.