Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in Toronto Sept 9th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Error: NameSpaceTool_tFileInputXML_1 cannot be resolved to a type

I am trying to run a very simple example job in TOS v2.3.2. I just have a tFileInputXML to parse an xml file and tLogRow component to print in the console the values of the xml file. When I run the job, I get the following error:
Exception in thread "main" java.lang.Error: Unresolved compilation problems:
NameSpaceTool_tFileInputXML_1 cannot be resolved to a type
NameSpaceTool_tFileInputXML_1 cannot be resolved to a type
Syntax error on tokens, delete these tokens
at mantis.mantis.Mantis.tFileInputXML_1Process(Mantis.java:267)
at mantis.mantis.Mantis.runJobInTOS(Mantis.java:917)
at mantis.mantis.Mantis.main(Mantis.java:836)
Is this a bug? Did I do something wrong? What can I try or where can I seek for more info on this problem?
Thanks in advance.
Labels (4)
13 Replies
Anonymous
Not applicable
Author

Initially I thought so but the programs works with no compilation errors when you close the Talend and reopen it.
Thanks
Yogesh
_AnonymousUser
Specialist III
Specialist III

Hi All,
I am new on talend , i have a existing application build on talend , here we are basically migrating data base from access to postgres , but it is working too slow , now we made change in process now we moving data base from postgres to postgres , i change my source data base to postgres(previously it was access) and prapogate change at other place , but still when i tried to run job it is giving error "url_tAccessInput_1 cannot be resolved",context group showing a previous value and when i select my new change data base it is showing a old value inside component .
Please help me , what more changes i have to make in my process
Thanks!
_AnonymousUser
Specialist III
Specialist III

Please look carefully if you have strings without defined length in schema. It was the root of such an issue in my case
suttong
Contributor
Contributor

Make sure your x-path variables are enclosed in " quotes e.g. "/x-path/path" vs. x-path/path