cancel
Showing results for 
Search instead for 
Did you mean: 

NWBC 4.0 logon hangs

Former Member
0 Kudos

I installed version 4.0 of NWBC earlier this week.  When I first opened the application, I was able to login to the system and it functioned correctly.  I closed the application and attempted to relaunch.  The system selection dialog displayed, I chose a system, provided my credentials, and clicked login.  The login screen went blank and doesn't proceed.  The top of the dialog reads Log on to 'my system'.  I have multiple systems and receive the same error for each.  The HTML version of NWBC continues to function correctly.  I have re-installed NWBC several times; however, it does not resolve the problem.  Any suggestions?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

NWBC 4.0 PL1 was delivered to Service Marketplace this morning and should be available to download.


This quick patch contains only one fix regarding the logon, nothing more. It is planned to deliver the next patch with serveral bug fixes and functional improvements in about 4 weeks.

It would be great if you try again with the new version and leave a short comment if the problem is gone. There is no quarantee that exactly your problem is solved, but hopefully it is.

If you still can't logon than it would be great if you will open a ticket on our component (BC-FES-BUS-DSK).


There are several topics about opening tickets and providing required information in our documentation Chapter 10 (SUP.XX).

Kind Regards,

Thomas

Former Member
0 Kudos

Hello Thomas,

works for me now!


Many Thanks!

a_vanengen
Explorer
0 Kudos

Hello Thomas,

thanks for your quick action. for me the problem is solved as well.

regards

Albert

Former Member
0 Kudos

Problem solved.  Thanks!

former_member192995
Participant
0 Kudos

For me as well.

Good job, thanks!

MattHarding
Active Contributor
0 Kudos

Hi Thomas,

Looks like a 100% hit ratio for the fix. 

Thanks!

Matt

Former Member
0 Kudos

Thank you for your help Thomas, greatly appreciated!

Former Member
0 Kudos

Hello Thomas,

could you please indicate the link where I can find NWBC 4.0 PL1 for download. I cannot find it.

Thank you,

Kind regards,

a_vanengen
Explorer
0 Kudos

Hi Martina,

in the meantime SAP has provided NWBC 4.0 PL 10

you can find NWBC on the service market place in SWDC under support Packages and Patches

use search and search for NWBC

or use this URL

https://websmp209.sap-ag.de/~form/handler?_APP=00200682500000001943&_EVENT=DISPHIER&HEADER=Y&FUNCTIO...

regards

Albert van Engen

Answers (7)

Answers (7)

Former Member
0 Kudos

Hi Thomas,

We experienced the same issue with NWBC5.0. After entering credentials and hitting enter, a white screen shows up and it hangs there. Any thoughts?

Thanks,

Hung

Former Member
0 Kudos

Hello Thomas,

In NetWeaver business client 4.0 PL 10, While connecting to NWBC I am getting initiation screen and going blank after 2 sec. Please suggest on this.

Thanks & Regards,

Bharath.

Former Member
0 Kudos

I have got an error in Solman MOPZ with text

"Failed to resolve Object Based Navigation target 'S30.SolmanNavigation.NavigateUrl'.

Contact your system administrator to assign a role to your user with the relevant OBN entries"

I removed all files in two directories

C:\Users\<username>\AppData\Roaming\SAP\NWBC

C:\Users\<username>\AppData\Local\SAP\NWBC

then I sep up trace level equal "error" again.

It helped me.

Former Member
0 Kudos

Hey Folks,

I wasnt sure whether to start a new thread or continue this one, but I am having the same problems with both NWBC 3.5 (PL8) and 4.0 (PL2).  I have tried uninstalling and re-installing them several times to no avail.  One will work when I start up my PC, but once I close it neither will work after that

With 3.5 I get to the login screen, and when I enter my details the login screen disappears, gives me a blank screen and stops responding

When I installed 4.0 and used it the first time it worked fine. When I close it and attempt to open it again it crashes at the splash screen, and won't work again unless I restart the computer, then it will work the first time again and crash each time after that

Windows 7  and SAP GUI 7.3, the last few lines of the log file are:

+++ Tracelevel for module 'NwbcTranslation.dll' = Info
11:22:35.804 [main] *          NwbcConfiguration.LoadOptionsFile: C:\Users\IBM_ADMIN\AppData\Roaming\SAP\NWBC\NwbcOptions.xml {
11:22:35.811 [main] *           NwbcConfiguration.ParseOptionsFile: NWBC_USER_FILE {
11:22:35.930 [main] *           } // NwbcConfiguration.ParseOptionsFile [ /u 109.2ms /e 115.0ms ]
11:22:35.930 [main] *          } // NwbcConfiguration.LoadOptionsFile [ /u 124.8ms /e 127.0ms ]
11:22:35.930 [main] *         } // NwbcConfiguration.Initialize [ /u 218.4ms /k 31.2ms /e 251.0ms ]
+++ Tracelevel for module 'NwbcRemoting.dll' = Info

