Topic Options
#36235 - 06/02/11 10:48 AM Error loading metadata file: I/O error 6.
cube Offline
OL User

Registered: 09/03/10
Posts: 76
Hi,

I am getting the below error when I try to generate capture ready docs through my process.


W4022 : Error while executing plugin: Error loading metadata file: I/O error 6.
Capture Fields Generator: W1603 : Plugin failed - 18:19:51

What I am trying to do is, in the Capture field generator's "Document title" property I want to use a unique number (which is present as a node in my xml data stream) -

E.g. - xmlget('/shipments[1]/shipment[1]/id[1]',Value,KeepCase,NoTrim)

Hence I am using a XML splitter at the beginning of my process. In my PP form I have defined the document marker begin based on the unique number(as described above) when it changes.

Here is my process

1-folder capture
2-create metadata (the pp form selected)
3-XML Splitter
4-Capture Fields generator (optimized PS selected)
5-Printer queue output

If I place the Create metadata node after XML splitter I get the following error.


W3001 : Error while executing plugin: I/O error 105
Create Metadata: W1603 : Plugin failed - 18:36:46


Please help

Thanks
_________________________
There is no Knowledge that is not Power - MK

Top
#36237 - 06/02/11 02:08 PM Re: Error loading metadata file: I/O error 6. [Re: cube]
Raphael Lalonde Lefebvre Offline
OL Expert

Registered: 10/14/05
Posts: 4956
Loc: Objectif Lune Montreal
cube,

I did some tests on this, and indeed, I am getting the same errors as you do. However, I did a bit of research, and the documentation recommends that we use the Metadata Sequencer if we need to split the job into multiple parts.

However, I am not sure I understand why you want to split it in the first place. From what I understand, it's because you want to preserve some values that are present in the first record? If that's the case, an alternative solution would be to add a Set Job Info action right before the create metadata that would contain the value that you need, and then call that job info in your form. This way, it will allow you to reuse the value of record 1 multiple times, while the other information will be the one of the current record.

Hope that helps!

Regards,
Raphaël Lalonde Lefebvre

Top
#36270 - 06/07/11 05:08 AM Re: Error loading metadata file: I/O error 6. [Re: Raphael Lalonde Lefebvre]
cube Offline
OL User

Registered: 09/03/10
Posts: 76
Hi Raphaël,

Thanks for the pointer. I was able to fix the issue without using metdata sequencer and still using the XML Splitter. However, I have tested with using Meta data sequencer instead of XML splitter and the error still persists. The fix was not related to what you use for splitting but to do with the Capture Fields Generator plugin as I describe below.

I will explain the scenario in detail.

My xml data stream has a node that has the id of the document with the following structure.

<records>

<record>
<id>001</id>
<other stuff>
<record>

<record>
<id>002</id>
<other stuff>
<record>

<record>
<id>003</id>
<other stuff>
<record>

</records>

I want to use the contents of the id node to identify the capture document in the database, so that when I go to Prefernces > PP Capture > Manage Documents, I see a list like as follows. (Please let me know if there is another better way to do this).

CaptureDoc_001
CaptureDoc_002
CaptureDoc_003

Here is my workflow that has removed the I/O errors but I have a new issue with printing the capture ready doc on the printer.

1 - Folder capture

2 - XML Splitter - It is set to split when condition node "<record>" is found.

3 - Create metadata - I have selected the appropriate ptk file.

4 - Capture Fields Generator - Here is where I have now selected "Continue Process with PDF (with new metadata)" instead of "Continue process with optimized PS (no metadata)". This is what fixed the errors as mentioned in my previous post. Also here is where in the "Document Title" field I am using the "<id>" field from the data stream through a data selection. This stores the capture documents as required and as mentioned above - CaptureDoc_001, CaptureDoc_002...etc.

5 - Unconditional Branch (go right) - Printer queue output (LPR pointing to the IP of my printer). I have selected passthrough mode. The new problem here is now that it gives PS errors in the printout. I assume it is because the printer is expecting PS and not an already ripped PDF?

6 - After the Branch (go down) - Send to folder and save as .pdf - this works without any problems.

My question is - How can I use optimized PS as output from the step 4 above and still have metadata?. Selecting - "Continue Process with PDF (with new metadata)" has fixed the problem of "Error loading metadata file: I/O error 6" errors, but metadata is lost.

I have tried placing the create metadata before and after step 4, without any success.

I have tried using windows driver output in step 5 above and the capture ready document is printed successfully, however I want to avoid using this because of performance and job file size issues when thousands of capture ready docs are printed, more over I noticed that the pattern is printed darker than how it prints through optimized PS and when writing on the pattern that was printed through windows driver output, the Anoto pen keeps vibrating and when docked it gives various intermittent errors like - the ink not showing correctly on the generated output (missing strokes), Document was inked outside of known fields.

Thanks for all your help
_________________________
There is no Knowledge that is not Power - MK

Top
#36348 - 06/14/11 08:28 AM Re: Error loading metadata file: I/O error 6. [Re: cube]
cube Offline
OL User

Registered: 09/03/10
Posts: 76
Hello,

Any one else facing this issue?

Thanks!
_________________________
There is no Knowledge that is not Power - MK

Top
#36886 - 08/12/11 09:03 AM Re: Error loading metadata file: I/O error 6. [Re: cube]
Lou Pace Offline
OL User

Registered: 01/10/04
Posts: 69
Loc: Bloomfield, New Jersey
Cube,

Add a Rename action just after your splitter and set the filename to something unique, like your key value + %u and you should be OK.

Lou
_________________________
thanks,
Lou Pace

Top