Unable to Start/Stop SQL Agent remotely through SSMS

  • Ed,

    I have checked and can connect to the cluster and its 2 nodes with regedit.

    In all 3 i nstances i see 'HKEY_LOCAL_MACHINE' and 'HKEY_USERS', however this is less then i get on my machine. Is this enough or do i need more?

    Wintel say it should be fine :s

    Adam Zacks-------------------------------------------Be Nice, Or Leave

  • Registry access is often the problem, but ther can be other blocks to getting this working...

    It is worth trying to control the services using a different tool as part of debugging the problem.

    Try using the Service Control applet to stop/start services on the other computer. You may need to run MMC in Author mode to get Service Control to connect to the other machine. If this does not work, you may be in a better position to get your Windows people to help, as you have ruled out SQL Server as the problem, and shown it occurrs with what they might call a 'real' tool.

    If Service Control can manage servces remotely, then you have something extra to add to your Google searches. Ther are some KB articles about this problem, but I think they apply to SQL2000.

    It is also worth Googling for 'Remote Service stop' and other things like this as you may find the cause. Other possible causes include a need to open a Firewall port to pass the command, or a Trust problem between you and the target, but these seldom occurr.

    Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.

    When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara

  • Ed,

    Our WIntel team have looked at this and confirmed that we have access to the registry. This has been confirmed by creating, modifying nad deleteing a key.

    Is there anything else we can check?

    I have gone back to the 2005 SSMS and it still works perfectly. It seems that the only issue is with our cluster under SSMS 2008.

    Adam Zacks-------------------------------------------Be Nice, Or Leave

  • Sorry, I am out of ideas.

    Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.

    When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara

  • Thanks for the info. I was having the same problems.

    Tariq

Viewing 5 posts - 16 through 19 (of 19 total)

You must be logged in to reply to this topic. Login to reply