++++++ GlobalTraceLevel set to: Error

+++ Tracelevel for module 'NwbcSapguiCom.dll' = Info
+++ Tracelevel for module 'NwbcThemes.dll' = Info
11:22:37.895 [main] *         Using PluginFolder: C:\Program Files (x86)\SAP\NWBC40\plugins
11:22:38.331 [main] *         AutomationHelper.Load {
11:22:38.333 [main] *         } // AutomationHelper.Load [ /u 15.6ms /e 2.0ms ]

So it seems to end abruptly.  Also the log file mentions C:\Program Files (x86)\SAP\NWBC40\plugins but this folder doesnt exist.  I created the folder and left it empty but still nothing happened.

Thanks in advance for your help

Former Member
0 Kudos

"Run as administrator" may help.

Former Member
0 Kudos

Hi Colm,

the trace does not have the correct level for a detailed analysis. The problem with NWBC 4.0 seems to be not related to the problem which is discussed in this thread.

The symptom for the hanging logon is the empty logon screen after submitting the credentials.The logon screen never disappears, it stays on top but it is completely white.

I could give you only the advice to change the trace level before starting NWBC and check if you can see something.

As you can't change the trace level with NWBC (if it not crashes, than it is possible with Menu Settings > Support) you can set it in the Options file stored in your User Profile folder:

C:\Users\<YOUR USER ID>\AppData\Roaming\SAP\NWBC

Open the file NwbcOptions.xml in any text editor and add or change the following xml tag to

<SingleOptions>

     <TraceLevel>Verbose</TraceLevel>

</SingleOptions>

The file is used for both clients.

Kind Regards,

Thomas

Former Member
0 Kudos

Thanks for your reply Thomas and Evgeniy,

I have tried running as administrator but again no joy.  I set the trace level to "Verbose" and got the below, unfotunately it means nothing to me!

10:26:23.981 [main]              } // InstallationConsistency.CheckInstallationFolder [ /u 265.2ms /k 140.4ms /e 418.0ms ] => True
10:26:23.982 [main]              NotifyableBool.Fire_PropertyChanged {
10:26:23.982 [main]              } // NotifyableBool.Fire_PropertyChanged
10:26:24.001 [main] .            {3} ProcessLifecycle.Startup [main<=>Runtime]: Waiting for result...
10:26:24.021 [Runtime]        ProcessLifecycle.Startup [main<=>Runtime] {
10:26:24.035 [Runtime]         CsRuntime.LoadConnections_via_Config {
10:26:24.041 [Runtime]          NwbcConfiguration.GetPropertyPageByID {
10:26:24.043 [Runtime]          } // NwbcConfiguration.GetPropertyPageByID [ /e 2.0ms ]
10:26:24.076 [Runtime] w        Unknown connection property: Name: Comment: Value: PPM Development
10:26:24.077 [Runtime] w        Unknown connection property: Name: Proxy User: Value:
10:26:24.077 [Runtime] w        Unknown connection property: Name: Proxy Password: Value:
10:26:24.077 [Runtime] w        Unknown connection property: Name: GUID Value: 2951fc59-051c-4e50-8043-d54063f7f30a
10:26:24.077 [Runtime] w        Unknown connection property: Name: No Text ID for: NWBC_PROPERTY_FINAL Value: False
10:26:24.077 [Runtime] w        Unknown connection property: Name: No Text ID for: NWBC_PROPERTY_TOBESAVED Value: True
10:26:24.078 [Runtime] w        Unknown connection property: Name: No Text ID for: NWBC_PROPERTY_INVISIBLE Value: False
10:26:24.086 [Runtime] w        Unknown connection property: Name: Comment: Value:
10:26:24.086 [Runtime] w        Unknown connection property: Name: Proxy User: Value:
10:26:24.086 [Runtime] w        Unknown connection property: Name: Proxy Password: Value:
10:26:24.087 [Runtime] w        Unknown connection property: Name: GUID Value: 7db2424b-70fe-4c43-a5f3-d82cb445dffe
10:26:24.087 [Runtime] w        Unknown connection property: Name: No Text ID for: NWBC_PROPERTY_FINAL Value: False
10:26:24.087 [Runtime] w        Unknown connection property: Name: No Text ID for: NWBC_PROPERTY_TOBESAVED Value: True
10:26:24.087 [Runtime] w        Unknown connection property: Name: No Text ID for: NWBC_PROPERTY_INVISIBLE Value: False
10:26:24.087 [Runtime]         } // CsRuntime.LoadConnections_via_Config [ /u 46.8ms /e 52.0ms ]
10:26:24.088 [Runtime] .       NotLoggedIn
10:26:24.089 [Runtime]         Translation.Refill_F {
10:26:24.089 [Runtime] .        Translation: TXTID_FND_NAVIGATION_FAILED -> FNavFail = Failed to resolve Object Based Navigation target '%0'. Contact your system administrator to assign a role to your user with the relevant OBN entries
10:26:24.090 [Runtime]          Translation.Fire_Refilled {
10:26:24.090 [Runtime]          } // Translation.Fire_Refilled
10:26:24.090 [Runtime]         } // Translation.Refill_F [ /e 2.0ms ]
10:26:24.091 [Runtime] .       {3} ProcessLifecycle.Startup [main<=>Runtime]: set_Result:
10:26:24.092 [main] .            {3} ProcessLifecycle.Startup [main<=>Runtime]: Result available:
10:26:24.092 [Runtime] .       NotifyFinished
10:26:24.092 [Runtime]        } // <>c__DisplayClassb.<BeginRun>b__a [ /u 78.0ms /e 71.0ms ]
10:26:24.094 [main]              App.FireRtlChanged {
10:26:24.094 [main]              } // App.FireRtlChanged
10:26:24.142 [main]             

