Home/ Questions/Q 8979819
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-15T19:56:03+00:00

I have a (dead-letter) queue on my local machine called logging/logdeadletterservice.svc . I have

  • 0

I have a (dead-letter) queue on my local machine called logging/logdeadletterservice.svc. I have a corresponding service running at appdev.me.com/logging/logdeadletterservice.svc to pull the messages from the queue and resubmit them. This works great so long as the worker process is running. However, once the worker process is shut down (or if it hasn’t come up yet), the service no longer gets messages from the queue unless I browse to the SVC manually.

According to this post, NETWORK SERVICE needs permissions to peek the queue. I went ahead and added that permission, but the message was not pulled from the queue. I tried restarting the Net.Msmq Listener Adapter (which is, indeed, running under Network Service), but still no go.

Any ideas on what I’m doing wrong?

EDIT: I’ve tried running sc sidtype netmsmqactivator unrestricted and restarting the service, but no go. Switched it back to restricted (original) after it didn’t resolve the issue.

EDIT2: Also tried running the Net.Msmq Listener Adapter as myself (which is the user under which the service is running), but no go.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Ended up using AppFabric and running the following commands against appcmd.exe to get the pool to be always available and always warmed up:

    %windir%\system32\inetsrv\appcmd.exe set apppool "My Site" /startMode:AlwaysRunning
%windir%\system32\inetsrv\appcmd.exe set app /app.name:"My Site/My App" /serviceAutoStartEnabled:True /serviceAutoStartMode:All /serviceAutoStartProvider:Service
    • 0