How to Fix OneDrive for Business Sign-In Error 5OBJN

Encountering the 5OBJN sign-in error in OneDrive for Business abruptly halts your ability to sync and access critical company files. This specific code indicates a breakdown in the authentication hand-off between your local Windows environment and Microsoft's Azure Active Directory services. Rather than a network outage, the application is actively rejecting the cached security tokens on your machine. To restore access, you must systematically clear the corrupted credential data and force the synchronization client to negotiate a fresh connection with the server.

Clear Stale Authentication Tokens in Windows

Windows Web Account Manager and the local Credential Manager often hold onto outdated session tokens, preventing the client from recognizing valid logins. Purging these specific records forces the system to request a new authentication token directly from the server.

• Access Credential Manager: Click the Windows Start menu, type Credential Manager, and hit Enter to launch the control panel applet.
• Navigate to Windows Credentials: Select the Windows Credentials tab, not the Web Credentials tab, to view your local system tokens.
• Remove Conflicting Entries: Scroll down to the Generic Credentials section. Look for any entries beginning with OneDrive Cached Credential Business or MicrosoftAccount:user=.
• Execute Removal: Click the drop-down arrow next to each relevant entry and select Remove. Confirm the deletion when prompted by the system dialog.
• Verification: Close the Credential Manager and launch OneDrive. The application should immediately prompt you to enter your email address and password, indicating the stale tokens are gone.

Rebuild the Office Identity via Registry Editor

If clearing the standard credentials fails, the corruption likely resides deeper in the Windows Registry where Office suite identities are stored. Deleting the specific identity folder clears misconfigured Single Sign-On (SSO) data without affecting your installed applications.

• Open Registry Editor: Press the Windows Key + R, type regedit into the Run dialog box, and click OK. Grant administrative privileges if prompted by User Account Control.
• Locate the Identity Key: Navigate through the left-hand folder tree to this exact path: HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity\Identities.
• Identify the Target Folder: Look for a subfolder within the Identities key that contains your business email address or an Azure AD Object ID string.
• Delete the Identity: Right-click this specific subfolder and select Delete. Do not delete the parent Identities folder itself.
• Verification: Restart your computer to ensure the registry changes initialize. Upon reboot, open your business sync client; it will generate a clean identity key upon your next successful login.

Execute the Client Reset Command

When the software's internal configuration state becomes desynchronized with the Windows operating system, a manual reset restores the application to its default parameters while preserving all downloaded data.

• Launch the Run Dialog: Press the Windows Key + R to open the execution window.
• Run the Reset Executable: Type %localappdata%\Microsoft\OneDrive\onedrive.exe /reset into the text field and click OK.
• Observe the System Tray: The cloud icon in your bottom-right taskbar will disappear entirely. This is the expected behavior as the background processes terminate.
• Restart the Client: Wait two minutes. If the icon does not reappear automatically, open the Start menu, search for OneDrive, and launch it manually to initialize the newly reset configuration.

Alternative: Disconnect and Reconnect the Work Account in Settings

When registry edits are restricted by your IT administrator, you can often bypass the error by completely severing the Windows-level connection to your organization's Azure Active Directory and re-establishing it.

• Open Account Settings: Press Windows Key + I to open Settings, navigate to Accounts, and select Access work or school from the left sidebar.
• Disconnect the Profile: Locate the listing that displays your company email address. Click on it, select Disconnect, and follow the prompts to remove the account profile from your PC.
• Reconnect: Click the Connect button at the top of the same page, enter your business credentials, and authenticate using your organization's multi-factor authentication method.
• Verification: Open your synchronization app. It will detect the newly established Windows account connection and automatically sign you in without generating the 5OBJN code.

Maintain Document Productivity with WPS Office During Sync Outages

WPS Office cannot change your Microsoft-side registry settings or resolve Azure Active Directory token errors. However, you do not have to halt your workflow while troubleshooting your connection. Your sync folder retains offline copies of your files, and you can use WPS Office to edit them independently of Microsoft's authentication servers.

Because WPS Office operates locally without requiring a Microsoft 365 license token, it bypasses the account lockout entirely, allowing you to meet deadlines while the primary cloud service is down.

• Locate Your Local Repository: Open Windows File Explorer and navigate to your offline directory, typically found at C:\Users\[Your Username]\OneDrive - [Company Name].
• Open Files Offline: Right-click your target .docx or .xlsx file, hover over Open with, and select WPS Office. The software handles native formats directly, ensuring your layout remains intact.
• Apply Document Edits: Utilize the WPS interface to update spreadsheets or draft reports. If you are reviewing contracts, use the WPS PDF tools to annotate or sign documents offline.
• Save and Queue for Sync: Save the file normally using CTRL+S. The modifications are written to your local drive. Once you resolve the 5OBJN code using the steps above, the client will automatically detect the updated timestamps and push your WPS-edited files to the cloud.

Frequently Asked Questions

Does resetting the sync client delete my local or cloud files?

No, executing the reset command only clears the application's internal configuration settings and interface preferences. All local files currently sitting on your hard drive remain completely untouched, and your cloud repository is entirely safe. Once you sign back in, the software simply verifies the existing files rather than downloading them again.

Why does this authentication failure only affect my business account?

The 5OBJN code specifically triggers due to token mismatches with Azure Active Directory, which governs enterprise and enterprise-level school accounts. Personal accounts utilize a completely different authentication infrastructure (Microsoft Account/MSA), which is why you might still be able to sign into a personal cloud folder on the exact same device that is blocking your work access.

How do I know if a firewall is blocking the connection instead of a token error?

To distinguish between a local token issue and a network block, attempt to log into the web version of the service through your browser. If you can successfully access your files via the web portal but the desktop application throws the 5OBJN code, your firewall is not the issue. The problem is definitively isolated to the local credential cache on your operating system.

Can I manually back up pending files before modifying the registry?

Yes, and it is highly recommended if you have files that have not yet uploaded. Before opening the Registry Editor, navigate to your sync folder in File Explorer. Look for files with a red X or a blue syncing arrow. Copy these specific files and paste them into a local directory outside the sync folder, such as your Windows Desktop or Documents folder, to ensure no data is lost during the identity rebuild.