search cancel

Altiris Express service stops followed by application crash or high CPU load.

book

Article ID: 164133

calendar_today

Updated On:

Products

Ghost Solution Suite

Issue/Introduction

Altiris Express service (AXENGINE.EXE) stops followed by application crash or high CPU load. Axengine.log has no record off it. Altiris Express database management service (dbmanager.exe) keeps running. Sometimes there is a socket error before the application crashes in log (when in debug mode).

From AeXEngine.log (Debug)

[12/05/16 14:56:02.687] 1288-Riloe - socket error = 10060 on 10.33.4.123 : 80
[12/05/16 14:56:02.687] d50-Riloe - socket error = 10060 on 10.33.4.123 : 80
[12/05/16 14:56:02.687] 1164-Riloe - socket error = 10060 on 10.33.4.123 : 80
[12/05/16 14:56:02.687] 1288-CheckForILO3 returned false, sending for ILO2.
[12/05/16 14:56:02.687] d50-CheckForILO3 returned false, sending for ILO2.
[12/05/16 14:56:02.687] 1164-CheckForILO3 returned false, sending for ILO2.
[12/05/16 14:56:02.687] 1288-Create a socket and connect to server using normal socket calls

Also within the Event viewer we receive :

Log Name:      Application
Source:        Application Error
Date:          12/5/2016 4:08:56 PM
Event ID:      1000
Task Category: Application Crashing Events
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      VNRPWADP003.rotterdam.local
Description:
Faulting application name: axengine.exe, version: 13.1.0.709, time stamp: 0x57ee7929
Faulting module name: ntdll.dll, version: 6.3.9600.18233, time stamp: 0x56bb4e1d
Exception code: 0xc0000005
Fault offset: 0x00041b71
Faulting process id: 0x1460
Faulting application start time: 0x01d24ed8c2bae258
Faulting application path: D:\Program Files (x86)\Altiris\eXpress\Deployment Server\axengine.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 056deebd-bad7-11e6-80fc-005056b358b2
 

Environment

GSS 3.1

Cause

Since this was an upgrade from old versions & also and upgrade from old database to new, the previous database held some information with the table [eXpress].[dbo].[riloe].

Resolution

Clear the information present in this table [eXpress].[dbo].[riloe]. After this changes there were no more crashes seen.