on 08-07-2014 12:17 PM
Hello All,
we are getting dumps CALL_FUNCTION_SIGNON_INCOMPL and when i checked the logs the short text states Incomplete logon data.
Error analysis shows
The logon data for the user "PASSWD= " is incomplete.
I checked the user PASSWD but it dose not exist into the system.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Runtime Errors CALL_FUNCTION_SIGNON_INCOMPL
Date and Time 07.08.2014 05:25:40
Short text
Incomplete logon data.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPMSSY1" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Error in the program
call 'RfcImport' id 'Type' field type.
if sy-xprog = 'JAVA'.
system-call plugin
id 'JAVA' value 'FORW_JAVA'
id 'RC' value rc.
* if there is no rollout on the JAVA side which
* rolls both, JAVA and ABAP, we return to the
* C-Stack and reach this point
* in case there was an rollout, the ABAP-C stack is lost
* and we jump direkt to this point
* here we trigger the rollout on this Abap side with
* the following statement
system-call plugin
id 'JAVA' value 'ROLL_OUT'
id 'RC' value rc.
else.
perform (sy-xform) in program (sy-xprog).
rsyn >scont sysc 00011111 0.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Can anyone suggest what action needs to be taken care for this?
Regards,
Mohit
Error analysis
The logon data for the user "PASSWD= " is incomplete.
How to correct the error
If, during an RFC (Remote Function Call), an explicit user
or an explicit client is requested, you must enter an explicit
password for the user (see Transaction SM59).
Hello Mohit,
Please refer to the SAP note: 1373811
http://service.sap.com/sap/support/notes/1373811
Regards,
Sandeep S
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mohit,
Please follow SAP Note 684788 - Possible reason for CALL_FUNCTION_SIGNON_INCOMPL
Regards,
Gaurav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mohit,
Please check the following note:
171805 - Determining RFC client when sign-on problems occur
Thanks
Adil
Hi Mohit,
Can you upload the full ST22 dump and dev_rfc log file for this error ?
Divyanshu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Divyanshu,
Please check dump details.
Runtime Errors CALL_FUNCTION_SIGNON_INCOMPL
Date and Time 07.08.2014 07:27:06
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Short text |
| Incomplete logon data. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|What happened? |
| Error in the ABAP Application Program |
| |
| The current ABAP program "SAPMSSY1" had to be terminated because it has |
| come across a statement that unfortunately cannot be executed. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|What can you do? |
| Note down which actions and inputs caused the error. |
| |
| |
| To process the problem further, contact you SAP system |
| administrator. |
| |
| Using Transaction ST22 for ABAP Dump Analysis, you can look |
| at and manage termination messages, and you can also |
| keep them for a long time. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Error analysis |
| The logon data for the user "PASSWD= " is incomplete. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|How to correct the error |
| If, during an RFC (Remote Function Call), an explicit user |
| or an explicit client is requested, you must enter an explicit |
| password for the user (see Transaction SM59). |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|System environment |
| SAP-Release 701 |
| |
| Application server... "BXXXX" |
| Network address...... "10.XXX.XX.122" |
| Operating system..... "Windows NT" |
| Release.............. "6.1" |
| Hardware type........ "8x AMD64 Level" |
| Character length.... 16 Bits |
| Pointer length....... 64 Bits |
| Work process number.. 4 |
| Shortdump setting.... "full" |
| |
| Database server... "BEXXX" |
| Database type..... "MSSQL" |
| Database name..... "XXX" |
| Database user ID.. "xxx" |
| |
| Terminal.......... "BXXXX" |
| |
| Char.set.... "C" |
| |
| SAP kernel....... 720 |
| created (date)... "Mar 10 2014 00:00:41" |
| create on........ "NT 5.2 3790 S x86 MS VC++ 14.00" |
| Database version. "SQL_Server_9.00 " |
| |
| Patch level. 600 |
| Patch text.. " " |
| |
| Database............. "MSSQL 9.00.2047 or higher" |
| SAP database version. 720 |
| Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows |
| NT 6.0, Windows NT 6.1, Windows NT 6.2, Windows NT 6.3" |
| |
| Memory consumption |
| Roll.... 0 |
| EM...... 4189792 |
| Heap.... 0 |
| Page.... 0 |
| MM Used. 1209824 |
| MM Free. 2977296 |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|User and Transaction |
| Client.............. 000 |
| User................ "SAPSYS" |
| Language Key........ "D" |
| Transaction......... " " |
| Transactions ID..... "75F31DE4D104F143A56B005056A47FD3" |
| |
| Program............. "SAPMSSY1" |
| Screen.............. "SAPMSSY1 3004" |
| Screen Line......... 2 |
| |
| Information on caller of Remote Function Call (RFC): |
| System.............. "########" |
| Database Release.... 720 |
| Kernel Release...... 720 |
| Connection Type..... "E" (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.) |
| Call Type........... "synchronous and non-transactional (emode 0, imode 0)" |
| Inbound TID.........." " |
| Inbound Queue Name..." " |
| Outbound TID........." " |
| Outbound Queue Name.." " |
| |
| Client.............. "###" |
| User................ "############" |
| Transaction......... " " |
| Call Program........."ssc_edew" |
| Function Module..... "RFCPING" |
| Call Destination.... "<unknown>" |
| Source Server....... "bexxx" |
| Source IP Address... "10.231.22.78" |
| |
| 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 "SAPMSSY1" - in |
| "REMOTE_FUNCTION_CALL". |
| The main program was "SAPMSSY1 ". |
| |
| In the source code you have the termination point in line 67 |
| of the (Include) program "SAPMSSY1". |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Source Code Extract |
----------------------------------------------------------------------------------------------------
|Line |SourceCde |
----------------------------------------------------------------------------------------------------
| 37|endmodule. |
| 38| |
| 39|module %_rfcdia_call output. |
| 40| "Do not display screen ! |
| 41| call 'DY_INVISIBLE_SCREEN'. |
| 42| perform remote_function_diacall. |
| 43|endmodule. |
| 44| |
| 45|module %_cpic_start. |
| 46| if sy-xprog(4) = '%RFC'. |
| 47| perform remote_function_call using rfctype_external_cpic. |
| 48| else. |
| 49| call 'APPC_HD' id 'HEADER' field header id 'CONVID' field convid. |
| 50| perform cpic_call using convid. |
| 51| endif. |
| 52|endmodule. |
| 53| |
| 54| |
| 55|form cpic_call using convid type c. |
| 56| communication send id convid buffer header. |
| 57| if sy-subrc eq 0. |
| 58| perform (sy-xform) in program (sy-xprog). |
| 59| else. |
| 60| message a800. |
| 61| endif. |
| 62|endform. |
| 63| |
| 64|form remote_function_call using value(type). |
| 65| data rc type i value 0. |
| 66| do. |
|>>>>>| call 'RfcImport' id 'Type' field type. |
| 68| if sy-xprog = 'JAVA'. |
| 69| system-call plugin |
| 70| id 'JAVA' value 'FORW_JAVA' |
| 71| id 'RC' value rc. |
| 72|* if there is no rollout on the JAVA side which |
| 73|* rolls both, JAVA and ABAP, we return to the |
| 74|* C-Stack and reach this point |
| 75| |
| 76|* in case there was an rollout, the ABAP-C stack is lost |
| 77|* and we jump direkt to this point |
| 78| |
| 79|* here we trigger the rollout on this Abap side with |
| 80|* the following statement |
| 81| system-call plugin |
| 82| id 'JAVA' value 'ROLL_OUT' |
| 83| id 'RC' value rc. |
| 84| else. |
| 85| perform (sy-xform) in program (sy-xprog). |
| 86| rsyn >scont sysc 00011111 0. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Active Calls/Events |
----------------------------------------------------------------------------------------------------
|No. Ty. Program Include Line |
| Name |
----------------------------------------------------------------------------------------------------
| 2 FORM SAPMSSY1 SAPMSSY1 67 |
| REMOTE_FUNCTION_CALL |
| 1 MODULE (PBO) SAPMSSY1 SAPMSSY1 30 |
| %_RFC_START |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Chosen variables |
----------------------------------------------------------------------------------------------------
|Name |
| Val. |
----------------------------------------------------------------------------------------------------
|No. 2 Ty. FORM |
|Name REMOTE_FUNCTION_CALL |
----------------------------------------------------------------------------------------------------
|No. 1 Ty. MODULE (PBO) |
|Name %_RFC_START |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Internal notes |
| The termination was triggered in function "isignon_do_it" |
| of the SAP kernel, in line 216 of the module |
| "//bas/720_REL/src/krn/rfc/absignon.c#8". |
| The internal operation just processed is "CALY". |
| Internal mode was started at 20140807072706. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|List of ABAP programs affected |
----------------------------------------------------------------------------------------------------
|Index |Typ|Program |Group |Date |Time |Size |Lang. |
----------------------------------------------------------------------------------------------------
| 0|Prg|SAPMSSY1 | 0|11.04.2005|09:27:15| 24576|D |
| 1|Prg|SAPLSYST | 1|20.07.2014|16:26:52| 43008|D |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|ABAP Control Blocks (CONT) |
----------------------------------------------------------------------------------------------------
|Index|Name|Fl|PAR0|PAR1|PAR2|PAR3|PAR4|PAR5|PAR6|Source Code |Line |
----------------------------------------------------------------------------------------------------
| 116|CLEA|00|0035| | | | | | |SAPMSSY1 | 60|
| 117|CLEA|00|0036| | | | | | |SAPMSSY1 | 60|
| 118|CLEA|00|0037| | | | | | |SAPMSSY1 | 60|
| 119|MESS|00|001C| | | | | | |SAPMSSY1 | 60|
| 120|ENDF|00|0000| | | | | | |SAPMSSY1 | 62|
| 121|----|00|0000| | | | | | |SAPMSSY1 | 62|
| 122|PERP|00|0001| | | | | | |SAPMSSY1 | 64|
| 123|PERP|02|0000| | | | | | |SAPMSSY1 | 64|
| 124|WHIL|00|0002|0000|0000|0000|0000|0000|0000|SAPMSSY1 | 66|
| 128|WHIL|00|0003|0000|0000|0000|0000|0000|0000|SAPMSSY1 | 66|
| 132|BRAN|05|001E| | | | | | |SAPMSSY1 | 66|
| 133|CALY|00|0003|0038|002A|0005|002B|0000|0000|SAPMSSY1 | 67|
|>>>>>|CALY|02|0000|0039|8000|0000|0000|0000|0000|SAPMSSY1 | 67|
| 141|COMP|00|0002|0010|003A| | | | |SAPMSSY1 | 68|
| 143|BRAF|02|000E| | | | | | |SAPMSSY1 | 68|
| 144|SRFC|01|0000|003A|003B| | | | |SAPMSSY1 | 69|
| 146|SRFC|01|0000|003C|C000| | | | |SAPMSSY1 | 69|
| 148|SRFC|02|0000|0000|0000| | | | |SAPMSSY1 | 69|
| 150|SRFC|01|0000|003A|003D| | | | |SAPMSSY1 | 81|
| 152|SRFC|01|0000|003C|C000| | | | |SAPMSSY1 | 81|
----------------------------------------------------------------------------------------------------
Regards,
Mohit
At the time you get this dump, did you check sm50 and sm21 ?
Referhttp://service.sap.com/sap/support/notes/171805
And put trace on as suggsuggested
Hi Mohit.
In the chosen variable section of the short dump, it showing this error: %_RFC_START
Check the following reports.
RSRFCCHK - RFC Connection Report and Status of connections , choose execute connection test. This will display problems with all RFC connection in the system.
RSRFCTRC - Display all RFC Trace files
Thanks
Hello Divyanshu,
I followed the note and got the below info from the dumps details
Call Program........."ssc_edew"
Function Module..... "RFCPING"
Call Destination.... "<unknown>"
Source Server....... "bellfrsa1XXX"
Source IP Address... "10.2X1.XXXX"
So now i know the call program and server from where it is running. Now can you tell me how i can correct it?
Regards,
Mohit
Hi Mohit,
Please check in relevant RFC destination whether userid and password is maintained correctly.
Regards,
Deepak Kori
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mohit
Its happen all the user ids?
BR
SS
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
80 | |
9 | |
9 | |
7 | |
7 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.