October 31, 2017 at 2:44 pm
Around 2am in the morning, certain jobs fails and report fails at the same time. Report (business objects) connects to SQL server using a generic sql account. When I look at the event log, I get the following error messages. Any idea what this means?
The Open Procedure for service "SQLSERVERAGENT" in DLL "perf-MSSQL12.MSSQLSERVER-sqlagtctr.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
The Open Procedure for service "ReportServer" in DLL "perf-ReportServer-rsctr12.0.2000.8.dll" failed. Performance data for this service will not be available. T he first four bytes (DWORD) of the Data section contains the error code.
The server will drop the connection, because the client driver has sent multiple requests while the session is in single-user mode. This error occurs when a client sends a request to reset the connection while there are batches still running in the session, o r when the client sends a request while the session is resetting a connection. Please contact the client driver vendor.
October 31, 2017 at 3:20 pm
SQL_Surfer - Tuesday, October 31, 2017 2:44 PMAround 2am in the morning, certain jobs fails and report fails at the same time. Report (business objects) connects to SQL server using a generic sql account. When I look at the event log, I get the following error messages. Any idea what this means?
The Open Procedure for service "SQLSERVERAGENT" in DLL "perf-MSSQL12.MSSQLSERVER-sqlagtctr.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
The Open Procedure for service "ReportServer" in DLL "perf-ReportServer-rsctr12.0.2000.8.dll" failed. Performance data for this service will not be available. T he first four bytes (DWORD) of the Data section contains the error code.
The server will drop the connection, because the client driver has sent multiple requests while the session is in single-user mode. This error occurs when a client sends a request to reset the connection while there are batches still running in the session, o r when the client sends a request while the session is resetting a connection. Please contact the client driver vendor.
Is this all Business Objects - anything else connecting at that time? And what jobs are failing - SQL Server jobs or other jobs?
I've only seen that last error when using MARS. And the best fix for that is to get rid of MARS. It seems to do nothing other than cause problems.
Sue
October 31, 2017 at 3:56 pm
Mainly just business objects and there are some agent jobs that run hourly also fail at that time. But those jobs run fine other times.
October 31, 2017 at 4:08 pm
SQL_Surfer - Tuesday, October 31, 2017 3:56 PMMainly just business objects and there are some agent jobs that run hourly also fail at that time. But those jobs run fine other times.
The jobs failing may or may not have anything to do with the other errors you posted.
You would want to look at the SQL Server jobs, check the history to see why they are failing.
Do you have access to the connection string that business objects is using? If you could post that, it would help. Pull out the user, password and server name.
Sue
October 31, 2017 at 5:20 pm
Thanks. Sorry, I should have made more clearer.
So, SQL server agent job on Server A fails during that time saying it couldn't log on to server B. It has a query that uses a link server to join one of the table in server B. Business objects hits server B. It uses ODBC connection with server name ServerB, reportuser, password.
October 31, 2017 at 5:21 pm
This is what I've in extended event around that time from server B.
Network error code 0x2746 occurred while establishing a connection; the connection has been closed. This may have been caused by client or server login timeout expiration. Time spent during login: total 0 ms, enqueued 0 ms, network writes 0 ms, network reads 0 ms, establishing SSL 0 ms, network reads during SSL 0 ms, network writes during SSL 0 ms, secure calls during SSL 0 ms, enqueued during SSL 0 ms, negotiating SSPI 0 ms, network reads during SSPI 0 ms, network writes during SSPI 0 ms, secure calls during SSPI 0 ms, enqueued during SSPI 0 ms, validating login 0 ms, including user-defined login processing 0 ms. [CLIENT: 10.212.19.244]
October 31, 2017 at 7:28 pm
SQL_Surfer - Tuesday, October 31, 2017 5:21 PMThis is what I've in extended event around that time from server B.Network error code 0x2746 occurred while establishing a connection; the connection has been closed. This may have been caused by client or server login timeout expiration. Time spent during login: total 0 ms, enqueued 0 ms, network writes 0 ms, network reads 0 ms, establishing SSL 0 ms, network reads during SSL 0 ms, network writes during SSL 0 ms, secure calls during SSL 0 ms, enqueued during SSL 0 ms, negotiating SSPI 0 ms, network reads during SSPI 0 ms, network writes during SSPI 0 ms, secure calls during SSPI 0 ms, enqueued during SSPI 0 ms, validating login 0 ms, including user-defined login processing 0 ms. [CLIENT: 10.212.19.244]
That could still just be from the last error and issues with MARS. You can tell if it's enabled or not from the connection string, pretty much why I suggested posting it if you have access to it. You could also check the documentation for whatever pieces of business objects is hitting SQL Server and see if they have anything documented about using MARS.
Other than checking for that issue - which you really should do, you could look at what is running around that time - and this would include other application/web servers that are hitting the database servers. So not just SQL Server jobs but also anything firing from business objects, some regular process that runs at that time, etc.
You could also run a trace, extended events session and track what it going on from both servers at that time. Since you have a general time frame you could trace just during that time, schedule it as a job to start up.
Sue
October 31, 2017 at 8:43 pm
Sorry, what is MARS?
November 1, 2017 at 6:40 am
SQL_Surfer - Tuesday, October 31, 2017 8:43 PMSorry, what is MARS?
Multiple Active Recordsets. It's where you can have multiple requests on a single connection.
Sue
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply