Ошибка 258 sql server

Симптомы

При попытке войти в систему или подключиться к экземпляру Microsoft SQL Server 2012 устанавливается в Windows Server 2012, может появиться одно из следующих сообщений об ошибке тайм-аута:

• Сообщение об ошибке 1

  [SQLSTATE 01000] (Сообщение 0) SQLState = 08001, NativeError = [SQLSTATE 01000] 258 ошибки (сообщение 0) = поставщик TCP [Microsoft] [SQL Server собственного клиента 11.0]: [258] ошибка истечения времени ожидания. [SQLSTATE 01000] (Сообщение 0) SQLState = 08001, NativeError = [SQLSTATE 01000] 258 ошибки (сообщение 0) = [Microsoft] [SQL Server собственного клиента 11.0] не удается завершить процесс входа в систему из-за задержки в ответ перед входом [SQLSTATE 01000] (сообщение 0) SQLState = S1T00 NativeError = 0 [SQLSTATE 01000] Ошибка (сообщение 0) = [Microsoft] [SQL Server собственного клиента 11.0] время ожидания входа истекло [SQLSTATE 01000] (сообщение 0)

• Сообщение об ошибке 2

  <Штамп времени> -! [165] Ошибка ODBC: 0, время ожидания входа истекло [SQLSTATE HYT00]
  <Штамп времени> -! [298] Ошибка SQLServer: 258, не удается завершить процесс входа в систему из-за задержки в ответ перед входом [SQLSTATE 08001]
  <Штамп времени> -! [382] Ошибка входа с сервера «<Имя_базы_данных>» (SubSystemStepHistoryLogger)
  <Штамп времени> -! [298] Ошибка SQLServer: 258, поставщик TCP: [258] ошибка истечения времени ожидания. [SQLSTATE 08001]

Решение

Для решения этой проблемы попытайтесь сначала применить следующих обновлений Windows Server 2012 в Microsoft Knowledge Base:

2779768 Windows Server 2012 и Windows 8 накопительный пакет обновления: Декабрь 2012 г.

Причина

Эта проблема может возникнуть из-за блокировки поток, который вызывает AcceptEX вызовов в режиме ядра (драйвер AFD.sys) в Windows Server 2012. Записывать трассировку сетевого монитора, может оказаться, что некоторые сетевые пакеты достигают сервера. Однако из-за изменений, диспетчер ввода-вывода, вызов GetQueuedCompletionStatus не удается обнаружить сеть данные, полученные и в результате задержки операции сетевого приложения (в данном случае приложением является SQL Server).

Примечание. Windows Server 2012 вносит изменение в диспетчер ввода-вывода, и это изменение влияет на поведение вызова AcceptEX .

Статус

Корпорация Майкрософт подтверждает, что это проблема продуктов Майкрософт, перечисленных в разделе «Относится к».

I get the following message when trying to connect to SQL database from a remote machine using MS Management Studio with Server Name [ XX.XXX.XXX.XXX,1433MyServerName ] and SQL authentication:

Cannot connect to XX.XXX.XXX.XXX,1433MyServerName.

ADDITIONAL INFORMATION:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 — The wait operation timed out.) (Microsoft SQL Server, Error: 258)

The wait operation timed out

---

I have done the following:

• Allowed remote connection in Server Properties window in SQL Management Studio
• Configured server machine to have static IPv4/DNS addresses.
• Enabled TCP/IP in SQL Configuration Manager (in SQL Server Network Configuration)
• In TCP/IP properties, adjusted [ Protocol -> Listen All -> No ] & set IP[1-8] to TCP port 1433 and IPAll port to 1433 (TCP dynamic ports left blank)
• Set Inbound/Outbound enable connection (Domain, public, private) rules in Windows Firewall for ports TCP 1433, UDP 1434 (should make no difference, since port is specified), service executables: sqlbrowser.exe in C:Program Files (x86)Microsoft SQL Server90Shared (not used I think because port is specified) and sqlservr.exe in C:Program FilesMicrosoft SQL ServerMSSQL13.MyServerName MSSQLBinn
• Set NAT actions in server-side router for ports 1433 (TCP), 1434 (UDP) (again, should not matter) to server’s local IPv4 address and ports 1433, 1434 accordingly.
• Made sure SQL service is running, ports are open and listening on server machine.

