RfcException: message: 'user' missing Return code: RFC_INVALID_PARAMETER

[former_member187977]

hi,

I was able to run a web dynpro application till now. And now suddenly I get a RFC Exception. The error is given below. Please suggest a solution

RfcException: message: 'user' missing Return code: RFC_INVALID_PARAMETER(19) error group: 101 key: RFC_ERROR_PROGRAM

Screenshot of the error is given below

[Screenshot|http://learnsaponline.blogspot.com/2011/12/rfcexception-message-user-missing.html]

Important lines from the Full exception chain are :

Caused by: com.sap.tc.webdynpro.progmodel.context.DictionaryException: failed to create provider: com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'user' missing{jco.client.lang=EN, jco.client.client=035, jco.client.passwd=<null>, jco.client.mshost=sari, jco.client.group=HCM Development, jco.client.r3name=DVO}

Thanks !

seventyros

Edited by: seventyros on Dec 4, 2011 7:51 AM

[Former Member]

This will happen if a user does not exist in your session.

In RFC programming you need to pass a user id and password for connecting to R/3 system.

However, your web dynpro application will automatically pick it up from existing session. You need not pass it manually.

In order to force the application to ask for a user if one does not exist in existing session, you will require to enable authentication for your application.

Browse you web dynpro application and navigate to WebDynpro -> Applications -> <Application Name>

Double click and select "Application Properties" tab.

Set below property:

Name -

---

value---description

sap.authentication - true -

---

Authentication mode.

[former_member187977]

hi,

The authentication mode of my application was already on. Now I turned off the authentication mode and deployed. I get following error now

com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: User not authorized.

Full exception is pasted below

com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exception was thrown in preprocessing phase of application session 78f0ade11e6a11e182b7000035bdebee. The causing exception is nested. RID=78ef243b1e6a11e18dd8000035bdebee

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:661)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:347)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:325)

at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)

at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:89)

at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doGet(AbstractDispatcherServlet.java:55)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:734)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)

at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:453)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)

at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:462)

at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:270)

at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)

at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

Caused by: com.sap.tc.webdynpro.progmodel.context.DictionaryException: TypeBroker failed to access SLD: Error while obtaining JCO connection.

at com.sap.tc.webdynpro.progmodel.context.DictionaryHandler.getScalarType(DictionaryHandler.java:378)

at com.sap.tc.webdynpro.progmodel.context.DictionaryHandler.getDataType(DictionaryHandler.java:126)

at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:438)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:1002)

at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:294)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:974)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:978)

at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:67)

at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:205)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:586)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doPreprocessing(ClientApplication.java:1453)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:658)

... 46 more

Caused by: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.

at com.sap.tc.webdynpro.services.datatypes.core.DictionarySetup$1.fillSldConnection(DictionarySetup.java:51)

at com.sap.dictionary.runtime.ProviderFactory.internalResolveLogicalNameToJCODestination(ProviderFactory.java:437)

at com.sap.dictionary.runtime.ProviderFactory.resolveLogicalNameToJCODestination(ProviderFactory.java:361)

at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:198)

at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:161)

at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:96)

at com.sap.dictionary.runtime.DdDictionaryPool.makeDictionary(DdDictionaryPool.java:75)

at com.sap.dictionary.runtime.DdDictionaryPool.makeDictionary(DdDictionaryPool.java:63)

at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:230)

at com.sap.tc.webdynpro.progmodel.context.DictionaryHandler.getScalarType(DictionaryHandler.java:370)

... 57 more

Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.

at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:153)

at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:161)

at com.sap.tc.webdynpro.services.sal.sl.core.SystemLandscapeInternal.getJCOClientConnectionUnMapped(SystemLandscapeInternal.java:64)

at com.sap.tc.webdynpro.services.datatypes.core.DictionarySetup$1.fillSldConnection(DictionarySetup.java:32)

... 66 more

Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: User not authorized.

at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.getPoolName(AbstractJCOClientConnection.java:519)

at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:253)

at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:222)

at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:84)

at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:151)

Screenshot is available at d

Edited by: seventyros on Dec 4, 2011 12:44 PM

[Former Member]

Do not turn it off.

Keep it as "true" only.

This error might be from your JCO destination configuration.

If you are using SSO ticket for authorization while defining a metadata JCO Destination you might see an exception like the one above.

Username/Password is the only valid Authorization concept while you define your Metadata JCO Destinations. Never try to use SSO or ticket in your security settings while defining metadata JCO Destinations. At least from SP18 onwards there are validity checks in the content administrator which prevent you from using SSO/ticket for metadata JCO destinations.

Check your JCO meta data definition "security" Tab.

Set SNC mode "off".

Set User Authentication "User/Password".

Enter name and password there.

If you are unaware of this process then contact your basis team.