on 01-19-2008 3:43 PM
Hy, i have this problem: i set a connection to Portal on SAP NetWeaver Business Client and after that i insert my user and password on logon portal screen, i receive this message: internal server error (500) - Exception in method getNavigationTree.
I find that getNavigationTree is a method of web service WSNavigation and i tested it on the portal and i didn't have no error exception.
Could you help me?
Thank's in advance.
Andrea Maraviglia
we have the same problem. Has anybody solved it yet?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Andrea,
we are already fresh on SPS14.
So there must be another reason for this error.
We are getting an answer from the server...., but the answer contains
.....<faultcode>SOAP-ENV:Client</faultcode><faultstring>Exception in method getNavigationTree.</faultstring>....
Do you have any other idea?
Best regard
Andreas
Hi,
I assume the problem is the parameter numberOfLevels, which is on "-1".
We are getting the same problem when testing it manually.
Thanks
Andreas
The NWBC sends the following REQUEST:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
<NWBC::CBackendConnection> | CPortalBackendConnection::getNavigationTree: sending HTTP request (connection HTTP://hptsapv14:50100/NavigationWS/NavigationWSConfig?wsdl=binding&style=document)
00000000: 3C 3F 78 6D 6C 20 76 65 72 73 69 6F 6E 3D 22 31 <?xml version="1
00000010: 2E 30 22 20 65 6E 63 6F 64 69 6E 67 3D 22 55 54 .0" encoding="UT
00000020: 46 2D 38 22 20 3F 3E 3C 53 4F 41 50 2D 45 4E 56 F-8" ?><SOAP-ENV
00000030: 3A 45 6E 76 65 6C 6F 70 65 20 78 6D 6C 6E 73 3A :Envelope xmlns:
00000040: 53 4F 41 50 2D 45 4E 56 3D 22 68 74 74 70 3A 2F SOAP-ENV="http:/
00000050: 2F 73 63 68 65 6D 61 73 2E 78 6D 6C 73 6F 61 70 /schemas.xmlsoap
00000060: 2E 6F 72 67 2F 73 6F 61 70 2F 65 6E 76 65 6C 6F .org/soap/envelo
00000070: 70 65 2F 22 20 78 6D 6C 6E 73 3A 78 73 69 3D 22 pe/" xmlns:xsi="
00000080: 68 74 74 70 3A 2F 2F 77 77 77 2E 77 33 2E 6F 72 http://www.w3.or
00000090: 67 2F 32 30 30 31 2F 58 4D 4C 53 63 68 65 6D 61 g/2001/XMLSchema
000000A0: 2D 69 6E 73 74 61 6E 63 65 22 20 78 6D 6C 6E 73 -instance" xmlns
000000B0: 3A 78 73 3D 22 68 74 74 70 3A 2F 2F 77 77 77 2E :xs="http://www.
000000C0: 77 33 2E 6F 72 67 2F 32 30 30 31 2F 58 4D 4C 53 w3.org/2001/XMLS
000000D0: 63 68 65 6D 61 22 3E 09 3C 53 4F 41 50 2D 45 4E chema">.<SOAP-EN
000000E0: 56 3A 42 6F 64 79 3E 09 09 3C 70 6E 73 3A 67 65 V:Body>..<pns:ge
000000F0: 74 4E 61 76 69 67 61 74 69 6F 6E 54 72 65 65 20 tNavigationTree
00000100: 78 6D 6C 6E 73 3A 70 6E 73 3D 27 75 72 6E 3A 4E xmlns:pns='urn:N
00000110: 61 76 69 67 61 74 69 6F 6E 57 53 56 69 27 3E 09 avigationWSVi'>.
00000120: 09 09 3C 6E 73 31 3A 72 65 71 75 65 73 74 50 61 ..<ns1:requestPa
00000130: 72 61 6D 20 78 6D 6C 6E 73 3A 6E 73 31 3D 27 75 ram xmlns:ns1='u
00000140: 72 6E 3A 4E 61 76 69 67 61 74 69 6F 6E 57 53 56 rn:NavigationWSV
00000150: 69 27 20 78 6D 6C 6E 73 3A 70 6E 73 3D 27 75 72 i' xmlns:pns='ur
00000160: 6E 3A 63 6F 6D 2E 73 61 70 2E 70 6F 72 74 61 6C n:com.sap.portal
00000170: 2E 6E 61 76 69 67 61 74 69 6F 6E 2E 77 73 27 3E .navigation.ws'>
00000180: 09 09 09 09 3C 70 6E 73 3A 76 65 72 73 69 6F 6E ....<pns:version
00000190: 3E 30 3C 2F 70 6E 73 3A 76 65 72 73 69 6F 6E 3E >0</pns:version>
000001A0: 09 09 09 09 3C 70 6E 73 3A 61 67 67 72 65 67 61 ....<pns:aggrega
000001B0: 74 65 43 6F 6C 6C 65 63 74 69 6F 6E 3E 66 61 6C teCollection>fal
000001C0: 73 65 3C 2F 70 6E 73 3A 61 67 67 72 65 67 61 74 se</pns:aggregat
000001D0: 65 43 6F 6C 6C 65 63 74 69 6F 6E 3E 09 09 09 09 eCollection>....
000001E0: 3C 70 6E 73 3A 65 6E 76 69 72 6F 6E 6D 65 6E 74 <pns:environment
000001F0: 3E 09 09 09 09 09 3C 70 6E 73 3A 4B 65 79 56 61 >.....<pns:KeyVa
00000200: 6C 75 65 45 6E 74 72 79 3E 3C 70 6E 73 3A 6E 61 lueEntry><pns:na
00000210: 6D 65 3E 4D 41 58 49 4D 55 4D 5F 4E 4F 44 45 53 me>MAXIMUM_NODES
00000220: 3C 2F 70 6E 73 3A 6E 61 6D 65 3E 3C 70 6E 73 3A </pns:name><pns:
00000230: 76 61 6C 75 65 3E 31 30 30 30 30 30 3C 2F 70 6E value>100000</pn
00000240: 73 3A 76 61 6C 75 65 3E 3C 2F 70 6E 73 3A 4B 65 s:value></pns:Ke
00000250: 79 56 61 6C 75 65 45 6E 74 72 79 3E 09 09 09 09 yValueEntry>....
00000260: 3C 2F 70 6E 73 3A 65 6E 76 69 72 6F 6E 6D 65 6E </pns:environmen
00000270: 74 3E 09 09 09 09 3C 6E 73 32 3A 6E 6F 64 65 41 t>....<ns2:nodeA
00000280: 64 64 69 74 69 6F 6E 61 6C 50 61 72 61 6D 73 20 dditionalParams
00000290: 78 6D 6C 6E 73 3A 6E 73 32 3D 22 75 72 6E 3A 63 xmlns:ns2="urn:c
000002A0: 6F 6D 2E 73 61 70 2E 70 6F 72 74 61 6C 2E 6E 61 om.sap.portal.na
000002B0: 76 69 67 61 74 69 6F 6E 2E 77 73 22 20 78 6D 6C vigation.ws" xml
000002C0: 6E 73 3A 70 6E 73 3D 22 75 72 6E 3A 6A 61 76 61 ns:pns="urn:java
000002D0: 2F 6C 61 6E 67 22 3E 09 09 09 09 09 3C 70 6E 73 /lang">.....<pns
000002E0: 3A 53 74 72 69 6E 67 3E 43 6C 69 65 6E 74 54 79 :String>ClientTy
000002F0: 70 65 3C 2F 70 6E 73 3A 53 74 72 69 6E 67 3E 09 pe</pns:String>.
00000300: 09 09 09 09 3C 70 6E 73 3A 53 74 72 69 6E 67 3E ....<pns:String>
00000310: 63 6F 6D 2E 73 61 70 2E 70 6F 72 74 61 6C 2E 6E com.sap.portal.n
00000320: 61 76 69 67 61 74 69 6F 6E 2E 49 73 4C 65 61 66 avigation.IsLeaf
00000330: 3C 2F 70 6E 73 3A 53 74 72 69 6E 67 3E 09 09 09 </pns:String>...
00000340: 09 3C 2F 6E 73 32 3A 6E 6F 64 65 41 64 64 69 74 .</ns2:nodeAddit
00000350: 69 6F 6E 61 6C 50 61 72 61 6D 73 3E 09 09 09 09 ionalParams>....
00000360: 3C 70 6E 73 3A 6E 75 6D 62 65 72 4F 66 4C 65 76 <pns:numberOfLev
00000370: 65 6C 73 3E 2D 31 3C 2F 70 6E 73 3A 6E 75 6D 62 els>-1</pns:numb
00000380: 65 72 4F 66 4C 65 76 65 6C 73 3E 09 09 09 3C 2F erOfLevels>...</
00000390: 6E 73 31 3A 72 65 71 75 65 73 74 50 61 72 61 6D ns1:requestParam
000003A0: 3E 09 09 3C 2F 70 6E 73 3A 67 65 74 4E 61 76 69 >..</pns:getNavi
000003B0: 67 61 74 69 6F 6E 54 72 65 65 3E 09 3C 2F 53 4F gationTree>.</SO
000003C0: 41 50 2D 45 4E 56 3A 42 6F 64 79 3E 3C 2F 53 4F AP-ENV:Body></SO
000003D0: 41 50 2D 45 4E 56 3A 45 6E 76 65 6C 6F 70 65 3E AP-ENV:Envelope>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
and gets the following response:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
<NWBC::CBackendConnection> | CPortalBackendConnection::getNavigationTree: received HTTP response (connection HTTP://hptsapv14:50100/NavigationWS/NavigationWSConfig?wsdl=binding&style=document)
00000000: 3C 53 4F 41 50 2D 45 4E 56 3A 45 6E 76 65 6C 6F <SOAP-ENV:Envelo
00000010: 70 65 20 78 6D 6C 6E 73 3A 53 4F 41 50 2D 45 4E pe xmlns:SOAP-EN
00000020: 56 3D 22 68 74 74 70 3A 2F 2F 73 63 68 65 6D 61 V="http://schema
00000030: 73 2E 78 6D 6C 73 6F 61 70 2E 6F 72 67 2F 73 6F s.xmlsoap.org/so
00000040: 61 70 2F 65 6E 76 65 6C 6F 70 65 2F 22 20 78 6D ap/envelope/" xm
00000050: 6C 6E 73 3A 78 73 3D 22 68 74 74 70 3A 2F 2F 77 lns:xs="http://w
00000060: 77 77 2E 77 33 2E 6F 72 67 2F 32 30 30 31 2F 58 ww.w3.org/2001/X
00000070: 4D 4C 53 63 68 65 6D 61 22 20 78 6D 6C 6E 73 3A MLSchema" xmlns:
00000080: 78 73 69 3D 22 68 74 74 70 3A 2F 2F 77 77 77 2E xsi="http://www.
00000090: 77 33 2E 6F 72 67 2F 32 30 30 31 2F 58 4D 4C 53 w3.org/2001/XMLS
000000A0: 63 68 65 6D 61 2D 69 6E 73 74 61 6E 63 65 22 20 chema-instance"
000000B0: 3E 3C 53 4F 41 50 2D 45 4E 56 3A 42 6F 64 79 3E ><SOAP-ENV:Body>
000000C0: 3C 53 4F 41 50 2D 45 4E 56 3A 46 61 75 6C 74 3E <SOAP-ENV:Fault>
000000D0: 3C 66 61 75 6C 74 63 6F 64 65 3E 53 4F 41 50 2D <faultcode>SOAP-
000000E0: 45 4E 56 3A 43 6C 69 65 6E 74 3C 2F 66 61 75 6C ENV:Client</faul
000000F0: 74 63 6F 64 65 3E 3C 66 61 75 6C 74 73 74 72 69 tcode><faultstri
00000100: 6E 67 3E 45 78 63 65 70 74 69 6F 6E 20 69 6E 20 ng>Exception in
00000110: 6D 65 74 68 6F 64 20 67 65 74 4E 61 76 69 67 61 method getNaviga
00000120: 74 69 6F 6E 54 72 65 65 2E 3C 2F 66 61 75 6C 74 tionTree.</fault
00000130: 73 74 72 69 6E 67 3E 3C 64 65 74 61 69 6C 3E 3C string><detail><
00000140: 6E 73 31 3A 63 6F 6D 2E 73 61 70 2E 65 6E 67 69 ns1:com.sap.engi
00000150: 6E 65 2E 73 65 72 76 69 63 65 73 2E 65 6A 62 2E ne.services.ejb.
00000160: 65 78 63 65 70 74 69 6F 6E 73 2E 42 61 73 65 45 exceptions.BaseE
00000170: 4A 42 45 78 63 65 70 74 69 6F 6E 20 78 6D 6C 6E JBException xmln
00000180: 73 3A 6E 73 31 3D 27 68 74 74 70 3A 2F 2F 73 61 s:ns1='http://sa
00000190: 70 2D 6A 32 65 65 2D 65 6E 67 69 6E 65 2F 63 6C p-j2ee-engine/cl
000001A0: 69 65 6E 74 2D 72 75 6E 74 69 6D 65 2D 65 72 72 ient-runtime-err
000001B0: 6F 72 27 3E 45 78 63 65 70 74 69 6F 6E 20 69 6E or'>Exception in
000001C0: 20 6D 65 74 68 6F 64 20 67 65 74 4E 61 76 69 67 method getNavig
000001D0: 61 74 69 6F 6E 54 72 65 65 2E 3C 2F 6E 73 31 3A ationTree.</ns1:
000001E0: 63 6F 6D 2E 73 61 70 2E 65 6E 67 69 6E 65 2E 73 com.sap.engine.s
000001F0: 65 72 76 69 63 65 73 2E 65 6A 62 2E 65 78 63 65 ervices.ejb.exce
00000200: 70 74 69 6F 6E 73 2E 42 61 73 65 45 4A 42 45 78 ptions.BaseEJBEx
00000210: 63 65 70 74 69 6F 6E 3E 3C 2F 64 65 74 61 69 6C ception></detail
00000220: 3E 3C 2F 53 4F 41 50 2D 45 4E 56 3A 46 61 75 6C ></SOAP-ENV:Faul
00000230: 74 3E 3C 2F 53 4F 41 50 2D 45 4E 56 3A 42 6F 64 t></SOAP-ENV:Bod
00000240: 79 3E 3C 2F 53 4F 41 50 2D 45 4E 56 3A 45 6E 76 y></SOAP-ENV:Env
00000250: 65 6C 6F 70 65 3E elope>
ERROR <NWBC::CBackendConnection> | CPortalBackendConnection::getNavigationTree: server returned HTTP error code 500
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
the system is an EP core system with java stack only...so there is no SICF transaction.
Hi,
we tested the WS in test mode with the following combinations:
numberOfLevels = -1
lastModification not initial
-> Successful, but empty result
numberOfLevels = -1
lastModification initial
-> Error 500
numberOfLevels = 1
lastModification initial
-> Successful, first hierarchy is being set
numberOfLevels = 2
lastModification initial
-> Error 500
So we are trying the SPS 15 from last week, maybe it helps.
Thanks
Andreas
Hi All,
I see this message was created in 2008 and we are testing now and still getting the same error.
We are on NWBC 3.0. Has anybody found a solution for this problem?
The complication is we are taking a bunch of Portal roles and grouping them together and assigning that group to a userid.
That is when we get the same error as described in this thread. We have provided merge IDs for different iViews and I suspect if there are too many iViews with the same merge ID, NWBC does not like it.
We have created a super role containing about 7-8 folders in detailed navigation with a total of about 1000+ transactions and it seems to work fine. So i think NWBC can handle the volume but the Merge IDs is where it is getting tripped.
Would appreciate if somebody can help us.
regards,
Atul
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.