Error: 17300, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.

Someone sent me a request to diagnose the error message : Error: 17300, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped. A close inspection of the error logs revealed some relate messages. Most importantly There was insufficient memory to run this query Observations: Max Memory not set. It was set with no limit . This means it was competing with OS memory requirements One of the nice features of SQL Server when there is extreme memory pressure is a good level of detail in... Read more →

Service Exit Code 1077 and false negatives

This is not a trick question, but what is the Windows Exit Code 1077? In the Microsoft Windows documentation the details related to this Exit Code are No attempts to start the service have been made since the last boot. ERROR_SERVICE_NEVER_STARTED I’m writing some Powershell script to review Windows services which failed to start and I’m getting loads of rows of services with Exit Code 1077 and the Windows service is stopped. Answer: As the documented definition states “No attempts to start the service have been made since the last boot” . Therefore there is no failure in this case.... Read more →

How to write to a sql error to windows server event viewer

Over the last few versions SQL Server has improved greatly on writing sql server error messages . A good example is writing to both SQL Server Error Log and the windows server event viewer. There are a number of benefits in writing a SQL Server error to the windows event viewer. Centralising error messages to the one source makes it more efficient for a monitoring application. It is possible for the monitoing package to parse the Windows event viewer and extract all alerting situations from the one source. This minimises the access footprint on the server . There is no... Read more →

Microsoft ACE OLEDB 12.0 provider is not registered on the local machine

Question : A user contacted me with an error message on a newly installed SQL Server Management Studio. The error message appeared while using the Import Data Wizard on Excel, connecting a SQL Server and extracting the data. Microsoft ACE OLEDB 12.0 provider is not registered on the local machine (System.Data) How can I fix this issue? Answer: This is not strictly a SQL Server Database Engine problem. The error is related to the installation of SQL Server Management Studio. The prerequisite for Microsoft Access Database Engine 2010 is missing. Microsoft Office or the free Microsoft Access Database Engine redistributable... Read more →

Error 17836 Length specified in network packet payload did not match number of bytes read; the connection has been closed

Question: This error appeared in the SQL Server Logs today. Error: 17836, Severity: 20, State: 14. Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library. [CLIENT: an_ip] How can I find out what application is attempting to connect ? Answer: The most common reason for this error are Nessus scanners or similar detection intrusion systems. They usually scan servers looking for vulnerabilities. It’s not obvious from the logs – but you can build a correlation between the timings in the SQL Server Error... Read more →