p01 Kansas City Southern
Skip to main content

Recent Topics

xx

clip
New press
by Slappy
Today at 12:39:25 PM

xx

xx
PitStop 2018 just announced. Ships in April
by Joe
May 22, 2018, 01:37:18 PM

angry
Trouble with InD VDP
by delooch
May 21, 2018, 06:01:35 PM

xx
Adobe Creative Cloud Price Increases
by Joe
May 17, 2018, 05:48:25 PM

xx
PKG Installer Inspection
by Slappy
May 17, 2018, 01:36:00 PM

xx
Business Card order
by scottrsimons
May 16, 2018, 10:27:26 AM

xx
Ink saving,4d colour conversion
by danydany
May 16, 2018, 10:10:07 AM

clip
java and 3D Export
by Joe
May 15, 2018, 08:42:11 PM

xx
Individual Page Proofs
by Slappy
May 14, 2018, 11:12:05 PM

xx
Prinergy 1st Refines Questions
by DPSprint
May 14, 2018, 10:48:01 PM

xx
Xeikon Indigo toner press Iso standards
by danydany
May 14, 2018, 10:21:55 AM

Topic: Error in import module (Read 7905 times) previous topic - next topic

Re: Error in import module

Reply #15
you don't mention what the version of .ai you are using.
Is it CS4, CS5, or?
Prepress guy - doin' jobs one at a time


Re: Error in import module

Reply #17


From Prepressure...

PostScript error: typecheck
A PostScript error: typecheck is one of the most common PostScript errors. It signals that the RIP encounters an operand of a wrong type – i.e. an operator expected one type of data and got something else.

Most common causes:

Typecheck errors are usually cause by corrupted data. This may indicate a problem with the printer driver. Try reinstalling it if the error occurs printing from various applications. Check the network and/or server if the error persists.

Try copying and pasting your data to a new document.
Try opening and resaving all images and links.

Offending command “dF3(!2xT” (or other random characters)

If the offending command contains random characters, it may indicate a problem with the communications link or driver. This problem may also occur when PostScript files are transferred from one computer platform to another. Try using an ‘ASCII’ or ‘Text only’ format instead of a binary format when saving.


It's been awhile but what I remember from Nexus is once it throws the VMerror, any errors afterward are not really relevant since the stream is corrupted once it runs out of VM.


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.
Bates  •  Vorhees  •  Meyers  •  Krueger  •  Hobbs  •  Lecter  •  Dollarhyde  •  Bateman  •  Gumb  •  Doe  •  Morgan •  Todd •  Kevin •  DCS •  Kasem

"Does it really matter? There's shit in the meat and we're all pink inside. Live a little..." The Gnub

"I look forward to the sweet release of death..." Dave, on behalf of all Prepress

Member #285 • OG PH8 • Award-Winning • Population Control Enthusiast • Master of Freehand Jobs • Hater of All • Prodigy of Addition & Subtraction

Re: Error in import module

Reply #18



From Prepressure...

PostScript error: typecheck
A PostScript error: typecheck is one of the most common PostScript errors. It signals that the RIP encounters an operand of a wrong type – i.e. an operator expected one type of data and got something else.

Most common causes:

Typecheck errors are usually cause by corrupted data. This may indicate a problem with the printer driver. Try reinstalling it if the error occurs printing from various applications. Check the network and/or server if the error persists.

Try copying and pasting your data to a new document.
Try opening and resaving all images and links.

Offending command “dF3(!2xT” (or other random characters)

If the offending command contains random characters, it may indicate a problem with the communications link or driver. This problem may also occur when PostScript files are transferred from one computer platform to another. Try using an ‘ASCII’ or ‘Text only’ format instead of a binary format when saving.


It's been awhile but what I remember from Nexus is once it throws the VMerror, any errors afterward are not really relevant since the stream is corrupted once it runs out of VM.


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.


Yes, it could be the file. And probably is.
Mac OS 10.12 Sierra | Prinergy 7.5 | Adobe Creative Cloud 2017 | Two Luscher XPose 160 CTP units

Prepress: One who does precision guess work based on unreliable data provided by those of questionable knowledge.

Re: Error in import module

Reply #19
Hard to tell without something to look at/test.
Bates  •  Vorhees  •  Meyers  •  Krueger  •  Hobbs  •  Lecter  •  Dollarhyde  •  Bateman  •  Gumb  •  Doe  •  Morgan •  Todd •  Kevin •  DCS •  Kasem

"Does it really matter? There's shit in the meat and we're all pink inside. Live a little..." The Gnub

"I look forward to the sweet release of death..." Dave, on behalf of all Prepress

Member #285 • OG PH8 • Award-Winning • Population Control Enthusiast • Master of Freehand Jobs • Hater of All • Prodigy of Addition & Subtraction

Re: Error in import module

Reply #20


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.

Re: Error in import module

Reply #21



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.


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]

That's going to be a huge PDF. Hope you don't need to email it. :laugh:
Mac OS 10.12 Sierra | Prinergy 7.5 | Adobe Creative Cloud 2017 | Two Luscher XPose 160 CTP units

Prepress: One who does precision guess work based on unreliable data provided by those of questionable knowledge.

Re: Error in import module

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

Thanks again.

Re: Error in import module

Reply #23

Haha. 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?

Re: Error in import module

Reply #24


Haha. 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.

Re: Error in import module

Reply #25



Haha. 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.


Sounds like it's time to delete one image at a time and try to re-rip. Fonts converted to outlines?

Re: Error in import module

Reply #26
Yes, all fonts are outlines. If my workaround didn't work, which it did thankfully, deleting images one at a time was going to be my next step. When I have some time, I am probably going to do that anyway because I would like to get to the root of the problem in case it should happen again.

Re: Error in import module

Reply #27

Yes, all fonts are outlines. If my workaround didn't work, which it did thankfully, deleting images one at a time was going to be my next step. When I have some time, I am probably going to do that anyway because I would like to get to the root of the problem in case it should happen again.


Smart man... work in Prepress? :hello:
Bates  •  Vorhees  •  Meyers  •  Krueger  •  Hobbs  •  Lecter  •  Dollarhyde  •  Bateman  •  Gumb  •  Doe  •  Morgan •  Todd •  Kevin •  DCS •  Kasem

"Does it really matter? There's shit in the meat and we're all pink inside. Live a little..." The Gnub

"I look forward to the sweet release of death..." Dave, on behalf of all Prepress

Member #285 • OG PH8 • Award-Winning • Population Control Enthusiast • Master of Freehand Jobs • Hater of All • Prodigy of Addition & Subtraction

Re: Error in import module

Reply #28

[/quote]

Smart man... work in Prepress? :hello:
[/quote]

Sometimes I think WAY too long :rolleyes:

Re: Error in import module

Reply #29




Smart man... work in Prepress? :hello:
[/quote]

Sometimes I think WAY too long :rolleyes:
[/quote]

Welcome to the club.
Bates  •  Vorhees  •  Meyers  •  Krueger  •  Hobbs  •  Lecter  •  Dollarhyde  •  Bateman  •  Gumb  •  Doe  •  Morgan •  Todd •  Kevin •  DCS •  Kasem

"Does it really matter? There's shit in the meat and we're all pink inside. Live a little..." The Gnub

"I look forward to the sweet release of death..." Dave, on behalf of all Prepress

Member #285 • OG PH8 • Award-Winning • Population Control Enthusiast • Master of Freehand Jobs • Hater of All • Prodigy of Addition & Subtraction