cancel
Showing results for 
Search instead for 
Did you mean: 

read/write memory popups while using easydms

Former Member
0 Kudos

hi experts!

we actually get more and more windowserrors(in explorer.exe) while working with easydms.

so we decided to use windbg to locate the source of the problems...

cause we dont have the source code of easydms i hope somebody here can help us?

our last errorlog was: (problem occurs while logging in)

(de0.8c): Access violation - code c0000005 (!!! second chance !!!)

eax=035a3730 ebx=00000000 ecx=035a3730 edx=035ccfa0 esi=034585b0 edi=034585b8

eip=00000000 esp=0170b4e0 ebp=0170b50c iopl=0 nv up ei ng nz na pe nc

cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000286

Missing image name, possible paged-out or corrupt data.

Missing image name, possible paged-out or corrupt data.

Missing image name, possible paged-out or corrupt data.

Missing image name, possible paged-out or corrupt data.

Missing image name, possible paged-out or corrupt data.

00000000 ?? ???

0:022> k

ChildEBP RetAddr

WARNING: Frame IP not in any known module. Following frames may be wrong.

0170b4dc 01e61328 0x0

0170b4e4 01e61742 EasyDmsExplorer!ATL::CStringData::Release+0x19

0170b50c 01e65642 EasyDmsExplorer!ATL::CStringT<wchar_t,StrTraitMFC<wchar_t,ATL::ChTraitsCRT<wchar_t> > >::~CStringT<wchar_t,StrTraitMFC<wchar_t,ATL::ChTraitsCRT<wchar_t> > >+0x1d

0170b544 01e73ca3 EasyDmsExplorer!CRfcFunctionInfo::~CRfcFunctionInfo+0xab

0170b774 00700061 EasyDmsExplorer!CRfcCaller::OnLogon+0x956

0170b780 0031005f <Unloaded_hsip.dll>+0x6fffa0

0170b784 00000000 <Unloaded_hsip.dll>+0x30ff9e

any ideas what that can be ?

best regards

harald wiesinger

Edited by: Harald Wiesinger on Feb 2, 2010 2:17 PM

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

hi and thanks for your reply,

we are using EasyDMS SP15 P2.(the problem is that its not only this one kind of error... we get more and more different ones - i will post a new one if a get another debuglog)

what kind of plugin do you mean? if you mean that we are using addin.dll... yes we do.

most people are getting this error while logging in the first time of the day or sometimes after rfccrashes and the user had to stop explorer.exe per tastmanager.

best regards

Harald

Edited by: Harald Wiesinger on Feb 3, 2010 10:47 AM

former_member345274
Participant
0 Kudos

There might be issues here with addin.dll. Is the SAP note 1370364 implemented while makning rfc call in addin.dll? This is required. More over please reset RFC cache and see if your issue is still happening.

we need to reset cache only if

1.Change in function signature related to the functions in EasyDMS or change in the definition of parameters/fields (including nested fields) used in the respective functions.

2.Change in structures/tables used by EasyDMS(including nested/linked structures/tables)

3.Addition/activation/deactivation/renaming of new/alternate function modules/BAdI method implementation w.r.t EasyDMS.

There needs to be an RFC reset only if there is a change in function signatures/structures/tables w.r.t EasyDMS/DMS in the respective system. There is no need to reset the RFC cache if notes ate implemented which involves only an implementation logic change.

Someone has to manually reset the RFC cache. This can be also done centrally by executing EASYDMS_RESET_RFC_CACHE after the changes.

Data that is cached for RFC :Tables and structures and data related to function signatures (parameters/fields (including nested fields) ) associated with EasyDMS. Also the cache stores the list of active functions used by EasyDMS.

Advatages of RFC cache:- Fast execution.

former_member345274
Participant
0 Kudos

Are you using any plugins with easyDMS? If yes, you need to lock RFC calls to avoid this. If not, Reset the Rfc cache to solve the problem.Please let me know if you need more info.

Edited by: Jomerce PJ on Feb 3, 2010 1:36 PM

former_member345274
Participant
0 Kudos

Also which version of easydms are you using? Are you getting this crash on a fresh logon or is it the logon after an rfc time out? Have you configured SSO for easyDMS logon?