Search

Set-MsmqQueueManager breaks msmq service by Blindrood

Active

1
0
Sign in
to vote
Type: Bug
ID: 770591
Opened: 11/9/2012 3:48:03 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
Trying to invoke:
Set-MsmqQueueManager -JournalQuota 5000 -MsgLogStore 'D:\logs\MSMQ' -TransactionLogStore 'D:\logs\MSMQ' -MsgStore 'D:\logs\MSMQ' -Confirm:$false

This command modifies registry data and tries to restart msmq service but this service is not getting up.

Restoring registry data back to default fixes problem

I think this is because setting storage directories should be done with few other operations but this command doesn't execute them. It only modifies registry.

Modifying registry manually gives the same result (msmq service is not starting)

Setting journalquota and msglogstore only works, adding transactionlogstore or msgstore breaks msmq service
Details (expand)
How often does this happen?
Always Happens

Have you seen this problem before in this product?

No, this is new to the most recent version
Reproduction Steps
Install msmq
execute:
Set-MsmqQueueManager -JournalQuota 5000 -MsgLogStore 'D:\logs\MSMQ' -TransactionLogStore 'D:\logs\MSMQ' -MsgStore 'D:\logs\MSMQ' -Confirm:$false
Expected Results
Datastores should be set and service should be up and running
File Attachments
0 attachments
Sign in to post a comment.
Sign in to post a workaround.