Error: rangecheck; OffendingCommand: endcidrange

G

Guest

I am attempting to print an e-mail message to Acrobat PDF within Outlook
2003. When I try in various ways to print this message, I get a log file
that shows this error: "Error: rangecheck; OffendingCommand: endcidrange."

I have had no problem printing other messages in the existing setup. This
particular e-mail message appears to differ from the others only in regard to
the fonts it uses. It uses Tahoma, Times New Roman, Arial, Lucida
Handwriting, and @Arial Unicode MS. Many of my printable messages use TNR,
Arial, and (I think) Tahoma; but the Lucida and Unicode fonts look unusual to
me.

Any idea what solutions might work? Thanks!
 
R

Ray

Sorry for the double-post. I posted one entry through Microsoft's
support page. I thought it might be the same as this forum, except
that the list of messages shown there and here didn't look the same.

Anyway, on Adobe's site I am finding messages indicating that it sounds
like a font problem, and that particularly the @Arial Unicode MS font
might be the issue. I would avoid the problem by simply not using the
font, but in this case I'm trying to print someone else's message to
me.

I would do a workaround if this were the only problematic e-mail
message, but I figure I am likely to have this problem again before I'm
finished with the present task. I am attempting to print about 9,700
e-mail messages in Outlook 2003 to a single PDF. That process has
failed so far. I don't know that this will be the only glitch in the
process, but at least I have managed to identify this one. BTW, I am
using Acrobat 6.0.4.
 
R

Ray

I just tried one workaround -- saving the e-mail to an RTF, opening in
Microsoft Word, and printing that as a PDF. Same problem. Seems it's
not just an Outlook issue. BUT ... just now I was able to open that
RTF in OpenOffice 2.0 Writer, and that program did succeed in printing
this e-mail message as a PDF. Now I'm wondering if I can import the
Outlook PST into Thunderbird and try printing it all from there.
 
R

Ray

I didn't find any solutions in Adobe's Knowledgebase or forums. I
called Adobe tech support. They wanted to charge me $40 to start an
incident, on grounds that they are no longer supporting Acrobat 6.0.
The guy said, "I know you'd like to get free support, but ..." I said,
"Free? I paid a lot of money for this program!" It's an old tune, but
we're still dancing to it ...

He said document 317147 on Adobe's website has some relevant content.
That document is presently at
http://www.adobe.com/support/techdocs/317147.html. It is a
troubleshooting document. It begins with this remark: "Before you
begin troubleshooting, be sure that the version of Acrobat you are
running is compatible with the version of Office you are running.
Acrobat 6.0 Standard and Professional are compatible with Office XP,
2000, and 97; Acrobat 7.0 Professional and Standard are compatible with
Office 2003, XP, and 2000."

In other words, there are two possible solutions, for someone in my
situation: keep using Outlook 2003, and upgrade to Acrobat 7 in order
to finish this printing project; or downgrade to Outlook XP, 2000, or
97, and use Acrobat 6. I could probably restore an old drive image
that has Outlook XP on it, import this outlook.pst file into that
version of Outlook, and print from there.

As for the kludge solution, Thunderbird imported only about 70% of the
e-mails in this outlook.pst file, for some reason. I'm not even sure
which outlook.pst it was importing; it gave me no control over the
process. So I bagged that. The other kludge solution is to keep
hammering away in Outlook 2003, printing the occasional recalcitrant
e-mail message into RTF, printing that to PDF in OpenOffice 2.0 Writer,
and then slipping that page back into the proper place in the completed
PDF. I'm going to try this first, in case there aren't too many
misbehaving e-mails to worry about -- it may be the fastest solution.
 
R

Ray

Printing the file in Outlook 2003 actually produced few other errors.
The number of recalcitrant e-mail messages proved to be quite small.
As the Adobe tech advised, I have downloaded the free 30-day trial of
Acrobat 7.0 Professional. I have seen a few reviews that indicate it
is much more stable. I may try it out and go for the $140 upgrade at
some point, if it seems essential.

Meanwhile, having solved this problem, I am appending my remaining
notes on the matter, for posterity, as follows:

I reviewed postings containing various bits of advice. I went to
Outlook 2003 > File > Print > Adobe PDF > Properties > Layout >
Advanced > Document Options > PostScript Options. There, I changed
"Optimize for Speed" to "Optimize for Portability." Unfortunately,
that did not solve the problem. Someone else said that was not a
helpful change, so I changed it back.

Microsoft has identified this problem: "An HTML formatted message may
print successfully before you open it on the first attempt and not
print on subsequent attempts, or the message may not print on the first
attempt and print on subsequent attempts." The workaround is to open
the message and then select File > Print > OK. See
http://support.microsoft.com/default.aspx?scid=kb;en-us;301910.
Unfortunately, that did not solve the problem in this case.

Next, I tried this: In Acrobat, Edit > Preferences > Convert to PDF >
Microsoft Office > Edit Settings > uncheck Enable accessibility &
reflow (Microsoft Office 2000 & XP only). That did not solve the
problem.

I then went back and tried another thing in that same dialog box,
"Adobe PDF Settings for supported documents." I clicked the Edit
button and, in the General tab, I changed Object Level Compression to
Off. It gave me the option to save. I saved as "Print Outlook PDF En
Masse." This, too, did not solve the problem.

In the place just mentioned, I changed the "Print Outlook PDF En Masse"
settings to shut off "Optimize for fast web view" and I changed from
Acrobat 5 to Acrobat 6.0 compatibility. This failed too.

Instead of the General tab in that place, I chose the Fonts tab and
changed the "When embedding fails" option to Ignore. This failed too.
 
Joined
Feb 12, 2007
Messages
1
Reaction score
0
I also received the error

Error: rangecheck; OffendingCommand: endcidrange

After reading this thread, it sounds like the error was due to fonts. After changing the fonts, I can now convert my Access report to PDF.


Thank you :)
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top