cancel
Showing results for 
Search instead for 
Did you mean: 

Portal 7.3 not working through NWBC 4.0

former_member182416
Active Contributor
0 Kudos

Hi

Installed NWBC 4.0.

Tried to open Portal 7.3 through NWBC.

Got the Logon Page.After Logging in got the Following Error.

Could not open the logon window for the server with the supplied URL.

Check that the URL is valid and server is running.To do this, call the same URL in the browser.

The URL Works fine in Browser.

Portal 7.0 works fine in NWBC. Any Clues?

Regards

Rajendra

Accepted Solutions (1)

Accepted Solutions (1)

Jnouwen
Explorer
0 Kudos

We got following solution from SAP support:

connect to http://[host]:[port]/nwa/ssadmin

In the configuration of WSDL port type ConfigurationWSSI, you find an endpoint and for this endpoint security settings. Here: switch to HTTP and remove check marks for x.509 client certificate under HTTP authentication and remove all checkmarks under Message Authentication.

The same must be done for WSDL port type NavigationWSVi.

This works !!

former_member182416
Active Contributor
0 Kudos

Hi

Does this Reuire Portal Restart?

After performing the changes suggested by you,still it is not working.

Regards

Rajendra

Former Member
0 Kudos

Worked for me without restart. So should be good to go.

Cheers

Jnouwen
Explorer
0 Kudos

The follow-on problem is now that OBN does not work in NWBC 3.5 or 4.0.

Symptom is similar: in Fiddler trace a http 500 error on /NavigationWS/NavigationWSConfig?wsdl=binding&style=document.

Issue at sap is open since 2 weeks (message 6563).

Can any of you confirm to have the same issue and eventually found the solution ?

Rgds.






6563 / 2013

    
Former Member
0 Kudos

Hi Jos,

Thanks it works !

@ Rajendira - No portal restart needed .

Regards

Kumar

former_member182416
Active Contributor
0 Kudos

We upgraded to 7.31 SP6 and it worked with default settings!

No change required from https to http and no checkmarks to be removed etc.

Regards

Rajendra

Jnouwen
Explorer
0 Kudos

Must say that we started with SPS 6 on a brand new 7.31 and there it was needed to change the services as explained.

Jnouwen
Explorer
0 Kudos

SAP support has compiled a new NWBC patch that will re-enable OBN with Portal.

Official release would be somewhere in June 2013.

Answers (3)

Answers (3)

Jnouwen
Explorer
0 Kudos

Hi,

We have the issue reported to OSS on Jan 28th. Sent a lot of trace files, still waiting for a solution.

I would be happy if you would share the solution (if any yet) through this post !

Thanks in advance.

former_member182416
Active Contributor
0 Kudos

No Luck yet.

Regards

Rajendra

0 Kudos

Hi Jos,

could you please provide OSS number?

Regards,

Andriy

Jnouwen
Explorer
0 Kudos

Hi Andriy,

Number is 87986 / 2013.

Regards

julieplummer20
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Jos,

Now that Andriy has picked this up, it is a support issue, so I shall close this question.

Former Member
0 Kudos

Hi Andy, will be great if you can share resolution for this issue. We are also waiting to see if we need to raise an OSS for this. Please advice.

regards,

julieplummer20
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Sudhir,

Yes, OSS message is the fastest, most efficient way to get the answer from Support. I would strongly advise it. Hope you get resolution quickly.

Best wishes,

Julie.

Former Member
0 Kudos

G'day Andriy,

We have raised OSS message 214098 / 2013

Regards,

Sudhir

sandra_thimme
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Raj,

could you please have a look at the following information and open an OSS-Mesage.

http://help.sap.com/saphelp_nw70ehp3/helpdata/en/4c/5bd5ab97817511e10000000a42189b/content.htm?frame...

thanks,

Sandra

Former Member
0 Kudos

Same issue. This is not browser restriction in our case. Any luck with your issue Rajendra?

Rgds

former_member182416
Active Contributor
0 Kudos

The Trace File Shows the Following :

WebException: The remote server returned an error: (500) Internal Server Error.


   at System.Net.HttpWebRequest.GetResponse()


   at com.sap.nw.nwbc.csruntime.implementation.navigation.core.CsNavigationVirtualRoot.DoGZIPRequest(String url, String requestData, String& responseData, Boolean addSapClientAndNwbcContext)



10:17:54.882 [Runtime] E          Body of error response is EMPTY


10:17:55.194 [Runtime] E          DoXmlGzipRequest failed


================================================================


HHHHHH                     Exception                      HHHHHH


================================================================


WebException: The remote server returned an error: (500) Internal Server Error.


   at System.Net.HttpWebRequest.GetResponse()


   at com.sap.nw.nwbc.csruntime.implementation.navigation.core.CsNavigationVirtualRoot.DoGZIPRequest(String url, String requestData, String& responseData, Boolean addSapClientAndNwbcContext)



10:17:55.194 [Runtime] E          Body of error response is EMPTY


10:17:55.256 [Runtime] E          DoXmlGzipRequest failed


================================================================


HHHHHH                     Exception                      HHHHHH


================================================================


WebException: The remote server returned an error: (500) Internal Server Error.


   at System.Net.HttpWebRequest.GetResponse()


   at com.sap.nw.nwbc.csruntime.implementation.navigation.core.CsNavigationVirtualRoot.DoGZIPRequest(String url, String requestData, String& responseData, Boolean addSapClientAndNwbcContext)



10:17:55.256 [Runtime] E          Body of error response is EMPTY


10:17:55.256 [Runtime] E          Failed to retrieve system info of navigation tree: The remote server returned an error: (500) Internal Server Error.


10:17:55.615 [main] E             Error: translation without placeholder #1: SH_LOGON_LOADING_FAILED_MSG -> Sh71 -> Could not open the logon window for the server with the supplied URL:



http://<serverName>:50000/irj/portal/ajax



Check that the URL is valid and the server is running. To do this, call the same URL in the browser.