AHD52034:A system error occurred writing the file into the Document Repository.
Article ID: 129738
Updated On:
Products
SUPPORT AUTOMATION- SERVER
CA Service Desk Manager - Unified Self Service
KNOWLEDGE TOOLS
CA Service Management - Asset Portfolio Management
CA Service Management - Service Desk Manager
Issue/Introduction
What do these messages mean?
AHD52031:An incoming email message contained one or more attached files which could not be saved for the following reason(s):
AHD52034:A system error occurred writing the file into the Document Repository.
These errors seem to occur around the same time that maileater has issues (ie. fails and needs restarting)
Is there a known cause?
Or is it likely a performance issue?
Environment
CA Service Desk Manager prior to ITSM 17.1 CP1.
Resolution
Please monitor for general performance issues with the CA Service Desk Manager server and application.
The first error (AHD52031) is a generic error indicating an Attachment failure, and may occur for any Attachment failure.
The second error (AHD52034) is uncommon, and would need troubleshooting to identify the specific cause.
Some possible root causes are:
It typically has an environment cause.
Please diagnose around those sources to get to root cause.
If there is a known performance issue, then that could feed into this.
LOGGING
Note that these instructions are for advanced users only, as the log output would need to be read and interpreted along with information on the system as a whole.
From the CA SDM side to turn on logging:
pdm_logstat -n pdm_maileater_nxd TRACE
pdm_trace pdm_maileater_nxd ON
pdm_trace spelsrvr ON
And to turn off after the issue occurs:
pdm_logstat -n pdm_maileater_nxd
pdm_trace pdm_maileater_nxd OFF
pdm_trace spelsrvr OFF
Also look at CPU and memory at the time.
This might provide further information.
Note that the mail processes were completely rewritten in ITSM 17.1 CP1 to java.
The messages were reported on a system prior to this version.
The first error (AHD52031) is a generic error indicating an Attachment failure, and may occur for any Attachment failure.
The second error (AHD52034) is uncommon, and would need troubleshooting to identify the specific cause.
Some possible root causes are:
- Failure to write to hard disk (eg disk full)
- Failure to communicate over the network (eg firewall, antivirus, network down)
- Failure of the operating system (eg out of memory)
It typically has an environment cause.
Please diagnose around those sources to get to root cause.
If there is a known performance issue, then that could feed into this.
LOGGING
Note that these instructions are for advanced users only, as the log output would need to be read and interpreted along with information on the system as a whole.
From the CA SDM side to turn on logging:
pdm_logstat -n pdm_maileater_nxd TRACE
pdm_trace pdm_maileater_nxd ON
pdm_trace spelsrvr ON
And to turn off after the issue occurs:
pdm_logstat -n pdm_maileater_nxd
pdm_trace pdm_maileater_nxd OFF
pdm_trace spelsrvr OFF
Also look at CPU and memory at the time.
This might provide further information.
Note that the mail processes were completely rewritten in ITSM 17.1 CP1 to java.
The messages were reported on a system prior to this version.
Feedback
Powered by
