Wrong order of layer IDs causes printing error

This chapter describes typical log messages for print problems due to the layer IDs of map services.

Warning in the WebOffice log file

caused by failed to process SOE operation (message: failed to process SSC transaction (handlerAction: MAP_ASSEMBLE), possible error codes: [UNKNOWN], details: [failed to process SSC transaction (handlerAction: MAP_ASSEMBLE), failed to handle map assembly, failed to handle map serialization, failed to get layer by ID (layerID: xx)])

The Layer IDs of the service '<servicename>' ('publisher@https://wodemo.mysynergis.com/WebGIS/<servicename>/MapServer') are not in ascending order or there are gaps. WebOffice print and ePaper might not work correctly, because WebOffice only supports ascending layer IDs. Please open the MXD for your service and use "Save a Copy..." with type "ArcMap 10.1 and 10.2 Documents (*.mxd)" and re-publish the new MXD to consolidate the layer IDs.

Possible reason

Due to a change in the LayerID order of the MXD, WebOffice 10.8 SP2 can no longer assign the correct Layer IDs.

To avoid complications when printing (plot) or reporting (ePaper), WebOffice 10.8 SP2 requires ascending IDs of the layers in the map service. It is also important, that the Layer IDs have no gaps.

Problem solutions

There are two ways to fix this problem inWebOffice 10.8 SP2.

1) Automatic sorting of Layer IDs in ArcMap by WebOffice author:

If this option is activated, the Layer IDs are sorted automatically in ascending order in ArcMap by the WebOffice author. WebOffice author corrects this sorting. After that, the map must be republished and the resources for the WebOffice 10.8 SP2 project reloaded.

Note: See chapter Basic Settings for configuration details in WebOffice 10.8 SP2.

2) Workaround, if automatic sorting of Layer IDs in ArcMap by WebOffice author is NOT activated:

Please open the MXD for your service and use "Save a Copy..." with type "ArcMap 10.1 and 10.2 Documents (*.mxd)" and re-publish the new MXD to consolidate the layer IDs. After that the resources for the WebOffice 10.8 SP2 project must be reloaded.

3) Additional workaround if the steps in 1) or 2) did not help:

1. Create new group layer in TOC of MXD

2. copy all layers from affected 'problem' group layers to the new group layer

3. remove original 'problem' group layer from TOC in MXD

4. move the new group layer to the original position in the TOC of the MXD

5. Publish new map service (or overwrite service)

6. SynAdmin: Reload Resources of WebOffice Project