Post reply

Configuration Manager Bug?

  • February 15, 2010 at 10:58 am

    #141287

    Hello All,

    I have a serious issue with a SQL Server Service configuration in SQL Server Configuration Manager. The setup is a simple two node cluster if that helps any.

    When I log into the actually SQL Server and try to remove a trace flag someone added, it adds it back in after I restart the service. Is there a way to remove it? When the service restarts it gets an error because it thinks the trace flag is a part of a file path. So I been trying to remove it.

    Thanks.

  • February 15, 2010 at 12:05 pm

    #1118911

    Have you made sure, who added that trace flag?

    From the screen shot given by you, it is missing a semi colon ";" after the mastlog.ldf

    It should be something like this mastlog.ldf;-T3608

    Bru Medishetty

    Blog -- LearnSQLWithBru

    Join on Facebook Page Facebook.comLearnSQLWithBru

    Twitter -- BruMedishetty

  • February 15, 2010 at 12:09 pm

    #1118913

    Yeah it's missing the semi colon thats why it thinks its a part of the file path. We don't need the traceflag anymore so I wanted to remove it completely.

    Everytime I remove it and restart the service it adds the flag back in. So I have to go to services.msc and restart the service that way and it works fine.

  • February 15, 2010 at 2:02 pm

    #1118951

    SQL Iron Chef (2/15/2010)

    Yeah it's missing the semi colon thats why it thinks its a part of the file path. We don't need the traceflag anymore so I wanted to remove it completely.

    Everytime I remove it and restart the service it adds the flag back in. So I have to go to services.msc and restart the service that way and it works fine.

    You should never start SQL Server services that have been clustered using the services applet. When you do that, the cluster no longer has control over the instance and will not be able to failover or manage the instance.

    Clustered services need to be set the manual startup mode also.

    Now, to change your trace flag you need to go into cluster administrator and modify the services parameters from there. That is what is controlling how the services are going to start up.

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs

  • February 16, 2010 at 8:15 am

    #1119308

    Thanks Jeffrey.

    I set the services to manual. I was wondering where do I configure the startup parameters in the cluster administrator console. I was browsing around and couldn't find it.

    Thanks Again!

  • February 16, 2010 at 2:01 pm

    #1119539

    Sorry - you still have to modify the startup parameters using SQL Configuration Manager. I believe you might have to modify the registry directly to get the changes to stick, because Cluster Administrator is managing the service.

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs

  • February 17, 2010 at 2:39 am

    #1119911

    I think you need to make this change to the active instance of SQL Server. If you want the change to take effect immediately you also need to run a DBCC TRACEOFF command on the active instance.

    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

Viewing 7 posts - 1 through 6 (of 6 total)

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