How do I give file system access to SQL Server's SQLSERVERAGENT virtual account?

I'm trying to grant the NT ServiceSQLSERVERAGENT Windows account file system access, based on the marked answer in this question. I believe it's a virtual service account, and it does not show up in the control panel -> user accounts area.

How do I give this service account access to the file system? Specifically, on Windows 7.

I've read several approaches and none seem to be an option for me. I tried a powershell approach, but the AD commands were not valid commands. I even downloaded and installed the required windows patch for those commands. I've also read that I should be able to do this via the SQL configuration manager or the management studio. I can't seem to figure out where to adjust these permissions, though.

Any help appreciated, thanks!

edited Apr 13 '17 at 12:42

Community♦

asked Jul 9 '14 at 15:55

Ryan

248238

1

The SQL Server Agent process fails to start, with the following error message: Login failed for user 'NT SERVICESQLSERVERAGENT'. Reason: Failed to open the explicitly specified database 'msdb'. [CLIENT: <local machine>]. Based on my Googling, it has to do with this account's permissions.

– Ryan
Jul 9 '14 at 16:28

@SeanGallardy its part of the sysadmin and public groups

– Ryan
Jul 9 '14 at 19:24

@mrdenny i updated my question with the exact error messages from the agent logs. im not sure if the database is corrupt, but it says the database is in a Normal status.

– Ryan
Jul 10 '14 at 15:44

add a comment |

How do I give this service account access to the file system? Specifically, on Windows 7.

Any help appreciated, thanks!

edited Apr 13 '17 at 12:42

Community♦

asked Jul 9 '14 at 15:55

Ryan

248238

1

The SQL Server Agent process fails to start, with the following error message: Login failed for user 'NT SERVICESQLSERVERAGENT'. Reason: Failed to open the explicitly specified database 'msdb'. [CLIENT: <local machine>]. Based on my Googling, it has to do with this account's permissions.

– Ryan
Jul 9 '14 at 16:28

@SeanGallardy its part of the sysadmin and public groups

– Ryan
Jul 9 '14 at 19:24

@mrdenny i updated my question with the exact error messages from the agent logs. im not sure if the database is corrupt, but it says the database is in a Normal status.

– Ryan
Jul 10 '14 at 15:44

add a comment |

How do I give this service account access to the file system? Specifically, on Windows 7.

Any help appreciated, thanks!

edited Apr 13 '17 at 12:42

Community♦

asked Jul 9 '14 at 15:55

Ryan

248238

How do I give this service account access to the file system? Specifically, on Windows 7.

Any help appreciated, thanks!

sql-server permissions sql-server-agent

edited Apr 13 '17 at 12:42

Community♦

asked Jul 9 '14 at 15:55

Ryan

248238

edited Apr 13 '17 at 12:42

Community♦

asked Jul 9 '14 at 15:55

Ryan

248238

edited Apr 13 '17 at 12:42

Community♦

edited Apr 13 '17 at 12:42

Community♦

edited Apr 13 '17 at 12:42

Community♦

asked Jul 9 '14 at 15:55

Ryan

248238

asked Jul 9 '14 at 15:55

Ryan

248238

asked Jul 9 '14 at 15:55

Ryan

248238

1

The SQL Server Agent process fails to start, with the following error message: Login failed for user 'NT SERVICESQLSERVERAGENT'. Reason: Failed to open the explicitly specified database 'msdb'. [CLIENT: <local machine>]. Based on my Googling, it has to do with this account's permissions.

– Ryan
Jul 9 '14 at 16:28

@SeanGallardy its part of the sysadmin and public groups

– Ryan
Jul 9 '14 at 19:24

@mrdenny i updated my question with the exact error messages from the agent logs. im not sure if the database is corrupt, but it says the database is in a Normal status.

– Ryan
Jul 10 '14 at 15:44

add a comment |

1

The SQL Server Agent process fails to start, with the following error message: Login failed for user 'NT SERVICESQLSERVERAGENT'. Reason: Failed to open the explicitly specified database 'msdb'. [CLIENT: <local machine>]. Based on my Googling, it has to do with this account's permissions.

