Solved: Problema com o usuário PIRWBUSER

Bom dia Pessoal,

Estou com um problema no PI/GRC quando vou monitorar as mensagens no Runtime Workbench ocorre o seguinte erro:

javax.ejb.CreateException: Unable to log on to system NW1 in language en with user PIRWBUSER

Ja verifiquei as configuracoes do Exchange Profile e esta tudo ok, nao sei mais onde procurar.

SAP Managed Tags:
SAP Electronic Invoicing for Brazil (SAP Nota Fiscal Eletronica)

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (1)

Bom dia Fábio,

A mensagem é bem clara, a solução nem tanto, porém pode estar ocultando o verdadeiro erro.

Primeiro verifique o usuário, SU01 do client PI, além disso vc tem o idioma EN instalado ?

No internet explorer (ou o browser que está usando), quais os idiomais que tem instalado ? Está forçando EN ?

Além de checar o usuário, verifique no defaultTrace do java por mensagens de erro após uma tentativa de acesso ao RWB, caminho: transação AL11 -> duplo clique em DIR_INSTANCE -> j2ee -> cluster -> servern (normalmente server0) -> log (arquivos defaultTrace)

ordene por data/hora e pegue o mais recente.

Atenciosamente, Fernando Da Ró

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Fernando,

Verificando o arquivo de log, encontrei a seguinte msg:

1.5 #C0000A0A0112005A000000810000158C000480BD9C2E9978#1267451763381#XIRWB.com.sap.aii.mdt.frames.jsp_error#sap.com/com.sap.xi.rwb#XIRWB.com.sap.aii.mdt.frames.jsp_error#PIRWBUSER#5119##n/a##2a28ebe0253a11df837af4690a0a0112#SAPEngine_Application_Thread[impl:3]_18##0#0#Error#1#/Applications/ExchangeInfrastructure/RuntimeWorkbench#Plain###Unable to log on to system NW1 in language en with user PIRWBUSER

Thrown:

javax.ejb.CreateException: Unable to log on to system NW1 in language en with user PIRWBUSER

Olá Fábio,

Esta mensagem é a mesma que você tinha informado, veja se no defaultTrace existe alguma outra informação que aponte outra fonte de erro.

Veja também as sugestões do José Nunes e do Henrique.

Atenciosamente, Fernando Da Ró

Fernando,

Segue outra msg de erro que encontrei:


#1.5 #C0000A0A011200590000000600001BFC000480C0D1E62576#1267465549485#com.sap.aii.af.ra.ms.runtime.Resources##com.sap.aii.af.ra.ms.runtime.Resources.lookupFromJNDI(String, boolean)#J2EE_GUEST#0##n/a##fe6197d3255911dfb6dac6740a0a0112#SAPEngine_Application_Thread[impl:3]_9##0#0#Error##Plain###Failed to lookup object from JNDI for name localejbs/TestListener within app level thread. Reason: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of TestListener.#
#1.5 #C0000A0A011200590000000700001BFC000480C0D1E62622#1267465549485#com.sap.aii.af.ra.ms.runtime.Resources##com.sap.aii.af.ra.ms.runtime.Resources.getListener(String, boolean)#J2EE_GUEST#0##n/a##fe6197d3255911dfb6dac6740a0a0112#SAPEngine_Application_Thread[impl:3]_9##0#0#Error##Plain###Failed to create listener localejbs/TestListener for connection test. Reason: java.lang.Exception: Failed to lookup object from JNDI for name localejbs/TestListener within app level thread. Reason: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of TestListener.#
#1.5 #C0000A0A011200590000000800001BFC000480C0D58FABF2#1267465609516#com.sap.aii.af.ra.ms.runtime.Resources##com.sap.aii.af.ra.ms.runtime.Resources.lookupFromJNDI(String, boolean)#J2EE_GUEST#0##n/a##fe6197d3255911dfb6dac6740a0a0112#SAPEngine_Application_Thread[impl:3]_9##0#0#Error##Plain###Failed to lookup object from JNDI for name localejbs/TestListener within app level thread. Reason: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of TestListener.#
#1.5 #C0000A0A011200590000000900001BFC000480C0D58FAD10#1267465609532#com.sap.aii.af.ra.ms.runtime.Resources##com.sap.aii.af.ra.ms.runtime.Resources.getListener(String, boolean)#J2EE_GUEST#0##n/a##fe6197d3255911dfb6dac6740a0a0112#SAPEngine_Application_Thread[impl:3]_9##0#0#Error##Plain###Failed to create listener localejbs/TestListener for connection test. Reason: java.lang.Exception: Failed to lookup object from JNDI for name localejbs/TestListener within app level thread. Reason: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of TestListener.#
#1.5 #C0000A0A011200780000000100001BFC000480C0D8CD2C69#1267465665266#com.tssap.dtr.client.lib.protocol.requests.RequestBase##com.tssap.dtr.client.lib.protocol.requests.RequestBase####n/a##fff222e0255911df809fc6740a0a0112#OrderedChannel for {internal} service##0#0#Error##Plain###
java.net.SocketException: Software caused connection abort: socket write error

