IM Not updating Contact Status

[ya]

E2K IM contact and .NET(MSN) Messenger contact status information has no
relation.

(1) Is each IM client actually updating its status? Do the IIS logs contain
PROPPATCH entries, with successful HTTP 207 response, from each client.
(2) Are you signing-in to E2K IM with the same account(s) from more than one
workstation simultaneously? Status will not be updated properly, as the IM
server will be receiving updates from multiple sources for the same IM
object.
(3) Are you running E2K SP2? which version of IM client?

-yury

"Alan" <akro...@sistemasesco.com.ar> wrote in message
news:1bb701c1b0cd$b9d23570$3bef2ecf@TKMSFTNGXA10...
> Hi, i have a Windows 2000 Server and serveral Windows 2000
> Professional workstations.
> The Server is running Exchange 2000 and Instant Message
> Protocol. All the workstations are using MSN and they log
> and send messages to each other correctly but the status
> of the contacts are not refreshed until you close and re-
> open the MSN Messenger. However this does not happen with
> contacts on the internet.
>
> The IM address of the users is USER@SERVER
>
> Can anyone give me hand on this ?
> Thanks in advance,
> Alan.

[Alan]

1) The clients are updating their status, but sometimes i
get 207 responses and sometimes not. I have several 200,
404 and 401 responses every now and then.

2) I'm only signing from one terminal for each account.

3) Yes, Exchange is SP2 and the IM client is MSN 4.6
(4.6.0073)

Thanks
Alan.

>.
>

[ya]

I haven't checked the NG in several days.
HTTP 401s are normal during IIS authentication - in fact should precede most
HTTP requests. The contact(s) status info is held in the msimnode.edb. In
fact the only data in the file is status and subscriber info. To rule out
any DB problem, I would replace the database. Stop w3svc and replace the
file (better yet, move all of the contents of the directoty into a different
folder). The db files will be recreated after services restart and IM users
sign-on.

One suggestion about doing this. Either notify all users to sign-off before
you do this - or keep services stopped for at least 20 minutes (the default
max. timeout for an IM client to re-update it's status with the IM server).
If you do not do this, IM clients will not get updates for their contact(s)
status until they sign-off and sign-on again.

Otherwise, run a NetMon trace on the IM server. Filter for HTTP to confirm
status updates (NOTIFY) are sent and reaching the IM client(s). Just don't
confuse them with actual IM msgs (which also use the NOTIFY HTTP method)

Lastly, check permissions (test using an admin acct.)

good luck.
-yury

"Alan" <AKro...@sistemasesco.com.ar> wrote in message
news:238001c1b313$83de77b0$a4e62ecf@tkmsftngxa06...