MSMQ won't enable on windows 7 machine
up vote
0
down vote
favorite
I'm trying to enable MSMQ on my development computer (running Windows 7).
I go to turn windows features on or off -> Microsoft Message Queue (MSMQ) Server Core -> Check MSMQ Active Directory Domain Services Integration AND MSMQ HTTP Support.
When I click OK, I get the error "An Error has occurred. Not all of the features were successfully changed." -> Click OK -> "You must restart your computer to apply these changes".
I've clicked Restart Now and Restart later and no matter what, same issue every time.
If I selected Restart later and go into Services...I see Message Queuing (stopped), and if I try to start the service, I get the error "Windows could not start the Message Queuing service on Local Computer. Error 0x80070005: Access denied."
I checked my privileges and I am an Admin on the machine. Just to be safe, I even logged into the machine as the actual Administrator. Same scenario.
Furthermore, when I go into the Event Viewer, I check the Application logs. I have an error with MSMQ as the Source. EventID: 2076, Error: The logger files cannot be initialized. The file QMLog in the MsmqStorage folder is corrupted or absent. Error 0x80070005: Access denied.
If I check the System Logs, I see another error with the source being Service Control manager. Error eventId: 7023, Error: The Message Queuing service terminated with the following error: %%-2147024891
When I look up the error codes on Microsoft, there is NOTHING.
msmq windows-7-x64
edited Sep 19 '15 at 22:02
Community♦
11
asked Jun 25 '13 at 14:11
Josh Hostetler
815
add a comment |
up vote
0
down vote
favorite
I'm trying to enable MSMQ on my development computer (running Windows 7).
I go to turn windows features on or off -> Microsoft Message Queue (MSMQ) Server Core -> Check MSMQ Active Directory Domain Services Integration AND MSMQ HTTP Support.
When I click OK, I get the error "An Error has occurred. Not all of the features were successfully changed." -> Click OK -> "You must restart your computer to apply these changes".
I've clicked Restart Now and Restart later and no matter what, same issue every time.
If I selected Restart later and go into Services...I see Message Queuing (stopped), and if I try to start the service, I get the error "Windows could not start the Message Queuing service on Local Computer. Error 0x80070005: Access denied."
I checked my privileges and I am an Admin on the machine. Just to be safe, I even logged into the machine as the actual Administrator. Same scenario.
Furthermore, when I go into the Event Viewer, I check the Application logs. I have an error with MSMQ as the Source. EventID: 2076, Error: The logger files cannot be initialized. The file QMLog in the MsmqStorage folder is corrupted or absent. Error 0x80070005: Access denied.
If I check the System Logs, I see another error with the source being Service Control manager. Error eventId: 7023, Error: The Message Queuing service terminated with the following error: %%-2147024891
When I look up the error codes on Microsoft, there is NOTHING.
msmq windows-7-x64
edited Sep 19 '15 at 22:02
Community♦
11
asked Jun 25 '13 at 14:11
Josh Hostetler
815
-2147024891 is also 0x80070005. "I checked my privileges and I am an Admin on the machine." That is not relevant - MSMQ runs as a service under a System account, not your admin account. If MSMQ is getting "Access Denied" then it doesn't have permission to do what it needs to do, it's really as simple as that. In this case it means the WindowsSystem32MsmqStorage folder is locked down too tight - can happen through draconian company security policies being applied, for example.
– John Breakwell
Jun 26 '13 at 12:20
My machine is the only one out of 10 other developers that has this issue. All machines are built the exact same way, same security, etc. Are you aware of what I should try and do to resolve this? I have gotten nowhere with Microsoft help, this is the most feedback I've gotten. So thanks.
– Josh Hostetler
Jun 26 '13 at 14:09
If the machines were all built the same, they would all behave the same :-) Have you checked the permissions on the WindowsSystem32MsmqStorage folder and compared with a working machine?
– John Breakwell
Jun 28 '13 at 12:55
permissions are the same :/
– Josh Hostetler
Jul 17 '13 at 15:09
OK, have you tried focusing on QMLOG's permissions? Have you looked at this article? technet.microsoft.com/en-us/library/cc733510.aspx.
– John Breakwell
Jul 18 '13 at 12:44
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm trying to enable MSMQ on my development computer (running Windows 7).
I go to turn windows features on or off -> Microsoft Message Queue (MSMQ) Server Core -> Check MSMQ Active Directory Domain Services Integration AND MSMQ HTTP Support.
When I click OK, I get the error "An Error has occurred. Not all of the features were successfully changed." -> Click OK -> "You must restart your computer to apply these changes".
I've clicked Restart Now and Restart later and no matter what, same issue every time.
If I selected Restart later and go into Services...I see Message Queuing (stopped), and if I try to start the service, I get the error "Windows could not start the Message Queuing service on Local Computer. Error 0x80070005: Access denied."
I checked my privileges and I am an Admin on the machine. Just to be safe, I even logged into the machine as the actual Administrator. Same scenario.
Furthermore, when I go into the Event Viewer, I check the Application logs. I have an error with MSMQ as the Source. EventID: 2076, Error: The logger files cannot be initialized. The file QMLog in the MsmqStorage folder is corrupted or absent. Error 0x80070005: Access denied.
If I check the System Logs, I see another error with the source being Service Control manager. Error eventId: 7023, Error: The Message Queuing service terminated with the following error: %%-2147024891
When I look up the error codes on Microsoft, there is NOTHING.
msmq windows-7-x64
edited Sep 19 '15 at 22:02
Community♦
11
asked Jun 25 '13 at 14:11
Josh Hostetler
815
I'm trying to enable MSMQ on my development computer (running Windows 7).
I go to turn windows features on or off -> Microsoft Message Queue (MSMQ) Server Core -> Check MSMQ Active Directory Domain Services Integration AND MSMQ HTTP Support.
When I click OK, I get the error "An Error has occurred. Not all of the features were successfully changed." -> Click OK -> "You must restart your computer to apply these changes".
I've clicked Restart Now and Restart later and no matter what, same issue every time.
If I selected Restart later and go into Services...I see Message Queuing (stopped), and if I try to start the service, I get the error "Windows could not start the Message Queuing service on Local Computer. Error 0x80070005: Access denied."
I checked my privileges and I am an Admin on the machine. Just to be safe, I even logged into the machine as the actual Administrator. Same scenario.
Furthermore, when I go into the Event Viewer, I check the Application logs. I have an error with MSMQ as the Source. EventID: 2076, Error: The logger files cannot be initialized. The file QMLog in the MsmqStorage folder is corrupted or absent. Error 0x80070005: Access denied.
If I check the System Logs, I see another error with the source being Service Control manager. Error eventId: 7023, Error: The Message Queuing service terminated with the following error: %%-2147024891
When I look up the error codes on Microsoft, there is NOTHING.
msmq windows-7-x64
msmq windows-7-x64
edited Sep 19 '15 at 22:02
Community♦
11
asked Jun 25 '13 at 14:11
Josh Hostetler
815
edited Sep 19 '15 at 22:02
Community♦
11
asked Jun 25 '13 at 14:11
Josh Hostetler
815
edited Sep 19 '15 at 22:02
Community♦
11
edited Sep 19 '15 at 22:02
Community♦
11
edited Sep 19 '15 at 22:02
Community♦
11
11
asked Jun 25 '13 at 14:11
Josh Hostetler
815
asked Jun 25 '13 at 14:11
Josh Hostetler
815
asked Jun 25 '13 at 14:11
Josh Hostetler
815
815
-2147024891 is also 0x80070005. "I checked my privileges and I am an Admin on the machine." That is not relevant - MSMQ runs as a service under a System account, not your admin account. If MSMQ is getting "Access Denied" then it doesn't have permission to do what it needs to do, it's really as simple as that. In this case it means the WindowsSystem32MsmqStorage folder is locked down too tight - can happen through draconian company security policies being applied, for example.
– John Breakwell
Jun 26 '13 at 12:20
My machine is the only one out of 10 other developers that has this issue. All machines are built the exact same way, same security, etc. Are you aware of what I should try and do to resolve this? I have gotten nowhere with Microsoft help, this is the most feedback I've gotten. So thanks.
– Josh Hostetler
Jun 26 '13 at 14:09
If the machines were all built the same, they would all behave the same :-) Have you checked the permissions on the WindowsSystem32MsmqStorage folder and compared with a working machine?
– John Breakwell
Jun 28 '13 at 12:55
permissions are the same :/
– Josh Hostetler
Jul 17 '13 at 15:09
OK, have you tried focusing on QMLOG's permissions? Have you looked at this article? technet.microsoft.com/en-us/library/cc733510.aspx.
– John Breakwell
Jul 18 '13 at 12:44
add a comment |
-2147024891 is also 0x80070005. "I checked my privileges and I am an Admin on the machine." That is not relevant - MSMQ runs as a service under a System account, not your admin account. If MSMQ is getting "Access Denied" then it doesn't have permission to do what it needs to do, it's really as simple as that. In this case it means the WindowsSystem32MsmqStorage folder is locked down too tight - can happen through draconian company security policies being applied, for example.
– John Breakwell
Jun 26 '13 at 12:20
My machine is the only one out of 10 other developers that has this issue. All machines are built the exact same way, same security, etc. Are you aware of what I should try and do to resolve this? I have gotten nowhere with Microsoft help, this is the most feedback I've gotten. So thanks.
– Josh Hostetler
Jun 26 '13 at 14:09
If the machines were all built the same, they would all behave the same :-) Have you checked the permissions on the WindowsSystem32MsmqStorage folder and compared with a working machine?
– John Breakwell
Jun 28 '13 at 12:55
permissions are the same :/
– Josh Hostetler
Jul 17 '13 at 15:09
OK, have you tried focusing on QMLOG's permissions? Have you looked at this article? technet.microsoft.com/en-us/library/cc733510.aspx.
– John Breakwell
Jul 18 '13 at 12:44
-2147024891 is also 0x80070005. "I checked my privileges and I am an Admin on the machine." That is not relevant - MSMQ runs as a service under a System account, not your admin account. If MSMQ is getting "Access Denied" then it doesn't have permission to do what it needs to do, it's really as simple as that. In this case it means the WindowsSystem32MsmqStorage folder is locked down too tight - can happen through draconian company security policies being applied, for example.
– John Breakwell
Jun 26 '13 at 12:20
-2147024891 is also 0x80070005. "I checked my privileges and I am an Admin on the machine." That is not relevant - MSMQ runs as a service under a System account, not your admin account. If MSMQ is getting "Access Denied" then it doesn't have permission to do what it needs to do, it's really as simple as that. In this case it means the WindowsSystem32MsmqStorage folder is locked down too tight - can happen through draconian company security policies being applied, for example.
– John Breakwell
Jun 26 '13 at 12:20
My machine is the only one out of 10 other developers that has this issue. All machines are built the exact same way, same security, etc. Are you aware of what I should try and do to resolve this? I have gotten nowhere with Microsoft help, this is the most feedback I've gotten. So thanks.
– Josh Hostetler
Jun 26 '13 at 14:09
My machine is the only one out of 10 other developers that has this issue. All machines are built the exact same way, same security, etc. Are you aware of what I should try and do to resolve this? I have gotten nowhere with Microsoft help, this is the most feedback I've gotten. So thanks.
– Josh Hostetler
Jun 26 '13 at 14:09
If the machines were all built the same, they would all behave the same :-) Have you checked the permissions on the WindowsSystem32MsmqStorage folder and compared with a working machine?
– John Breakwell
Jun 28 '13 at 12:55
If the machines were all built the same, they would all behave the same :-) Have you checked the permissions on the WindowsSystem32MsmqStorage folder and compared with a working machine?
– John Breakwell
Jun 28 '13 at 12:55
permissions are the same :/
– Josh Hostetler
Jul 17 '13 at 15:09
permissions are the same :/
– Josh Hostetler
Jul 17 '13 at 15:09
OK, have you tried focusing on QMLOG's permissions? Have you looked at this article? technet.microsoft.com/en-us/library/cc733510.aspx.
– John Breakwell
Jul 18 '13 at 12:44
OK, have you tried focusing on QMLOG's permissions? Have you looked at this article? technet.microsoft.com/en-us/library/cc733510.aspx.
– John Breakwell
Jul 18 '13 at 12:44
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
I had something like this - not sure how it came about as I always had AD integration turned ON for my MSMQ (as I needed it) but somewhere along the line, it got turned off and I couldn't turn it back on again via Control Panel - I would get the error behaviour (and restart!) that the OP describes. To fix it, I accessed my machine via the AD services manager app on one of our domain servers and deleted the "msmq" object that was under it.
I restarted my local MSMQ service on my machine AND rebooted (not sure which or both was required) and then when I checked my local registry entries, it indicated I was correctly running in AD mode once again. Everything started to work again after that.
This link was helpful in giving me the right direction to go in: Technet MSMQ delete stale objects article
answered Aug 1 '13 at 16:09
Rory Solley
1,376185
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f17299636%2fmsmq-wont-enable-on-windows-7-machine%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
I had something like this - not sure how it came about as I always had AD integration turned ON for my MSMQ (as I needed it) but somewhere along the line, it got turned off and I couldn't turn it back on again via Control Panel - I would get the error behaviour (and restart!) that the OP describes. To fix it, I accessed my machine via the AD services manager app on one of our domain servers and deleted the "msmq" object that was under it.
I restarted my local MSMQ service on my machine AND rebooted (not sure which or both was required) and then when I checked my local registry entries, it indicated I was correctly running in AD mode once again. Everything started to work again after that.
This link was helpful in giving me the right direction to go in: Technet MSMQ delete stale objects article
answered Aug 1 '13 at 16:09
Rory Solley
1,376185
add a comment |
up vote
0
down vote
I had something like this - not sure how it came about as I always had AD integration turned ON for my MSMQ (as I needed it) but somewhere along the line, it got turned off and I couldn't turn it back on again via Control Panel - I would get the error behaviour (and restart!) that the OP describes. To fix it, I accessed my machine via the AD services manager app on one of our domain servers and deleted the "msmq" object that was under it.
I restarted my local MSMQ service on my machine AND rebooted (not sure which or both was required) and then when I checked my local registry entries, it indicated I was correctly running in AD mode once again. Everything started to work again after that.
This link was helpful in giving me the right direction to go in: Technet MSMQ delete stale objects article
answered Aug 1 '13 at 16:09
Rory Solley
1,376185
add a comment |
up vote
0
down vote
up vote
0
down vote
I had something like this - not sure how it came about as I always had AD integration turned ON for my MSMQ (as I needed it) but somewhere along the line, it got turned off and I couldn't turn it back on again via Control Panel - I would get the error behaviour (and restart!) that the OP describes. To fix it, I accessed my machine via the AD services manager app on one of our domain servers and deleted the "msmq" object that was under it.
I restarted my local MSMQ service on my machine AND rebooted (not sure which or both was required) and then when I checked my local registry entries, it indicated I was correctly running in AD mode once again. Everything started to work again after that.
This link was helpful in giving me the right direction to go in: Technet MSMQ delete stale objects article
answered Aug 1 '13 at 16:09
Rory Solley
1,376185
I had something like this - not sure how it came about as I always had AD integration turned ON for my MSMQ (as I needed it) but somewhere along the line, it got turned off and I couldn't turn it back on again via Control Panel - I would get the error behaviour (and restart!) that the OP describes. To fix it, I accessed my machine via the AD services manager app on one of our domain servers and deleted the "msmq" object that was under it.
I restarted my local MSMQ service on my machine AND rebooted (not sure which or both was required) and then when I checked my local registry entries, it indicated I was correctly running in AD mode once again. Everything started to work again after that.
This link was helpful in giving me the right direction to go in: Technet MSMQ delete stale objects article
answered Aug 1 '13 at 16:09
Rory Solley
1,376185
answered Aug 1 '13 at 16:09
Rory Solley
1,376185
answered Aug 1 '13 at 16:09
Rory Solley
1,376185
answered Aug 1 '13 at 16:09
Rory Solley
1,376185
1,376185
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f17299636%2fmsmq-wont-enable-on-windows-7-machine%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
-2147024891 is also 0x80070005. "I checked my privileges and I am an Admin on the machine." That is not relevant - MSMQ runs as a service under a System account, not your admin account. If MSMQ is getting "Access Denied" then it doesn't have permission to do what it needs to do, it's really as simple as that. In this case it means the WindowsSystem32MsmqStorage folder is locked down too tight - can happen through draconian company security policies being applied, for example.
– John Breakwell
Jun 26 '13 at 12:20
My machine is the only one out of 10 other developers that has this issue. All machines are built the exact same way, same security, etc. Are you aware of what I should try and do to resolve this? I have gotten nowhere with Microsoft help, this is the most feedback I've gotten. So thanks.
– Josh Hostetler
Jun 26 '13 at 14:09
If the machines were all built the same, they would all behave the same :-) Have you checked the permissions on the WindowsSystem32MsmqStorage folder and compared with a working machine?
– John Breakwell
Jun 28 '13 at 12:55
permissions are the same :/
– Josh Hostetler
Jul 17 '13 at 15:09
OK, have you tried focusing on QMLOG's permissions? Have you looked at this article? technet.microsoft.com/en-us/library/cc733510.aspx.
– John Breakwell
Jul 18 '13 at 12:44