S
Simon Weel
Virtual Machine guest running Server 2016. Been running for months without problems. A couple of weeks ago, I switched on the Search Service. This service is disabled by default, see https://support.microsoft.com/nl-nl/help/3204979/windows-search-is-disabled-by-default-in-windows-server-2016. The reasons mentioned in that article don't apply to our situation, so I saw no problem in switching the service on. A couple of hours later, the VM hang. Could not restart it with Hyper-V manager. I had to reboot the physical server to get it running again. Within 15 minutes, it again stalled. Another reboot required. And again, within 30 minutes, it hang. Yet another reboot and after switching the search service off, no more hanging. The System log reads 'bugcheck-0xa-0x1a-0xbe'. No other errors logged. I created a forum post about this: Bugcheck 0xa, 0x1a, 0xbe
This weekend, I gave the search service another try. And the VM hang again, after some time. This time without any errors / warnings in the event log. So my conclusion: the Search Service hangs the VM, but why? And more important - how do I get Search to behave?
Simon Weel
Continue reading...
This weekend, I gave the search service another try. And the VM hang again, after some time. This time without any errors / warnings in the event log. So my conclusion: the Search Service hangs the VM, but why? And more important - how do I get Search to behave?
Simon Weel
Continue reading...