Illustrator CS3 Filter issue

[Halcyon]

When using the Filters > Create > Crop Marks command I get the following message

"The Filetr cannot complete because of an unknown error" Error: NESS

This doesn't happen all the time, sometimes I can copy all the artwork and paste it on a new document and then the problem is solved, other times it just won't work. This has happened before ever since the days I was using version 8, 9, CS and CS2, but now woth CS3 it is very frequent.

Any of you have encountered the same issue?
Is it worthwhile reporting to Adobe?

TIA

JC

[Blue Velvet]

Is this in RGB documents or CMYK? Or both?

[Halcyon]

Is this in RGB documents or CMYK? Or both?

It could go either way.
It's rather difficult to identify what causes the problem because you cannot isolate a certain circumstance of when it happens.

For example: On the same document, first I select an object an when the fileter is applied the error shows up, if a second object is selected and the filter is applied then it work...sometimes :-)

More than anything I'm curious if this is an unresolved bug worthwhile reporing to Adobe...of course it is an annoying bug.

JC

[hessdesigns]

Instead of using the filter, I normally create a rectangle around my artwork, then choose Object > Crop Area > Make. Beauty of this is that if you change the size of your art, simply choose Object > Crop Area > Release, then resize your box and make a new crop area. Maybe that will help?

[Halcyon]

Instead of using the filter, I normally create a rectangle around my artwork, then choose Object > Crop Area > Make. Beauty of this is that if you change the size of your art, simply choose Object > Crop Area > Release, then resize your box and make a new crop area. Maybe that will help?

Yes it works...but not all the time.

Some of the files have imposition of two or more jobs (artworks) and each needs its own crop marks. With the option you mention only one set of crop marks is allowed per file.

JC

[iMeowbot]

Yes it works...but not all the time.
I don't have any ideas to offer, but can confirm that you're not the only one to run into this problem (pasting everything into a new document is the same workaround I've used when this happened). It seems to be more of a problem if the drawing was saved down to either an older Illustrator format or as SVG, but i don't think that's even been the case every time.

[Halcyon]

I don't have any ideas to offer, but can confirm that you're not the only one to run into this problem (pasting everything into a new document is the same workaround I've used when this happened). It seems to be more of a problem if the drawing was saved down to either an older Illustrator format or as SVG, but i don't think that's even been the case every time.

So I'm not alone on this :-)

Maybe it's time I drop a few lines to Adobe so they can patch this and have it fixed on a future update. In the meantime will cross my fingers and hope for the best next time the filter is applied :-)

Thanks everybody.

JC

[cijeff78]

I had that same issue. I found that when trying to make crops marks using the filter, it wants to add them on the top layer above the layer your box is on. If your top layer or layer above the box is invisible, it will give you that error:NESS. Just turn it on so it can create those crop marks.

[Halcyon]

I had that same issue. I found that when trying to make crops marks using the filter, it wants to add them on the top layer above the layer your box is on. If your top layer or layer above the box is invisible, it will give you that error:NESS. Just turn it on so it can create those crop marks.

This is interesting...I really don't remember if this was the given situation whenever I got the error while trying to apply the Crop Marks filter, but I will ost definetely check it next time I get the error. Better yet, I'll try to reproduce the error under the conditions you explain.

Thanks very much.

Update!! - YES, just like you said making the top layer visible eliminates the problem :-)

[red5dsd]

In my opinion, this is still a bug. Seems silly to have to activate the top layer just to make a filter work. However, it does work!