A user logs in to the Web Interface and no longer sees the payroll application while other users are able to continue working. What should the administrator do?

Ingrid P.Jun 26, 2026

D is your answer. When only one user loses visibility of an application that others can still access, that is a permissions issue isolated to that account, so checking the user's application permissions in the Access Management Console is exactly the right place to start, since infrastructure problems like a broken XML Service or a bad Local Host Cache would affect everyone, not a single user.

Viktor S.Jun 22, 2026

D is the only answer that makes sense here. If one user cannot see an app that everyone else can, that is a permissions problem by definition, not a server or cache issue, and you fix it in the Access Management Console where you control which users or groups are enumerated for each published application.

Ola B.Jun 26, 2026

When one user loses access to an app in the Web Interface while everyone else is fine, the first thing I go after is the Web Interface server itself, specifically IIS. My thinking is that IIS can get into a bad state on a per-session or per-connection basis, and a targeted restart clears out whatever stale session data or application pool hiccup is causing that one user to get a blank or missing app listing. I have reproduced this exact scenario in my home lab running CPS 4.0 on Server 2003, and a quick iisreset brought the missing app right back without touching any permissions or zone settings. Spin up a Web Interface install in a VM and break it intentionally by letting an app pool go into a stopped state, and you will see for yourself how one user can lose visibility while others stay completely unaffected.