Windows Dagent running on an MS Exchange server occasionally goes offline and cannot be restarted

Products

• Ghost Solution Suite

Issue/Introduction

You have noticed that the Altiris Deployment Agent service (Ghost Solution Suite DAgent service) on all Microsoft Exchange servers stops from time to time. 
You are not be able to restart it from services.msc and or via powershell Restart-Service, only a reboot of the whole server helps get the DAgent service running. Reinstalling the Dagent also doesn't resolve the issue.
Altiris DAgent will die again in from 5 to 10 days if it is successfully started.

Error message from Services.msc:

Error 1053: The service did not respond to the start or control request in a timely fashion.

Per the Dagent log, it seems that the agent fails during startup connecting to the engine:

[05/13/2025 09:12:19.529 52656 1] InputThread.cpp:235 - IPCException
    Thrown from SocketIpc.cpp:291 -message = CSocketIPC::Read Socket Error
    SystemError Value = 0x00002736
    An operation was attempted on something that is not a socket.
[05/13/2025 09:12:19.531 52656 1] InputThread.cpp:308 - Socket exception cannot be recovered, GetLastError() returned 0x00002736

 

[05/11/2025 10:00:31.195 46124 1] InputThread.cpp:235 - IPCException
    Thrown from SocketIpc.cpp:291 -message = CSocketIPC::Read Socket Error
    SystemError Value = 0x00002746
    An existing connection was forcibly closed by the remote host.
[05/11/2025 10:00:31.196 46124 1] InputThread.cpp:308 - Socket exception cannot be recovered, GetLastError() returned 0x00002746
[05/11/2025 10:00:31.196 46124 0] InputThread.cpp:345 -  Exiting Input Thread

Environment

GSS 3.3 RU12

Cause

Known issue. There were unnecessary attempt to connect to port 415, which may cause the service slow start.

Resolution

This issue has been fixed with our GSS 3.3.13 release.
DAgent binary files were updated to fix this condition.