"Karl Timmermans" wrote in message
...
What is the exact error that is being thrown? (We apply the exact same
filter in our products and have never run across this as an issue so
curious as to what the error is that you're running into)

The exact error is:

Description: Condition is not valid.
Number: -451805175

For what it's worth given your description being that it works accessing
same account from a different machine which indicates that the folder
contents are valid - would try the following:
#1) do a detect and repair on problem machine (but really don't see
how this would affect filtering on a single message class)

He did that on his own, no affect.

#2) have the user connect to the account in "non-cached" mode to see
if the problem persists

Hmm... I've already scheduled him some more time on the proverbial
treadmill, I asked him to create another user login, connect Outlook to
Exchange, etc to see if the problem is machine wide or user profile
specific. I'll add that to his exercises... but I hope that's not it, we
need CEM.


Mark

Message classes are not language dependant so that wouldn't be the cause.

Karl
__________________________________________________ ____
Karl Timmermans - The Claxton Group
ContactGenie - Importer/DataPorter/Exporter/Toolkit
"Contact import/export/data management tools for Outlook '2000/2007"
http://www.contactgenie.com



"Mark McGinty" wrote in message
...
Greets,

Out of the thousands of installed copies of our AddIn, exactly one throws
an error when we call Restrict aginsts the items collection of the
default contacts folder. The filter expression is static, and is as
folllows:

[MessageClass] 'IPM.DistList'

Since it works as expected on every other machine, I can't imagine how
this might be a problem in my code, because I can't imagine how this
condition would be invalid in any folder.

The system is Outlook 2003, connected to Exchange, using CEM. I asked
the user to perform an advanced search using the same criteria on this
machine, he said it returned the items he expected.

The user logged-into Exchange from another machine, and our AddIn ran
against his contacts without errors. The user said he forced the .OST to
be regenerated on the problem machine, he said it didn't change the
problem.

Anyone ever seen this, or have an idea what might cause it? I'm thinking
Outlook might need to be reinstalled, but I don't want to suggest that
frivolously.


TIA,
Mark