Error and alert catalog

📘 Description

This catalog gathers the errors and alerts shown by the xDoc services. It lets your technical team and Gosocket Support know what an error means and what to check when they see it in errTXT, in the Event Viewer or in an alert email.

For each service, the most frequent messages are listed with their probable cause and where to look. The messages are copied exactly as xDoc shows them, in Spanish. Text between < > is replaced by the actual value (file, area, instance, document type, etc.).

info

This catalog does not replace the documentation of each service, which has its full configuration.

📍 Where errors appear

When a service cannot process a document, it leaves a trace in one or more of these places. The folders are under <installation>\areas\<area>.

Place	What it contains	Services that use it
errTXT of the instance instances\<instance>\errTXT	Copy of the document that failed. In Conversion, a detail XML with the same name is added (for example, 33_NPG_123.txt and 33_NPG_123.xml) with the code, type, origin, date and message of the error. In Signing, the detail is stored in <name>_sign_error.xml.	Conversion, Signing, Dispatch, Webservice
alerts of the area	alert_<id>.xml files pending to be sent by email, plus a copy of the document or the response as an attachment. The Alerts service deletes them after sending them.	All services that generate alerts (see Alert codes)
Folder toprint of the area	Documents that could not be printed are left with the .err extension.	Printing
logs of the area	log*.txt text files with the conversion trace: service, file, date, document data and message (OK or the error). They are generated only if Generate conversion traceability is checked in Configuration → Traceability. A copy of the event log is also saved here when it is cleared.	Conversion (trace); all services (copy of the event log)
Event Viewer	Main record of errors and information for all services. It is viewed in xDoc Manager → Event Viewer (filters Service: and Instance:) or in the Windows Event Viewer, in the log named after the area. The source of each event is Servicio xdoc@<service>_<area>, or Servicio xdoc@<service>_<area>_<instance> for per-instance services (Conversion, Signing, Dispatch). The Webservice writes to the xdoc@webservice log with source Servicio WebServices_<area>.	All
Alert email	Email sent by the xDoc Alerts Service with the Code, Type, Source, Date and Time, Message, Attachment and Additional Info of the alert. It requires alerts to be enabled, an SMTP server configured and recipients defined for the alert type.	All services that generate alerts

🧾 Alert email format

If the template is not customized in Configuration → Services → Alerts, the email arrives with this format:

• Subject: Alerta generada en xDoc para el área: <área>
• Body: Alerta, Código, Tipo, Fuente, Fecha y Hora, Mensaje, Adjunto and Info Adicional.

The Code identifies what happened (see the following table). The Message carries the error text. The Attachment is usually the affected document or the tax authority's response.

🏷 Alert codes

Each alert carries a 6-digit code. The first 3 digits define the type (classification). Based on that type, the Alerts service picks the recipients and the email template. See Alerts.

Alert types

Prefix	Type (Alerts view)	Use in the current version
000	All	Not an error type. The recipients of All receive a copy of every alert.
010	Conversion Error	Conversion errors and Schematron validation errors (the latter when alerts are enabled).
020	Signing error	The standard services do not generate alerts with this prefix. Signing errors arrive with code 050002.
030	Printing error	Errors from the Printing service.
031	Dispatch error	Rejections from the tax authority and dispatch notices.
032	Webservice error	Conversion or signing errors received through the Webservice.
040	Availability, Numbering expiration	The standard services do not generate alerts with this prefix.
050	Certificate expiration	Certificate about to expire or expired, and also any signing error.
070	Connector processing	Connector errors and notices.
080	Pre-processing	Reserved for pre-processing connectors. The xDoc Global connectors do not use it.
090	Processing finished	Reserved for end-of-process notices. The xDoc Global connectors do not use it.

Codes generated by the services

