Microsoft 365 OneDrive Android (OxygenOS 13.1) login fails with WebView / Error 2604
On OneDrive Android app, login through Microsoft 365 work / corporate profile fails and always ends up with either blank screen or "No Internet connection" error 2604. Here's the details: Device & Environment: Device: OnePlus 8 Pro (IN2023) OS Version: OxygenOS 13.1 (build IN2023_13.1.0.591(EX01)) Android System WebView Version: 142.0.7444.102 App Affected: OneDrive (latest version from Google Play, 26th Nov 2025) Network: Wi-Fi / Cellular (both tested) VPN/ Private DNS / AdBlockers: Disabled Problem Description: Attempting to log in to OneDrive using a corporate/work Microsoft 365 account: The login screen either shows a blank white screen or fails immediately with Error 2604: “No network”, despite internet connectivity being functional. Logging in with the same credentials in Chrome works, confirming network is not the issue. Issue persists after clearing app data, reinstalling OneDrive, updating Chrome, updating Android System WebView, and ensuring all app permissions and background data settings are correct. Steps to Reproduce: Start with OnePlus 8 Pro (IN2023) running OxygenOS 13.1 Ensure Android System WebView is version 142.0.7444.102 Install latest OneDrive app from Google Play Open OneDrive and attempt to log in with corporate/work Microsoft 365 credentials Observe blank screen or error 2604 Expected Behavior: OneDrive should allow login with corporate Microsoft 365 account Embedded WebView authentication should complete successfully Account token should be saved for ongoing use Additional Notes: Problem appears specific to embedded WebView login on this OS/device combination Likely a systemic issue affecting Microsoft 365 apps relying on WebView for login flows on OxygenOS 13.1 Logging in to a personal outlook.com microsoft account works normally. Hence, it seems to be tied to the WebView failure. Is there any fix to this?
SQL Server account locked out and password did not match?
Hi We have this situation that a SQL Server account has been having two different login failures recently. The errors appear in the SQL Server log without much details. Wonder if any one had encountered the same situation and if it had been resolved? The two different error messages are: 1. Login failed for user 'sql_account_name'.Reason: The account is currently locked out. The system administrator can unlock it. [CLIENT: ip_of_another_computer] 2. Login failed for user 'sql_account_name'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>] Note: I replaced the actual account name and ip with sql_account_name and ip_of_another_computer respectively. I found a query that displays the user account SQL agent jobs run under, but I did not see this SQL account. Also, I checked linked servers, but did not see this account. Furthermore, I checked Windows services of the two computers in the error messages, but I did not see that SQL account. I did look Windows task scheduler, but do not think we can use SQL account as run under for a task. Any idea or insight? ThanksLesson Learned #515:Recommendations for Troubleshooting - Login failed for user 'XXX'. (18456)
During a recent support case, a customer encountered the error: pyodbc.InterfaceError: ('28000', "[28000] [Microsoft][ODBC Driver 18 for SQL Server][SQL Server]Login failed for user 'XXX'. (18456) (SQLDriverConnect); ") using a Python code. Following, I would like to share my lessons learned to fix this issue. The error code 18456 is typically caused by login issues, such as incorrect or missing credentials, rather than connectivity or networking problems. In our investigation, we identified the root cause and suggested recommendations to prevent and resolve similar issues. Root Cause The application was configured to retrieve the database server and host name from environment variables. However: Missing Environment Variables: One or more variables were not set. Default Value Misconfiguration: The code defaulted to a hardcoded value when variables were missing. For example, the server defaulted to "localhost", which was not the intended database server. As a result, the application attempted to connect to an unintended server with incorrect or missing credentials, leading to the Login failed error. Recommendations 1. Validate Environment Variables Always validate critical environment variables like server, username, and password. If a required variable is missing or empty, the application should raise an explicit error or log a clear warning. 2. Avoid Misleading Defaults Use placeholder values, such as "NOT_SET", as defaults for critical variables. This approach ensures that misconfigurations are immediately visible and do not silently fail. 3. Log Connection Details Log critical details like the server and database being accessed. Ensure this information is included in application logs to make troubleshooting easier. Avoid logging sensitive information such as passwords. Python Solution I was thinking how to improve the Python code, implementing a validation of environment variables, handle errors and log critical connection details: import os def get_env_variable(var_name, default_value=None, allow_empty=False): """ Retrieves and validates an environment variable. :param var_name: The name of the environment variable. :param default_value: The default value if the variable is missing. :param allow_empty: If False, raises an error for empty variables. :return: The value of the environment variable or default_value. Example: server = get_env_variable("DB_SERVER", default_value="NOT_SET") """ value = os.getenv(var_name, default_value) if value is None or (not allow_empty and (value.strip() == "" or value.strip() == "NOT_SET" or default_value is None)): raise ValueError(f"Environment variable '{var_name}' is required but not set.") return value
Error with Login
Hello SharePoint Community! Question for you all. I have access to a few different SharePoint accounts for various clients, and I keep running into issues loading the apps when I'm switching between different accounts. This is the latest error message that I've been getting when I try to open the Word application on my computer. Access to the web version is just fine. Does anyone have a workaround?
Surface Hub 2s Microsoft Teams Error code caa 90014
Hi all, Anyone in here encounter this Microsoft Teams problem on your Surface Hub after performed Windows update on 24th Nov 2021. Any idea what happened? I have tried to recovery the Surface Hub, but fail to get rip off this issue. And I tried to use other device account on the Surface Hub, and nothing change. If anyone here resolved this issue, please help. Thank you very much.No puedo suscribirme a MS Teams Free
Hola, Necesito ayuda para borrar una organización que creé en MS Teams en su momento. Me comuniqué con el soporte técnico telefónico y me derivaron acá. En este momento no puedo loguear ni suscribirme a MS Teams Free. Mi suscripción es Office 365 Hogar por lo que no estoy usando ningún mail laboral o educativo. Esto ocurre cuando intento suscribirme. Y esto cuando intento loguearme Básicamente no puedo usar MS Teams de ninguna manera. Necesito ayuda para poder solucionar este issue. Saludos y gracias.
Stuck on Teams mobile app "We are signing you in, please wait..."
Hello I am having an issue with the Android Teams app since Friday 13 of November. I needed to reinstall the app and since then I cannot login anymore. Once I enter my username and select the Account it open the below page and remains there indefinetly. I h https://answers.microsoft.com/en-us/msoffice/forum/all/stuck-on-teams-mobile-app-we-are-signing-you-in/8196f2fb-ab61-4240-8ca1-5752ce6e79fdUnable to log into Teams Desktop App - macOS Mojave
I have been unable to log into the Teams desktop app on macOS 10.14.5 (and for many earlier versions of Mojave). The app starts and asks for my email address. I enter it and it asks to select a certificate. If I either cancel or choose one it still fails. This error is presented at the bottom: desktop-54d39932-dafe-4ca7-b90e-0c959948b078 Error code - 2:-1001 There's a more permanent way to sign in to Microsoft Teams. If you're having trouble completing the process, talk to your IT admin. There is no response from the app when clicking "signing out". If I right click on the dock icon and choose "Sign Out", similarly nothing happens. If it matters, our tenant is in a hybrid environment with our AD on premises.
