You should never rely on Interactive User, regardless of this patch.
Interactive User runs under the context of the user logged in on the console.
If noone is logged into the console, then there is not user context. You also
have no idea who that user might be so you can't count on the user context to be
one that will work the way you want.
It is always a good idea with callouts to verify the identity.
Matt Parks
MVP - Microsoft CRM
----------------------------------------
----------------------------------------
On 28 Jul 2005 06:36:54 -0700, "CRM Customizer" <wdwcrazy@adelphia.net> wrote:
I think this may be a classic case of the right hand not knowing what
the left hand is doing. I have developed a postcallout for CRM and
have a few customers that are using it. It was developed straight out
of the SDK, and I followed the installation/distribution instuctions to
the letter. It has been running wonderfuly - easy to setup at
different sites with no issues. Until now.
One of my customers just loaded up SBS2003 with some new patch that
covered exchange and the server and a bunch of other things. Suddenly
the postcallout isn't working. Turns out that the default way that a
COM+ application gets registered has the Identity set to run with
Interactive User selected. (Right click on the COM + app in component
services|computers|my computer|com+applications and select properties -
then select the identity tab). With the new patch, this user is
invalid. You must select either Local Service or put in a userID that
is on the Server.
If you have a mission critical application that relies on postcallout -
you had better switch this setting before you upgrade your server or it
won't work and you won't get any errors in CRM - it just tries to
execute it, can't, and moves on.
I would like to hear from some of the MS guys that look in this forum
to see if MS is even aware of this HUGE problem.
