cancel
Showing results for 
Search instead for 
Did you mean: 

NWBC v3.0 installed, but "nothing happens" upon executing desktop shortcut

Former Member
0 Kudos

I have a problem with v3.0 of NWBC that I have recently installed. Upon double clicking on the desktop shortcut icon, the initial NWBC 3.0 splash screen is displayed, but then nothing else happens. I am not presented with any screen where I am able to select a backend system to connect to. Task Manager shows the service "sapstartsrv.exe" still running (I'm assuming that this is linked to NWBC), but no other evidence can be seen that NWBC is actually running.

I would like to add that NWBC v1.0 works perfectly well on the same PC, and connects successfully to backend SAP systems.

Some additional information.

- I have just installed SAPlogon 7.20 + restarted (as the previous version 7.10 patch level 14 did not meet the required level of 7.1 level 15)

- I am running XP SP3. Windows hotfix 919477 is not required, as it is already present as part of one of the XP SPs.

- I have reverted from Google Chrome as my default browser back to IE (+ restarted), to see if this made any difference, but still no luck.

Many thanks in advance to anyone who can shed any light on this issue, given the "scraps" of information provided above.

Alistair Crawshaw

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi Ali,

I am also facing the same issue. After installing NWBC 3.0 when I try to run it, it just display the SAP splash screen and then get closed automatically and I am not getting any screen to select the backend system to connect.

I saw your reply:

+Please ignore my question above. The problem was due to the fact that the backend ECC system that we were connecting to did not have the relevant EHP + Support Pack Level. After updating these, the connection was successful.+

But how did you get the screen to add backend system to which you want to connect?

Regards,

Vikram

Former Member
0 Kudos

Please ignore my question above. The problem was due to the fact that the backend ECC system that we were connecting to did not have the relevant EHP + Support Pack Level. After updating these, the connection was successful.

Ali

Former Member
0 Kudos

Thanks for the feedback Cesar.

Unfortunately, I already have the following .NET versions installed:

version 1.0

version 2.0 SP2

version 3.0 SP2

version 3.5 SP1

Alistair

Former Member
0 Kudos

Hi Ali,

Aditional to the requeriments that you coment are cover, check if you have installed Microsoft .Net Runtime 3.0 or higher that is mandatory.

I hope this be usefull.

Kindest regards.

Cesar M. Hurtado