cancel
Showing results for 
Search instead for 
Did you mean: 

Error parsing Export plan file: erreur : ?

former_member685625
Discoverer
0 Kudos

Hi all,

i have installed SAP dataservices on a new computeur last week, today for my first try, i'll try to export a job by ATL and an error occurs :

(14.2) 06-16-20 10:58:20 (E) (15220:2820) RUN-055007:Export
L'erreur interne <Error parsing Export plan file: L'analyseur XML a échoué : erreur : <expected entity name for reference> ?
la ligne <2>, caract. <92> dans le fichier <C:Users\*****\AppData\local\SAP\Data Services\Workspace\Exp1C49.tmp>.> est survenue

a part of this message is in french sorry 🙂

I found nothing about this... somebody have an idea ? i tried to export some job or just some DF same error... and same error too if i export to .xml file instead of .atl

thanks !

Accepted Solutions (1)

Accepted Solutions (1)

former_member685625
Discoverer
0 Kudos

Hi all and thanks,

the problem with me was that there was a character '&' in the path where i want to record my atl file (on one drive)

if i record it first in my computer then i can copy it on the one drive and it work with tis process.

thanks.

Answers (1)

Answers (1)

vijayb
Participant
0 Kudos

Hello liegeus,

Please check the below content of 2870233 note and link.

Symptom

In the Designer Application, export a job to an ATL file and the process will fail with the following error: Error " RUN-055007: Export Internal error <Error parsing Export plan file: XML parser failed: Error: <invalid character 0x1F in attribute value 'name'> at line <19>, char <23> in file <SAP\Data Services\Workspace\Exp###.tmp>.> occurred. • Object exists in the <Local Repository>.AL_Lang table. • Creating a new object with the same name does not fail with a duplicate naming error.

Environment

SAP Data Services 4.2

Cause

There is an unprintable character in the name of the object stored in the local repository.

Resolution

If you do not want to modify the local repository content:

1. In the Designer Application, re-create the failing object and add it to the job design.

2. Save the edited job and export to an ATL file. The error should be resolved.

If you want to modify the local repository content:

Find the corrupted record in the <Local Repository>.AL_Lang table and edit the name.

Note: this is not recommended best practice as the AL_Lang table interacts with other repository tables such as ALVW_ParentChildObject, so all the references of the object name would have to be edited.

https://answers.sap.com/questions/12297295/error-when-export-job-to-atlxml-file-error-parsing.html

Hope it will helpful.

Thanks,

Vijay