April 29, 2013 at 9:23 am
Hello All,
I have MS SQL 2005/SP3 running on Windows 2003 standard. The server has 4GB and that is the maximum based on the OS. I am running SSIS as well as SQL server. Max memory is 3168 mb.
I have SSIS packages that poll for files on a scheduled basis that can fail intermittently.
I have also been seeing this in the SQL server logs.
Error: 26050, Severity: 17, State: 1.
Server local connection provider has stopped listening on [ \\.\pipe\SQLLocal\MSSQLSERVER ] due to a failure. Error: 0xe8, state: 4. The server will automatically attempt to re-establish listening.
Server local connection provider has successfully re-established listening on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
I am thinking of backing down max memory to 2500 mb on the theory that the OS/SSIS is a bit starved.
Any thoughts?
April 29, 2013 at 11:31 am
Start logging the "available MBs" counter, "page life expectancy" and the "page file % used" counter and see how they do over time. If you have memory pressure drops or increases in those counters would possibly correlate to the error message and maybe your scheduled job.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
May 3, 2013 at 1:22 pm
I think this was actually low C drive space. Once this was rectified the phantom failures stopped. I did educate myself on performance monitor and SQL counters for future reference. Thanks!
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply