Remote uploading issue for Industrial Edge and Industrial AI Suites

0
Hi everyone,My recent project gave me the opportunity to explore using applications within Industrial AI Suites and also publishing within Industrial Edge. However, I was not able to remotely upload files or any data remotely, through either channels below. Could anyone advise?(i) from Local Drive to AI Inference Server (of Industrial AI Suites). It gets stuck at 100% and after re-trying several times, it still gets stuck. File size is ~300MB (.zip file).(ii) from Industrial Edge App Publisher (IEAP) to Industrial Edge Management (IEM). It gets stuck at 30% or 50%, with no indicator of progress. I also try to export the file from IEAP onto my local drive, then import remotely to IEM. This also does not work and gets stuck. File size is less than 1GB (.app file)
asked
1 answers
1

Hi Foo,


Since uploads are getting stuck at different stages in both Industrial AI Suite's AI Inference Server and Industrial Edge App Publisher (IEAP) → Industrial Edge Management (IEM), I would investigate the network connection, proxy configuration, and server-side logs before assuming the file size is the problem.


I'd troubleshoot the two upload paths separately.


1. AI Inference Server — upload stuck at 100%

The progress bar reaching 100% does not necessarily mean the pipeline has been imported successfully. The server may still be processing or validating the uploaded package.

Check the following:

  • Validate the ZIP package: Ensure it was generated correctly using the Industrial AI SDK and contains the required files, including pipeline_config.yml and runtime_config.yml.
  • Check the package integrity: Try importing a smaller, known-good pipeline package. If that works, investigate the larger package and its contents.
  • Check server-side logs: Look for errors during package import, validation, or extraction.

Siemens documents errors such as MD20013 (invalid ZIP header) and MD20014 (missing mandatory files) in the AI Inference Server troubleshooting guide.


Documentation: AI Inference Server API and documentation


2. IEAP → IEM — upload stuck at 30%


Your screenshot shows the operation getting stuck around “Preparing app file - downloading image.” I would first investigate how IEAP accesses the Docker images and communicates with IEM.

Check these items:

  1. Docker images: Verify that all container images referenced by the application are available through the configured Docker Engine and can be accessed successfully.
  2. Network and proxy: If your organization uses a corporate proxy, VPN, or firewall, check whether it interferes with communication between IEAP and IEM. IEAP supports proxy configuration for its IEM connection.
  3. Available disk space: Check free space on the development machine and the IEM host, particularly if the application contains large container images.
  4. Authentication: Disconnect and reconnect IEAP to IEM, then retry the upload. IEAP's authenticated session token expires after two hours of inactivity.
  5. IEM logs: Ask the IEM administrator to check server-side logs at the time of the failed upload.

Siemens documents the IEAP upload workflow and explains how the publisher uses the configured Docker Engine and connects to IEM.


3. Run these isolation tests

I would perform these tests in order:

Test

What it helps identify

Upload a small, known-good application or pipeline

Whether the issue affects all uploads or only particular packages

Retry using a different network, if permitted

Whether a proxy, firewall, or network connection is involved

Export the IEAP logs using its log-export function

Whether the publisher reports an upload or packaging error

Check IEM logs during the failed upload

Whether IEM receives the upload and fails while processing it

Compare the results with another development machine

Whether the issue is specific to the local environment

IEAP provides both Error and Trace logs that can be exported for troubleshooting.


My recommendation

Because both upload paths fail, I would not focus exclusively on the 300 MB ZIP or the 1 GB application package.

Start by checking the IEAP logs and IEM logs, then test a small known-good package. This should help distinguish a local packaging problem from a network or server-side issue.

One question that would help narrow this down: Does the upload fail when you use a different computer on the same network, or does it work from another computer? That result would help determine whether to focus first on the local environment or the shared network/IEM infrastructure.


Hope this helps.

answered