I facing an issue on Microsoft Authenticator App it didn't work I got below error message
No network connection
Add account failed .Please check your internet connection and try again
now I can't login into all accounts that already I enabled the 2 Factor Authentication on them ! Does anyone faced that problem ?
Related
When I open my Website hosted by Firebase Hosting Google Chrome or my Antivirus program does not let me access the page but shows me an error message:
This is not a secure connection.
Hackers might try to steal your data from (website), for example, passwords, messages or credit card details.
Error code: NET::ERR_CERT_COMMON_NAME_INVALID
Any Ideas?
I solved it! I just had to exclude the www. in the url_launcher String and it will not display any SSL-Error.
I am trying to test my oracle datasource connection in websphere admin console. Though, I give the correct username and password, I am getting invalid username/password logon denied. I know there are several posts related to this. But, none of them solved my issue. I tried the following,
1. I am able to connect to the same environment in Toad with the same credentials.
2. I tried updating the password in admin console under Security->J2C authentication, still getting the same error.
3. After changing the password in console, restarted the server.
4. this is a standalone application, so there are no nodeagents to be restarted as mentioned in other posts.
5. Some posts online shows that this is a bug with Oracle. Need to connect with Oracle support team and get this fixed.
I have no clue, how should I proceed with this!! Any help would be greatly appreciated.
I created a db via app-data folder, migrated over to server explorer and tried to connect to it and I get
Cannot open database "abc" requested by the login. The login failed. Login failed for user 'xyz'. I came across this: [Cannot open database “test” requested by the login. The login failed. Login failed for user 'xyz\ASPNET'
I have two questions concerning the best answer.
Whenever I connect to ssms windows authentication is selected. So does windows authentication still matter if a db is created using visual studio?
Second is concerning this:
UPDATE: Ok, you're using integrated Windows authentication --> you need to create a SQL Server login for "xyz\ASPNET" on your SQL Server"
What does he mean by create a sql login for user "xyz"?
I thought the purpose of win authentication was so you didnt have to type login and pass to connect. You're automatically connected through windows. Right?
A few years ago I signed up as a LinkedIn developer, registered an application and received my Client ID and Secret.
Using OAuth2, when I attempt to get an access token I get an error message saying "OAuth2 access is denied."
I've checked all the settings in my developer account and cannot see anything wrong, so I don't know why access is denied.
RESOLVED: I discovered that if I untick all of the Default Application Permissions with the exception of "r_basicprofile", I no longer get the OAuth2 access denied error.
I've developed a website which connects to a SQL Server 2012 instance. This works fine in my development environment. However, when trying to deploy to a production environment, the page returns the following error:
Server Error in "/theapp" Application.
Invalid User Account
Description: an unhandled exception occured during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code
Exception Details: System.Data.SqlClient.SqlException: Invalid User Account
screen shot of stack trace
I am struggling to find any documentation regarding this on the Internet; is there anyone who might know where I can start looking for a resolution?
Thanks kindly!
Update (4/7/2016 # 3:18pm): The service account is a domain account which has correct permissions on the database. In addition, the same account is used by another website to connect to the same database, and this works fine.
Update (5/7/2016 # 10:16am): The only thing I can think of is something to do with the usage of LINQ to SQL queries within the application. Does this sound like a possible cause?
As the error says, the credentials you are using to connect to sql server are incorrect.
Make sure you are using correct credential viz. user name and password in your connection string. You can check it by logging on to sql server instance from these credentials.
If you are using integrated security, i.e. windows authentication, verify if the user have given permission on sql.
When you pass Windows authentication through a website, the identity of your app pool is the user credentials that are supplied. Be sure your app pool for the site is set to use the same user as you expect in the identity of the app pool. Also, be sure integrated security is set to SSPI, not true, in the connection string.