Unable to publish Map service in ArcGis Pro 2.6

[SreekanthK]

I tried to publish a service in arcgis server from ArcGIS Pro (Version 2.6) and got the Below Error. The staging of the service was successful while Publish Service Definition was Failed. I am able to publish the services from ArcMap (10.6) in same server . Please go through the logs and help to rectify the issue.

Steps executed

1.Import the mxd into ArcGIS Pro

2.Connected to the server from Pro

3.Publish the service with Name,Summary, Tag and folder Name

4. There was no Analysis erros

5. Executed the publish and Got the error as Failed to publish the service

Status: InProgress StatusMessage: Preparing data references and staging map service
Status: InProgress StatusMessage: Using ArcGIS Version 12.3 for staging (Source for version: GP Staging Parameters)
Status: InProgress StatusMessage: Stage Tool initialized
Status: InProgress StatusMessage: Preparing maps and layers for processing
Status: InProgress StatusMessage: Retrieving and processing fonts
Status: InProgress StatusMessage: Submitted.
Status: InProgress StatusMessage: Executing...
Status: InProgress StatusMessage: Executing (Available Fonts): AvailableFonts
Status: InProgress StatusMessage: Start Time: Mon Mar 8 17:14:16 2021
Status: InProgress StatusMessage: Succeeded.
Status: InProgress StatusMessage: Consolidate data
Status: InProgress StatusMessage: Staging map service
Status: InProgress StatusMessage: Compressing package into SD file
Status: InProgress StatusMessage: Staging successful
Status: InProgress StatusMessage: Uploading service definition
Status: InProgress StatusMessage: Publishing tool initialized
Status: InProgress StatusMessage: Publishing map service (AGS)
Status: InProgress StatusMessage: Submitted.
Status: InProgress StatusMessage: Executing...
Status: InProgress StatusMessage: Executing (Publish Service Definition): PublishServiceDefinition if075460d-935b-41c5-b505-539d0e85feac # {"buildInitialCache":false}
Status: InProgress StatusMessage: Start Time: Mon Mar 8 17:14:22 2021
Status: InProgress StatusMessage: ERROR 999999: Error executing function.
Status: InProgress StatusMessage: Bad syntax in request. (status code 400).
Status: InProgress StatusMessage: Failed to execute (Publish Service Definition).
Status: InProgress StatusMessage: Failed at Mon Mar 8 17:14:44 2021 (Elapsed Time: 22.02 seconds)
Status: InProgress StatusMessage: Failed.
Status: InProgress StatusMessage: Server-side publishing failed
Status: InProgress StatusMessage: Publishing tool execution failed
Status: Failed ErrorMessage: Failed to publish map service

[MichaelVolz]

This workflow was not always supported in Pro, but I think at 2.6 it is.

Have you tried recreating the mxd from scratch in Pro instead of importing the mxd into Pro and see if that workflow works better?  I know its more work, but it might do the trick here.

[SreekanthK]

Thank you @MichaelVolz for the reply . I already tried like Instead of importing the mxd file in to Arcgis Pro, I tried to load the feature class from fgdb and published. Same error is throwing in that scenario also.

[MichaelVolz]

Do you have all appropriate ArcGIS Server (AGS) patches applied?

Is AGS federated with a Portal or is it standalone?

[SreekanthK]

Yes we applied all AGS patches.

ArcGIS server is a standlone one.

[Anonymous User]

Please check data is registered with the server or try to select copy all data when publishing 

[SreekanthK · Accepted solution]

Thank you everyone for the replay.

I resolved the issue by below steps.

1. Repaired the server

2.Restarted publishing service

3. As indicated in my steps I successfully published the service.

[DanNarsavage_IDWR]

Can you please expand on what exactly you mean by "repaired the server"? 

[LisaG]

Hi Dan, 

Sreekanth was most likely referring to their ArcGIS GIS Server. When publishing from ArcGIS Pro to ArcGIS Enterprise Portal or to a standalone ArcGIS GIS Server, this utilizes the publishing tools present in the ArcGIS Server. It sounds like there was an issue with ArcGIS Server in which a repair of the actual application itself on the ArcGIS Server machine (via Control Panel) resolved the issue.