Sign in
Microsoft.com
 
Microsoft
 
 
 
Microsoft >
> 
> 
> 
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the HpcScheduler service

Unanswered A timeout (30000 milliseconds) was reached while waiting for a transaction response from the HpcScheduler service

  • Thursday, October 13, 2011 8:40 AM
     
     
    Sign In to Vote
    0

    Hallo,

    can someone explain me why I always found the error "A timeout (30000 milliseconds) was reached while waiting for a transaction response from the HpcScheduler service" in the Event Viewer -> System (event id 7011) ?

    Thank you very much.

     

All Replies

  • Tuesday, October 18, 2011 7:33 PM
     
     
    Sign In to Vote
    0

    Hi,

    This error occurs, when Windows Service Control Manager can't start a service within 30 seconds. Despite the error service will start up. In case of the Job Scheduler service this can be caused by variety of reasons, for example:

    - problems with database connectivity,

    - large number of old jobs in the database,

    - poor system performance.

    Could you provide some more details about your cluster setup?

    Thank you,
    Łukasz

     
  • Monday, October 24, 2011 2:47 PM
     
     
    Sign In to Vote
    0
    Hi,
    We have a cluster of 3 servers (one is head/compute node, the other 2 are compute nodes).
    Servers are HP BL685 with HP on board NICs. They are in different subnets 02,03 and 04, connected to 1 Gig switches, running 1 gig full duplex.
    The database is local to the same server marked as head node. We use the SQL Express that comes with HPC to host the database.