[ISS Support Case] Galaxy Cannot Connect
Last updated: October 17th, 2025Description
Galaxy Cannot Connect: Cannot connect to galaxy. See logger for details. Additionally, when attempting to connect to the SQL Server via SQL Server Management Studio (SSMS), it prompts for a server name. Troubleshooting Steps Performed: 1. Verified SQL Server Status Confirmed that SQL Server service was running on the local machine. Identified the correct SQL Server instance name via: SQL Server Configuration Manager ? SQL Server Services Verified that the expected instance was present and running. Attempted to connect via SSMS: Tested using localhost, MACHINENAME, and MACHINENAME\INSTANCE formats. Ensured appropriate authentication was used (Windows Authentication preferred). 2. Tested Network Port Accessibility Ran PowerShell command to verify port 1433 (default SQL Server port) was accessible: powershell Copy Edit Test-NetConnection -ComputerName localhost -Port 1433 Output confirmed whether port was open and responding. Also tested with telnet: bash Copy Edit telnet localhost 1433 (Confirmed telnet was installed if not already present via dism command.) 3. Checked for SQL Server Listening on Port Ran command to confirm SQL Server was actively listening on port 1433: bash Copy Edit netstat -an | find "1433" Further validated which process was using the port: bash Copy Edit netstat -ano | find "1433" tasklist | findstr Confirmed SQL Server process was listening on the correct port. 4. Reviewed AVEVA System Management Diagnostic Logger Opened SMDiagnostics Logger to investigate detailed errors related to: SQL Server connectivity Galaxy Repository issues Authentication or permission errors Looked for recent error entries around the time the issue occurred. 5. Restarted Services Restarted the following services: SQL Server (INSTANCE) All ArchestrA platform-related services Retried launching the IDE and reconnecting to the Galaxy.
- Author: Kevin Modlin
- Published: October 17th, 2025
Details:
| Product: Application Server |
| Version: 2023 R2 |
| Solution: [Solution is visible below when you're logged in and have a current subscription] |
| Date Created: | 04/22/2025 |
| Case: | 97700 |
Give feedback about this article
Recommended articles
[ISS Support Case] Synchronize Views is not working correctly in the IDE
Read More[ISS Support Case] Historian Data Gap On Appengine Failover In SP Version 2023 R2 P1
I am seeing an issue with SP2023 R2 P1 related to appengine failovers. When I cause an appengine failover, data (primarily analog) has a gap in the trend until the data changes. Sometimes the gap stays but sometimes the gap is "filled" in for some reason. I'm having a bit of a consistency issue trying to replicate this problem. Every time I cause a failover, the results are slightly different but I do see bad results. To demonstrate this, I created two videos to show what I'm seeing. If someone can create a problem ticket and reach out to me, I can forward the videos to InSource to show what I'm seeing.
Read More[ISS Support Case] MQTT setup crashes OCMC
MQTT server - CDP 2023 check encryption/validate security - no issue port validates enable user identity/try to bring certs in shuts down OCMC nothing in OCMC logs event viewer shows an app crash for mmc with cfg_mqtt_plctype1.dll as the faulting module advised repair after conferring with aveva - called client to discuss and confirm New SR960455477 (requesting) Log file Config Files Do Not upgrade Stay @ the same version of CDP Call in on 9/12/2024 No success on the MQTT server with the antivirus turned off, and it was even worse this time. Could not hook to AWS server. Proceeded to step 2, entered certificate in case it needed to log in to AWS server, but the OCMC shut down. Restarted OCMC acted strange, restarted computer. OCMC behaved normally after, but still no success with MQTT. Wants a call back whenever you're available, doesn't have to be tonight. CDP shows 2023
Read More