Old format or invaild type library

[Jonas Back]

We have an application built by a company for us and it
has worked fine on WinNT. But when we install it on a
WinXP you have to be a member Privileged Users or Local
Administrators group to get the program to work. If
you're not, you get the follwing errormessage when
starting it (telelist.exe is the application file):
"Exception EOleSysError in module Telelist.exe at
000051CB9. Old format or incalid type library"

The company who built the program for us doesn't know why
so I'm asking if someone else have similiar problems with
other application?

Also, when you install this application you have to
install something called OLE 5.1 - Desktop Toolkit
Interface. I don't know what this is but it might help
solving this strange behaviour.

 

[Malke]

We have an application built by a company for us and it
has worked fine on WinNT. But when we install it on a
WinXP you have to be a member Privileged Users or Local
Administrators group to get the program to work. If
you're not, you get the follwing errormessage when
starting it (telelist.exe is the application file):
"Exception EOleSysError in module Telelist.exe at
000051CB9. Old format or incalid type library"

The company who built the program for us doesn't know why
so I'm asking if someone else have similiar problems with
other application?

Also, when you install this application you have to
install something called OLE 5.1 - Desktop Toolkit
Interface. I don't know what this is but it might help
solving this strange behaviour.

I'd certainly be uncomfortable using software written by people who
don't know why their program doesn't work with permissions. It probably
accesses areas of the system that a limited account user isn't able to
use. You can try using "RunAS", change registry entry permissions, or
give users Administrative privileges (really a bad idea). Or just find
some software that is better written. Or keep NT 4.0.

Malke

 

[Steven Liu]

Hi Jonas,

I have said that the problem is caused by the application incompatible
issue. You need to consult the application vender. They can check for the
source code to determine why the application need certain permission to
run.

Or, you can set the Run As to run the application as another account which
has enough permission.

Thanks for using Microsoft News Group!

Sincerely,

Steven Liu

Microsoft Online Partner Support

MCSE 2000

Get Secure! - www.microsoft.com/security

This posting is provided "as is" with no warranties and confers no rights.

 

[Jonas Back]

I know. I'm mad at the company who refuses to help us.
They can, but since the application was delivered and
made for WinNT, they want more $$$ to do the changes to
make it work properly under WinXP. The reason why I
posted the question was because to see if anyone had any
other idea like upgrading OLE Desktop Toolkit Interface
which I have no idea what it is.

// Jonas

 

[Jonas Back]

Hi Steven,

Sorry for posting the question twice. I was uncertain if
I had posted it or not so I dead a search on my "Sender's
Name" but didn't find anything so I posted the question.
However, I later realised that I by mistake hadn't
written any Sender's Name when posting the question a few
days earlier.

Sorry about that. And thanks for all the help you guys
give us here at the newsgroups!!

// Jonas Back, Sweden

 

[Steven Liu]

Hi Jonas,

I still think it's the application compatible issue. Only modify the source
code can solve the issue.

It's not the operation system problem. Sorry about this.

Thanks for using Microsoft News Group!

Sincerely,

Steven Liu

Microsoft Online Partner Support

MCSE 2000

Get Secure! - www.microsoft.com/security

This posting is provided "as is" with no warranties and confers no rights.