Error server failed to transmit file maps

error server failed to transmit file maps

PROBLEM: The following error message appears when opening JeppView for Windows: "Data server failed to initialize. · CAUSE: Themes files are either corrupt or. Scan File Failure: Not enough disk space to pack the file 0x01510001, Failed to Upload the Job to Server: Upload file failed during. › › Game and voice servers › CS 1.6/DoD/TFC/CZ.

Error server failed to transmit file maps - but not


Basemap cannot be reprojected.

You've selected a projection that the current basemap does not support.

Choose a vector basemap (Vector Street Map, Natural Earth) or change the map's projection to match the basemap.

Data is outside of the map.

There are no features to draw at the current extent of your map.

Change the extent to view features, or add a data source that does contain features at the extent of your map.

Failed to load image server layer.

Failed to load map service layer.

The image service is unreachable. It may no longer exist, or the service URL may have changed.

Check whether the service is still reachable through the REST endpoint, and consult the author of the service.

Failed to load image service layer. The image output size exceeds the layer's max image height or width.

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.

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).

Feature layer has the Shape field turned off.

When the service in question was published, the Shape field was turned off. The Shape field contains geometry information for features in the service and is required for many spatial operations.

Republish the service with the Shape field turned on.

Feature layer query exceeded the maxRecordCount or tileMaxRecordCount limit.

Map and feature services have a maximum number of records that they will return to a query. 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.

The max record count can be increased to support larger queries.

Read more on how you can increase the maxRecordCount and the tileMaxRecordCount.

Finished with error. Pattern swatches are not supported with this process. Please choose a solid swatch.

The Illustrator library file specified for the Custom Swatch process contains a patterned swatch, which can't be applied using the process.

Apply pattern swatches in the downloaded map using Adobe Illustrator instead (or use solid swatches when running the Custom Swatch process).

Layer incompatible with current mapping profile.

A layer in the Compilation window is not compatible with the currently selected mapping profile. This could affect the downloaded map if it's synced with the current layer and mapping profile.

Replace the layer with one that is compatible or change the mapping profile. For example, if you're using the Default mapping profile and add the VectorStreetMap layer, this warning will appear. 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.

Map service layer does not support Query operation; features will be downloaded as raster.

The service in question does not have the Query operation enabled. This operation allows querying of the underlying features that are contained in the service. If it is disabled, you will get raster data in the output rather than vector features.

Enable the Query operation on the service.

One or more layers are not visible at the scale.

When the mapping community and users share multiscale maps and layers on ArcGIS Online, they may choose to set a visible range or zoom levels on these maps and layers to reduce the amount of clutter. This is a standard practice when authoring a multiscale map. It allows you to continually view geographic data across a range of scales—global to building level.

Increase (or decrease) the scale of the mapboard.

Doing this could alter the amount of detail you see and the size of the mapboard.

The Clip to graphics extent option is not currently supported, recreate the AIX file with this option disabled.

The layout exported from ArcGIS Pro 2.6 (or earlier) has Clip to graphics extent turned on. With this setting enabled in ArcGIS Pro versions before 2.7, the extension cannot properly align the mapboard with the layers from your ArcGIS Pro project.

Upgrade to ArcGIS Pro 2.7 or later. If that's not an option, in your ArcGIS Pro project, turn off Clip to graphics extent and export your layout to AIX again.

The layer cannot be added to the map. Please check your permissions to the layer or layers.

The signed-in user does not have access to the layer or layers in question.

Contact the author of the service to get access.

The layer cannot be added to the map. The layer's spatial reference is different from the map.

You are trying to add a cached map service that uses a different spatial reference than the current map.

Change the spatial reference in Current Map Settings to match your cached service, create a new mapboard, and add your service again.

To create a mapboard, you must select a basemap that uses Web Mercator projection.

The Mapboard window requires a basemap that uses a Web Mercator projection. 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.

In the Mapboard window, click the Select Basemap button and choose another 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). Contact your organization administrator if the basemap gallery doesn't include a supported basemap. (You can change the basemap and map projection later in the Compilation window.)

