Brand:

• AMX

Affected Products:

• CloudworX Manager Desktop (v1.03.0.205)

Summary:

• When attempting to launch CloudworX Manager Desktop for the first time, the application fails to open and displays a critical error message: "Unable to Start Application.  There was an error starting dependent services. The Cloudworx application will now quit."
   
• Even after executing a clean installation - manually purging leftover application directories across ProgramFiles, ProgramData, and user profile spaces the initialization failure persists.  Investigation has isolated this issue to a local network socket conflict: the underlying application core service cannot bind to its required system communication port (TCP Port 32000) because another background process or service on the host computer is already listening on that same address.

Troubleshooting:

• To confirm a port binding conflict and locate where the application logs reside:

1. Locate the Correct Application Logs:
   Contrary to looking in C:\ProgramData\, CloudworX Manager writes its diagnostic runtime traces directly inside the active user's home profile:
   C:\Users\[username]\CloudworX Manager
    
2. Identify Binding Failures in the Logs:
   Open the log file and check for a socket initialization failure or port rejection error trace resembling:
   Could not bind to port 32000 for service coreapi
    
3. Verify Port 32000 Availability via Command Prompt:
   Open an elevated Command Prompt window and execute the following network statistics utility to map active port usage:
   
   netstat -aon | findstr "32000"
   
   If the command returns an active state line, look at the number listed at the far right of the output.  This value represents the Process Identifier (PID) currently hogging the socket connection.
    
4. Kill the Conflicting Process:
   Open Task Manager, navigate over to the Details tab, and sort the list by the PID column. Highlight the task matching the conflicting PID discovered via the network lookup tool and click End Task.
    
5. Relaunch Manager:
   Once the blocked socket path is clear, relaunch the CloudworX Manager Desktop executable.  If it still struggles to launch immediately following clean environment installations, verify through the Windows Control Panel that the host machine has .NET Runtime v3.1 (or higher) actively deployed to satisfy local dependencies.