Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

NetWeaver 7.0 ABAP Trial: Not able to login

Hi,

I have installed the trial version & also the sap logon pad. I have configured the NSP system in the logon pad as instructed in the html document provided. The problem is When I logon to the SAP system (NSP) using the SAP logon pad, i am not getting the login screen. Instead I am getting the following dump:

-


Runtime Errors DBIF_RSQL_INVALID_REQUEST

Date and Time 17.11.2007 07:54:57

Short text

Invalid request.

What happened?

The current ABAP/4 program terminated due to

an internal error in the database interface.

What can you do?

Note which actions and input led to the error.

For further help in handling the problem, contact your SAP administrator.

You can use the ABAP dump analysis transaction ST22 to view and manage

termination messages, in particular for long term reference.

Error analysis

An invalid request was made to the SAP database interface in a statement

in which the table "DOKTL " was accessed.

The situation points to an internal error in the SAP software

or to an incorrect status of the respective work process.

For further analysis the SAP system log should be examined

(transaction SM21).

For a precise analysis of the error, you should supply

documents with as many details as possible.

How to correct the error

Start the work process involved and repeat the action that lead to the

error.

If the error position is in a program that you can change, you can try

to create preliminary solution: Reformulate the database command by

varying the properties such as individual record access instead of

input/output via internal tables, the structure of the selection

conditions (WHERE clause), nested SELECT loops instead of FOR ALL

ENTRIES and other such variations.

Please check the entries in the system log (Transaction SM21).

Check the entries in the developer trace of the work process involved

(transaction ST11).

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:

"DBIF_RSQL_INVALID_REQUEST" " "

"SAPMSYST" or "SAPMSYST"

"FILL_INFO_TAB"

......

......

System environment

SAP-Release 700

Application server... "localhost"

Network address...... "127.0.0.1"

Operating system..... "Windows NT"

Release.............. "5.1"

Hardware type........ "Intel 801586 (M"

Character length.... 8 Bits

Pointer length....... 32 Bits

Work process number.. 0

Shortdump setting.... "full"

Database server... "localhost"

Database type..... "ADABAS D"

Database name..... "NSP"

Database user ID.. "SAPNSP"

Char.set.... "English_United State"

SAP kernel....... 700

created (date)... "Jan 29 2007 00:33:09"

create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"

Database version. "SQLDBC 7.6.2.014 CL 152175 "

Patch level. 95

Patch text.. " "

Database............. "MaxDB 7.6, MaxDB 7.7"

SAP database version. 700

Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"

Memory consumption

Roll.... 8112

EM...... 1045296

Heap.... 0

Page.... 0

MM Used. 523136

MM Free. 520824

User and Transaction

Client.............. 000

User................ " "

Language key........ "E"

Transaction......... "SESSION_MANAGER "

Transactions ID..... " "

Program............. "SAPMSYST"

Screen.............. "SAPMSYST 0020"

Screen line......... 3

Information on where terminated

Termination occurred in the ABAP program "SAPMSYST" - in "FILL_INFO_TAB".

The main program was "SAPMSYST ".

In the source code you have the termination point in line 2556

of the (Include) program "SAPMSYST".

-


Please help me out.

Regards.

Former Member
Not what you were looking for? View more on this topic or Ask a question