PJeOffice Is Not Available: How to Fix It on Windows, Mac, and Court Portals
When a PJe portal reports that the PJeOffice application is not available, first prove whether the desktop app is running, the certificate is visible, and the local browser request reaches the app. Reinstall only after the faster checks isolate an installation failure.
Start the quick checkCheck these items before reinstalling PJeOffice
Perform the checks in order and retry the portal once after each meaningful change.
- Confirm PJeOffice Pro is open and its tray/menu icon is present.
- Open the application and refresh the certificate list; note whether the expected certificate appears.
- Close duplicate PJeOffice windows or old signer instances.
- Close the affected PJe tab, reopen it from the court's official website, and initiate authentication again.
- If using an A3 token, disconnect it, wait about ten seconds, reconnect it, wait for recognition, and refresh certificates.
- Check official court notices or ask a colleague whether the portal is failing for multiple users.
- Record the exact error message and the last step that worked.
Which PJeOffice stage is unavailable?
The word unavailable can describe different failures. The correct repair depends on the last successful stage.
| Stage | Test | Meaning if it fails |
|---|---|---|
| Application launch | Open PJeOffice Pro directly | Wrong build, incomplete installation, permissions, or duplicate process |
| Certificate detection | Refresh certificates inside the app | A1 configuration, A3 driver, PKCS#11, device, or architecture issue |
| Local connection | Initiate PJeOffice authentication from the portal | Browser-to-local-app request is not reaching the running service |
| Court service | Check official notices and another authorized workstation | Remote portal or court infrastructure may be unavailable |
| Account authorization | Reach the portal but fail access to an account or case | Court account, role, certificate registration, or case permission issue |
Fix the PJeOffice unavailable error step by step
Move from reversible local checks to more disruptive repair actions.
- 1
Start one PJeOffice Pro instance
Exit the old signer and any duplicate Pro process. On Windows, check the tray before opening another copy. If the process state is unclear, restart the workstation and launch only Pro.
- 2
Confirm the correct build
A wrong architecture can prevent launch or driver loading. Check Windows 32/64-bit, Mac Intel/Apple Silicon, or Linux architecture against the installed file.
- 3
Confirm the certificate locally
If the certificate is absent inside PJeOffice, the portal connection is not the first problem. Use the certificate guide before continuing.
- 4
Restart the portal flow
Open the court site from its official page, start a new authentication request, and approve any local prompt. Avoid repeatedly refreshing an old failed tab with an expired request.
- 5
Review local security without disabling it
A firewall, endpoint security policy, or managed browser rule may block a local connection. Use organizational support to review the specific event; do not disable protections globally.
- 6
Update only from the official source
If the installed edition is old or damaged, close it and install the currently listed Pro build from the verified download page.
PJeOffice cannot repair a court outage
A working local signer may still be reported as unavailable when the remote service is degraded.
Check the official court status before changing a working workstation
If multiple users cannot authenticate, the portal is unreachable, or official notices report maintenance, wait for the court service or follow its support instructions. Reinstalling PJeOffice during a remote outage adds local risk without changing the unavailable service.
If only one workstation fails, compare it with a working workstation: PJeOffice version, operating system, certificate source, browser flow, and network/security policy.
When reinstalling PJeOffice is appropriate
Reinstall after evidence points to the application files or an incompatible edition.
A reinstall is reasonable when PJeOffice Pro cannot launch, files are missing, the installed architecture is wrong, an upgrade left conflicting editions, or the app is clearly older than the current official build. Close and remove the incompatible edition before installing the correct file.
A reinstall is less likely to help when the certificate authority driver cannot see the token, the court portal is down, the account lacks authorization, or endpoint security is intentionally blocking the local request. Those failures belong to a different component.
Information to collect for support
Record the operating system and architecture, PJeOffice version, exact error, certificate type (A1 or A3), token model when relevant, court portal, time of failure, and which stages passed. Do not include passwords, PINs, certificate files, confidential documents, or unnecessary personal case data.
A separate Java update is not the normal fix
PJeOffice Pro contains its own tested Java runtime.
Focus on the failing component
Installing system Java does not replace the runtime embedded in PJeOffice Pro. Check application state, architecture, certificate driver, PKCS#11, local connection, and court availability instead.
PJeOffice unavailable questions
Short answers for common failure patterns.
Why does PJe say the PJeOffice app is not available?
The app may not be running, a duplicate or old instance may be active, the local browser request may be blocked, or the court service may be unavailable. Identify the last successful stage before reinstalling.
Should I restart PJeOffice or the computer?
Exit all PJeOffice instances first. If the tray or process state is unclear, a workstation restart is a reasonable reversible check before reinstalling.
Will reinstalling fix a missing certificate?
Not necessarily. A missing A3 certificate often indicates a device driver, PKCS#11, USB, architecture, or certificate-validity issue.
Can antivirus block PJeOffice?
Endpoint security or organizational policy can block a local connection, but do not disable it globally. Ask authorized support to review the specific event and official file.
How can I tell if the court is down?
Check official court notices, test the official portal, and ask whether other authorized users are affected. A widespread failure points away from one workstation.