Troubleshooting First-Time Slice Login Failures on Restricted Networks

This guide documents a repeatable troubleshooting approach for cases where Slice cannot complete the initial sign-in flow from a restricted external or corporate network, even though the same environment may open successfully in a standard web browser.

When to use this guide

Use this guide when a user reports that Slice fails during first-time login or after profile reset, especially when the issue occurs only from a specific network location.

• Slice shows Failed to connect to the Arc server.

• Logs or browser output show arcSSOComplete is not defined.

• Excel formulas remain at #Connect.

• The application can still be reached from Chrome, Edge, or another standard browser.

Summary of the issue

The failure is commonly caused by the embedded browser used by Slice being blocked by local security controls, proxy rules, or network policy. In these cases, browser-based access appears healthy, but the Slice sign-in flow cannot complete because the embedded browser process does not receive or return the expected SSO callback.

Technical background

Slice Server Explorer uses an embedded browser component to display the login window. That component runs as a separate Windows process named eowp.exe.

eowp.exe is the EO.WebBrowser helper process used by the embedded login window inside Slice. It is separate from excel.exe and separate from standard browsers such as chrome.exe or msedge.exe.

In restricted environments, outbound access may be allowed for approved browsers but denied for lesser-known application processes. If eowp.exe is blocked from reaching the Cognos/IdP endpoint or the Arc endpoint, the login page may not complete correctly and the JavaScript callback used to finalize authentication may never run.

Typical symptoms

• First-time login fails in Slice from one location but works from another.

• The login prompt appears, but the session does not complete.

• Slice reports connection failure after credentials are entered.

• JavaScript-related callback errors appear in logs or diagnostics.

• Existing cached sessions may work, while fresh authentication fails.

Likely cause

The embedded browser process eowp.exe cannot reach one or more required authentication or application endpoints. This prevents the SSO flow from returning the token or completion event that Slice expects.

Troubleshooting steps

1. Confirm the scope

• Test whether the same environment opens successfully in a standard browser.

• Confirm whether the problem is limited to one workstation, one network, or first-time login only.

• Check whether the issue disappears when using a different connection path or a different network.

2. Check for the known indicators

• Failed to connect to the Arc server

• arcSSOComplete is not defined

• #Connect in workbook formulas after attempted login

3. Use Namespace mode as the immediate workaround

If Gateway or SSO mode fails, switch the connection to Namespace mode and test again.

1. Open the Slice connection settings.

2. Select Namespace mode instead of Gateway or SSO mode.

3. Enter the namespace, username, and password directly.

4. Retry the connection.

This workaround is effective because the authentication flow does not depend on the local embedded browser process in the same way as Gateway-based sign-in.

4. Request network or security review

If SSO mode must be used, ask the internal IT or security team to verify that the required processes are permitted outbound access.

Ask the reviewing team to confirm that these processes can reach the required Cognos/IdP endpoint and Arc endpoint over the necessary ports, without relying on browser-only allow rules.

Resolution guidance

Apply one of the following based on customer constraints:

• Use Namespace mode as the preferred workaround when direct credentials are acceptable.

• Adjust proxy, firewall, or endpoint security rules so eowp.exe is treated as an approved outbound process for the required authentication and application destinations.

• Retest the login after any network rule change.

Verification

1. Launch Slice and start a fresh login.

2. Confirm the environment opens without the Arc connection error.

3. Confirm no callback error appears.

4. Open or refresh a workbook and verify formulas no longer show #Connect.

5. If possible, repeat the test from the previously affected network.

What to record in the ticket

• Whether the issue affected Gateway/SSO mode, Namespace mode, or both

• Whether the problem was location-specific

• Whether browser access worked while Slice failed

• Whether allowing eowp.exe resolved the issue

• Any relevant log excerpt, sanitized to remove names and host details

Recommended internal note

If Slice fails only during the embedded SSO flow and standard browser access still works, check whether eowp.exe is blocked by network or endpoint security controls. Use Namespace mode as a fast workaround while reviewing process-level allow rules.