When you create a MS CRM 3.0 queue and it does not work, don't forget to ...

May 31, 2006 · 1 min read

<< MS CRM 3.0 ExchangeSinkServiceException | Home | MS CRM 3.0: Add menu items to detail forms of entities that are not supported in ISV.config >>

Ok, today I got something to laugh about for you guys out there. I don't know why it hasn't happened before, but this week was the first time I had to create a CRM queue on a new 3.0 system. So what I did was to grab my copy of CRM Installation and configuration course documents and proceed the mentioned step by step instructions. I created the user, set the correct privileges and attributes, disabled the user account and added the queue in MS CRM application. Finally I sent an email to the queue... but nothing happened. So I checked the event logs on both Exchange and CRM servers. But there were no entries in there. After some NG and google research I played around with user privileges and registry keys, but still nothing happened. Because I had restarted IIS, Exchange Router service and Exchange itself several times, the system administrator got mad at me because MOM (MS Operations Manager) was driving him crazy with alert messages.:-) Of course I checked the procedure to add a queue several times, and I did it exactly as stated. In a sudden inspiration I checked the official Implementation guide and found the solution: as a last step you have to add mailbox rules to your queue user using the rule deployment wizard. It's that simple. There are 2 reasons why I post this here: 1. maybe there is someone out there who is also relying on the offical course documents and encountering the same situation. Hopefully he reads this and saves some time. 2. it's another lesson for me: never trust information - even if its printed and packed in a fancy white ring binder with happy looking people on the cover.:-)

Wednesday, May 31, 2006 9:23 AM

This article is part of the GWB Archives. Original Author: Guenter Wallnoefer

New on Geeks with Blogs

  • We Won The One Award I Actually Care About

    Full Scale made the Inc. 5000 for the fifth year straight, the 12th listing across my three companies. Here is why the one award you cannot buy is worth stopping for.

  • Your Customers Build the Features Now

    I let a tool I liked sit dead for a year rather than build the features I wanted. An MCP server meant I never had to, and your customers can do the same to your product.

  • Get the Size of a Directory in Linux the Easy Way

    du -sh for the quick answer, ncdu for the cleanup, df for the disk itself: every command for checking directory size in Linux, plus why du and df never agree.

  • Vim Search and Replace: The Ultimate Guide

    One :%s command replaces every match in a file before a find dialog would even open. The Vim substitute patterns worth the muscle memory: flags, ranges, capture groups, and multi-file edits.