Unable to load file. This dataset is too large to add directly to the map.

The file size or the number of records in the shapefile, .csv, or .txt file exceeds the limit.

Publish a large dataset as a hosted feature layer, and add the hosted layer to the map. If you use ArcGIS Pro and don't have publishing privileges, you can add the large dataset to a map in ArcGIS Pro and export the map or layout to AIX, which you can open in Illustrator using the extension.

Unsupported map service type.

The service in question is of an unsupported type (WMS, WCS, and so on).

Republish the data as a supported layer type (map, feature, or image service).

Vector tile layers are not supported.

The service in question is a vector tile layer, which is only supported with an ArcGIS organizational account.

Republish the data as a supported layer type (map, feature, or image service).

Web Tiled Layers are not supported yet.

The service in question is a Web Tiled layer, which is not currently supported in the ArcGIS Maps for Adobe Creative Cloud extension.

Republish the data as a supported layer type (map, feature, or image service).

Problem: Receiving errors when uploading a shapefile to ArcGIS Online, Business Analyst Online, or Community Analyst


When uploading shapefiles to ArcGIS Online, Business Analyst Online, or Community Analyst, the service sometimes produces an error. There are several reasons as to why this happens.


This is most often caused by either invalid shapefile packaging, improper shapefile formatting, or because the shapefile does not meet the requirements for uploading to the online applications.

Solution or Workaround

The first two steps outline general required shapefile formatting and packaging that applies to all of the online applications. The third step goes into specific requirements for each.

  1. Check for improper packaging.
    • The ZIP file must contain one shapefile.
    • The ZIP file must contain the .shp, .shx, .dbf, and .prj files that comprise the shapefile.
    • The ZIP file must be created by selecting the required files and zipping them directly. If the files are moved to a folder and then the folder is zipped, it causes an error upon uploading.
  2. Check for invalid formatting.
    • The shapefile must contain valid geometries. Currently, self-intersection in polygon shapefiles is not supported. If using ArcMap or ArcGIS Pro, the Repair Geometry tool can be used to correct invalid geometries in shapefiles.
    • The name of the shapefile and the field names of the shapefile must not contain any spaces or special characters (with the exception of the underscore).
  3. Make sure that the shapefile meets requirements.
    • ArcGIS Online
      • Compression formats other than a .zip archive are not supported.
      • Files containing more than 4,000 point features or 2,000 line or polygon features cannot be added directly to a map. If the data has more than 4,000 point features, or more than 2,000 line or polygon features, or is larger than 10 MB, publish it as a hosted feature layer.
      • The following features are not supported: multipoint geometries, geometries that cross the dateline and self-intersections in polygons. Shapefiles with these features cannot be added to a map. Multipatch layers are only supported in a scene layer.
      • Zip files over 10 MB cannot be added directly to the map.
    • Business Analyst Online / Community Analyst
      • A maximum of 100 records and a file size limit of 3 MB.
      • Only point and polygon geometry (no lines, multipoint or multi-part geometry) can be added.
      • Compression formats other than a .zip archive are not supported

Related Information

Last Published: 4/29/2021

Article ID: 000011508

Software: ArcGIS Business Analyst Web App 9.1, 8.4, 8.3, 8.2, 8.1, 7.4, 7.3, 7.2, 7.1 ArcGIS Community Analyst Web App 9.1, 8.4, 8.3, 8.2, 8.1, 7.4, 7.3, 7.2, 7.1, 6.1, 6.0, 5.9

Translation Feedback

How can we make this translation better?

Get notified about latest updates to this technical article?

Do you want to Unsubscribe?

There are a lot of FTP errors out there.
Way too many, right?

time blueQuick fix

Many FTP users come across error message 550. As all 5xx errors, the “550 No such file or directory” error message is a permanent negative completion reply status of the FTP server. The requested action could not be processed, because the command was not accepted by the server. This problem has several possible causes, for example access restrictions for the requested file, an incorrect path, or mounted file systems.

