SqlException: A connection was successfully established with the server, but then an error occurred during the login process.

Q: SqlException: A connection was successfully established with the server, but then an error occurred during the login process.

Question: How do you resolve, SqlException: A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) Answer: If you are developing in Asp.Net Core, you will have to include User ID="YourDatabaseUserName"; Password="YourPassword" in the connection string. See another article <a href="https://www.ernestech.com/articles/details?title=Login-failed-for-user-.-%28Microsoft-SQL%2C-Error%3A-18456%29%26id%3D725" target="_blank" rel="noopener">related to SQL Server Login Failure Here.</a>

Question

Accepted Answer

Question: How do you resolve, SqlException: A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)

Answer: If you are developing in Asp.Net Core, you will have to include User ID="YourDatabaseUserName"; Password="YourPassword" in the connection string.

See another article related to SQL Server Login Failure Here.

SqlException: A connection was successfully established with the server, but then an error occurred during the login process.

Gosh said:

SqlException: A connection was successfully establ

SqlException: A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.)

Connection Timeout Expired. The timeout period el

Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake

SQL 0x80004005 Description: "Cannot continue the

SQL 0x80004005 Description: "Cannot continue the execution because the session is in the kill state"

The type or namespace name 'IHttpContextAccessor'

The type or namespace name 'IHttpContextAccessor' could not be found (are you missing a using directive or an assembly reference)

10964 ExecStop=/usr/sbin/corosync-cfgtool -H --fo

10964 ExecStop=/usr/sbin/corosync-cfgtool -H --force (code=exited, status=1/FAILURE)

The INSERT statement conflicted with the FOREIGN K

The INSERT statement conflicted with the FOREIGN KEY constraint "FK_tableName_key". The conflict occurred in database "Database Name", table "dbo.tableName", column 'id'

An error occurred during the compilation of a reso

An error occurred during the compilation of a resource required to process this request. Please review the following specific error details and modify your source code appropriately

Error 0xc0202009: Data Flow Task 1: SSIS Error Cod

Error 0xc0202009: Data Flow Task 1: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005

Apex 7000 Cash Acceptor Wont show up on COM Port (

Apex 7000 Cash Acceptor Wont show up on COM Port (shows as Other Devices "FT232R USB UART")

Sql Server Error: the log for the database is not

Sql Server Error: the log for the database is not available

Microsoft SQL Server, Error: 258

Microsoft SQL Server, Error: 258

How to Scaffold or Generate a Custom Identity Logi

How to Scaffold or Generate a Custom Identity Login UI in Asp.Net Core 3.1

The instance of entity type 'IdentityUserLogin<str

The instance of entity type 'IdentityUserLogin<string>' cannot be tracked because another instance with the same key value for {'LoginProvider', 'ProviderKey'} is already being tracked

Can not connect to SQL server in docker container

Can not connect to SQL server in docker container from another docker container hosting asp.net core 3.0 application