– Ryan
Jul 9 '14 at 16:28

@SeanGallardy its part of the sysadmin and public groups

– Ryan
Jul 9 '14 at 19:24

@mrdenny i updated my question with the exact error messages from the agent logs. im not sure if the database is corrupt, but it says the database is in a Normal status.

– Ryan
Jul 10 '14 at 15:44

The SQL Server Agent process fails to start, with the following error message:

Login failed for user 'NT SERVICESQLSERVERAGENT'. Reason: Failed to open the explicitly specified database 'msdb'. [CLIENT: <local machine>]

. Based on my Googling, it has to do with this account's permissions.

– Ryan
Jul 9 '14 at 16:28

The SQL Server Agent process fails to start, with the following error message:

Login failed for user 'NT SERVICESQLSERVERAGENT'. Reason: Failed to open the explicitly specified database 'msdb'. [CLIENT: <local machine>]

. Based on my Googling, it has to do with this account's permissions.

– Ryan
Jul 9 '14 at 16:28

@SeanGallardy its part of the sysadmin and public groups

– Ryan
Jul 9 '14 at 19:24

@mrdenny i updated my question with the exact error messages from the agent logs. im not sure if the database is corrupt, but it says the database is in a Normal status.

– Ryan
Jul 10 '14 at 15:44

add a comment |

3 Answers
3

active

oldest

votes

To specifically answer your question, here's how you give disk access rights to the built in SQL Server Agent account. But read on as I answer what I believe to be the real issue:

