PLEASE NOTE: I OPENED A CASE AT BAAN CONCERNING THE
ISSUES COVERED IN THAT THREAD. IT TURNED OUT TO BE KNOWN
BUG. THEY ARE WORKING ON IT RIGHT NOW (2002-03-19)

ORIGINAL POST FOLLOWS:
-----------------------------------------------------------------------------------
I put this posting here and not in third party software, because the integrated reporting seems to become standard functionality.

However: Here at my client site it still doesn't work. When we try to print through the crystal device, we get the following error message:

"Senden des Berichts an Berichtsumgebung über Gerät TEST ist
fehlgeschlagen. Details finden Sie in "Device Queue" (ttaad3520m001)."

In English (translated by me, I do not know how the original english Baan error text is):

"Sending report to report environment by device TEST failed.
For details see session "Device Queue"...

The session mentioned shows no details: The error string is empty, the URL also. A report within crystal enterprise is not created.


Baan Version is IVc4 SP8, Crystal related solutions are installed.

The Crystal device TEST is a Baan Device "Append File",
ttstpconv argument is: XML port=7688 server=520crep

I can ping the machine "520crep" where all crystal software is running (win 2000) from the Baan server (HP UX)
All crystal services (also the Baan Crystal Server) is running.
The user accounts BaanAdmin (Group Administrators) and BaanViewer (Group Baan Admin Viewers do exist).


Any idea? And how can I track down where the connection fails?

Yours,
Uli

Try modifying your device to

ttstpconv argument is: XML:%s port=7688 server=520crep


The :%s after the XML argument certainly helps, if you still have probelms please come back to me.

Stewart Oakden
www.bsp-uk.com

the new argument to ttstpconv didn't help, Stewart. Any other idea?

Question: Should Baan produce an intermediate XML file somewhere? I do not find anything...

(UPDATE: It does produce one in $BSE/tmp - as a "regular" named Baan temp file)

Ok, some additional information from me, as far as I figuered things out:

As I understand, the communication between Baan and Crystal works as following:

User prints to device Append File
(ottstpconv is NOT INVOLVED!)
an XML file is created in $BSE/tmp
ottstpclose is called
ottstpclose called ttdllreporting
ttdllreporting calls binary ogclient6.1
ogclient6.1 connects to crystal socket 7688

However, where does it fail?
If I start ogclient by hand, I get an error message NO CLASS::FUNCTION not present, and an entry in $BSE/log/log.ogclient6.1

However, with the regular way from the print dialog, no entry is made in the log file.


Hmmm....

?????

hi

you might want to try your device data "TEST", by keeping the 4GL Program : blank.

it seems it helps for printing reports in XML format

VISH

Hi Vish,

thanks for the suggestion, but I tried it already. Still doesn't work, unfortunately. I now believe that the spooler is not able to call the ogclient6.1 binary for some reason. But why?

Uli

I now found an error message in the table ttad322 of the company where I start the report saying:

"Missing template info. Error record inserted"

And now? Where do we get that bloody template info from???

Uli

any update on this?

Hello

Any news on this error?