Code	Type	Service / source	Meaning	Attachment
010001	Conversion Error	Conversion xdoc@converter - Error de conversión	The document could not be converted. The message carries the <code>: <description> of the error.	Integration file (spool)
010099	Conversion Error	Schematron validation (Conversion or Signing) <servicio> - Se detectaron errores durante la validación con Schematron.	The document does not meet the Schematron rules configured for its type. The message lists each rule that failed. The alert is generated when alerts are enabled in the area (Enable alerts option).	No attachment
030002	Printing error	Printing xdoc@batchprinter - Error de impresión or - Impresión con XSLT-PCL	The document could not be printed (batch printing or XSLT-PCL printing).	Document to print
030003	Printing error	Printing xdoc@batchprinter - Impresión de documento	Printing or PDF generation ended with an error.	Document (.err)
030004	Printing error	Printing xdoc@batchprinter - Tipo de documento no definido	The type of the document to print could not be identified.	Document (.err)
030005	Printing error	Printing xdoc@batchprinter -	Unexpected error during printing.	Document (.err)
031001	Dispatch error	Dispatch xdoc@dispatch, type Rechazado por la Entidad Tributaria	The platform or the tax authority rejected the document. Info carries the rejection code (or [Sin código]).	Tax authority response or the document
031001 (Brazil)	Dispatch error	Dispatch, type El documento superó el tiempo de espera…	The document was not authorized in time and was not sent to printing.	Response obtained
031000 to 031003 (Paraguay)	Dispatch error	SIFEN dispatch, source TaxAuthority	SIFEN notices. See Country variations.	Depends on the case
032002	Webservice error	Webservice WebServices Core.asmx - Error de conversión or type Firmado	Conversion error of a document received through the Webservice, or expired certificate when signing through the Webservice.	Document or certificate
050002	Certificate expiration	Signing xdoc@batch (type Firmado) or xdoc@batchsigner (type SignError.Exception)	Three cases: the certificate is about to expire (daily alert), the certificate has expired, or the document could not be signed. They are told apart by the message.	Document or certificate
070001	Connector processing	Connectors (for example, ExcelToXML, MegaPrint, PackageToPrint)	A connector ended with an error. The PackageToPrint connector also uses it to notify that a file is available (type Procesamiento terminado).	Depends on the connector

note

To receive Signing errors by email, define recipients for the Certificate expiration type (or for All). The Signing error type does not receive alerts in the current version.

🧰 Errors by service

The messages are grouped by service. The Message column indicates where each one appears: EV = Event Viewer, errTXT = detail XML in errTXT, Email = alert email.

🔁 Messages common to all services

Message	Probable cause	What to check
Área <área> La ruta de ejecución no coincide con la ruta de instalación. (EV)	The service runs from a folder other than the xDoc installation (for example, after copying or moving the installation).	Path of the service executable in Windows. Reinstall the area services from Administration → Services.
No se pudo leer el archivo de configuración Config.xml. <detalle> (EV)	The area configuration file does not exist, is corrupted or has no read permissions.	cnfg\Config.xml file of the area. Open the area in the Manager and save the configuration.
Se excedió el tiempo (<n>s) intentando conectarse con el servidor. (EV)	Gosocket did not respond within the maximum time.	Server connectivity to the Internet, proxy and firewall.
El log de eventos ha sido guardado y limpiado automáticamente. (EV)	The event log filled up. xDoc saved a copy to a <date>.log file and cleared it.	The earlier events are in that file, inside the area folder.

🔄 Conversion

Reference: Conversion and Duplicate Control. The file stays in errTXT with its detail XML and alert 010001 is generated.

