cancel
Showing results for 
Search instead for 
Did you mean: 

Error when calling WebDynpro application

Former Member
0 Kudos

When calling an Web Dynpro application we get the following error:

The initial exception that caused the request to fail, was:

com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'password' missing

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:413)

at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:841)

at com.sap.mw.jco.JCO$Client.connect(JCO.java:3159)

at com.sap.dictionary.runtime.mdi.DataProvider.<init>(DataProvider.java:90)

at com.sap.dictionary.runtime.mdi.DataProvider.<init>(DataProvider.java:122)

When I test the individual JCo connections via the Web Dynpro Content Administrator they are all succesfull. What goes wrong?

Kind regards,

Dave Arends

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Arends,

When you configure JCO destinations, you might have configured with a wrong password(to connect to R/3 system) , but you will see it as a green, just check it.

Thanks,

Raj.

Former Member
0 Kudos

Raj,

I did not use the method username/password User Authentication but used the ticket method. That's why I find it strange to get a 'password missing' error.

Kind regards,

Dave

Former Member
0 Kudos

Hi Arends,

Check the URL

<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/71/52fa40fe14f423e10000000a155106/content.htm">http://help.sap.com/saphelp_nw2004s/helpdata/en/71/52fa40fe14f423e10000000a155106/content.htm</a>

You need to check if this logon method was chosen by navigating to System Administration -> System Configuration -> System landscape in the portal and select the correct system from System Landscape. It might be necessary to ask the portal administrator for the name he entered when creating the system. Right-click on the system and select Edt” -> Object from the context menu. Select the Property Category with the designation User Management and make sure that the Logon Method is set to UIDPW. Additionally, the user mapping for this user needs to be set up correctly. See section Folder Selection iView in BEx Broadcaster for details. However, it is also possible to setup the system with the Logon Method named SAPLOGONTICKET which is more common. In that case, the exception above should not appear.

hope it helps...

Lokesh

Message was edited by: Lokesh Aggarwal

Former Member
0 Kudos

Dave,

In that case check your single sign on configuration with your basis team...the log on tickets (creation and acceptance..means sender and receiver). are correctly configured!!.

/Raj.

Former Member
0 Kudos

Arends,

The ticket issuing system (TIS) and the ticket accepting system (TAS) should have the correct user mapping. Check if the user ID you've used works well in both TIS & TAS.

Bala

Answers (1)

Answers (1)

Former Member
0 Kudos

There are two reasons why you get this error :

a) As you mentioned, you have used <b>Ticket</b> as Authentication method.

Refer this <a href="http://http://help.sap.com/saphelp_nw04/helpdata/en/44/45a04028f40160e10000000a1550b0/frameset.htm">Setting up a Web Dynpro Application for a Logon Ticket</a>

It mentions that for WD_RFC_METADATA_DEST JCo Destination, you should user <b>User/Password</b> authentication approach and not the Ticket approach.

b) You don't have <b>DD_DOMA_GET function module in R/3</b> as <b>RFC enabled</b>. You can check this function module in SE37 , go to Attributes.

Best Regards,

Subramanian V.