=========> Loaded assembly: NwbcThemes, Version=40000.1210.11118.19719, Culture=neutral, PublicKeyToken=null

+++ Tracelevel for module 'NwbcThemes.dll' = Info
10:26:24.162 [main]              ThemeManager.SwitchTheme: newTheme= (DARK) {
10:26:24.162 [main]              } // ThemeManager.SwitchTheme
10:26:24.250 [main]              App.TryLoadMessageSpyHelper {
10:26:24.250 [main]              } // App.TryLoadMessageSpyHelper
10:26:24.255 [main] *            Using PluginFolder: C:\Program Files (x86)\SAP\NWBC40\plugins
10:26:24.255 [main]              PluginManager.RefreshPluginCache {
10:26:24.256 [main]               Cannot refresh plugins, NwbcUtil is missing in plugins folder
10:26:24.256 [main]              } // PluginManager.RefreshPluginCache [ /e 1.0ms ]
10:26:24.256 [main]             } // ProcessLifecycle.Startup [ /u 468.0ms /k 156.0ms /e 706.0ms ]
10:26:24.256 [main]            } // StaThread.Run [ /u 499.2ms /k 156.0ms /e 740.0ms ]
10:26:24.256 [main]           } // App.OnStartup [ /u 514.8ms /k 156.0ms /e 745.0ms ]
10:26:24.547 [main]          

=========> Loaded assembly: PresentationFramework.Aero, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35

10:26:24.579 [main]           ShellMenu..ctor {
10:26:24.688 [main]           } // ShellMenu..ctor [ /u 109.2ms /e 109.0ms ]
10:26:24.699 [main] *         AutomationHelper.Load {
10:26:24.703 [main]            Automation library Nwbc.Automation.dll not installed.
10:26:24.703 [main] *         } // AutomationHelper.Load [ /u 15.6ms /e 4.0ms ]
10:26:24.727 [main]           CanvasWindow.OnInitialized {
10:26:24.730 [main] .          ====> CanvasWindow.Initialized: SAP NetWeaver Business Client
10:26:24.730 [main]           } // CanvasWindow.OnInitialized [ /e 3.0ms ]
10:26:24.737 [main]           CanvasWindow.RestoreWindowState: persistenceIdentifier=ShellWindow {
10:26:24.741 [main]            Settings.GetRestoreState: identifier=ShellWindow {
10:26:24.743 [main]            } // Settings.GetRestoreState [ /e 1.0ms ] => 25/52 1200x632 (Maximized)
10:26:24.751 [main]            UiUtil.EnsureCompletelyVisible {
10:26:24.754 [main]            } // UiUtil.EnsureCompletelyVisible [ /e 3.0ms ] => 25,52,1200,632 => 25,52,1200,632
10:26:24.758 [main] .          Setting Top=52
10:26:24.758 [main] .          Setting Left=25
10:26:24.758 [main] .          Delay until loaded: Setting WindowState=Maximized
10:26:24.758 [main]           } // CanvasWindow.RestoreWindowState [ /u 15.6ms /e 21.0ms ] => 25/52 1200x632 (Maximized)
10:26:24.777 [main]           CanvasWindow.OnLocationChanged {
10:26:24.779 [main]            OnRefreshShadow: OnLocationChanged {
10:26:24.779 [main]            } // CanvasWindow.OnRefreshShadow
10:26:24.779 [main]           } // CanvasWindow.OnLocationChanged [ /u 15.6ms /e 2.0ms ]
10:26:24.873 [main]          

=========> Loaded assembly: System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=************e089

