Quote from: G_Town on January 26, 2012, 02:51:57 PM

Quote from: DHG on January 26, 2012, 02:48:47 PMHaha. I know. Only 150mb going on a disc or FTP so not an issue.

Thanks again.

You are printing out of ai to nexus?

Have you tried making saving a pdf from ai and submitting that to nexus?

Doing a run file on the .ai file. Do it all the time without any problem. Tried printing out of .ai to the same workflow too.

Yes, tried a PDF too as well as placing in InDesign and printing. All gave me the same exact errors.

Also tried copying and pasting into a new .ai document as well as changing the name of the file. All came up with the same errors.

Haha. I know. Only 150mb going on a disc or FTP so not an issue.

Thanks again.

I'm kinda flying blind on this, since I have no idea what to expect from Nexus. I still think it's the file. Unfortunately, DHG won't post it, so I can't really help any more than that.
[/quote]

I know. Thanks, I appreciate it, but because of the whole confidentiality agreement, with it, I can't.

I may have come up with a workaround that I have used in the past where I print it to a raster workflow and then make the PDF from the PSTI file.

Quote from: david on January 26, 2012, 02:18:19 PMyou don't mention what the version of .ai you are using.
Is it CS4, CS5, or?

Tried both 4 and 5.

Quote from: david on January 26, 2012, 11:42:59 AMare all the images embedded or linked?

if links, you may need to open each one and resave to check the options. For instance, some may have LZW, some may not (some programs have issues with that, depending on the age of the software).

Only 6 images in the .ai file. All are embedded. I embedded them, BTW, so I have the original PSD files. First thing I checked was the images themselves. All CMYK with nothing out of the norm. All 8 bit. No LZW.  After the initial failures. I flattened the images that I could. Tried with images embedded and without. Same results.

Quote from: G_Town on January 26, 2012, 11:42:11 AM

Quote from: DHG on January 26, 2012, 10:58:16 AMOnly number and underscore.

18563_3589.ai

Don't suppose you could post/send the file for me to look at?

What type of file are you actually importing, PDF, PS?

I would love to send you the actual file, but unfortunately can't. Thanks for the offer

Only number and underscore.

18563_3589.ai

No fonts. All outlines.

Running Nexus 9.0.3. Getting error in import module.

 -  VMerror; OffendingCommand: --@fetchroutine-- ]%
 - : VMerror; OffendingCommand: --@fetchroutine-- ]%
 -  typecheck; OffendingCommand: handleerror ]%
 - : typecheck; OffendingCommand: handleerror ]%
 -  undefined; OffendingCommand: ReportError ]%
 - : undefined; OffendingCommand: ReportError ]%
 -  )--print-- errorname --dup-- --type-- /stringtype --ne-- {256
 - : )--print-- errorname --dup-- --type-- /stringtype --ne-- {256
 - PS Interpreter ended with error nr 40


Any clue what the errors mean?

Using DCS2 because that is what the printer requires, trapped DCS2. They will not except any other file format.

We do not have support so I am reaching out to this forum in the hope that someone here can lead me in the right direction. Currently running Nexus 9.0.3. I have 2 workflows that create DCS2 files, one raster and the other vector. Problem I am having is the vector workflow does not hold the spot color, but the raster the raster workflow does. The Assemble DCS and Merge DCS modules in each workflow are identical. The raster workflow only creates the DCS2 file. The vector workflow also creates a PDF (high and low res), Artpro file and PSTI files along the DCS2. All the other files produced in the in the vector workflow retain the spot color. If I highlight the Assemble DCS and Merge DCS modules that the actual file is going through it still shows the spot color listed in the separations, but ultimately the spot color converts to process in the DCS2. Any clue where this may be going wrong?