• Tom Van Harpen - Monday, March 20, 2017 4:42 PM

    Thanks Sue,
    I've removed the linked server since I've found some posts regarding issues that reference linked servers.
    It appears so far that its been the last 3 Sundays, but since the event viewer is cutoff last Monday i cant confirm that. There are no jobs running during those times. 
    I'll dig around some more and see what i can find, will update if i find anything useful. 

    Thanks,
    Tom

    Hi Tom.
    The exception has not been cached by the SQL dumper. I assume that the event log entry was from Windows error reporting (WER). You should find the mini dump under the WER directory.
    Your susspiscion that this is caused by the linked server provider might be correct. Analyzing the dump would confirm that.
    To avoid the instance crash, you should set the provider to run outside of the SQL server process (instance restart required- in some rare cases OS reboot is needed for the change to become affected). This way, next time a failure in the linked server provider will result just in an error message and will not affect the SQL Server process.
    Please.S. some providers work only inprosess of the SQL Server.
    Hth