To get rid of FTP error 550, check the path that you are using is correct and leads you to the requested file. If this is not the case, try using the absolute path of the file. If the error persists, check the mount points and make sure that the file system exists and that you have the permission to access it.


Best solution:

Troubleshooting common deployment issues

This section provides the list of solutions and workarounds for common problems with deployments in PhpStorm.

Collecting PhpStorm deployment logs

If your issue is not addressed in this section, contact our support engineers. If asked to provide deployment logs, follow the instructions to collect them.

Collect deployment logs

  1. Select in the main menu.

  2. In the Custom Debug Log Configuration dialog that opens, add the following lines depending on the issues you are experiencing:

    • Issues with deployment/synchronization:

    • Issues with issues with SSH/SFTP:

    Collect logs
  3. Click OK and reproduce the issue.

  4. Locate the log file by selecting (for Windows and Linux) or (for macOS).

    If necessary, you can locate the log manually:













    The most recent log file is named idea.log; older files names end with a number, that is idea.log.1, idea.log.2, and so on. In most cases you need only the most recent one.

  5. Attach the log file(s) to the issue or forum thread.

General troubleshooting

Deployment is slow or fails

Deployment can be a resource-intensive operation, especially if a project or a deployment server contains lots of directories and files. In the Settings/Preferences dialog (), navigate to Build, Execution, Deployment and explore the following configuration options, which can speed up deployment:

  • Exclude directories that are not needed from deployment (for example, images). This can be done from the Deployment: Excluded Paths Tab page.

  • On the Options page, clear the Overwrite up-to-date files to skip uploading files that don't need to be uploaded.

  • Depending on the server, switching between active and passive transfer mode in the advanced FTP settings may help. This can be done by toggling Passive mode in the Deployment: Connection Tab for the server.

File transfer becomes unresponsive

This can happen in case PhpStorm tries to resolve an IPv4 host via IPv6. By default, PhpStorm only listens for incoming IPv4 connections. To make sure IPv6 is disabled, check the PhpStorm JVM options:

  1. Select from the main menu.

  2. In the .vmoptions file that opens, make sure the line is present.

  3. Restart PhpStorm.

Otherwise, to enable IPv6 support, delete the line. In this case, make sure to add the IPv6 entry for your host to the /etc/hosts file.

Download/upload actions are not available

Download/upload actions may not be available because of a missing mapping. If a file or folder that you want to download is not configured in any mapping, PhpStorm will not download it. Mappings can be configured as described in the Map project folders to folders on the server and the URL addresses to access them.

For some actions, a default deployment server needs to be selected on the Deployment page of the Settings/Preferences dialog.

Some folders are not deployed

A common cause for folders not being deployed is when they are explicitly excluded. To solve this, in the Remote host tool window right-click the given folder and select Remove Path From Excluded from the context menu. Once this is done, the folder will be deployed.

This can also be configured from the Deployment page of the Settings/Preferences dialog (). Open the Excluded Paths tab for the server and remove the excluded path. Note that both the source and the target folders should be checked. Folders can also be excluded by name on the Options page under Exclude items by name.

Sharing deployment configurations between projects

Deployment Servers are configured at the IDE level: they are available for all projects and can be shared between them.

Note that only the name and connection details (specified on the Deployment: Connection Tab tab) are shared between projects: mappings and excluded paths are project-specific and have to be configured separately. Using this approach, connection details have to be entered just once, while mappings and excluded paths can be configured per-project, sharing the connection details. This can be useful when projects share the same deployment server and use the same connection settings. If connection settings are different between projects, they have to be configured for every project separately.

If necessary, you can set a server to be visible in a single project by selecting the Visible only for this project checkbox on the Deployment: Connection Tab.

IDE settings do not allow me to configure mappings

The default new project settings are used to configure the default settings for new projects and do not affect the currently opened projects. To configure settings for the current project, use the Settings/Preferences dialog .

Can subfolders within the same folder have different deployment settings? Can a local folder be deployed to multiple locations?

