ADP Error Code 100 | Fix Login And Sync Problems

Code 100 tends to pop up right when you’re trying to view a pay statement, punch in, or submit payroll. It can show on desktop browsers, inside the mobile app, or after a single sign-on button sends you to ADP. Most of the time, you can clear it with a few targeted checks.

This guide starts with fast fixes you can run in minutes, then moves to deeper checks for repeat failures. It’s written for employees using MyADP or Workforce Now, plus admins logging in through company-facing portals.

What ADP Error Code 100 Means In Plain Terms

Most people meet this code during login. You enter your user ID and password, tap Sign In, and the site or app refuses to start a session. “100” acts like a catch-all for “the login flow didn’t finish,” not a single-cause message you can decode with certainty.

Here’s a clean way to frame it: when the sign-in flow breaks, it’s usually breaking in one of three places.

• Browser data breaks the session — A bad cookie, an old cached script, or blocked storage stops the page from finishing authentication.
• Network blocks the request — A VPN, captive portal, strict Wi-Fi, or company filter blocks the call the login page needs to finish.
• Account rules stop access — Lockouts, missing registration, or SSO settings prevent the account from being accepted.

ADP Error Code 100 Fix Steps That Work

Start here even if you suspect an outage. These steps clear the most common causes without risky changes. Run them in order, then try logging in after each one so you know what fixed it.

Fast fixes you can do in two minutes

1. Try a private window — Open an Incognito or Private tab, go to the login page again, and sign in. If it works there, cookies or cached files are the usual cause.
2. Switch networks — Turn off Wi-Fi and use mobile data, or swap to a different Wi-Fi. Many “100” errors are a blocked or flaky connection.
3. Disable VPN and blockers — Pause any VPN or strict content blocker for the login attempt, then reload the page.
4. Restart the device — Power off, wait ten seconds, then power back on.

Browser cleanup that fixes most desktop cases

1. Clear site data for ADP — In your browser settings, remove cookies and site data for the ADP sign-in domain, then sign in again.
2. Update the browser — Install the latest version of Chrome, Edge, Firefox, or Safari, then retry.
3. Allow cookies for sign-in — If you block all cookies, create an exception for the ADP sign-in site so the session token can be stored.
4. Turn on JavaScript — If scripts are disabled, the login page can load but never finish authentication.

Mobile app resets that help on iOS and Android

1. Force close the ADP app — Swipe it away from recent apps, then reopen.
2. Update the app — Install the newest build from the App Store or Google Play, then try again.
3. Reset app data — On Android, clear cache and storage for the app. On iOS, uninstall and reinstall to reset local data.
4. Check device time settings — Set date and time to automatic. Wrong time can break security tokens.

ADP Error Code 100 On Sign-In And Mobile App Triggers

Once you’ve tried the quick fixes, match what you see to what’s likely happening. These patterns point to the next best move instead of random guessing.

Portal mix-ups that look like an error

ADP has several login entry points. MyADP, Workforce Now, and RUN are different doors. If you use the wrong one, the page may accept your details, then fail with a generic code because your account isn’t meant for that portal.

• Use the link from your employer — Many companies provide a specific bookmark or SSO button that routes you to the right tenant.
• Confirm you’ve activated the account — If you never completed registration with your company’s code, you may need to register first.
• Try the MyADP login page — MyADP explains registration and activation steps when your employer provides access.

If you’re an employee and you’re missing a registration code, ADP points employees back to their company payroll or HR team for access setup. You can keep this page handy: ADP login help.

Account Access Checks That Matter For Employees And Admins

When browser and network fixes don’t help, shift to access rules. This is the part that feels personal: coworkers can log in, you can’t. In many cases, the account is blocked, not broken.

Employee-side checks

1. Reset the password from the portal — Use the official “Forgot Password” flow on the same portal you normally use, then sign in with the new password.
2. Confirm your user ID format — Some companies issue user IDs that look like email, others don’t. Use the format your employer provided.
3. Wait after repeated attempts — If you tried many times in a row, pause for a few minutes before trying again so you don’t keep tripping risk checks.
4. Ask payroll or HR to reset access — For many employee accounts, only the employer team can reset or reissue access.

