Skip to Content
0
May 11, 2017 at 01:42 PM

BExAddin Fehler: Attempted to read or write protected memory.

1088 Views

Dear Community,

Since installation of BEx 7.40 patch 800 and recently version 7.50 I sometimes get this error screen when starting Excel with the BEXAddin enabled:

--------------------------- BExAddin --------------------------- Fehler: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. at Microsoft.VisualBasic.CompilerServices.LateBinding.InternalLateSet(Object o, Type& objType, String name, Object[] args, String[] paramnames, Boolean OptimisticSet, CallType UseCallType) at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateSet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean OptimisticSet, Boolean RValueBase, CallType CallType) at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateSet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments) at com.sap.bi.et.analyzer.addin.BExConnect.SetExcel(Object iExcel) --------------------------- OK ---------------------------

If I start via the BEx Analyzer icon(starts an instance of Excel) then it does not happen, only when starting Excel directly wit the pulgin enabled.

I tried to search similar issues but could not find anything about it.

I think it is something connected to .Net Framewrok right?

Any feedback on this is very welcome!

Reg.,

Niels