When uploading folders and configuring mappings, note the following:

  • You can specify mappings for specific folders to different paths on the deployment server. This can be configured on the Deployment: Mappings Tab for the server.

  • You can exclude specific folders and files from being uploaded/downloaded. This can be configured on the Deployment: Excluded Paths Tab for the server.

  • You cannot upload the same folder (or subfolders) to different sites at once. A separate deployment configuration needs to be created for each of them and uploaded to each site one by one.

If this is what you want to do, we recommend automating the process with a capable tool. For example, Phing has an FTP task which can be used from PhpStorm. Within PhpStorm, you can use the Sync with Deployed... command and select from available deployment servers for every upload.

It is not possible to assign a keyboard shortcut directly to the Sync With Deployed to <server name> command, only to the generic Sync with Deployed to... command, which will then display a popup menu with the list of servers. Refer to Configure keyboard shortcuts for details.

If you do wish to assign a keyboard shortcut to a specific deployment server, it is possible to record a Macro and assign a shortcut to it instead:

  1. Select and start recording a Macro.

  2. Select <server name> and close the sync window.

  3. Stop recording the Macro by selecting from the main menu.

  4. Set the Macro name, for example Sync with <server name>.

  5. Open in the Settings/Preferences dialog (), select Keymap and find the Macros node. From the context menu of the new sync Macro that was just recorded, select Add Keyboard Shortcut and provide the desired shortcut .

How do I deploy a database using PhpStorm?

There are a couple of ways to deploy a database using PhpStorm:

Can I run a script or executable on my files before the upload occurs?

Things like minifying CSS, optimizing images, encoding PHP files using IonCube, and so on are actions that you may want to execute before an upload happens. The best approach to do this is run them not when the upload is started, but when the files are changed, by using File Watchers in PhpStorm. When the time comes to upload them to a deployment server, upload the processed files instead.

Note that the Skip external changes checkbox must be cleared on the Options page for this to work.

Sometimes files are not uploaded automatically

By default, PhpStorm uploads the files if they are changed by some external processes (VCS, transpilers, and so on). If the files are not uploaded, make sure that the Upload changed files automatically to the default server on the Options page is set to Always and the Skip external changes checkbox is cleared.

Can I run pre- and post-deployment actions?

It's possible using Run/Debug configurations. You can create a fake Run/Debug Configuration, or a Run/Debug configuration that should be the last step, and add the required steps under Before launch.

As an alternative, we recommend using Phing or any other build system to execute complex sequences of steps.

FTP troubleshooting

FTP issue: Invalid descendent file name "http:"

When a deployment server has been configured or when using the Test Connection button in the project settings, the Invalid descendent file name "http:" error is displayed. Note that all file names with a colon : in the name will be considered invalid.

This can happen if a file containing http: in its name exists in the project. The library that PhpStorm uses to connect to FTP (Apache Commons VFS) cannot read the contents of a folder containing such a file, which causes the operation to fail. The only solution is to remove the file containing http: in its name from the project.

PhpStorm seems to connect to the server but can't list files or perform upload

This may be because the deployment server requires a so-called passive FTP connection. To set this mode, select the Passive mode checkbox in the Deployment: Connection Tab for the selected server.

Deploying files when changing branches using Git checkout

There are a couple of ways to go about deploying files when switching between branches using Git checkout:

  • One way is to configure deployments to always upload files and external changes. To do this, on the Options page, set Upload changed files automatically to the default server to Always and clear the Skip external changes checkbox. Note that this will upload all files to the server when switching branches.

  • Use git-ftp. It performs minimal uploads and is also able to mirror file and directory removals.

FTPS troubleshooting

PhpStorm cannot establish connection with an FTPS server

If an FTPS server is configured to use TLS 1.0 / TLS 1.1, PhpStorm cannot connect to it and the following error message is displayed:

WARN - deployment.ui.WebServerConfigForm - Could not connect to FTPS server on "<deployment-server>". org.apache.commons.vfs2.FileSystemException: Could not connect to FTPS server on "<deployment-server>".