Message	Probable cause	What to check
Instancia <instancia> en el area <área> No pudo convertir el archivo: <archivo> <detalle>. (EV)	General conversion error message. The cause is in <detalle>.	The detail and the detail XML in errTXT.
Instancia <instancia> en el area <área> No pudo convertir el archivo: <archivo>. Tipo de documento no válido. (EV) Tipo de documento no válido. (errTXT)	The file name prefix does not match any defined document type.	File name (<type>_NPG_…) and the document types configured for the country.
No se encontró ningún conversor de documentos asociados al tipo <tipo>.	The document type exists but has no converter associated.	Document type definition in MessagesTypes.xml. If it is a standard type, contact Gosocket Support.
Debe especificar las propiedades ConverterClass y ConverterLib en el MessageTypes para el tipo <tipo>.	Incomplete document type definition.	MessagesTypes.xml (entry for the type).
No se ha encontrado el archivo con la definición de los tipos de documentos. (EV, at startup)	The country document types file is missing.	Country installation and xDoc update.
Plantilla no encontrada. / No se ha podido cargar la plantilla <archivo>.	The document type template does not exist or has errors.	<type>_Template.xml file in the area's cnfg folder.
No se pudo cargar el archivo <archivo>.	The input file could not be read (locked, empty or with the wrong encoding).	Content and encoding of the spool.
TXTConversionError: <detalle> (errTXT)	Error converting a text spool with the template.	Alignment of the spool with the template (rows and columns) and the error detail.
XSLTConversionError: El tipo de documento <tipo> no tiene ninguna regla asociada para transformación por XSLT. (errTXT)	XSLT conversion is enabled, but the type has no XSLT rule.	Rules in the Conversion / XSLT view.
El documento: <archivo>, Tipo: <tipo>, presenta errores de esquema: <errores>.	The generated XML does not meet the official schema of the document.	Fields listed in <errores> and the spool data.
Se detectaron errores durante la validación con Schematron. + list of rules (EV; Email 010099, when alerts are enabled)	The document does not meet the Schematron business rules.	Each listed rule and the spool data.
Faltan campos obligatorios en el grupo <grupo>, campos esperados: <campos>.	The spool is missing mandatory fields.	Data sent by the ERP for that group.
No se encontró folio para este documento. El campo folio/número no puede ser null o 0. / El folio del documento no es válido.	The document has no folio or the folio is not valid.	Folio field of the spool and numbering configuration.
No se pudo actualizar el historial de folios para el tipo de documento <tipo> en la ruta <ruta>.	xDoc could not record the folio used.	Permissions on the area's cnfg folder and the configured numbering.
Documento duplicado + file, type, issuer and folio	Duplicate Control detected a document already converted with the same key.	Whether it is an intentional resend or an actual duplicate. See Duplicate Control.
El documento tipo <tipo>, folio <folio>, RUT <rut>, folio duplicado.	The folio validation against Gosocket indicates that the folio already exists.	Document folio and documents already issued.
Error al tratar de consultar por el documento tipo <tipo>, folio <folio>, RUT <rut>, consultando si el folio existe. <detalle>	Gosocket could not be queried to check whether the folio already exists.	Connectivity with Gosocket and the detail.
Se ha producido en error durante la conversión.	General message from the country converter. The cause follows it.	The detail that follows the message.
Carta Porte: la version '<x>' no esta soportada (se admiten 2.0 y 3.1). (Mexico)	The spool indicates a Carta Porte version that the conversion does not generate.	Carta Porte complement Version field in the spool.
Carta Porte: el spool trae IdCCP (3.1) pero no Version. (Mexico)	The Carta Porte 3.1 identifier was provided without indicating the version.	Carta Porte complement Version field in the spool.
Carta Porte 3.1: <sección> aun no esta implementado en el converter (TODO-3.1). (Mexico)	Carta Porte 3.1 by spool covers motor freight (autotransporte); maritime, air and rail transport, rights of way and customs regimes are not available.	The section named in the message. Use Carta Porte 2.0 for those cases or remove that data from the spool.
CO <tipo>: el documento no trae UUID, SoftwareSecurityCode o QRCode; no se puede calcular el CUFE (Colombia, XSLT conversion)	The XSLT sheet did not deliver the nodes that xDoc completes when calculating the CUFE.	XSLT sheet of the document type.

✍ Signing

Reference: Signing. The document stays in errTXT, the detail in <name>_sign_error.xml, and alert 050002 is generated.

