PDA

View Full Version : Entry Point Not Found during Com Extraction.



NewsArchive
12-05-2001, 01:00 AM
I seem to be getting this error when trying to extract com information on
NT4 box. It works fine on a 2k box. The title on the msg box

Title: No: isdev.exe - Entry Point Not Found
Msg: The procedure entry point CLSIDFromProgIDEx could not be located in the
dynamic link library ole32.dll.

Any help is appreciated.

Thanks, Jeff

NewsArchive
12-05-2001, 01:00 AM
Jeff:

What version of ole32.dll do you have? My NT4 box has version 4.0.

Thanks,
Mike Marino



"Jeff" <jfoege@rsinc.com> wrote in message
news:3c0ea71f$1@news.installshield.com...
> I seem to be getting this error when trying to extract com information on
> NT4 box. It works fine on a 2k box. The title on the msg box
>
> Title: No: isdev.exe - Entry Point Not Found
> Msg: The procedure entry point CLSIDFromProgIDEx could not be located in
the
> dynamic link library ole32.dll.
>
> Any help is appreciated.
>
> Thanks, Jeff
>
>
>

NewsArchive
12-05-2001, 01:00 AM
It's probably not installshield itself, but one of your COM components that
has hardlinked into a function that is not available in NT4. Try using
Dependency Walker (www.dependencywalker.com) to figure out which COM module
is causing the error.

Ted.

"Jeff" <jfoege@rsinc.com> wrote in message
news:3c0ea71f$1@news.installshield.com...
> I seem to be getting this error when trying to extract com information on
> NT4 box. It works fine on a 2k box. The title on the msg box
>
> Title: No: isdev.exe - Entry Point Not Found
> Msg: The procedure entry point CLSIDFromProgIDEx could not be located in
the
> dynamic link library ole32.dll.
>
> Any help is appreciated.
>
> Thanks, Jeff
>
>
>

NewsArchive
12-06-2001, 01:00 AM
I have figured out that one of my developers is using a function ole32 that
is avaiable on 2k but not nt4.

We found the offending files and I get to talk to the developers.

Thanks, Jeff

"Ted" <Ted@t__xx.org> wrote in message
news:3c0ead80$1@news.installshield.com...
> It's probably not installshield itself, but one of your COM components
that
> has hardlinked into a function that is not available in NT4. Try using
> Dependency Walker (www.dependencywalker.com) to figure out which COM
module
> is causing the error.
>
> Ted.
>
> "Jeff" <jfoege@rsinc.com> wrote in message
> news:3c0ea71f$1@news.installshield.com...
> > I seem to be getting this error when trying to extract com information
on
> > NT4 box. It works fine on a 2k box. The title on the msg box
> >
> > Title: No: isdev.exe - Entry Point Not Found
> > Msg: The procedure entry point CLSIDFromProgIDEx could not be located in
> the
> > dynamic link library ole32.dll.
> >
> > Any help is appreciated.
> >
> > Thanks, Jeff
> >
> >
> >
>
>