OT about Crystal, but you guys know a lot

[Stephanie Stowe]

I am doing a support rotation for our massive ASP app. We use Crystal
Reports / Enterprise. By some magic which I am unfamiliar with Crystal
Enterprise allows the creation of a report on the server, then the report
containing the data can be viewed within the browser using a Crystal Viewer.
My experience with Crystal is limited to VB client apps, so this is the
limit of my understanding of precisely how this works in the ASP world.

Once upon a time a user could export a report within the Crystal Viewer to
Word, PDF and RTF format. Then, in order to fix some other problems, the
latest Crystal service packs and hotfixes were applied. This company
repackages the installs in a package which can be run unattended.
Apparently, they were applied incorrectly. The user could no longer export
to Word, PDF or RTF format, RTF being the only one they really care about. I
got called in as the next tier of support.

I reapplied the service packs and hotfixes properly. The user can now export
to PDF and Word. The user still cannot export to RTF. The user receives the
error "The export format 'u2frtf:0' is not supported on " with the server
info. Off I went to the Crystal KB, such as it is. I found two articles
(c2012677 and c2011207) which I can detail if anyone actually picks up on
this post and would like more info. (This is sort of obscure, so I am not
betting large quantities of money that anyone will have any pointers for me.
Not meant as disparagement.) The solutions provided in this article provided
a fix. I noticed on the test report server, where exports work, that there
was a u2frtf.dll which was present and registered. There was not one on the
live server. So I copied, registered, held my breath and got a reboot. It
did not break anything else, as was my fear. But it did not fix anything
either.

Anyone have an insight into what might me missing from the live server in
whcih export does not work and test server which does work?

Any tips would help.

Thanks.

Stephanoe

[s_m_b]

"Stephanie Stowe" <No****@IWishICould.com> wrote in
news:uW**************@TK2MSFTNGP09.phx.gbl:

Off topic, yes, but as with any third party product being used by ASP (or
whatever) that gets mangled by a messed upgrade, the best by far is to
take the offending app off (having backed up config) and start from
scratch with a new install and sp and then hotfix. That should not break
anything - if it does, there are more fundamental problems around and the
supplier will have some guidance...

I am doing a support rotation for our massive ASP app. We use Crystal
Reports / Enterprise. By some magic which I am unfamiliar with Crystal
Enterprise allows the creation of a report on the server, then the
report containing the data can be viewed within the browser using a
Crystal Viewer. My experience with Crystal is limited to VB client
apps, so this is the limit of my understanding of precisely how this
works in the ASP world.

Once upon a time a user could export a report within the Crystal
Viewer to Word, PDF and RTF format. Then, in order to fix some other
problems, the latest Crystal service packs and hotfixes were applied.
This company repackages the installs in a package which can be run
unattended. Apparently, they were applied incorrectly. The user could
no longer export to Word, PDF or RTF format, RTF being the only one
they really care about. I got called in as the next tier of support.

I reapplied the service packs and hotfixes properly. The user can now
export to PDF and Word. The user still cannot export to RTF. The user
receives the error "The export format 'u2frtf:0' is not supported on "
with the server info. Off I went to the Crystal KB, such as it is. I
found two articles (c2012677 and c2011207) which I can detail if
anyone actually picks up on this post and would like more info. (This
is sort of obscure, so I am not betting large quantities of money that
anyone will have any pointers for me. Not meant as disparagement.) The
solutions provided in this article provided a fix. I noticed on the
test report server, where exports work, that there was a u2frtf.dll
which was present and registered. There was not one on the live
server. So I copied, registered, held my breath and got a reboot. It
did not break anything else, as was my fear. But it did not fix
anything either.

Anyone have an insight into what might me missing from the live server
in whcih export does not work and test server which does work?

Any tips would help.

Thanks.

Stephanoe