The remote procedure call failed. (Exception from HRESULT: 0x800706BE)

[Former Member]

Hi,

I am running a few script logic packages and then all fails with this error:

The remote procedure call failed. (Exception from HRESULT: 0x800706BE)

I am getting the below message in my event viewer.

This happened while I was running a few packages of script logic. I have included the XDIM_MAXMEMBERS in my script logic, but it seems like the COM+ component fails.

Does anyone have an idea what the error below means?

Or what I can do to prevent this from happening?

The system has called a custom component and that component has failed and generated an exception. This indicates a problem with the custom component. Notify the developer of this component that a failure has occurred and provide them with the information below.

Component Prog ID:

Server Application ID: {A3985281-9DD0-4B2B-BD24-254F9D67ECC1}

Server Application Instance ID:

{D5A7AAB9-B051-472D-8121-E0C5158A4ACD}

Server Application Name: Everest Update

The serious nature of this error has caused the process to terminate.

Exception: E06D7363

Address: 0x77E4BEF7

Call Stack:

kernel32!RaiseException + 0x3c

msvcrt!_CxxThrowException + 0x36

MFC42!Ordinal1265 + 0x1b

MFC42!Ordinal823 + 0x34

scrrun!DllRegisterServer + 0x146d

scrrun!DllGetClassObject + 0x22bf

ole32!CoCreateInstance + 0x3b1

ole32!CoCreateInstanceEx + 0x196

ole32!CoCreateInstanceEx + 0x5b

ole32!CoCreateInstanceEx + 0x23

MSVBVM60!__vbaBoolErrVar + 0x29fd

MSVBVM60!__vbaNew + 0x21

K2Logic!DllCanUnloadNow + 0x27993

K2Logic!DllCanUnloadNow + 0x2f153

K2Logic!DllCanUnloadNow + 0x34999

K2Logic!DllCanUnloadNow + 0xa6025

K2Logic!DllCanUnloadNow + 0xa4629

K2Logic!DllCanUnloadNow + 0x4de18

OLEAUT32!DispCallFunc + 0xab

MSVBVM60!__vbaAptOffset + 0x68b

MSVBVM60!BASIC_CLASS_Invoke + 0x65

OLEAUT32!DispGetParam + 0x718

OLEAUT32!DllRegisterServer + 0x5bf

RPCRT4!NdrAsyncServerCall + 0x1e7

RPCRT4!CStdStubBuffer_Invoke + 0x82

OLEAUT32!DispGetParam + 0x5b6

ole32!StgGetIFillLockBytesOnFile + 0x13b27

ole32!StgGetIFillLockBytesOnFile + 0x13ad4

ole32!DcomChannelSetHResult + 0xaab

ole32!DcomChannelSetHResult + 0x495

ole32!CoFreeUnusedLibrariesEx + 0xb06

ole32!StgGetIFillLockBytesOnFile + 0x139e1

ole32!StgGetIFillLockBytesOnFile + 0x13872

ole32!StgGetIFillLockBytesOnFile + 0x12d59

ole32!CoFreeUnusedLibrariesEx + 0x9f5

ole32!CoFreeUnusedLibrariesEx + 0x9c0

USER32!LoadCursorW + 0x4cf5

USER32!LoadCursorW + 0x4e86

USER32!TranslateMessageEx + 0x10d

USER32!DispatchMessageW + 0xf

COMSVCS!DllUnregisterServer + 0x270

COMSVCS!DllUnregisterServer + 0x180

COMSVCS!DllUnregisterServer + 0xc6c

COMSVCS!DllUnregisterServer + 0xf4d

msvcrt!_endthreadex + 0xa3

kernel32!GetModuleHandleA + 0xdf

Regards

Henry

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

[sorin_radulescu]

This error happen in both application servers or just in one?

If happen in both then you have a problem.

If it is happen just in one server then you can take out from NLB for 20 minutes that server.

Make sre that version of k2logic.dll from server working is the same wiht k2logic.dll from second server.

If not then

1. Open Component Services into that server

2. Go to Everest Update and expand Components

3. Delete all components from Everest Update with K2logic

4. Execute into comand line regsvr32 -u C:\PC_MS\Websrvr\bin\K2logic.dll

5. Execute into Comand line regvr32 C:\PC_MS\Websrvr\bin\K2logic.dll

6. Drag and Drop k2logic.dll into Components of EverestUpdate from Component Services

7. You can put back this server into NLB

8. test to see if this solve the problem ...if not then probably you have to reinstall

Reinstall means you will need to sytop for 1 hour the production environment.

I hope this will help you.

Please check also the other answer which I provided to you into other thread.

Kind Regards

Sorin Radulescu

[Former Member]

Hi Sorin,

This seems to be only on the first application server that I get this error. I started to run the package now on the second application server and all is successful and performing a lot faster than on the first app server.

We had issues to get the second application server as part of the loadbalancer, will post the result on the thread I posted for that, but the server is now up and running.

I will try your suggestion with manually registering the K2Logic, if that fails we will schedule some downtime for the other application server for longer period.

Thanks for your help!

[sorin_radulescu]

The error message is saying that actually you have an issue with installation because it seems something is not register correct.

Do you have the same issue running any script logic or just a specific script logic.

This test will provide the information if the problem is related to installation of EverestUpdate component or it is a problem with script logic.

Looking to the error message it seems to be more a problem regarding how EverestUpdate dll was register.

Kind Regards

Sorin Radulescu

[Former Member]

Hi Sorin, Thankyou for your response.

This error happens if I ran multiple script logics at a time, and is not specific to a specific script logic file, and also happens when I run logic from different applications.

If the possible error is in the everest update.dll, is it then necessary for a reinstall? or is there an easier way to correct the file.

We are current in a production environment, and will be difficult to arrange for a reinstall at this stage.

Henry