SPONSORS:






User Tag List

Results 1 to 3 of 3
  1. #1
    Junior Member
    Join Date
    Jul 1999
    Location
    SF, CA, USA
    Posts
    19
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Agent is not responding Error

    Hi
    Occasionaly, I get the above error and need to reboot in order to be able to run silk again.
    I have been installing the newest version of SilkTest (5.02) and running IE5 on NT4. However is had happened before (2.14, 5)

    Any suggestions how/what can I do to avoid this problem?

    BTW: It usually happened upon running the script as oppose to in the middle of execution.

    Thanks

    Hagay

  2. #2
    Senior Member
    Join Date
    Feb 2000
    Posts
    1,497
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Agent is not responding Error

    These kinds of problems are depressing. I'd really hoped that Segue had fixed them since the occurred with some frequency in 2.1.2 - a long time ago. :-(

    You won't usually have to reboot if you go through task manager and kill all of the Agent tasks; don't forget the one that appears under NTDVM.

    The problem was (is?) exacerbated if you kill a test run prematurely with shift-shift. In that case you may be able to get away with killing and restarting Silk (as well as the Agent), rather than rebooting.

  3. #3
    Junior Member
    Join Date
    Jul 1999
    Location
    SF, CA, USA
    Posts
    19
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Agent is not responding Error

    Thanks
    I was hoping there is some work around I am not aware of. I guess there is none.
    At any case, I do kill the agent first and close Silk, however sometimes it is not enough.

    Hagay


    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by John J. Miller:
    These kinds of problems are depressing. I'd really hoped that Segue had fixed them since the occurred with some frequency in 2.1.2 - a long time ago. :-(

    You won't usually have to reboot if you go through task manager and kill all of the Agent tasks; don't forget the one that appears under NTDVM.

    The problem was (is?) exacerbated if you kill a test run prematurely with shift-shift. In that case you may be able to get away with killing and restarting Silk (as well as the Agent), rather than rebooting.
    <HR></BLOCKQUOTE>


 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

vBulletin Optimisation provided by vB Optimise v2.6.0 Beta 4 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.0.9 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Questions / Answers Form provided by vBAnswers (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
vBNominatevBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Feedback Buttons provided by Advanced Post Thanks / Like (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Username Changing provided by Username Change (Free) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
BetaSoft Inc.
Digital Point modules: Sphinx-based search
All times are GMT -8. The time now is 02:27 AM.

Copyright BetaSoft Inc.