---

I can connect to the database on server machine using Windows or Sql credentials with either PC name, or machine’s local IPv4.

Interesting thing is, when >telnet XX.XXX.XXX.XXX 1433 is run, it takes about 10-12 seconds to fail (Could not open connection to the host, on port 1433: Connect failed), but I can see the 2 packets coming to the router itself. Same with the login using SQL Manager — packets come to the router, but either server machine refuses (doesn’t resolve?) the connection, or it doesn’t even get to the machine.

Appreciate your suggestions.

---

Versions used:

• MS SQL Server 2016 Express, MS SQL Management Studio 17, SQL Server 2016 Configuration Manager, Windows 10 Pro.

Появляется сообщение об ошибке времени ожидания при подключении к экземпляру SQL Server 2012, который работает под управлением Windows Server 2012

Симптомы

При попытке войти в систему или подключиться к экземпляру Microsoft SQL Server 2012 устанавливается в Windows Server 2012, может появиться одно из следующих сообщений об ошибке тайм-аута:

Сообщение об ошибке 1

[SQLSTATE 01000] (Сообщение 0) SQLState = 08001, NativeError = [SQLSTATE 01000] 258 ошибки (сообщение 0) = поставщик TCP [Microsoft] [SQL Server собственного клиента 11.0]: [258] ошибка истечения времени ожидания. [SQLSTATE 01000] (Сообщение 0) SQLState = 08001, NativeError = [SQLSTATE 01000] 258 ошибки (сообщение 0) = [Microsoft] [SQL Server собственного клиента 11.0] не удается завершить процесс входа в систему из-за задержки в ответ перед входом [SQLSTATE 01000] (сообщение 0) SQLState = S1T00 NativeError = 0 [SQLSTATE 01000] Ошибка (сообщение 0) = [Microsoft] [SQL Server собственного клиента 11.0] время ожидания входа истекло [SQLSTATE 01000] (сообщение 0)

Сообщение об ошибке 2

Штамп времени> -! [165] Ошибка ODBC: 0, время ожидания входа истекло [SQLSTATE HYT00]
Штамп времени> -! [298] Ошибка SQLServer: 258, не удается завершить процесс входа в систему из-за задержки в ответ перед входом [SQLSTATE 08001]
Штамп времени> -! [382] Ошибка входа с сервера « Имя_базы_данных>» (SubSystemStepHistoryLogger)
Штамп времени> -! [298] Ошибка SQLServer: 258, поставщик TCP: [258] ошибка истечения времени ожидания. [SQLSTATE 08001]

Решение

Для решения этой проблемы попытайтесь сначала применить следующих обновлений Windows Server 2012 в Microsoft Knowledge Base:

2779768 Windows Server 2012 и Windows 8 накопительный пакет обновления: Декабрь 2012 г.

Причина

Эта проблема может возникнуть из-за блокировки поток, который вызывает AcceptEX вызовов в режиме ядра (драйвер AFD.sys) в Windows Server 2012. Записывать трассировку сетевого монитора, может оказаться, что некоторые сетевые пакеты достигают сервера. Однако из-за изменений, диспетчер ввода-вывода, вызов GetQueuedCompletionStatus не удается обнаружить сеть данные, полученные и в результате задержки операции сетевого приложения (в данном случае приложением является SQL Server).

Примечание. Windows Server 2012 вносит изменение в диспетчер ввода-вывода, и это изменение влияет на поведение вызова AcceptEX .

Статус

