Pesky Internal Database

I’ve spotted this one a couple of times recent – on different systems and not both ones I’m responsible for looking after (it’s always good to know it’s not purely my fault!) where after a reboot the FIM service isn’t available.

When looking into the Event Log for information, there is a large number of errors raised by the both the FIM Service and WSS (we’re looking at a very substantial number as this appears to be retried every second or so and generates multiple eventlog entries) – the key issue being that WSS is unable to connect to SQL.

Naturally I’ve checked my SQL instance and found it running safely however when I remembered that the Windows Internal Database is also SQL based and checked that – it turns out that for some reason this service was not started (even though it was set to  automatic) – a quick restart on this and FIM returns to normal operation.

This entry was posted in FIM, Troubleshooting and tagged , , , , , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *