Skip to content
TROUBLESHOOTING

Cannot Connect

Summary

The workbook or application cannot establish a connection to the expected server or environment, so publishing, subscribing, or related features do not work.

Symptoms

  • Connection status shows disconnected
  • A connect action fails immediately
  • A timeout or network-related error appears
  • Publish or subscribe features remain unavailable
  • The workbook worked previously but no longer connects

Likely Causes

  • Host name or port is incorrect
  • The target service is not running
  • A firewall or proxy is blocking the connection
  • Credentials or authentication settings are invalid
  • The workbook is pointed at the wrong environment

Quick Checks

  • Confirm the configured host and port are correct
  • Confirm the target service is running
  • Confirm you are on the expected network or VPN
  • Confirm the workbook is using the expected credentials and environment
  • Retry with a known-good connection configuration

Step-by-Step Diagnosis

1. Verify the connection settings

What to check: - The configured host name, port, and environment settings

How to check: - Open the workbook or add-in connection settings - Compare the values to a known-good configuration - Check for typos, outdated server names, or incorrect ports

Expected result: - The workbook should be configured to connect to the correct host, port, and environment

If not: - Correct the configuration and retry the connection

2. Verify the target service is available

What to check: - Whether the target server or service is running and accepting connections

How to check: - Confirm the service is running on the host - If you have a status page, admin UI, or service monitor, verify it is healthy - Compare against another workbook or client known to work

Expected result: - The target service should be up and reachable

If not: - Start or restart the service - Escalate to the system owner if the service is down

3. Verify network access

What to check: - Whether the current machine can reach the target over the network

How to check: - Confirm VPN access if required - Test from a known-good network if available - Check firewall, proxy, or endpoint security rules that may block the connection

Expected result: - The machine should be allowed to reach the target host and port

If not: - Connect to the required network or VPN - Update firewall or proxy rules as needed

4. Verify credentials or authentication

What to check: - Whether the configured credentials, token flow, or authentication settings are valid

How to check: - Re-enter credentials if applicable - Request a fresh token if your setup uses short-lived tokens - Compare authentication settings against a known-good client

Expected result: - Authentication should succeed and allow the session to connect

If not: - Correct the credentials or auth configuration - Retry with a fresh authentication flow

5. Verify the correct environment is selected

What to check: - Whether the workbook is pointed at the intended environment or deployment target

How to check: - Compare settings with another workbook that is known to work - Check labels, host names, and entity/environment identifiers

Expected result: - The workbook should target the same environment you intend to use

If not: - Change the environment configuration and reconnect

Resolution

Incorrect host or port

  • Update the workbook to use the correct host and port
  • Save the corrected configuration if appropriate

Service unavailable

  • Start or restore the target service
  • Confirm service health before retrying

Network blockage

  • Connect to the required VPN or network
  • Allow traffic through firewall or proxy controls

Authentication problem

  • Correct credentials or request a fresh token
  • Re-run the login or authentication workflow

Wrong environment

  • Repoint the workbook to the intended environment
  • Retest after reconnecting

Edge Cases

  • A workbook may connect successfully to the wrong environment, which looks like a data problem rather than a connection problem
  • A token may be valid only briefly and expire before use
  • Endpoint security tools can intermittently block local applications without a clear Excel-side error

Applies To

  • U Toolset
  • U Studio
  • Excel Add-in

Last Updated

2026-03-21