Корпорация Майкрософт подтверждает, что это проблема продуктов Майкрософт, перечисленных в разделе «Относится к».

Источник

Ms sql server error 258

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

Please check the below screenshot once, One of my client getting this error he was unable to connect to the server.

As I checked TCPIP protocol was enabled and i’m able to access the server as well but the guy getting below error message.

Please suggest me how to troubleshoot this issue..Thanks in advance!

Answers

Please read the following article:

Hope this helps.

• Proposed as answer by Raul Garcia — MS Microsoft employee Tuesday, March 22, 2016 6:51 PM
• Marked as answer by Lydia Zhang Microsoft contingent staff Thursday, March 31, 2016 7:02 AM

Windows authentication or SQL authentication?

The message as such is the standard message when the instance cannot be reached. However, error 258 is unusual in this context. And it is not an SQL Server error, it’s an OS error; NET HELPMSG 258 says The wait operation timed out.

This could possibly indicate that you are arriving somewhere, but no one is actually listening. That is, the port is open but the process is busy with something else. (And that is necessarily not an SQL Server process.)

Try connecting by IP-address and port number in case there is some DNS problem.

• Proposed as answer by Naomi N Wednesday, March 23, 2016 10:20 PM
• Marked as answer by Lydia Zhang Microsoft contingent staff Thursday, March 31, 2016 7:02 AM

I will surmise that the problem is specific to the one person, otherwise users would be complaining.

My first thought is to check is connectivity, make sure he is on a network that can actually reach the SQL server. At the risk of sounding like a network guy, can he ping the server? Can he at least make an RDP connection to the point of being prompted for credentials? (Successful logon is a moot point as long as he is prompted).

There is always the standard Windows question of how long has it been since the affected client machine (not the SQL server) has been rebooted, if it has been a while reboot.

Please read the following article:

Hope this helps.

• Proposed as answer by Raul Garcia — MS Microsoft employee Tuesday, March 22, 2016 6:51 PM
• Marked as answer by Lydia Zhang Microsoft contingent staff Thursday, March 31, 2016 7:02 AM

Windows authentication or SQL authentication?

The message as such is the standard message when the instance cannot be reached. However, error 258 is unusual in this context. And it is not an SQL Server error, it’s an OS error; NET HELPMSG 258 says The wait operation timed out.

This could possibly indicate that you are arriving somewhere, but no one is actually listening. That is, the port is open but the process is busy with something else. (And that is necessarily not an SQL Server process.)

Try connecting by IP-address and port number in case there is some DNS problem.

• Proposed as answer by Naomi N Wednesday, March 23, 2016 10:20 PM
• Marked as answer by Lydia Zhang Microsoft contingent staff Thursday, March 31, 2016 7:02 AM

select * from sys.messages
where message_id = 258 and language_id = 1033

Cannot call methods on %ls.

make sure below check list is passed.

1) ping the server from your client machine. (this will make sure network connection is ok)

2) tcp/ip is enables

3) if you are using different port make sure your client is including that number in the connection string

4) finally on your SQL server make sure remote connection are allowed.

select * from sys.messages
where message_id = 258 and language_id = 1033

Cannot call methods on %ls.

Enric, 258 is an OS error message. You can’t get an error message from SQL Server if you cannot connect to it. 🙂

what clever am I, sorry, this error is previous to SQL

Oddly, I see this happening more often than I’d expect. I did notice that a PING to the server name came back with the IPv6 address rather than the IPv4 address. I don’t expect that would be the case with everyone, but I have the Windows 2016 Business Essentials setup as my domain controller and it may have been upgraded from previous versions. I am still getting accustomed to differences.

That said, at this point, there is a continuous Error 258 returned. I tried changing the hosts file to reflect the IPv4 rather than the IPv6 (which worked), but the timeout still occurs. I suspect there is an issue with certificates that may be beyond my ability to understand at this point. I will persist here and discover some other method.

