They way you read these, is whatever is at the top is the culprit. I would
recommend contacting both vendors to see if they have an update that
resolves the issues.
Pat
"Roberto Ortolano" <ortorob.DeleteThis@ch.alicom.com> wrote in message
news:aeb49246.0309030829.339f37e5@posting.google.com...
> Hello
>
> a few days ago I installed all the available patches from MS to my
> IIS4 (NT4 server).
>
> Yesterday and today I got the following errors:
>
> - YESTERDAY:
>
> An object call caused an exception. (IID:
> {51372AEF-CAE7-11CF-BE81-00AA00A2FA25}) (Method: 3) (Microsoft
> Transaction Server Internals Information: File:
> i:\viper\src\runtime\mtxex\activity.cpp, Line: 889) (Exception:
> C0000005) (Address: 0x146c14e5)
> safileup + 0x914E5
> safileup + 0x1D251
> OLEAUT32!DispCallFunc + 0x15D
> OLEAUT32!ClearCustData + 0x588
> safileup!DllUnregisterServer + 0x5FBF
> safileup!DllUnregisterServer + 0x5F61
> vbscript + 0x1869D
>
>
> TODAY:
>
> An object call caused an exception. (IID:
> {51372AEF-CAE7-11CF-BE81-00AA00A2FA25}) (Method: 3) (Microsoft
> Transaction Server Internals Information: File:
> i:\viper\src\runtime\mtxex\activity.cpp, Line: 889) (Exception:
> C0000005) (Address: 0x10a50f56)
> FdfTk + 0x20F56
> FdfTk!FDFSave + 0xCC
> fdfacx + 0x3F73
> OLEAUT32!DispCallFunc + 0xB6
> OLEAUT32!VarBstrFromDec + 0x72CD
> fdfacx + 0x39EB
> vbscript + 0x3715
>
>
> The first one show the safileup dll (software artisans file upload),
> the second one the PDF dll from Adobe.
>
> At the end of both you see vbscript... should I upgrade or change
> vbscript? what can the problem be?
>
> Thanks<!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: An object call caused an exception.