The scheduler was unable to commit a transaction
-
3 octombrie 2011 09:34
Hi,
please can you explain me why in the event viewer (log name: Microsoft-HPC-Scheduler/Operational) I found these errors (3 events at the same time) ? Thank you very muchevent 1 :
An unexpected exception occurred. For more information about this exception, see the Details tab.
Additional data:
Expected to update 1 rows, but actually updated 0, for SQL command:
SET NOCOUNT ON;
SET NOCOUNT OFF;
SET NOCOUNT OFF;
UPDATE Job SET
ChangeTime = @Param0,RequiredNodes = @Param1,TaskLevelUpdateTime = @Param2,MinMaxUpdateTime = @Param3,ComputedMinCores = @Param4,ComputedMaxCores = @Param5
WHERE ID = 755 AND timestamp <= 0x000000000009A26D
SET NOCOUNT ON;
event 2:The scheduler was unable to commit a transaction.
event 3:
The operation could not be completed because the affected object is already in use by the scheduler. Please try again later.
Toate mesajele
-
13 octombrie 2011 08:37Any idea about this error ? I always find 2-3 alerts in the event viewer each day...
Thank you very much -
18 octombrie 2011 18:57
Hi,
This error is expected to occur in some situations and should be treated as a warning. Actually in next version of Windows HPC Server it will be marked as a warning is the event log. Scheduler will retry the failed transaction automatically.
Regards,
Łukasz -
19 octombrie 2011 13:44Thank you very much. So I can ignore these errors.