Fiz as verificações informadas pelo José Nunes e Henrique. Estão todas ok.

Fabio,

esse erro do TestListener não é a causa do seu problema. Esse erro é de um componente de teste padrão que vem no J2EE e pode ser desabilitado via Visual Admin.

No teu caso, você consegue logar com o PIRWBUSER pelo stack ABAP?

[]'s

Jose Nunes,

Sim, conseguimos logar com o usuário PIRWBUSER no stack abap.

com o master password? ou a senha foi trocada?

Abs,

Henrique.

Henrique,

A senha foi trocada.

Segue outros erros que eu encotrei.


#1.5 #00155D012003006D0000005E0000118C000480C5891A7036#1267485800975#com.sap.aii.af.ra.ms.impl.core.queue.consumer.RequestConsumer##com.sap.aii.af.ra.ms.impl.core.queue.consumer.RequestConsumer.onMessage(QueueMessage, boolean)#J2EE_GUEST#0##n/a##666c9910258711dfcc9600155d012003#SAPEngine_Application_Thread[impl:3]_8##0#0#Error##Java###Set message {0} to status FAILED.#1#df25896a-660a-9cf1-a341-00155d012003(INBOUND)#
#1.5 #00155D012003007A000000970000118C000480C5891A746D#1267485800975#com.sap.aii.adapter.xi.ms.XIEventHandler#sap.com/com.sap.aii.af.ms.app#com.sap.aii.adapter.xi.ms.XIEventHandler.onRequest(Services, TransportMessage)#PIISUSER#212##dc0145nfe_NW1_7529450#PIISUSER#6c989350258911dfb9b700155d012003#SAPEngine_Application_Thread[impl:3]_13##0#0#Error##Java###Message {0}: was not delivered due to {1}#2#df25896a-660a-9cf1-a341-00155d012003(INBOUND)#com.sap.aii.af.ra.ms.api.DeliveryException: Peer sent alert: Alert Fatal: unexpected message#
#1.5 #00155D012003006D0000005F0000118C000480C5891EB925#1267485801256#com.sap.aii.af.service.alerting.Alert#sap.com/com.sap.aii.af.soapadapter#com.sap.aii.af.service.alerting.Alert.setMDTUrl()#J2EE_GUEST#0##n/a##666c9910258711dfcc9600155d012003#XI AF AAM AlertingStatusListener$AsyncAlerter@61855429_19##0#0#Error##Plain###Failed to set MDT URL: HTTP error: Invalid begin of response [expected: 'HTTP', found: 'Server: SAP J2EE Engine/7.00']#
#1.5 #00155D012003007A000000980000118C000480C5891EC268#1267485801256#com.sap.aii.af.service.alerting.Alert##com.sap.aii.af.service.alerting.Alert.setMDTUrl()#J2EE_GUEST#0##n/a##6cec0a80258911df88a600155d012003#SAPEngine_Application_Thread[impl:3]_13##0#0#Error##Plain###Failed to set MDT URL: HTTP error: Invalid begin of response [expected: 'HTTP', found: 'TTP/1.1 400 Bad Request']#
#1.5 #00155D0120030059000000560000118C000480C5891F147F#1267485801272#com.sap.engine.services.httpserver##com.sap.engine.services.httpserver#J2EE_GUEST#0##n/a##6cee7b80258911df840500155d012003#SAPEngine_Application_Thread[impl:3]_31##0#0#Error##Plain###User J2EE_GUEST, IP address
Cannot parse the http request. Http error response [400 Bad Request] will be returned. Request is [°ùu0160f<å¬?¥¬8¥u2122?þìÌ9?Ó Ñ¯ø3/N ©Gs-££?W»§"Wò]u2122-Éh ý Ñ¯ø3/N ©Gs-££?W»§"Wò]u2122¬Éh ýst: dc01-nfe:50000
Content-Encoding: deflate
Accept-Encoding: identity, deflate
Accept-Charset: UTF-8
SAP-CIM-Client: 3.3.2
Content-Type: application/xml; charset=utf-8
Cookie: $Version=1;JSESSIONID=(DC01-NFE_NW1_00)ID0227398050DB00487802484388825785End;$Path=/,$Version=1;saplb_*=(DC01-NFE_NW1_00)7529450;$Path=/, $Version=1;MYSAPSSO2=AjExMDAgAA9wb3J0YWw6UElBRlVTRVKIAAdkZWZhdWx0AQAIUElBRlVTRVICAAMwMDADAANOVzEEAAwyMDEwMDMwMTIzMjMFAAQAAAAICgAIUElBRlVTRVL%2FAQYwggECBgkqhkiG9w0BBwKggfQwgfECAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHATGB0TCBzgIBATAiMB0xDDAKBgNVBAMTA05QSTENMAsGA1UECxMESjJFRQIBADAJBgUrDgMCGgUAoF0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTAwMzAxMjMyMzIxWjAjBgkqhkiG9w0BCQQxFgQUA3D8HxuR2JRZ!RrgHV7ZtQu8UoAwCQYHKoZIzjgEAwQwMC4CFQCZvJB7O8IrKrFH5yZKhhdH!NkxpQIVAN%2Fln2yrSdnRtw3pjUm3Q57mq6FP;$Path=/sld/cimom
Content-Length: 385
CIMObject: sld/active
User-Agent: SAP HTTP CLIENT/6.40
CIMOperation: MethodCall
CIMProtocolVersion: 1.0
CIMMethod: Associators
Accept: application/xml, text/xml

                                                xu0153?u201C]Ou01920 u2020ïMü