Message	Probable cause	What to check
No se pudo firmar el archivo: <archivo>. Error <detalle> (EV, errTXT, Email)	General signing error message. The cause is in <detalle>.	The detail and the _sign_error.xml file.
El certificado <archivo> ha expirado. (Email) / El certificado configurado ha expirado.	The certificate has expired. No document is signed.	Renew the certificate in Configuration → Services → Signing and restart the service.
El certificado <archivo> está próximo a expirar. Fecha Expiración: <fecha> (Email)	Daily notice: fewer days remain than the number configured in Daily alert.	Arrange the certificate renewal.
El formato del archivo de certificado no es el correcto.	The file is not a valid certificate or does not match the expected format.	.pfx/.p12 file (or .cer + .key in Mexico).
No se encontró la llave privada. / No se pudo encontrar la llave privada en el certificado. / CSP no contiene una clave privada	The certificate was exported without its private key, or the .key file is missing.	Export the certificate again with its private key.
No se ha definido un algoritmo de firmado para el documento [<archivo>] del tipo [<tipo>]	The document type has no signing algorithm defined.	Type definition in MessagesTypes.xml. Contact Gosocket Support.
El tipo de documento '<tipo>' no tiene asociado ningún firmador.	The document type has no signer associated.	Type definition in MessagesTypes.xml.
Este tipo de documento xml no está soportado. / Tipo de documento desconocido.	The received XML does not match a type the signer recognizes.	Origin of the file in outXML.
Falló la validación del archivo <archivo> utilizando el esquema <esquema>. <detalle>	The signed document does not meet the official schema.	Fields in the detail and the source data.
No se pudo firmar el documento json.	Error signing a JSON document (El Salvador).	Ministry of Finance certificate and JSON content.
No se pudo determinar la fecha de expiración en el certificado.	The certificate expiration date could not be read (El Salvador).	Configured certificate file.
Error al intentar agregar QRCodeURL.	The QR code URL could not be added to the document.	Country QR configuration. Contact Gosocket Support with the document.
El archivo de certificado debe contener exactamente 1 certificado de firma y contiene <n> (…utilizables…). (Ecuador)	The file contains several certificates and none is usable for signing, or more than one has the same expiration date.	That the file has a valid signing certificate with its private key; load a file with only that certificate.
No se pudo exportar la llave privada. (Ecuador)	The certificate private key could not be read in the format that signing needs.	Export the certificate again with its private key and try another .pfx file.
El valor de 'pa_qrcode_url' no es un formato válido. Use chFE={0}&iAmb={1}&digestValue={2}&jwt={3}. (Panama)	The configured QR code URL does not have the expected format.	Local configuration → URL for the QR code. Both the format with iAmb and the previous one without it are accepted.

🚚 Dispatch

Reference: Dispatch. If the document is rejected, a copy stays in errTXT (without a detail XML) and alert 031001 is generated. If the connection with Gosocket fails, the document does not move forward: it remains in signXML and is retried in the next cycle.

Message	Probable cause	What to check
Type Rechazado por la Entidad Tributaria, message with the rejection description (Email 031001)	The platform or the tax authority rejected the document.	The description and the code in Info. The attachment carries the response. Fix the source data and resend. In the current version the message may start with [Sin mensaje]; the rejection description follows it.
Instancia <instancia> en el area <área>. + Documento Enviado a Gosocket. + Code, Success, ID, Descripcion (EV, information)	Record of each submission with the Gosocket response.	Check Success, Descripcion and Messages for the document.
Instancia <instancia> en el area <área>. + API: <dirección>. <código HTTP>. <motivo> (EV)	Gosocket responded with an HTTP error (for example, 401 credentials, 500 server error).	Dispatch credentials and Gosocket service status. The document is retried.
Instancia <instancia> en el area <área>. + Se excedió el tiempo (<n>s) intentando conectarse con el servidor. (EV)	No response from Gosocket in time.	Connectivity, proxy and firewall.
Ocurrió un error despachando el archivo <archivo> en el área <área>, instancia <instancia>. (EV)	Error processing a file before or after submission.	The detail, folder permissions and the file in signXML.
Ocurrió un error chequeando archivos pendientes en el área <área>, instancia <instancia>. (EV)	Error checking documents pending a response.	The detail and connectivity.
Ocurrió un error inicializando el servicio. (EV)	The service could not start (configuration or credentials).	Dispatch configuration and the event detail.
No se ha encontrado el archivo con la definición de los tipos de documentos. (EV)	The country document types file is missing.	Country installation.
La respuesta obtenida no contiene un mensaje XML SOAP	The server response does not have the expected format.	Proxy or intermediate device altering the response.
Error enviando comentario a Gosocket	A comment on the document could not be recorded in Gosocket.	Connectivity and the detail.
El documento superó el tiempo de espera para su aprobación por la autoridad fiscal y no se envió a impresión. (Brazil, Email 031001)	SEFAZ did not return the authorization in time.	Document status in Gosocket.
No se encontró la transformación para el registro del sello fiscal del documento despachado. (El Salvador)	The transformation to store the fiscal seal is missing.	Country installation. Contact Gosocket Support.
El archivo ya no existe; se deja de reintentar su envío: <ruta> (EV, warning)	Another process moved or deleted the file from signXML before it was sent.	Which process moved or deleted it; if it was a pending document, generate it again. Sending of the other documents continues.

