Changing the Dump Directory Location may SQL Agent to not start

Hey Guys,

I was those days changing a few settings in the environment, where I had this small problem and I would like to share what did I do to fix it. The task in question was actually easy: To change the default directory of the LOG folder, that usually is where the SQL Server Agent logs, ERRORLOG and some other things are stored.

PS: Portuguese version below

So far, so good! I stopped the SQL Server and SQL Agent services and then I changed the following.

 

 

 

 

 

 

 

My problem in this case, started to happen after the changes, specifically when I tried to start the SQL Server Services. It happened that the SQL Server Service started, but not the Agent. The error in the errorlog is bellow.

 

 

 

To fix this problem, is quite easy. Open the Registry Editor by typing regedit on cmd and go to the following key and validate if the directory has changed, or it is still pointing to the old one.

 

 

 

 

 

 

 

 

 

In my case, the key on Regedit was still pointing to the old directory. So, I had just to change this key to point to the new folder, save it and try to start the SQL Agent Service again.

Done!! Problem solved.

Regards,
Marcos Freccia
Data Platform MVP

_________________________________________________________________________________________________________________________________________________

Ola Pessoal,

Realizando algumas configuracoes de ambiente recentemente, passei por esse pequeno problema que gostaria de compartilhar com você. A tarefa era bem simples, mudar o diretorio da pasta LOG, que geralmente é onde fica os logs do SQL Agent, ERRORLOG, etc.. Ate ai tudo bem, você para os servicos do SQL e SQL Agent e realiza a troca nas configurações, muda as seguintes configurações.

 

 

 

 

 

 

 

O problema ocorre que após as mudanças o serviço do SQL Server inicia, mas o serviço do SQL Server Agent não e apresenta o seguinte erro:

 

 

 

Quando acontecer isso com vocês a minha dica eh bem simples. Navegue no regedit ate a chave desejada e veja se o diretório esta igual, pois o serviço sempre ira ler o regedit para pegar as ultimas configurações

 

 

 

 

 

 

 

 

 

Veja, para o meu caso o regedit ainda estava apontando para o caminho antigo. O que fiz foi apenas mudar esse diretorio para o correto, salvar e assim iniciar o serviço do SQL Server Agent. Pronto!! Problema resolvido.

Espero que tenham gostado dessa dica e até a próxima

Abraços,
Marcos Freccia
Data Platform MVP

Advertisements

About Marcos Freccia

MVP em SQL Server (Data Plataform) , especialista em SQL Server, e atualmente trabalhando com Microsoft Azure!

Posted on March 30, 2017, in Administração, Dicas, SQL Server, VirtualPass and tagged , , , . Bookmark the permalink. Leave a comment.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: