cancel
Showing results for 
Search instead for 
Did you mean: 

NWBC 5.0 Crashing

shane_kelly2
Participant
0 Kudos
796

Whenever i start NWBC 5.0 it crashes immediately.

I checked the trace files and I get this message:

##########  Log continued from previous file C:\Users\Shane_2\AppData\Local\SAP\NWBC\Traces\NWBC.exe.#2852.0.log  ##########

22:25:53.810 [main] E         Failed to execute SAP NetWeaver Business Client

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

HHHHHH                     Exception                      HHHHHH

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

NotSupportedException: An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See http://go.microsoft.com/fwlink/?LinkId=155569 for more information.

   at System.Reflection.RuntimeAssembly.nLoadFile(String path, Evidence evidence)

   at System.Reflection.Assembly.LoadFile(String path)

   at com.sap.nw.nwbc.starter.implementation.NWBC.StartNwbcCore(IDisposable splash)

   at com.sap.nw.nwbc.starter.implementation.NWBC.Main(String[] args)

I checked this thread () and verified I am running .NET framwork 4.5.1 (Which meets the minimum requirements)

.NET version is 378675 = .NET Framework 4.5.1 installed with Windows 8.1

Any ideas?

Accepted Solutions (1)

Accepted Solutions (1)

former_member183060
Contributor

Dear All,

c# - .net local assembly load failed with CAS policy - Stack Overflow

Here is a possible cause of this issue. Please check on it.

Best regards

Melinda

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Shane,

I have the same error and have opened an OSS on it, but haven't gotten very far on that.

But you can use NWBCcore.exe instead, this works.

former_member195792
Participant
0 Kudos

Hi,I also faced this issue.

I used the workaround that Jakob gave(putting NWBCCore.exe in the shortcut)

After this I openend the NWBC, and closed it again.
I changed the entry in the shortcut "NWBCCore.exe"back to "NWBC.exe"

It now suddenly works.

Hope this helps,

Menno