The Analyze button on the Service Editor dialog box in ArcMap or the Share Web Map, Share Web Scene, and Share Web Layer dialog boxes in ArcGIS Pro help you identify potential performance bottlenecks and errors that you will need to address before you can publish your GIS resource as a service.
When you click Analyze, analyzer messages appear that identify the issues you need to address before publishing. In ArcMap, these messages appear in the Prepare window. In ArcGIS Pro, these messages appear in the Messages tab. Once you have addressed all these issues, your GIS resource is ready to publish.
If publishing from ArcMap and you need more time to correct the issues in your analysis, close the Service Editor and save your service configuration as a draft. You can continue your work by opening the draft in a future session in ArcMap. See Open a draft service in ArcMap for full instructions. If publishing from ArcGIS Pro, close the sharing dialog box, correct the issue, and share again later.
When analyzing your GIS resource, you'll notice three types of messages in the Prepare window in ArcMap, or two message types in the Messages tab in ArcGIS Pro. You can right-click each message to get a quick suggestion on how to address that specific issue. This also gives you access to a help topic with more information, such as additional repair options. The following table describes each message type.
These issues must be fixed before you can publish your GIS resource to the server.
These issues may affect performance, appearance, or data access.
You have the option to address or ignore a warning. If you choose to ignore a warning in ArcMap, you can mark it as an exception by right-clicking the warning and choosing Mark As Exception.
These informative messages appear in ArcMap. They suggest methods and best practices that can help you optimize your GIS resource for deployment on the server.
You have the option to address or ignore a message. If you choose to ignore a message, you can mark it as an exception by right-clicking the message and choosing Mark As Exception.