I starred out the "PublicKeyToken" on the final line because I thought it might be a security issue, but it is a 15 letter key.  That is the last quarter of the trace file and thats where it ends. 

I have attached a screenshot of how far I get to, ie just as far as the splash screen!

Former Member
0 Kudos

Hi Colm,

my trace file has another content

+++ Tracelevel for module 'NwbcTranslation.dll' = Info

NwbcConfiguration.LoadOptionsFile: C:\ProgramData\SAP\NWBC\NwbcOptions.xml {

NwbcConfiguration.ParseOptionsFile: NWBC_ADMIN_FILE {

} // NwbcConfiguration.ParseOptionsFile [ /u 546.0ms /e 1.7sec ]

} // NwbcConfiguration.LoadOptionsFile [ /u 592.8ms /k 15.6ms /e 1.7sec ]

NwbcConfiguration.LoadOptionsFile: C:\Users\seleznev\AppData\Roaming\SAP\NWBC\NwbcOptions.xml {

NwbcConfiguration.ParseOptionsFile: NWBC_USER_FILE {

Validation of options xml file(severity type Error):

NWBC4.0 requires 2 files -

NWBC_ADMIN_FILE = C:\ProgramData\SAP\NWBC\NwbcOptions.xml

NWBC_USER_FILE = C:\Users\<user>\AppData\Roaming\SAP\NWBC\NwbcOptions.xml

NWBC_USER_FILE is the copy of NWBC_ADMIN_FILE

NWBC_ADMIN_FILE includes the default connection.

that connection can't be established.

Possibly it's necessary to delete all temp files but NWBC_ADMIN_FILE

Then it's necessary "run as administrator".

may be...

Evgeniy

Former Member
0 Kudos

Hello,

we are aware of this problem. Unfortunatly it affects all versions (3.0, 3.5 and 4.0) and is based on the response of the ticket issuing server. This is pure XML and a browser interprets the xml sometimes different - which might cause the problems especially with IE9.

The server response needs to be parsed from NWBC to finally decide if the user is logged in and a login ticket is issued. If the login is not able to parse the response, the login control hangs and nothing happens any more. (seems to be not on every machine)

You can easily check if this is the root cause of your NWBC problem by checking the trace file.

Go to "C:\Users\<YOUR USERNAME>\AppData\Local\SAP\NWBC\Traces" and open the log file "Nwbc.exe.#XXXX.1.log" in your preferred editor (e.g. Notepad). Then at the end of the trace you can check if "LoginControl.CheckLogonComplete" is one of the last entries and you can't find "LoginControl.LogonSucceeded" afterwards.

We did a fix last week and today we decided to do a quick patch asap as this problems seems to be a showstopper on more and more systems.

Hopefully next week we will deliver NWBC 4.0 PL1 containing this fix.

We apologize for any inconvenience.

Kind Regards,

Thomas

MattHarding
Active Contributor
0 Kudos

Thanks Thomas. Was about to do a workshop and NWBC stopped working for me due to this issue a week ago (after working continously for some time).  Leveraging the info you stated, quickfix for my purpose (and for reference, the issue didn't seem to have the trace information you referred to) was to create a new user on my laptop (I'm running against a local NSP instance), and to use that new user which obviously didn't have any corrupted config information.  When I get time, I'll try remove any user specific application data and see if it continus to wor

Cheers,

Matt

a_vanengen
Explorer
0 Kudos

Hello,

I do have the same problem on many SAP systems, however on some systems the NWBC 4.0 works quite well.

My feeling is that the problem is caused by security settings on the server in combination with updated software/configuration on the client.

Regards

Albert

Former Member
0 Kudos

Hello,

I got the exact same problem, neither of the mentioned sollutions worked for me. This is really strange, as the same thing happend to my colleague as well.

Regards

Sebastian

EDIT...

It worked for me once again after I have messed with the options folder in %appdata% and the certificate options for our domain.... nevertheless now it doesnt work again.

former_member192995
Participant
0 Kudos

Hi Russell Manning,

i have exactly the same problem.

The first login after installing the NWBC works, but now i have the same problem.

Did you solve the problem until now ?

Thanks

Simon

Former Member
0 Kudos

No.  Unfortunately, I have not found a solution.

Former Member
0 Kudos

there are several reasons. maybe one of the reasons is the usage SAPGUI as ActiveX for NWBC.

I have found some explanations.

this link http://help.sap.com/saphelp_nw73ehp1/helpdata/en/4c/5bdad097817511e10000000a42189b/content.htm informs that it's necessary to create suitable NwbcOptions.xml

Trace logs of nwbc informs about issue with SSO-ticket.

"Note 1638715 - NWBC authentication - SSO trouble shooting against ABAP"

I hope it help you.