📥 Reception

Reference: Reception. Errors are logged in the Event Viewer with the format Área <área> + message. They do not generate email alerts.

Message	Probable cause	What to check
Error descargando documentos: + detail (EV)	The list of received documents could not be obtained.	Connectivity and Reception credentials.
Error descargando documentos:Se excedió el tiempo (<n>s) intentando conectarse con el servidor. (EV)	No response from Gosocket in time.	Connectivity, proxy and firewall.
Error guardando documento recibido ID: <id> (EV)	The document was downloaded but could not be saved.	Disk space and permissions on the area's rcv folder.
Error guardando guía de remisión recibida ID: <id> (EV)	The dispatch guide was downloaded but could not be saved.	Disk space and permissions on the rcv folder.
Error confirmando documentos recibidos / Error confirmando guías recibidas (EV)	The download could not be confirmed to Gosocket. The documents may be downloaded again.	Connectivity. Check for duplicates in rcv.
Error al procesar los documentos. Error en backup de documento (EV)	The backup of the received document could not be saved.	Backup folder, space and permissions.
Error al procesar las guías de remisión. Error en backup de guías de remisión (EV)	The backup of the dispatch guide could not be saved.	Backup folder, space and permissions.
Error descargando los mensajes desde Inbox (EV)	The Inbox messages (acknowledgments) could not be downloaded.	Connectivity and credentials.
Error al confirmar los mensajes a Inbox (EV)	The message download could not be confirmed.	Connectivity.
Error procesando archivo MsgBatch (EV)	A batch of messages could not be processed.	.err files in the area's rcv folder.

🖨 Printing

Reference: Printing. The document stays in toprint with the .err extension and alerts 030002 to 030005 are generated.

Message	Probable cause	What to check
El archivo <archivo> no pudo ser impreso. Error: <detalle> (EV, Email 030002)	Error sending the document to the printer.	Configured printer, connection and the detail.
El archivo <archivo> no pudo ser impreso. Error <detalle> (EV, Email 030005)	Unexpected error while printing.	The error detail. If it repeats, contact Gosocket Support.
xdoc@batchprinter - Impresión de documento <archivo> + errors (EV, Email 030003)	Printing or the PDF ended with errors.	Printing rule, template and the error text.
El tipo de documento para el documento <archivo> no está definido. (EV, Email 030004)	The type of the document to print was not identified.	XML content and country document types.
No se encontró ninguna plantilla asociada al documento <archivo>. La plantilla no existe<ruta>	There is no print template for the document.	Printing Rules and templates in cnfg.
No se ha encontrado el archivo de plantilla Jasper: <ruta>.	The template's .jrxml file is missing.	Template path in the printing rule.
Ya existe un PDF con nombre <archivo> en la ruta <ruta>	The PDF had already been generated.	If it is a reprint, move or delete the previous PDF.
Error al paquetizar PDF. <detalle>.	The PDF package could not be built.	The detail, disk space and permissions.
No se ha encontrado el archivo con la definición de los tipos de documentos. (EV, at startup)	The country document types file is missing.	Country installation.
Se ha producido un error con el formato de los archivo de comandos de reimpresión. …	The reprint command file does not have the [RUT];[TipoDoc];[Folio] format.	Content of the command file.
Se ha producido un error descargando el documento desde el server para su reimpresión	The document to reprint could not be downloaded from Gosocket.	Connectivity and document data.

📄 Pagination

Reference: Pagination. Errors are logged in the Event Viewer. They do not generate email alerts.

