We run Exchange Server 2003, Outlook 2003. Since this morning, entering a distribution list name in the "To..." field, the distribution list is resolved. However, when I try to expand the distribution list, I get the following error: "Cannot perform the requested operation. The command selected is not valid for this recipient. There was an error wihle expanding the list. The list was not fully expanded." Windows Removal tool does not detect any malware. The server and workstation are up to date. Could anybody help, please? Thanks.ruben

Couple of things... Is it non-universal group and are you running in multi-domain enviornment? Are you running outlook in Cache mode? If so, check in online mode... Amit Tank | MVP Exchange Server | MCITP:EMA MCSA:M | http://ExchangeShare.WordPress.com

Hello,Please answer Amit's post.If DL is non-universal then please change the type to Universal which is recommended and that will resolve the issue.Arun Kumar | MCSE - 2K3 + Messaging | ITIL-F V3

Hi, I agree with Amit that you need to check whether it is a universal group. It is because only universal group memberships are replicated across all domains to all global catalog servers in the forest. Microsoft always recommends using universal distribution groups for mail distribution in a multi-domain environment. For your reference: http://support.microsoft.com/kb/839949/en-us In addition, the error may also occur if the group has no member or has hidden members. Mike

Thanks everybody for you responses. Indeed, all Universal Distribution Lists expand well and the others (i.e. Domain Local and Global) do not. Changing the DL to Universal does not resolve the problem. So, I guess time is needed for replication. Finally, I have restarted the Exchange server and I get my problem resolved. I conclude that the Universal DLs goes right because of replication. But I did have a problem with my Exchange server. Ruben.ruben

Kewl... It takes up to 2 hours to refresh Information Store recipient cache or you need to restart IS service. You rebooted the server which has restarted the IS service ultimately and solved the issue.Amit Tank | MVP Exchange Server | MCITP: EMA, MCSA: M | http://ExchangeShare.WordPress.com