The SQL Browser is running meaning the first one should have worked since it is all within the domain. In the calling application D:Program FilesMicrosoft SQL ServerMSSQL14.HALLORANMSSQLBinnsqlservr.exe is a firewall exception and in the destination server, the port is open in the inbound rules.

I am thinking the remote timeout being too short is nonsense — Ping is 3ms — but I’ll try that too.

Different than what the others have here — my database engine service is running on a group Managed Service Account that has domain and SPN capability across three servers running SQL Server Enterprise or Developer — whichever is preferred. The SPN’s will need to be checked. Possibly that is also the issue. One of the SPN requirements is to create the SPN only from the server itself (and I keep saying server but these instances are actually running on Windows 10 v1809 machines).

So much to check now. What happened to those good old days? When life was so much easier.

Источник

Ms sql server error 258

Вопрос

Please check the below screenshot once, One of my client getting this error he was unable to connect to the server.

As I checked TCPIP protocol was enabled and i’m able to access the server as well but the guy getting below error message.

Please suggest me how to troubleshoot this issue..Thanks in advance!

Ответы

Please read the following article:

Hope this helps.

• Предложено в качестве ответа Raul Garcia — MS Microsoft employee 22 марта 2016 г. 18:51
• Помечено в качестве ответа Lydia Zhang Microsoft contingent staff 31 марта 2016 г. 7:02

Windows authentication or SQL authentication?

The message as such is the standard message when the instance cannot be reached. However, error 258 is unusual in this context. And it is not an SQL Server error, it’s an OS error; NET HELPMSG 258 says The wait operation timed out.

This could possibly indicate that you are arriving somewhere, but no one is actually listening. That is, the port is open but the process is busy with something else. (And that is necessarily not an SQL Server process.)

Try connecting by IP-address and port number in case there is some DNS problem.

• Предложено в качестве ответа Naomi N 23 марта 2016 г. 22:20
• Помечено в качестве ответа Lydia Zhang Microsoft contingent staff 31 марта 2016 г. 7:02

Все ответы

I will surmise that the problem is specific to the one person, otherwise users would be complaining.

My first thought is to check is connectivity, make sure he is on a network that can actually reach the SQL server. At the risk of sounding like a network guy, can he ping the server? Can he at least make an RDP connection to the point of being prompted for credentials? (Successful logon is a moot point as long as he is prompted).

There is always the standard Windows question of how long has it been since the affected client machine (not the SQL server) has been rebooted, if it has been a while reboot.

Please read the following article:

Hope this helps.

• Предложено в качестве ответа Raul Garcia — MS Microsoft employee 22 марта 2016 г. 18:51
• Помечено в качестве ответа Lydia Zhang Microsoft contingent staff 31 марта 2016 г. 7:02

Windows authentication or SQL authentication?

The message as such is the standard message when the instance cannot be reached. However, error 258 is unusual in this context. And it is not an SQL Server error, it’s an OS error; NET HELPMSG 258 says The wait operation timed out.

This could possibly indicate that you are arriving somewhere, but no one is actually listening. That is, the port is open but the process is busy with something else. (And that is necessarily not an SQL Server process.)

Try connecting by IP-address and port number in case there is some DNS problem.

• Предложено в качестве ответа Naomi N 23 марта 2016 г. 22:20
• Помечено в качестве ответа Lydia Zhang Microsoft contingent staff 31 марта 2016 г. 7:02

select * from sys.messages
where message_id = 258 and language_id = 1033

Cannot call methods on %ls.

make sure below check list is passed.

1) ping the server from your client machine. (this will make sure network connection is ok)

2) tcp/ip is enables

3) if you are using different port make sure your client is including that number in the connection string

4) finally on your SQL server make sure remote connection are allowed.

select * from sys.messages
where message_id = 258 and language_id = 1033

Cannot call methods on %ls.

Enric, 258 is an OS error message. You can’t get an error message from SQL Server if you cannot connect to it. 🙂

