locked
Communicator signs in, and back out repetitively every 5-10seconds RRS feed

  • Question

  • We have had at least two users / instances where a user of Communcator after signing in, see their communcator sign them out, then start signing back in again, over and over.

     

    From the other user's point of view the user presence appears to flick back and forth between available and away.

     

    Manually signing out and signing in as another user was working fine, but when the original user attemped to sign back in again on that computer they continued to sign in and out repetitively.

     

    The problem in one instance seems to resolve itself after a long period of time (more than 15minutes).

     

    Has anybody else come accross this problem? we are using OCS Enterprise Beta3

     

    Thanks

    Thursday, June 14, 2007 11:56 PM

Answers

  • We had this problem too with beta 3 TR. We opened a case and it was identified as a bug : when a same user opens a session on more than one workstation at a time, and when the user has a roaming profile, the issue occurs. It is apparently due to a session ID stored in the roaming profile ....

     

    Matthieu

    Thursday, July 19, 2007 7:47 PM

All replies

  • Hi,

     

    I haven't seen this before.

     

    What have you done for troubleshooting up to now?

    Did you already activate client side logging of OC?

     

    Thanks

    Bernd

    Monday, June 18, 2007 1:10 PM
  • Hi Northtec,

    Can you let us know the status of your issue? Were you able to check out Bernd's suggestions?

    Monday, June 25, 2007 7:17 PM
  • Have only noticed the problem occurring again once since my original post.

    We turned on logging for that user. I could try to retreive them and post these results up here if there's anything you want to see..

     

    We plan on upgrading to RC next week so will see if we continue to experience this problem and post here...

    Monday, July 2, 2007 12:51 AM
  • This happened again yesterday and we turned on both tracing logs and Windows event viewer logs.

    The event viewer just made an information log every few seconds that it was enabling logging.

    The tracing .etl log was growing very quickly - about 5MB every few seconds that it cycled the logging out and in again.. So have now got an 80MB communicator.etl log file.

    Don't spose either of these are any help after all

    Wednesday, July 4, 2007 10:24 PM
  • We had this problem too with beta 3 TR. We opened a case and it was identified as a bug : when a same user opens a session on more than one workstation at a time, and when the user has a roaming profile, the issue occurs. It is apparently due to a session ID stored in the roaming profile ....

     

    Matthieu

    Thursday, July 19, 2007 7:47 PM