÷u017D±u02DCL `©Pu2022F¾Fqu2122W¦B1U>
eu203A?ßÂØu2021u0160ºxAÒÓóu017Eç´/§úä=ÏÀu0161Uu201Au2014u2026¡hu0192¡21ÏÏt
»@~
  ì{u20202u2019    `Gö§
Sw !pu0160 ¶
åR _?Æ£ñµ u201AÐ?|Ëwöj¬U ì

ÑÜÔ±u2039¢u2122o[Ðqu20AC]d(Pu02C62æ´.+!¥u017D/SMu201A ÐB u0152f¦¾ »
u2018%u0160ú}u203AÆ5_³&£öQp Cè. s¿+ðu0178^X\{4g²1öH =
5)`9??¬u02C6Ààqu2030aBßjVÝVR¼)«WYpu2021 n°gcoÚá¬u0160ÑZºieTu02C6u017D*EmG³¬£«{A»ìu20AC=ð¯<u0161 
u0160?6Hâ¡vQ¤ìG?z|¯&<¸ÐgIû3Ú
Èf{ ÀÁu0160Y)ju2013,qÈò²f0ÉyAXµæñÖø?ð! «¬þ?ÿ_2.âlu2022].
com.sap.engine.services.httpserver.exceptions.ParseException: Incorrect request line: [°ù?f<å¬?¥¬8¥??þìÌ9?Ó Ñ¯ø3/N ©Gs-££?W»§"Wò]?¬Éh ý Ñ¯ø3/N ©Gs-££?W»§"Wò]?-Éh ýst: dc01-nfe:50000].
    at com.sap.engine.services.httpserver.lib.impl.RequestLineImpl.init(RequestLineImpl.java:332)
    at com.sap.engine.services.httpserver.lib.impl.RequestLineImpl.parseRequestLine(RequestLineImpl.java:213)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.initialize(RequestAnalizer.java:207)
    at com.sap.engine.services.httpserver.server.Client.initialize(Client.java:87)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:170)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

#
#1.5 #00155D0120030061000000290000118C000480C5891F28DE#1267485801272#com.sap.engine.services.httpserver##com.sap.engine.services.httpserver#J2EE_GUEST#0##n/a##6cee7b81258911df982e00155d012003#SAPEngine_Application_Thread[impl:3]_6##0#0#Error##Plain###User J2EE_GUEST, IP address 
Cannot parse the http request. Http error response [400 Bad Request] will be returned. Request is [°ùu0160f<å¬?¥¬8¥u2122?þìÌ9?ÓContent-Encoding: deflate
Accept-Encoding: identity, deflate
Accept-Charset: UTF-8
SAP-CIM-Client: 3.3.2
Content-Type: application/xml; charset=utf-8
Cookie: $Version=1;JSESSIONID=(DC01-NFE_NW1_00)ID0227398050DB00487802484388825785End;$Path=/,$Version=1;saplb_*=(DC01-NFE_NW1_00)7529450;$Path=/, $Version=1;MYSAPSSO2=AjExMDAgAA9wb3J0YWw6UElBRlVTRVKIAAdkZWZhdWx0AQAIUElBRlVTRVICAAMwMDADAANOVzEEAAwyMDEwMDMwMTIzMjMFAAQAAAAICgAIUElBRlVTRVL%2FAQYwggECBgkqhkiG9w0BBwKggfQwgfECAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHATGB0TCBzgIBATAiMB0xDDAKBgNVBAMTA05QSTENMAsGA1UECxMESjJFRQIBADAJBgUrDgMCGgUAoF0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTAwMzAxMjMyMzIxWjAjBgkqhkiG9w0BCQQxFgQUA3D8HxuR2JRZ!RrgHV7ZtQu8UoAwCQYHKoZIzjgEAwQwMC4CFQCZvJB7O8IrKrFH5yZKhhdH!NkxpQIVAN%2Fln2yrSdnRtw3pjUm3Q57mq6FP;$Path=/sld/cimom
Content-Length: 349
CIMObject: sld/active
User-Agent: SAP HTTP CLIENT/6.40
CIMOperation: MethodCall
CIMProtocolVersion: 1.0
CIMMethod: GetInstance
Accept: application/xml, text/xml

xu0153u2022u2019QOu01920 u2026ßMü u201EwL _u20AC¥u2013º5 Ê(.úd (u2020Øu ØÔoa 
§bÔu2021&½=ç~7½9îìu-??¨êr£<Óu2122ØæÌ?=q! 

}V(au02DCFu017E9Õu201A ¤Á§ß
 c`u017D 
 xæåtzîØ¶}a qBS
) ÜNçf8u0152    JÐÒwqu02C6Ò 
  Äu02C6@u02C6<s. ¬êu2020«Lh+¡Zj   u02C6b?.|w(ûu017DZæ¦õýu2122gM¹ ¬b?Qp 
  ® ¹=4 ÆF|Ýu017DÆ KA Q+ ? Æö6 âu2021; 
rþÜu02C6êºÒæu2014Mõ¤ nÐý u017D  Í{ ¬ oô>¡äuÝSµ©u203Aé?c\k0t× 8 ÿÊãÅD½8u201C<³?3Uu02C6-AÖñ¿Úòc cK!u203Au0152Kªäu203Au017Eµ7 \Ö `ÿÒ?U&u2022¹Xn¹,u2039Rçkà4Õößu02DCnu201C´*-Kõ u017Du /] åÎê «o:Þþ;~´àc].
com.sap.engine.services.httpserver.exceptions.ParseException: Incorrect request line: [°ù?f<å¬?¥¬8¥??þìÌ9?ÓContent-Encoding: deflate].
    at com.sap.engine.services.httpserver.lib.impl.RequestLineImpl.init(RequestLineImpl.java:332)
    at com.sap.engine.services.httpserver.lib.impl.RequestLineImpl.parseRequestLine(RequestLineImpl.java:213)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.initialize(RequestAnalizer.java:207)
    at com.sap.engine.services.httpserver.server.Client.initialize(Client.java:87)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:170)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

#
#1.5 #00155D0120030078000003700000118C000480C5892BEEB9#1267485801913#com.sap.aii.messaging.net.HTTPClientConnection#sap.com/com.sap.aii.af.soapadapter#com.sap.aii.messaging.net.HTTPClientConnection.getInputStream(Socket)#J2EE_GUEST#0##n/a##6d3129d0258911dfb28100155d012003#XI SOAP[SRVSC_SOAP_RCV/Ambiente_Homologacao/NFE_SEFAZ_MT]_20##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/SAPLibraries/SAPXDK#Plain###failed to get the input stream from socket: iaik.security.ssl.SSLException: Peer sent alert: Alert Fatal: unexpected message#
#1.5 #00155D0120030078000003720000118C000480C5892BF0CA#1267485801913#com.sap.aii.messaging.net.HTTPClientConnection#sap.com/com.sap.aii.af.soapadapter#com.sap.aii.messaging.net.HTTPClientConnection.call(Object)#J2EE_GUEST#0##n/a##6d3129d0258911dfb28100155d012003#XI SOAP[SRVSC_SOAP_RCV/Ambiente_Homologacao/NFE_SEFAZ_MT]_20##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/SAPLibraries/SAPXDK#Plain###additional info ssl_debug(11): Starting handshake (iSaSiLk 4.01)...
ssl_debug(11): Sending v3 client_hello message, requesting version 3.1...
ssl_debug(11): Received alert message: Alert Fatal: unexpected message
ssl_debug(11): SSLException while handshaking: Peer sent alert: Alert Fatal: unexpected message
ssl_debug(11): Shutting down SSL layer...
#
#1.5 #00155D0120030078000003750000118C000480C5892C012D#1267485801913#com.sap.aii.af.ra.ms.impl.core.queue.consumer.RequestConsumer##com.sap.aii.af.ra.ms.impl.core.queue.consumer.RequestConsumer.onMessage(QueueMessage, boolean)#J2EE_GUEST#0##n/a##6d3129d0258911dfb28100155d012003#SAPEngine_Application_Thread[impl:3]_0##0#0#Error##Java###Set message {0} to status FAILED.#1#df25896a-660a-a1f1-a341-00155d012003(INBOUND)#
#1.5 #00155D0120030067000000690000118C000480C5892C09AA#1267485801913#com.sap.aii.adapter.xi.ms.XIEventHandler#sap.com/com.sap.aii.af.ms.app#com.sap.aii.adapter.xi.ms.XIEventHandler.onRequest(Services, TransportMessage)#PIISUSER#215##dc0145nfe_NW1_7529450#PIISUSER#6d2edfe0258911dfcbda00155d012003#SAPEngine_Application_Thread[impl:3]_2##0#0#Error##Java###Message {0}: was not delivered due to {1}#2#df25896a-660a-a1f1-a341-00155d012003(INBOUND)#com.sap.aii.af.ra.ms.api.DeliveryException: Peer sent alert: Alert Fatal: unexpected message#
#1.5 #00155D012003005E000000220000118C000480C5898DAA3D#1267485808459#com.sap.aii.af.ra.ms.runtime.Resources##com.sap.aii.af.ra.ms.runtime.Resources.lookupFromJNDI(String, boolean)#J2EE_GUEST#0##n/a##31d04674258711dfa89700155d012003#SAPEngine_Application_Thread[impl:3]_26##0#0#Error##Plain###Failed to lookup object from JNDI for name localejbs/TestListener within app level thread. Reason: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of TestListener.#
#1.5 #00155D012003005E000000230000118C000480C5898DAAF4#1267485808475#com.sap.aii.af.ra.ms.runtime.Resources##com.sap.aii.af.ra.ms.runtime.Resources.getListener(String, boolean)#J2EE_GUEST#0##n/a##31d04674258711dfa89700155d012003#SAPEngine_Application_Thread[impl:3]_26##0#0#Error##Plain###Failed to create listener localejbs/TestListener for connection test. Reason: java.lang.Exception: Failed to lookup object from JNDI for name localejbs/TestListener within app level thread. Reason: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of TestListener.#
#1.5 #00155D012003005E000000240000118C000480C58D67B0A1#1267485868491#com.sap.aii.af.ra.ms.runtime.Resources##com.sap.aii.af.ra.ms.runtime.Resources.lookupFromJNDI(String, boolean)#J2EE_GUEST#0##n/a##31d04674258711dfa89700155d012003#SAPEngine_Application_Thread[impl:3]_26##0#0#Error##Plain###Failed to lookup object from JNDI for name localejbs/TestListener within app level thread. Reason: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of TestListener.#
#1.5 #00155D012003005E000000250000118C000480C58D67B1D4#1267485868491#com.sap.aii.af.ra.ms.runtime.Resources##com.sap.aii.af.ra.ms.runtime.Resources.getListener(String, boolean)#J2EE_GUEST#0##n/a##31d04674258711dfa89700155d012003#SAPEngine_Application_Thread[impl:3]_26##0#0#Error##Plain###Failed to create listener localejbs/TestListener for connection test. Reason: java.lang.Exception: Failed to lookup object from JNDI for name localejbs/TestListener within app level thread. Reason: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of TestListener.#
#1.5 #00155D012003005E000000260000118C000480C590F0E71F#1267485928506#com.sap.aii.af.ra.ms.runtime.Resources##com.sap.aii.af.ra.ms.runtime.Resources.lookupFromJNDI(String, boolean)#J2EE_GUEST#0##n/a##31d04674258711dfa89700155d012003#SAPEngine_Application_Thread[impl:3]_26##0#0#Error##Plain###Failed to lookup object from JNDI for name localejbs/TestListener within app level thread. Reason: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of TestListener.#
#1.5 #00155D012003005E000000270000118C000480C590F0E82E#1267485928506#com.sap.aii.af.ra.ms.runtime.Resources##com.sap.aii.af.ra.ms.runtime.Resources.getListener(String, boolean)#J2EE_GUEST#0##n/a##31d04674258711dfa89700155d012003#SAPEngine_Application_Thread[impl:3]_26##0#0#Error##Plain###Failed to create listener localejbs/TestListener for connection test. Reason: java.lang.Exception: Failed to lookup object from JNDI for name localejbs/TestListener within app level thread. Reason: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of TestListener.#

Fabio,

vocês mudaram a senha do PIRWBUSER de acordo com a nota 936093 ?

[]'s

Criamos o usuário no client do GRC e o problema foi resolvido.

Answers (1)

Fabio,

normalmente essa mensagem é relacionada a configuração do Exchange Profile, como você mesmo citou.

Verifique novamente os parâmetros:

com.sap.aii.rwb.serviceuser.name

com.sap.aii.rwb.serviceuser.pwd

com.sap.aii.rwb.serviceuser.language

Confira também se o usuário existe, se ele possui as permissões SAP_SLD_CONFIGURATOR, SAP_XI_RWB_SERV_USER e SAP_XI_RWB_SERV_USER_MAIN e se ele não está lockado.

[]'s

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

E se a senha dele nao foi trocada (deveria ser o master password da instancia).

Abs,

Henrique.

Ask a Question

Top Q&A Solution Author

User

Count

Problema com o usuário PIRWBUSER

Accepted Solutions (1)

Accepted Solutions (1)

Answers (1)

Answers (1)

Re: Group Reporting Rule Based COI - TP calculatio...

how to check business catalog to be assigned For c...

Re: Asset transfer ABUMN - partial transfer of wro...

Re: Asset transfer ABUMN - partial transfer of wro...

Re: Group Reporting Rule Based COI - TP calculatio...