Message	Probable cause	What to check
Área <área> + No se pudo paginar el archivo: <archivo> + detail (EV)	Error splitting the spool into documents.	The detail and the input spool.
No se pudo paginar el archivo: <archivo> + No se encontró la plantilla <tipo>_Template.xml (EV)	The document type template is missing.	<type>_Template.xml file in cnfg.
No se pudo paginar el archivo: <archivo> + La plantilla no contiene el elemento fin de documento. (EV)	The template does not define where each document ends.	End-of-document element in the template.
Tipo de documento no definido para el spool <archivo> (EV)	The spool prefix does not match a defined type. The spool is moved to the alerts folder.	Spool name and document types.
El spool <archivo> no cumple el formato de trazabilidad de lotes (TDC_NPG_IDLOTE<extensión>). (EV)	Batch traceability is enabled, but the name does not include the batch ID.	Name of the spool generated by the ERP.
No se pudo actualizar el historial de folios para el tipo de documento <tipo> en la ruta <ruta>. <detalle> (EV)	With auto-numbering, the assigned folio could not be recorded.	The area's CAF folder and available numbering.
Error paginando el archivo: <archivo> (EV)	Error writing the paginated documents.	Permissions and space on the printed folder.
No se ha encontrado el archivo con la definición de los tipos de documento. (EV, at startup)	The document types file is missing.	Country installation.

⚖ Load balancing

Reference: Load balancing. Errors are logged in the Event Viewer. They do not generate email alerts.

Message	Probable cause	What to check
Área: <área> + No existen instancias definidas para esta área. (EV)	The area has no active instances to distribute the documents to.	Area instances and their status.
Área: <área> + file path + detail (EV)	A document could not be moved to an instance's inTXTtoXML folder (file locked or duplicated).	The file in printed and the instance folder.
Área: <área> + No se pudo leer el archivo de configuración Config.xml. <detalle> (EV)	Area configuration corrupted or without permissions.	cnfg\Config.xml.

🔌 Connectors

