meaning: connect failed. SAPup> Process with PID 16231 terminated with status 232 at 20120717235636! Yes, during as part trouble shoot i tried follwoing sap notes 400241 and fixed the paswprd with brconnect for SAPSR3SHD as follows,, Step 1. exqadm 30> brconnect -u system/manager -f chpass -o SAPSR3SHD -p SAP. I was using my email as the username, which was not correct. I needed to use my "username". But since the portal allows me to login with my email, I thought that was my 'username'. We have setup coauthoring on a canvas app as per the Microsoft Doco and some of our users can access the canvas app using their email and access token and others cant and get the message "Invalid username or password. Please try again." All users have access to the repository, branch and folders that the canvas app resides in. By default, Oracle no longer supports case-insensitive password-based authentication; only the new password versions (11G and 12C) are allowed. The case-insensitive 10G password version is no longer generated. If the following conditions are true, then you may have accounts that are prevented from logging into the database after upgrading to 12.2: Solution: We need to reset the password for asmsnmp user. ASMCMD> lspwusr Username sysdba sysoper sysasm SYS TRUE TRUE TRUE ASMSNMP TRUE FALSE FALSE ASMCMD> orapwusr --modify asmsnmp Enter password: ******** ASMCMD>. Now try to promote the asm instance, using the password of asmsnmp which we set from the asmcmd prompt. I can share between 2 Windows 10 machines, that works not so between 10 and 11. Using the same Microsoft account (admin) on both machines. Was hoping to move some major data from old machine. The login screen complains invalid user ID or password before you enter anything. I can login to the account on ms site so.i know user and password are An underscore (_) is permitted anywhere in the user name, including at the beginning or end of the name. When creating a group, the number sign (#) can be used as part of the group's name. However, the email address you create for a distribution group or shared mailbox cannot use the # sign. jiNS.

invalid username or password