This happens because PhpStorm supports connecting to servers via TLS 1.2 and later. Using TLS 1.0 and TLS 1.1 is not supported, since these protocols are deprecated and considered insecure.

As a workaround, you can enable TLS 1.0 / TLS 1.1 support by adjusting the PhpStorm JVM options. Note that using outdated protocols can and will introduce security risks to your environment and consider it to be a last resort option.

  1. Create a file with the following contents:

    jdk.tls.disabledAlgorithms=SSLv3, RC4, DES, MD5withRSA, \ DH keySize < 1024, EC keySize < 224, 3DES_EDE_CBC, anon, NULL, \ include jdk.disabled.namedCurves

  2. Select from the main menu.

  3. In the .vmoptions file that opens, add the following line:${PATH_TO_CREATED_FILE}/

    Replace with the path to the created file.

  4. Restart PhpStorm.

Last modified: 01 August 2022

Edit individual files on remote hostsTutorial: Deployment in PhpStorm

response.Status.code != 200) { alert('Geocoding failed. ' + response.Status.code); } else { var bounds = new GLatLngBounds(new GLatLng( response.Placemark[0].ExtendedData.LatLonBox.south, response.Placemark[0].ExtendedData.LatLonBox.west error server failed to transmit file maps, new GLatLng( response.Placemark[0].ExtendedData.LatLonBox.north, response.Placemark[0].ExtendedData.LatLonBox.east )); map.setCenter(bounds.getCenter(), error server failed to transmit file maps map.getBoundsZoomLevel(bounds)); var latlng = new GLatLng( response.Placemark[0].Point.coordinates[1], response.Placemark[0].Point.coordinates[0]); infoPanel.innerHTML += '<p>1st result is <em>' + // No info about location type hp support error 21 10 response.Placemark[0].address + '</em> of <em>' + AccuracyDescription[response.Placemark[0]. AddressDetails.Accuracy] + '</em> at <tt>' + latlng + '</tt></p>'; error [244] invalid model id var marker_title = response.Placemark[0].address + ' at error server failed to transmit file maps + latlng; map.clearOverlays(); var marker = marker = new GMarker( latlng, {'title': marker_title} ); map.addOverlay(marker); } } function geocode_address() { var address = document.getElementById('input-text').value; infoPanel.innerHTML = '<p>Original address: ' + address + '</p>'; geocoder.getLocations(address, geocode_result_handler); } function initialize() { map = new GMap2(document.getElementById('map')); map.setCenter(new GLatLng(38, 15), 2); map.setUIToDefault(); infoPanel = document.getElementById('info-panel'); }
var geocoder = new google.maps.Geocoder(); var infoPanel; var map; var marker; function geocode_result_handler(result, status) { if (status != google.maps.GeocoderStatus.OK) { alert('Geocoding failed. ' + status); } else { map.fitBounds(result[0].geometry.viewport); infoPanel.innerHTML += '<p>1st result for geocoding is <em>' + result[0].geometry.location_type.toLowerCase() + '</em> to <em>' + result[0].formatted_address + '</em> of types <em>' + result[0].types.join('</em>, error server failed to transmit file maps, <em>').replace(/_/, ' ') + '</em> at <tt>' + result[0].geometry.location + '</tt></p>'; var marker_title = result[0].formatted_address + ' at ' + latlng; if (marker) { marker.setPosition(result[0].geometry.location); marker.setTitle(marker_title); } else { marker = new google.maps.Marker({ position: result[0].geometry.location, title: marker_title, map: map }); } } } function geocode_address() { var address = document.getElementById('input-text').value; infoPanel.innerHTML = '<p>Original address: ' + address + '</p>'; geocoder.geocode({'address': address}, geocode_result_handler); } function initialize() { map = new google.maps.Map(document.getElementById('map'), { center: new google.maps.LatLng(38, 15), zoom: 2, mapTypeId: google.maps.MapTypeId.HYBRID }); error server failed to transmit file maps infoPanel = document.getElementById('info-panel'); }