Select to view content in your preferred language

Error 001378: Tool Available Fonts 10.x is unsupported on Server

10597
21
12-02-2021 10:25 AM
BrendonRapinchuk
New Contributor

We recently migrated our enterprise server from 10.3.1 to 10.9.1 and are running into issues whenever we try to publish anything to the new server. It always happens after "StatusMessage: Compressing package into SD file"

 

Below is the message we receive no matter if it is a full project or a blank map with just a shape file added.

"ErrorMessage: ERROR 001378: Tool AvailableFonts 10.x is unsupported on server

ErrorMessage: Failed to execute (Available Fonts).

ErrorMessage: Failed.

ErrorMessage: Failed to execute (StageService).

ErrorMessage: Staging failed"

 

I cannot find any information on AvailableFonts 10.x and the only info on ERROR 001378 says to replace the tool, but no instructions on how to go about that. Has anyone run into this or have any ideas on things I could try to fix it? I have had a ticket open with support for several days, but so far haven't gotten any guidance about this particular issue.

 

Thanks.

21 Replies
LeviColdiron
Emerging Contributor

Had to upgrade ArcGIS Server from 10.7.1 to 10.9.1 due to 3rd party software compatibility. Ran into this same problem. This article held the solution. 

It still baffles me that I could go through the entire installation and config of ArcServer and Web Adaptor 10.9.1 and my machine still isn't actually upgraded. 

0 Kudos
Bill_Parker
New Contributor

I was getting this same error when using Python to overwrite or publish new services.

I had created a script that worked to a single stand alone server. But when I was publishing to our stand alone server that sits paired with another server with a load balancer in between it started throwing this error. But not all the time, it would publish sometimes and sometimes not publish. I started testing publishing and overwriting from Pro and would sometimes get the error and sometimes not.

Because I had the script I used some print and error statements to track the error to the creation of the draft sharing service, or draft .sd file.

The fix I came up with was to change the code to create the sharing draft as an offline file with an offline target of 10.x instead of setting the target server property as the .ags file for my server connection. I then used the same .ags file in the UploadServiceDefintion tool pointing to the .sd that had been created. It follows the code in the second to last example, Create and publish an offline service definition, here: https://pro.arcgis.com/en/pro-app/3.3/arcpy/sharing/geoprocessingsharingdraft-class.htm

I think a possible work around in Pro that doesn't use Python would be to create offline .sd files that doesn't connect to your server and then use the Upload Service Definition Tool in the Server->Publishing toolbox. It would be a cumbersome way to overwrite files, unless you are looking to use arcpy to automate the entire process.

0 Kudos