what clever am I, sorry, this error is previous to SQL

Oddly, I see this happening more often than I’d expect. I did notice that a PING to the server name came back with the IPv6 address rather than the IPv4 address. I don’t expect that would be the case with everyone, but I have the Windows 2016 Business Essentials setup as my domain controller and it may have been upgraded from previous versions. I am still getting accustomed to differences.

That said, at this point, there is a continuous Error 258 returned. I tried changing the hosts file to reflect the IPv4 rather than the IPv6 (which worked), but the timeout still occurs. I suspect there is an issue with certificates that may be beyond my ability to understand at this point. I will persist here and discover some other method.

The SQL Browser is running meaning the first one should have worked since it is all within the domain. In the calling application D:Program FilesMicrosoft SQL ServerMSSQL14.HALLORANMSSQLBinnsqlservr.exe is a firewall exception and in the destination server, the port is open in the inbound rules.

I am thinking the remote timeout being too short is nonsense — Ping is 3ms — but I’ll try that too.

Different than what the others have here — my database engine service is running on a group Managed Service Account that has domain and SPN capability across three servers running SQL Server Enterprise or Developer — whichever is preferred. The SPN’s will need to be checked. Possibly that is also the issue. One of the SPN requirements is to create the SPN only from the server itself (and I keep saying server but these instances are actually running on Windows 10 v1809 machines).

So much to check now. What happened to those good old days? When life was so much easier.

Источник

September 1, 2015 by Sameer

Possible Root Cause: Unstable Network connectivity to database server or problems with a server in the route

Steps Taken To Confirm Root Cause: 

Setup traceroute at regular intervals using the batch file below

@ECHO OFF

set SERVER=DBServerName.domainname.com

set INTERVAL=60

:TRACEINTERVAL

tracert %SERVER% >> C:DBServerNametracert.txt

timeout %INTERVAL%

GOTO TRACEINTERVAL

In my case, no issues were found, was able to connect to DBServerName continously. This would indicate there are no network connectivity issues.

---

Possible Root Cause: Issues connecting to Active Directory Server

Steps Taken To Confirm Root Cause: Tried connecting via a SQL id using SSMS & SQLCMD encountered the same issue.

---

Possible Root Cause: DNS Problems

Steps Taken To Confirm Root Cause: Tried connecting via IP, still encountered the same issue

---

Possible Root Cause: Issues connectiving via IPv4 or IPv6 address

Steps Taken To Confirm Root Cause:

Checked TCP/IP properties in configuration manager on database server; server was listening to all IP’s.

Tried connecting manually using the IPv4 addresses as well as IPv6 addresses; Encountered the same error in both, so issue was not related to this cause.

C:UserssameerDesktop>sqlcmd -S DBServerName.domainname.com -E

Sqlcmd: Error: Microsoft SQL Server Native Client 11.0 : TCP Provider: Timeout error [258].

Sqlcmd: Error: Microsoft SQL Server Native Client 11.0 : Login timeout expired.

Sqlcmd: Error: Microsoft SQL Server Native Client 11.0 : Unable to complete login process due to delay in prelogin response.

C:UserssameerDesktop>sqlcmd -S fe40::d0f8:6600:8b2:625b%14 -E

Sqlcmd: Error: Microsoft SQL Server Native Client 11.0 : Named Pipes Provider: Could not open a connection to SQL Server [53]. .

Sqlcmd: Error: Microsoft SQL Server Native Client 11.0 : Login timeout expired.

Sqlcmd: Error: Microsoft SQL Server Native Client 11.0 : A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.

---

Possible Root Cause: TCP/IP Port Exhaustion

Steps Taken To Confirm Root Cause:n netstat -ao on the database server while connecting to it from a client server. Consistently observed a TCP connection was being established between both servers, even when the SQL error message was occuring. This means the TCP connection is fine, and there is no TCP/IP port exhaustion.

