wrenchTroubleshooting

This guide helps you resolve common issues when using mini-eric.

Common Issues

Binary Not Found

Error:

ceric binary not found: /path/to/ceric

Solutions:

  1. PHP SDK: Ensure the ceric binary is in the correct location

    # Check if binary exists
    ls -la vendor/bin/ceric
    # Create symlink if needed
    ln -sf ../rechtlogisch/mini-eric-"$ID"/bin/ceric vendor/bin/ceric
  2. Standalone: Verify the binary path and permissions

    # Check if binary exists and is executable
    ls -la /path/to/ceric
    chmod +x /path/to/ceric
  3. Custom path: Specify the correct binary path

    $ceric = new Ceric(binaryPath: '/correct/path/ceric');

ERiC Libraries Missing

Error:

Solutions:

  1. Check library directory structure:

  2. Verify environment variable:

  3. Custom vendor path:

Certificate Issues

Error:

Solutions:

  1. Check certificate file exists:

  2. Verify certificate PIN:

  3. Inspect eric.log for ERRORs:

  4. Test with default certificate:

Note: For environment variable configuration, see Environment Variablesarrow-up-right.

  1. Check certificate format:

    • Ensure certificate is in PFX format

    • Verify certificate is not corrupted

    • Try to login with certificate on https://elster.de

    • Check certificate permissions

Permission Errors

Error:

Solutions:

  1. Check directory permissions:

  2. Check ownership:

  3. Create directory if missing:

XML Validation Errors

Error:

Solutions:

  1. Validate XML structure:

  2. Check XML encoding:

    • Ensure XML uses UTF-8 encoding

    • Check for BOM (Byte Order Mark) issues

  3. Verify data type matches content:

  4. Check required elements:

    • Ensure all mandatory XML elements are present

    • Verify element names and structure match ELSTER specifications

Process Execution Errors

Error:

Solutions:

  1. Inpect processResult of ceric:

  2. Check ERiC logs:

  3. Verify ERiC libraries:

    • Ensure all required ERiC libraries are present

  4. Test with simple XML:

Download Errors

Error:

Solutions:

  1. Check OTTO logs:

  2. Verify UUID format:

  3. Check network connectivity:

    • Ensure internet connection is available

    • Verify firewall settings allow outbound connections to https://objektspeicher.elster.de (Port 443)

Error Code Reference

Command Line Errors (1-19)

Code
Error
Solution

1

Unknown or incomplete argument

Check command syntax and parameters

10

Missing --pathXml

Provide input XML file path

11

Missing --dataType

Specify data type parameter

12

Unsupported data type

Use supported data type, check supported-data-types in composer.json

13

Invalid usecase

Use 'draft', 'send' or 'transmit'

14

Data type print not supported

Use other supported usecase for given data type

15-18

Storage directory errors

Check directory permissions and existence

19

Missing --objectUuid for download

Provide object UUID for download operations

File I/O Errors (20-29)

Code
Error
Solution

20

Could not open input XML file

Check file path and permissions

30

Invalid UUID format

Use valid UUID v4 format

ERiC Errors (100-199)

Code
Error
Solution

100

Could not initialize ERiC instance

Check ERiC libraries and configuration

101

Could not load certificate

Verify certificate path and PIN

110

Error while creating header

Check ERiC logs for details

120

XML validation failed

Validate XML structure and content

130

Could not create output file

Check storage directory permissions

140

Error while processing XML

Check ERiC logs and XML content

150-151

Empty buffer/content

Check ERiC processing logs

160

Server response contains errors

Review server response for error details

170-173

Download operation errors

Check OTTO logs and network connectivity

Debugging Tips

Enable Verbose Logging

Check Log Files

Test with Minimal Examples

PHP SDK Debugging

Performance Issues

Slow Processing

Causes:

  • Large XML files

  • Network latency for send/transmit operations

  • Insufficient system resources

Solutions:

  1. Optimize XML size:

    • Remove unnecessary whitespaces/tabs/line breaks

  2. Check system resources:

  3. Use appropriate use case:

    • Use draft for validation only

    • Use transmit when PDF is not needed

Memory Issues

Error:

Solutions:

  1. Increase PHP memory limit:

Getting Help

Check Documentation

  1. CLI Referencearrow-up-right - Complete command-line reference

  2. PHP SDK APIarrow-up-right - PHP SDK documentation

  3. XML Examplesarrow-up-right - Working XML examples

Support

For support and custom inquires, contact Recht logisch GmbH & Co. KGarrow-up-right.

Reporting Issues

When reporting issues, please include:

  1. System information:

    • Operating system and version

    • PHP version (for SDK issues)

    • ceric --version (and cotto --version)

  2. Error details:

    • Complete error message

    • Exit code

    • eric.log/otto.log file contents

  3. Reproduction steps:

    • Minimal XML file that reproduces the issue

    • Exact command used

    • Expected vs actual behavior

  4. Environment:

    • Certificate information (if applicable)

    • Network configuration

Last updated