1.> Right-click your drive, select properties, click the Add button and enter the SQLSERVERAGENT account(make sure your domain isn't selected in the From this location text box, but rather your computer name):

enter image description here

2.> Click the Check Names button to validate that the account is valid:

enter image description here

3.> Now, add the file permission you need to the SQLSERVERAGENT account. For trouble-shooting purposes, you may want to give Full control and then scale it back later as needed:

enter image description here

That being said, you probably just need to use SQL Server Configuration Manger to re-add the SQL Agent user--according to the comments I saw about msdb and logins. Configuration Manager makes more changes to SQL Server than using the Windows Services applet--so Configuration Manager should always be used to change ANY SQL Service.

This will fix the issue if someone may have changed the account within Windows Services causing the service to fail on startup. You need to reset it within Configuration Manager. Doing so allows Configuration Manager to add to SQL Server the much needed permissions to manage the MSDB database for the Local Service account (NT SERVICESQLSERVERAGENT) whereas changing accounts within the Windows services applet does not.

Caveat: Versions SQL Server Express above 2000 do not include a SQL Agent. Certain aspects of it may appear to be there, but its unusable in the Express version of the product.

To begin, open SQL Server Configuration Manager and double-click the SQL Server Agent service in the SQL Server Services. Select the Built-in account radio button and choose Local Service, and click the Apply button. Important : if you already see that this account is selected chose another account and click the Apply Button. Then, change it back to Local Service and click the Apply button to allow Configuration Manager to add the correct MSDB permissions for the SQL Agent service to start. Now, restart SQL Server Agent to reflect this new setting.

enter image description here

edited Jan 8 '16 at 16:14

answered Jan 8 '16 at 14:33

Sting

2,252416

1

My SQL Server Agent account was set to NT ServiceSQLAgent$MyInstanceName and trying to set security on a folder and pressing Check Names said Name Not Found and wouldn't find it. After much frustration I realised that the default 'From This Location' when pressing Add to add permissions wasn't set to my local machine, it was set to my domain. Changing it to my local machine (the very root node in the tree) allowed it to detect my NT ServiceSQLAgent$MyInstanceName account to add it to the folder permissions.

– SLC
Oct 9 '18 at 14:47

I obtained the "MyInstanceName" from the Event Log which logged the errors.

– Jasen
Dec 19 '18 at 20:57

add a comment |

I resolved this problem by setting SQL Server Agent Login account to LocalSystem.

edited Aug 8 '18 at 15:15

RDFozz

9,91231531

answered Aug 8 '18 at 14:32

louis

@Marco - note that this solution isn't provided by another answer - it is a separate solution.

– RDFozz
Aug 8 '18 at 15:16

1

While this is a workaround that can get things up and running, it is generally considered less secure than using the solution suggested in this answer

– RDFozz
Aug 8 '18 at 15:18

Well then what is the answer? How the heck do you manage these stupid virtual account NT ServiceMSSQL$ServerName things? There is no way. There's nothing on the internet about it. Just balogna answers that are false and don't work. The answer above doesn't work for me either.

– AyCabron
Oct 2 '18 at 23:39

add a comment |

I agree frustrating.. apparently it's as simple as just typing the name.
http://zarez.net/?p=3187

answered 15 mins ago

VJason

New contributor

add a comment |

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f70069%2fhow-do-i-give-file-system-access-to-sql-servers-sqlserveragent-virtual-account%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

3 Answers
3

active

oldest

votes

3 Answers
3

active

oldest

votes

To specifically answer your question, here's how you give disk access rights to the built in SQL Server Agent account. But read on as I answer what I believe to be the real issue:

enter image description here

2.> Click the Check Names button to validate that the account is valid:

enter image description here

3.> Now, add the file permission you need to the SQLSERVERAGENT account. For trouble-shooting purposes, you may want to give Full control and then scale it back later as needed:

enter image description here

Caveat: Versions SQL Server Express above 2000 do not include a SQL Agent. Certain aspects of it may appear to be there, but its unusable in the Express version of the product.

enter image description here

edited Jan 8 '16 at 16:14

answered Jan 8 '16 at 14:33

Sting

2,252416

1

My SQL Server Agent account was set to NT ServiceSQLAgent$MyInstanceName and trying to set security on a folder and pressing Check Names said Name Not Found and wouldn't find it. After much frustration I realised that the default 'From This Location' when pressing Add to add permissions wasn't set to my local machine, it was set to my domain. Changing it to my local machine (the very root node in the tree) allowed it to detect my NT ServiceSQLAgent$MyInstanceName account to add it to the folder permissions.

– SLC
Oct 9 '18 at 14:47

I obtained the "MyInstanceName" from the Event Log which logged the errors.

– Jasen
Dec 19 '18 at 20:57

add a comment |

To specifically answer your question, here's how you give disk access rights to the built in SQL Server Agent account. But read on as I answer what I believe to be the real issue:

enter image description here

2.> Click the Check Names button to validate that the account is valid:

enter image description here

3.> Now, add the file permission you need to the SQLSERVERAGENT account. For trouble-shooting purposes, you may want to give Full control and then scale it back later as needed:

enter image description here

Caveat: Versions SQL Server Express above 2000 do not include a SQL Agent. Certain aspects of it may appear to be there, but its unusable in the Express version of the product.

enter image description here

edited Jan 8 '16 at 16:14

answered Jan 8 '16 at 14:33

Sting

2,252416

1

My SQL Server Agent account was set to NT ServiceSQLAgent$MyInstanceName and trying to set security on a folder and pressing Check Names said Name Not Found and wouldn't find it. After much frustration I realised that the default 'From This Location' when pressing Add to add permissions wasn't set to my local machine, it was set to my domain. Changing it to my local machine (the very root node in the tree) allowed it to detect my NT ServiceSQLAgent$MyInstanceName account to add it to the folder permissions.

– SLC
Oct 9 '18 at 14:47

I obtained the "MyInstanceName" from the Event Log which logged the errors.

– Jasen
Dec 19 '18 at 20:57

add a comment |

To specifically answer your question, here's how you give disk access rights to the built in SQL Server Agent account. But read on as I answer what I believe to be the real issue:

enter image description here

2.> Click the Check Names button to validate that the account is valid:

enter image description here

3.> Now, add the file permission you need to the SQLSERVERAGENT account. For trouble-shooting purposes, you may want to give Full control and then scale it back later as needed:

enter image description here

Caveat: Versions SQL Server Express above 2000 do not include a SQL Agent. Certain aspects of it may appear to be there, but its unusable in the Express version of the product.

enter image description here

edited Jan 8 '16 at 16:14

answered Jan 8 '16 at 14:33

Sting

2,252416

To specifically answer your question, here's how you give disk access rights to the built in SQL Server Agent account. But read on as I answer what I believe to be the real issue:

enter image description here

2.> Click the Check Names button to validate that the account is valid:

enter image description here

3.> Now, add the file permission you need to the SQLSERVERAGENT account. For trouble-shooting purposes, you may want to give Full control and then scale it back later as needed:

enter image description here

Caveat: Versions SQL Server Express above 2000 do not include a SQL Agent. Certain aspects of it may appear to be there, but its unusable in the Express version of the product.

enter image description here

edited Jan 8 '16 at 16:14

answered Jan 8 '16 at 14:33

Sting

2,252416

edited Jan 8 '16 at 16:14

answered Jan 8 '16 at 14:33

Sting

2,252416

answered Jan 8 '16 at 14:33

Sting

2,252416

answered Jan 8 '16 at 14:33

Sting

2,252416

1

My SQL Server Agent account was set to NT ServiceSQLAgent$MyInstanceName and trying to set security on a folder and pressing Check Names said Name Not Found and wouldn't find it. After much frustration I realised that the default 'From This Location' when pressing Add to add permissions wasn't set to my local machine, it was set to my domain. Changing it to my local machine (the very root node in the tree) allowed it to detect my NT ServiceSQLAgent$MyInstanceName account to add it to the folder permissions.

– SLC
Oct 9 '18 at 14:47

I obtained the "MyInstanceName" from the Event Log which logged the errors.

– Jasen
Dec 19 '18 at 20:57

add a comment |

1

My SQL Server Agent account was set to NT ServiceSQLAgent$MyInstanceName and trying to set security on a folder and pressing Check Names said Name Not Found and wouldn't find it. After much frustration I realised that the default 'From This Location' when pressing Add to add permissions wasn't set to my local machine, it was set to my domain. Changing it to my local machine (the very root node in the tree) allowed it to detect my NT ServiceSQLAgent$MyInstanceName account to add it to the folder permissions.

– SLC
Oct 9 '18 at 14:47

I obtained the "MyInstanceName" from the Event Log which logged the errors.

– Jasen
Dec 19 '18 at 20:57

My SQL Server Agent account was set to NT ServiceSQLAgent$MyInstanceName and trying to set security on a folder and pressing Check Names said Name Not Found and wouldn't find it. After much frustration I realised that the default 'From This Location' when pressing Add to add permissions wasn't set to my local machine, it was set to my domain. Changing it to my local machine (the very root node in the tree) allowed it to detect my NT ServiceSQLAgent$MyInstanceName account to add it to the folder permissions.

– SLC
Oct 9 '18 at 14:47

I obtained the "MyInstanceName" from the Event Log which logged the errors.

– Jasen
Dec 19 '18 at 20:57

add a comment |

I resolved this problem by setting SQL Server Agent Login account to LocalSystem.

edited Aug 8 '18 at 15:15

RDFozz

9,91231531

answered Aug 8 '18 at 14:32

louis

@Marco - note that this solution isn't provided by another answer - it is a separate solution.

– RDFozz
Aug 8 '18 at 15:16

1

While this is a workaround that can get things up and running, it is generally considered less secure than using the solution suggested in this answer

– RDFozz
Aug 8 '18 at 15:18

Well then what is the answer? How the heck do you manage these stupid virtual account NT ServiceMSSQL$ServerName things? There is no way. There's nothing on the internet about it. Just balogna answers that are false and don't work. The answer above doesn't work for me either.

– AyCabron
Oct 2 '18 at 23:39

add a comment |

I resolved this problem by setting SQL Server Agent Login account to LocalSystem.

edited Aug 8 '18 at 15:15

RDFozz

9,91231531

answered Aug 8 '18 at 14:32

louis

@Marco - note that this solution isn't provided by another answer - it is a separate solution.

– RDFozz
Aug 8 '18 at 15:16

1

While this is a workaround that can get things up and running, it is generally considered less secure than using the solution suggested in this answer

– RDFozz
Aug 8 '18 at 15:18

Well then what is the answer? How the heck do you manage these stupid virtual account NT ServiceMSSQL$ServerName things? There is no way. There's nothing on the internet about it. Just balogna answers that are false and don't work. The answer above doesn't work for me either.

– AyCabron
Oct 2 '18 at 23:39

add a comment |

I resolved this problem by setting SQL Server Agent Login account to LocalSystem.

edited Aug 8 '18 at 15:15

RDFozz

9,91231531

answered Aug 8 '18 at 14:32

louis

I resolved this problem by setting SQL Server Agent Login account to LocalSystem.

edited Aug 8 '18 at 15:15

RDFozz

9,91231531

answered Aug 8 '18 at 14:32

louis

edited Aug 8 '18 at 15:15

RDFozz

9,91231531

edited Aug 8 '18 at 15:15

RDFozz

9,91231531

edited Aug 8 '18 at 15:15

RDFozz

9,91231531

answered Aug 8 '18 at 14:32

louis

answered Aug 8 '18 at 14:32

louis

answered Aug 8 '18 at 14:32

louis

@Marco - note that this solution isn't provided by another answer - it is a separate solution.

– RDFozz
Aug 8 '18 at 15:16

1

While this is a workaround that can get things up and running, it is generally considered less secure than using the solution suggested in this answer

– RDFozz
Aug 8 '18 at 15:18

Well then what is the answer? How the heck do you manage these stupid virtual account NT ServiceMSSQL$ServerName things? There is no way. There's nothing on the internet about it. Just balogna answers that are false and don't work. The answer above doesn't work for me either.

– AyCabron
Oct 2 '18 at 23:39

add a comment |

@Marco - note that this solution isn't provided by another answer - it is a separate solution.

– RDFozz
Aug 8 '18 at 15:16

1

While this is a workaround that can get things up and running, it is generally considered less secure than using the solution suggested in this answer

– RDFozz
Aug 8 '18 at 15:18

Well then what is the answer? How the heck do you manage these stupid virtual account NT ServiceMSSQL$ServerName things? There is no way. There's nothing on the internet about it. Just balogna answers that are false and don't work. The answer above doesn't work for me either.

– AyCabron
Oct 2 '18 at 23:39

@Marco - note that this solution isn't provided by another answer - it is a separate solution.

– RDFozz
Aug 8 '18 at 15:16

While this is a workaround that can get things up and running, it is generally considered less secure than using the solution suggested in this answer

– RDFozz
Aug 8 '18 at 15:18

Well then what is the answer? How the heck do you manage these stupid virtual account NT ServiceMSSQL$ServerName things? There is no way. There's nothing on the internet about it. Just balogna answers that are false and don't work. The answer above doesn't work for me either.

– AyCabron
Oct 2 '18 at 23:39

add a comment |

I agree frustrating.. apparently it's as simple as just typing the name.
http://zarez.net/?p=3187

answered 15 mins ago

VJason

New contributor

add a comment |

I agree frustrating.. apparently it's as simple as just typing the name.
http://zarez.net/?p=3187

answered 15 mins ago

VJason

New contributor

add a comment |

I agree frustrating.. apparently it's as simple as just typing the name.
http://zarez.net/?p=3187

answered 15 mins ago

VJason

New contributor

I agree frustrating.. apparently it's as simple as just typing the name.
http://zarez.net/?p=3187

answered 15 mins ago

VJason

New contributor

answered 15 mins ago

VJason

New contributor

answered 15 mins ago

VJason

answered 15 mins ago

VJason

New contributor

VJason is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Database Administrators Stack Exchange!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Vryjdfkk