---

 Possible Root Cause: Resource Constraints on DBServerName server can cause login denials

Steps Taken To Confirm Root Cause:Checked RAM, CPU usage on the database server; CPU was under 10% and RAM was around 60%

---

Possible Root Cause: AntiVirus software running on database server

Steps Taken To Confirm Root Cause:

Trend Micro was running on the database server. Removing this fixed the issue

Have same problem here:
Anyway to fix this

18/03/2022 07:22:34 - Error - Qi.TnNew.Core.Interfaces.IGlobalExceptionHandlerError: On url: http://study.hanoi.edu.vn/huong-dan-thi/on-tap-thcs-mon-tieng-anh-9-e-so-18-302 | 1173060 System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (258): Unknown error 258 at System.Data.SqlClient.SqlCommand.<>c.<ExecuteDbDataReaderAsync>b__126_0(Task1 result) at System.Threading.Tasks.ContinuationResultTaskFromResultTask2.InnerInvoke() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location --- at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread) --- End of stack trace from previous location --- at Dapper.SqlMapper.QueryRowAsync[T](IDbConnection cnn, Row row, Type effectiveType, CommandDefinition command) in /_/Dapper/SqlMapper.Async.cs:line 473 at Qi.TnNew.Infrastructure.Data.TestDetailsLogData.GetRawTestDetailsByKey(String key) in /src/src/Qi.TnNew.Infrastructure/Data/TestDetailsLogData.cs:line 34 at Qi.TnNew.Core.Services.ExamService.CacheGetRawTestDetailsAsync(String detailsLogKey) in /src/src/Qi.TnNew.Core/Services/ExamService.cs:line 504 at Qi.TnNew.Core.Services.ExamService.CreateTestDetailsAsync(Int64 examId, Int64 userId, String detailsLogKey) in /src/src/Qi.TnNew.Core/Services/ExamService.cs:line 520 at Qi.TnNew.Core.Services.ExamService.CreateTestDetailForUserAsync(Int64 examId, Int64 userId, String detailsLogKey) in /src/src/Qi.TnNew.Core/Services/ExamService.cs:line 176 at Qi.TnNew.Web.Controllers.HomeController.<TestGuide>g__TakeAnExamAsync|24_1(Int64 userId, Int64 examId, String examTypeCode) in /src/src/Qi.TnNew.Web/Controllers/HomeController.cs:line 514 at Qi.TnNew.Web.Controllers.HomeController.TestGuide(Int64 id) in /src/src/Qi.TnNew.Web/Controllers/HomeController.cs:line 515 at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.TaskOfIActionResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeActionMethodAsync>g__Awaited|12_0(ControllerActionInvoker invoker, ValueTask1 actionResultValueTask) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.g__Awaited|10_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.g__Awaited|13_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.g__Awaited|24_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResourceExecutedContextSealed context) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.g__Awaited|19_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.g__Logged|17_1(ResourceInvoker invoker) at Microsoft.AspNetCore.Routing.EndpointMiddleware.g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger) at Microsoft.AspNetCore.Authorization.Policy.AuthorizationMiddlewareResultHandler.HandleAsync(RequestDelegate next, HttpContext context, AuthorizationPolicy policy, PolicyAuthorizationResult authorizeResult) at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context) at Microsoft.AspNetCore.Builder.Extensions.MapWhenMiddleware.Invoke(HttpContext context) at Microsoft.AspNetCore.ResponseCompression.ResponseCompressionMiddleware.Invoke(HttpContext context) at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context) at Qi.TnNew.Web.Startup.<>c.<b__8_1>d.MoveNext() in /src/src/Qi.TnNew.Web/Startup.cs:line 177 — End of stack trace from previous location — at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.g__Awaited|6_0(ExceptionHandlerMiddleware middleware, HttpContext context, Task task) ClientConnectionId:017c41d4-d10b-445b-b356-9197e1814fd0 Error Number:-2,State:0,Class:11`