Reference: Connectors. Errors are logged in the Event Viewer with source Servicio xdoc@connector_<area>. Each connector also has its own messages (see the connector's page).

Message	Probable cause	What to check
Área: <área> + Error ejecutando el conector <conector> (EV)	The connector ended with an error.	Earlier events from the same connector (they carry the detail) and its configuration.
Área: <área> + Se ha ejecutado el conector <conector> (EV, information)	Normal execution record.	Useful to confirm that the connector is running.
Área: <área> + No se pudo leer el archivo de configuración Config.xml (EV)	Area configuration corrupted or without permissions.	cnfg\Config.xml.
SFTPConnector: Error general [<archivo>] <detalle> (EV)	SFTP connection or transfer error.	Server, port, credentials and permissions on the remote folder.
ConvertExcelToXML.IOException / ConvertExcelToXML.Exception (Email 070001)	The Excel connector could not read or transform the file.	Excel file open in another program, format and expected sheet.
MegaPrintConnector.Exception (Email 070001)	Error communicating with MegaPrint (Guatemala).	Credentials, connectivity and the error message.
Archivo <archivo> disponible en la carpeta <carpeta> del servidor (Email 070001, type Procesamiento terminado)	PackageToPrint notice: the package is available. Not an error.	Nothing; it confirms delivery.
Connector SAPRFCConnectorIn: Error / SAPRFCConnectorOut: Error / SAPRFCConnectorOut: Error al cargar el xml (EV)	Error communicating with SAP or in the received document.	RFC connection, SAP destination and the detail.
Error procesando documento: <documento> en SAP >> <detalle> (connector log)	SAP returned an error while processing a document.	The document in SAP and the detail.
Duplicado según secuencia <secuencia>.	The connector detected a file that was already processed.	Whether the resend is intentional.

🔔 Alerts

Reference: Alerts. Errors of the Alerts service itself (EV, source Servicio xdoc@alert_<area>).

Message	Probable cause	What to check
Área: <área> No se ha podido notificar de la alerta vía correo electrónico: <detalle>	Sending through SMTP failed. The alert stays in alerts and is retried.	SMTP server, port, user, proxy and network access.
Área: <área> Error procesando la alerta.	The alert file is corrupted or does not have the expected format.	The alert_*.xml file in alerts.
Área: <área> Error procesando la alerta, no se pudo eliminar archivo: <archivo>. / …no se pudo eliminar el adjunto <archivo>.	The email was sent, but the file remained locked.	Permissions on the alerts folder or antivirus.

⚙ How to investigate an error step by step

1. Locate the document. Search for the file by name in xDoc Manager → Documents (the instance's Errors node) or directly in errTXT. If it is not there, check signXML (pending dispatch), toprint (.err) or alerts.
2. Read the detail. Open the detail XML (same name in Conversion; _sign_error.xml in Signing). Note the code, the source and the message.
3. Check the Event Viewer. In the Event Viewer, filter by Service: and Instance:, and look for error events close to the time of the problem.
4. Look up the message in this catalog. Identify the service and the probable cause. If it is an alert, use the Code from the email and the Alert codes table.
5. Fix the cause. Data errors are usually fixed in the ERP and the document is resent. Configuration errors are fixed in the Manager and require restarting the service.
6. Verify. Once the document is resent, confirm in the Event Viewer that the error does not recur.

info

In Documents → Errors, the .txt files from errTXT are shown as Archivo en Conflicto (file in conflict) and the .xml files as Error de conversión (conversion error), even if the .xml is a document that failed in Signing or Dispatch. Check the file name and its detail to know at which stage it failed.

🧪 Examples

Example 1: rejection email in dispatch

• Code: 031001 · Type: Rechazado por la Entidad Tributaria · Source: xdoc@dispatch
• Message: rejection description · Additional Info: rejection code · Attachment: tax authority response
• What to do: read the description, fix the data at the source and resend. The rejected document stays in errTXT.

Example 2: document in errTXT due to an invalid type

• Event Viewer: Instancia 01 en el area FACTURAS No pudo convertir el archivo: 99_NPG_001.txt. Tipo de documento no válido.
• Cause: the 99 prefix is not a defined document type.
• What to do: fix the name of the file generated by the ERP.

Example 3: certificate about to expire

• Code: 050002 · Type: Firmado · Message: El certificado <archivo> está próximo a expirar. Fecha Expiración: <fecha>
• What to do: request the renewed certificate from the customer and load it in Signing before the expiration date.

🌎 Country variations

Country	Particularity
Paraguay	Dispatch to SIFEN generates alerts with source TaxAuthority: 031000 (error reading or processing a document, batch or event), 031001 (error sending to SIFEN), 031002 (document, batch or event approved) and 031003 (rejected or not processed). They are enabled in Local configuration with Generate alerts for failed operations and Generate alerts for successful operations. Approvals arrive with type Error even though they are not errors; rely on the message. If SIFEN does not respond to a batch query, the service records the failure (and, if alerts for failed operations are enabled, may generate 031000), moves on to the next batch and queries that batch again in the next cycle.
Brazil	Alert 031001 when the document exceeds the authorization wait time and is not sent to printing.
El Salvador	Specific messages for JSON signing and the fiscal seal (see Signing and Dispatch).
All	The converters of each country have their own field validation messages (for example, NFe in Brazil or CFDI in Mexico). These messages appear in the conversion error detail.

🧭 Implementation considerations

• Enable alerts in Configuration → Services → Alerts and define recipients at least for All. For signing errors, use the Certificate expiration type.
• Configure the SMTP server in Connectivity configuration…. Without SMTP, alerts are not sent.
• Reception, Pagination, Load balancing and the Connectors service log their errors in the Event Viewer; monitor them there in addition to email.
• Periodically check each instance's errTXT and the alerts folder; if files pile up, there are unattended errors or alerts without recipients.
• To investigate conversions, enable Generate conversion traceability in Configuration → Traceability during the diagnosis.
• Before clearing the Event Viewer from the Manager, accept saving the log to keep the history.

📦 What to report to Gosocket Support

If the error is not resolved with this catalog, contact Gosocket Support with these inputs (sanitized, without taxpayer data or credentials):

1. Country, area, instance and xDoc version.
2. Affected service and approximate time of the error.
3. Full text of the event from the Event Viewer (source and message).
4. The detail XML from errTXT or the alert email (code, type, source and message).
5. The input document (spool or XML) with test or anonymized data, and the template or rule involved.
6. What changed before the error (update, certificate, configuration) and whether it recurs with other documents.

note

Do not send certificates, passwords, complete Config.xml files or real customer documents without sanitizing them. Use test or anonymized data.