BOBJ report failed in SAP 6.0. "/CRYSTAL/OSQL_EXECUTE".*. short dump in S

Question

We have a set of crystal reports that run correctly in SAP4.6C. During the upgarde, we are unable to run any report against the new sap 6.0 but the same report run correctly against SAP4.6C. Whenever we run the bobj report, a short dump is created in SAP ECC6.0 as follow:
Information on where terminated
    Termination occurred in the ABAP program "/CRYSTAL/OSQL_EXECUTE" - in
     "START-OF-SELECTION".
    The main program was "/CRYSTAL/OSQL_EXECUTE ".
    In the source code you have the termination point in line 48
    of the (Include) program "/CRYSTAL/OSQL_EXECUTE".
We are using BOBJ XI SP2. SAPGUI 6.2. SAP ECC6.0 SERVER. The following sets of transports from BOBJ integration kit SP4 have been imported into SAP.
Open SQL Connectivity transport
Row-level security definition transprot
cluster definition transport
Infoset Connectivity transport
Authenticaton helpers tranport
BOBJ support has been unable to help so far..

Answer 1

Roland, we tried using the IP address to connect and create report and the same short-dump still occurs. We also applied BOBJ SP4 and it still didn't help. Please let us know if you have other thoughts. Thank you.
Here is a snapshot of the sap short-dump.
Error analysis                                                                                |
Short text of error message:
Syntax error in code: Error line #: 1 Message: REPORT/PROGRAM statement
missing, or program type
Long text of error message:
Technical information about the message:
Message class....... "AD"
Number.............. 010
Variable 1.......... "Syntax error in code: Error line #:"
Variable 2.......... 1
Variable 3.......... "Message:"
Variable 4.......... "REPORT/PROGRAM statement missing, or program type"
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"MESSAGE_TYPE_X" " "
"/CRYSTAL/OSQL_EXECUTE" or "/CRYSTAL/OSQL_EXECUTE"
"START-OF-SELECTION"
|----
System environment
SAP-Release 700
Application server... "ldcnadtc301"
Network address...... "20.22.185.84"
Operating system..... "SunOS"
Release.............. "5.10"
Hardware type........ "sun4u"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 1
Shortdump setting.... "full"
Database server... "ldc-nadtc301-db.ldco"
Database type..... "ORACLE"
Database name..... "DEV"
Database user ID.. "SAPR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Feb 3 2008 21:08:24"
create on........ "SunOS 5.9 Generic_117171-13 sun4u"
Database version. "OCI_102 (10.2.0.2.0) "
Patch level. 146
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "SunOS 5.9, SunOS 5.10"
User and Transaction
Client.............. 200
User................ "CRYSTAL"
Language Key........ "E"
Transaction......... " "
Transactions ID..... "48BE892424F37464E10000001416B954"
Program............. "/CRYSTAL/OSQL_EXECUTE"
Screen.............. "SAPMSSY0 1000"
Screen Line......... 6
Information on caller of Remote Function Call (RFC):
System.............. "DEV"
Database Release.... 700
Kernel Release...... 700
Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
Call Type........... "synchron and non-transactional (emode 0, imode 1)"
Inbound TID.........." "
Inbound Queue Name..." "
Outbound TID........." "
Outbound Queue Name.." "
Client.............. 200
User................ "CRYSTAL"
Transaction......... " "
Call Program........."/CRYSTAL/SAPLOPENSQL"
Function Module..... "/CRYSTAL/OSQL_EXECUTE_INTERNAL"
Call Destination.... "NONE"
Source Server....... "ldcnadtc301_DEV_00"
Additional information on RFC logon:
Trusted Relationship " "
Logon Return Code... 0
Trusted Return Code. 0
Note: For releases < 4.0, information on the RFC caller are often
only partially available.
Information on where terminated
Termination occurred in the ABAP program "/CRYSTAL/OSQL_EXECUTE" - in
"START-OF-SELECTION".
The main program was "/CRYSTAL/OSQL_EXECUTE ".
In the source code you have the termination point in line 48
of the (Include) program "/CRYSTAL/OSQL_EXECUTE".
Source Code Extract
Line
SourceCde
18
EXPORTING
19
PROGID                            = P_PROGID
20
GWHOST                            = P_GWHOST
21
GWSERV                            = P_GWSERV
22
IMPORTING
23
DESTINATION                       = DESTINATION
24
EXCEPTIONS
25
INVALID_PROGRAM_ID                = 1
26
CONNECT_TO_GATEWAY_FAILED         = 2
27
SERVER_NOT_REGISTERED             = 3
28
CONNECT_TO_REG_SERVER_FAILED      = 4
29
EXCLUSIV_NOT_SUPPORTED            = 5
30
OTHERS                            = 6
31
32
IF SY-SUBRC <> 0.
33
write   / 'Did not Connect to reg server'.
34
write : / 'SY-SUBRC', SY-SUBRC.
35
EXIT.
36
ENDIF.
37
38
IMPORT IMG_GETDATA_SOURCE[] FROM DATABASE INDX(ZA) ID P_JNAME.
39
DELETE FROM DATABASE INDX(ZA) ID P_JNAME.
40
41
GENERATE SUBROUTINE POOL IMG_GETDATA_SOURCE
42
NAME PROGNAME
43
MESSAGE SYNTAX_CHECK_MESSAGE
44
LINE ERROR_LINE_NO.
45
IF SY-SUBRC <> 0.
46
WRITE: / 'Syntax error, message', SYNTAX_CHECK_MESSAGE.
47
WRITE: / 'in line', ERROR_LINE_NO.
>>>>>
MESSAGE ID 'AD' TYPE 'X' NUMBER 010 WITH
49
'Syntax error in code: Error line #:'
50
ERROR_LINE_NO
51
'Message: '
52
SYNTAX_CHECK_MESSAGE.
53
ENDIF.
54
55
PERFORM GETDATA IN PROGRAM (PROGNAME)
56
using p_fname p_pksize p_progid p_gwhost p_gwserv destination.