Admin-side checks

Admins often see Error Code 100 during security registration, certificate selection, or SSO routing. If your company uses a security role like a Security Master, that person may need to step in.

1. Confirm your role assignment — If your account lost an admin role, the portal may refuse the session even with the right password.
2. Check certificate selection — For Netsecure-style logins, choosing an expired certificate can block access. Use the current certificate or reach your security admin.
3. Validate single sign-on setup — If your org uses Microsoft Entra ID, confirm the user is assigned to the ADP app and the sign-in flow still matches your configuration.

MFA loops and device trust checks

If you use text codes, an authenticator app, or an email one-time passcode, Code 100 can show up when the second step never finishes. It happens when a popup is blocked or the app hands you back to the browser without completing the redirect.

• Allow popups for the sign-in page — Allow popups, then retry the login so the verification screen can open.
• Finish verification on the same device — If you start on a laptop, complete the MFA prompt on that flow before switching to phone.
• Re-enroll the factor if it’s out of date — Ask your payroll or HR team to reset MFA if you changed phone numbers or lost your device.

For SSO admins, Microsoft’s Entra tutorial for ADP lays out the integration flow and common configuration steps. See: ADP federated SSO in Microsoft Entra ID.

Network And Device Issues That Cause Repeat Failures

If adp error code 100 keeps returning across browsers and devices, treat it like a connectivity or device rule issue. This section helps you spot hidden blockers between you and the login servers.

Wi-Fi traps that break login

• Sign in to the Wi-Fi first — Public Wi-Fi often needs you to accept terms on a splash page. Open any site first, accept the prompt, then return to ADP.
• Turn off private DNS for the test — On some phones, strict DNS settings can block login services. Switch back to default DNS, then retest.

Device checks that affect authentication tokens

• Set date and time to automatic — Security tokens rely on accurate clocks. A device that’s minutes off can fail token validation.
• Free up storage — Low storage can stop apps from writing secure session data.
• Update the operating system — Older OS builds can have outdated network libraries that struggle with modern sign-in flows.

When To Escalate And What To Share So It Gets Fixed Faster

Sometimes the fix is outside your reach. Employees can’t unblock accounts or change company access policies. Admins may need to involve their ADP client team for backend checks. You’ll get better results when you bring a short, clean set of facts.

Details to capture before you reach out

• Write down the exact portal — MyADP, Workforce Now, RUN, or a company SSO link.
• Note the time and time zone — Include the minute it happened, not just the day.
• Record the device and browser — Phone model, OS version, browser name and version.
• List what already worked or failed — Private window test, network swap, reinstall, password reset.
• Grab a screenshot — Make sure it shows the full code and the browser URL bar if possible.

If you’re an employee, the MyADP login page points users to their employer for registration codes and account resets: MyADP login.

If you’re a company admin and you need a direct contact path, ADP lists customer service options on its contact page: ADP customer service.

One-page Checklist Before You Try Again

This recap keeps you from repeating the same dead-end steps. Start at the top, stop once the login works, and note what changed.

1. Confirm the correct login door — Use the portal link your employer provided, not a random search result.
2. Run a private window test — If it works, clear ADP site data on your main browser.
3. Swap networks — Try mobile data or a different Wi-Fi, then retry the login.
4. Pause VPN and blockers — Disable VPN and strict blockers for the test.
5. Update browser or app — Install updates, then reboot the device.
6. Reset app data — Clear cache/storage on Android, reinstall on iOS.
7. Check device time — Set date and time to automatic, then retry.
8. Use password reset once — Reset through the portal, then sign in with the new password.
9. Stop after repeated failures — Wait a few minutes before another attempt to avoid lockouts.
10. Escalate with a clean note — Share portal, time, device, and a screenshot with payroll/HR or your security admin.

If you still see adp error code 100 after the checklist, the fastest path is often an account-level reset by your employer team or a tenant-side review by your admin group.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback