Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

Straightforward this one - when failing over from one sql server 2008 node to another, should the browser service be running on the passive node ? At the moment, on attempting to failover, a an error is produced saying that certain clustering related dlls can't be found. The dlls are present, I just wondered whether this browser service was stopping access.

share|improve this question
    
I've provided an answer for one of the questions you are asking - the direct question - it shouldn't come into play with failover and whether it is running or not won't affect that, generally if you need the browser it just runs on each node all the time and shouldn't cause an issue. For the real question here - why are you not failing over - can you post the actual error message and more information about your setup and what you've tried? –  Mike Walsh Dec 4 '13 at 0:49

1 Answer 1

There really isn't a short answer because there are a few hidden questions in the question.

A few thoughts to help here:

1.) The Browser service is not cluster aware, so it generally would be just running on each node. The browser is really used to handle incoming connections to a SQL instance. When you don't have a fixed port, are using named instances and in other situations the browser handles the "finding" of the instance a client desires to connect to. So if you have it running on the active node and it is being used to direct connections, I would make sure it is automatic and running on each node.

2.) That said the browser shouldn't prevent DLLs from being found or take any part in preventing or allowing a failover. So the issue you are having with failing over is most likely not related to the browser but something else. Instead you should be looking at things like - Have you failed over before? Is this a new install of a second node? Have there been any required restarts missed on that node? Did the install throw up any errors? Are there issues in the clustering logs? Can you post the exact error you are receiving? Have you searched for that exact error?

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.