469,924 Members | 1,417 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,924 developers. It's quick & easy.

Visual Studio can't add COM reference.

Using Visual Studio .NET 2003 I've tried to add a COM reference
to a Windows Form project via the Add Reference dialog (specifically
the Active DS Type Library) but always get the error message:

"A reference to 'Active DS Type Library' could not be added. The
type library wrapper tool 'tlbimp' cannot be found on this system.
Please re-install Visual Studio."

This occurs regardless of the actual tlb or dll selected and happens
on Win2000 and XP with various flavors of SP's using Framework 1.1
SP1.

TlbImp.exe exists in the Framework SDK bin directory and can be
executed from the Visual Studio command-line tool with no
qualification.

I've chatted with other developers over the phone and they
add COM references with no problem. While seeking a solution I've
made clean installs of Win2000 and XP, reinstalled Framework from
my prerequistite disk, and reinstalled VS a number of times with
identical results.

On searching these groups I've found a couple others (over the last
couple years) who've had the same problem, but I've never seen a
solution.

MS has a KB article 883608 that discusses a scenario that generates
the same error message, but doesn't seem to apply in my case.

Any help?
Thanks,
--J.
Nov 22 '05 #1
7 10950
Did you try running tlbimp.exe from commandline? Try that out.

- Sahil Malik
You can reach me thru my blog http://www.dotnetjunkies.com/weblog/sahilmalik

"jemmaq99" <jemmaq99@hotmail!.com> wrote in message
news:me********************************@4ax.com...
Using Visual Studio .NET 2003 I've tried to add a COM reference
to a Windows Form project via the Add Reference dialog (specifically
the Active DS Type Library) but always get the error message:

"A reference to 'Active DS Type Library' could not be added. The
type library wrapper tool 'tlbimp' cannot be found on this system.
Please re-install Visual Studio."

This occurs regardless of the actual tlb or dll selected and happens
on Win2000 and XP with various flavors of SP's using Framework 1.1
SP1.

TlbImp.exe exists in the Framework SDK bin directory and can be
executed from the Visual Studio command-line tool with no
qualification.

I've chatted with other developers over the phone and they
add COM references with no problem. While seeking a solution I've
made clean installs of Win2000 and XP, reinstalled Framework from
my prerequistite disk, and reinstalled VS a number of times with
identical results.

On searching these groups I've found a couple others (over the last
couple years) who've had the same problem, but I've never seen a
solution.

MS has a KB article 883608 that discusses a scenario that generates
the same error message, but doesn't seem to apply in my case.

Any help?
Thanks,
--J.

Nov 22 '05 #2
Yes, tlbimp executes fine from the command line. With no additional
environment variable settings and a plain DOS box, you have to
naviagate to the framework SDK bin drectory to execute it, or you
can use the fully-quaified pathname "c:\Program File\Microsoft Visual
Studio .NET 2003\SDK\v1.1\bin\tlbimp.exe"

From the Visual Studio command-line tool (Start->Programs->Microsoft
Visual Studio .NET 20030->Visual Studio .NET tools->Visual Studio .NET
2003 Command Prompt" (which is just a DOS box with vsvars32.bat
already run) it executes with no qualification.

I've also set the path environment variable so that it'll execute with
no qualifiaction, but still Visual Studio itself can't seem to find it
when I try to add a reference.

I've performed clean installations of Win2000 and XP partitoned and
formatted the drive during the installation, gotten all of the updates
at windowsupdates.microsoft.com, installed clean versions of
Visual Studio .NET 2003. Nevertheless, when I try to add a COM
reference to a simple "hello world" Windows Form app, I consistenly
get the same error. The .tlb and the .dll for the target COM component
exist in the c:\Windows\System32 directory.

I'm at a loss for an explanation.

Thanks, though, for your response...
--J.
On Sat, 9 Oct 2004 22:52:12 -0400, "Sahil Malik"
<co*****************@nospam.com> wrote:
Did you try running tlbimp.exe from commandline? Try that out.

- Sahil Malik
You can reach me thru my blog http://www.dotnetjunkies.com/weblog/sahilmalik

"jemmaq99" <jemmaq99@hotmail!.com> wrote in message
news:me********************************@4ax.com.. .
Using Visual Studio .NET 2003 I've tried to add a COM reference
to a Windows Form project via the Add Reference dialog (specifically
the Active DS Type Library) but always get the error message:

"A reference to 'Active DS Type Library' could not be added. The
type library wrapper tool 'tlbimp' cannot be found on this system.
Please re-install Visual Studio."

This occurs regardless of the actual tlb or dll selected and happens
on Win2000 and XP with various flavors of SP's using Framework 1.1
SP1.

TlbImp.exe exists in the Framework SDK bin directory and can be
executed from the Visual Studio command-line tool with no
qualification.

I've chatted with other developers over the phone and they
add COM references with no problem. While seeking a solution I've
made clean installs of Win2000 and XP, reinstalled Framework from
my prerequistite disk, and reinstalled VS a number of times with
identical results.

On searching these groups I've found a couple others (over the last
couple years) who've had the same problem, but I've never seen a
solution.

MS has a KB article 883608 that discusses a scenario that generates
the same error message, but doesn't seem to apply in my case.

Any help?
Thanks,
--J.


Nov 22 '05 #3
Funny .. but atleast you have a workaround ..

- Sahil Malik
You can reach me thru my blog http://www.dotnetjunkies.com/weblog/sahilmalik

"jemmaq99" <jemmaq99@hotmail!.com> wrote in message
news:n9********************************@4ax.com...
Yes, tlbimp executes fine from the command line. With no additional
environment variable settings and a plain DOS box, you have to
naviagate to the framework SDK bin drectory to execute it, or you
can use the fully-quaified pathname "c:\Program File\Microsoft Visual
Studio .NET 2003\SDK\v1.1\bin\tlbimp.exe"

From the Visual Studio command-line tool (Start->Programs->Microsoft
Visual Studio .NET 20030->Visual Studio .NET tools->Visual Studio .NET
2003 Command Prompt" (which is just a DOS box with vsvars32.bat
already run) it executes with no qualification.

I've also set the path environment variable so that it'll execute with
no qualifiaction, but still Visual Studio itself can't seem to find it
when I try to add a reference.

I've performed clean installations of Win2000 and XP partitoned and
formatted the drive during the installation, gotten all of the updates
at windowsupdates.microsoft.com, installed clean versions of
Visual Studio .NET 2003. Nevertheless, when I try to add a COM
reference to a simple "hello world" Windows Form app, I consistenly
get the same error. The .tlb and the .dll for the target COM component
exist in the c:\Windows\System32 directory.

I'm at a loss for an explanation.

Thanks, though, for your response...
--J.
On Sat, 9 Oct 2004 22:52:12 -0400, "Sahil Malik"
<co*****************@nospam.com> wrote:
Did you try running tlbimp.exe from commandline? Try that out.

- Sahil Malik
You can reach me thru my blog
http://www.dotnetjunkies.com/weblog/sahilmalik

"jemmaq99" <jemmaq99@hotmail!.com> wrote in message
news:me********************************@4ax.com. ..
Using Visual Studio .NET 2003 I've tried to add a COM reference
to a Windows Form project via the Add Reference dialog (specifically
the Active DS Type Library) but always get the error message:

"A reference to 'Active DS Type Library' could not be added. The
type library wrapper tool 'tlbimp' cannot be found on this system.
Please re-install Visual Studio."

This occurs regardless of the actual tlb or dll selected and happens
on Win2000 and XP with various flavors of SP's using Framework 1.1
SP1.

TlbImp.exe exists in the Framework SDK bin directory and can be
executed from the Visual Studio command-line tool with no
qualification.

I've chatted with other developers over the phone and they
add COM references with no problem. While seeking a solution I've
made clean installs of Win2000 and XP, reinstalled Framework from
my prerequistite disk, and reinstalled VS a number of times with
identical results.

On searching these groups I've found a couple others (over the last
couple years) who've had the same problem, but I've never seen a
solution.

MS has a KB article 883608 that discusses a scenario that generates
the same error message, but doesn't seem to apply in my case.

Any help?
Thanks,
--J.

Nov 22 '05 #4
Hi

I have exactly the same problem since upgrading to WinXP SP2.
Have you figured out the cause of the problem?
I've been searching desperately for a solution but Microsoft's only knowledge base article doesnt seem relevant. I'm a .net newbie so would welcome some help from anybody on this one.

I can be contacted at jp@oxoboys.com

Thanks
Using Visual Studio .NET 2003 I've tried to add a COM reference
to a Windows Form project via the Add Reference dialog (specifically
the Active DS Type Library) but always get the error message:

"A reference to 'Active DS Type Library' could not be added. The
type library wrapper tool 'tlbimp' cannot be found on this system.
Please re-install Visual Studio."

This occurs regardless of the actual tlb or dll selected and happens
on Win2000 and XP with various flavors of SP's using Framework 1.1
SP1.

TlbImp.exe exists in the Framework SDK bin directory and can be
executed from the Visual Studio command-line tool with no
qualification.

I've chatted with other developers over the phone and they
add COM references with no problem. While seeking a solution I've
made clean installs of Win2000 and XP, reinstalled Framework from
my prerequistite disk, and reinstalled VS a number of times with
identical results.

On searching these groups I've found a couple others (over the last
couple years) who've had the same problem, but I've never seen a
solution.

MS has a KB article 883608 that discusses a scenario that generates
the same error message, but doesn't seem to apply in my case.

Any help?
Thanks,
--J


User submitted from AEWNET (http://www.aewnet.com/)
Nov 22 '05 #5
Here a guess: maybe this is a path problem. Are you using the same account
that the one you have used for installing VS.NET 2003 and have you checked
the available paths in your environment?

S. L.

"Guest" <Guest@aew_nospam.com> wrote in message
news:uG**************@TK2MSFTNGP12.phx.gbl...
Hi

I have exactly the same problem since upgrading to WinXP SP2.
Have you figured out the cause of the problem?
I've been searching desperately for a solution but Microsoft's only
knowledge base article doesnt seem relevant. I'm a .net newbie so would
welcome some help from anybody on this one.

I can be contacted at jp@oxoboys.com

Thanks
Using Visual Studio .NET 2003 I've tried to add a COM reference
to a Windows Form project via the Add Reference dialog (specifically
the Active DS Type Library) but always get the error message:

"A reference to 'Active DS Type Library' could not be added. The
type library wrapper tool 'tlbimp' cannot be found on this system.
Please re-install Visual Studio."

This occurs regardless of the actual tlb or dll selected and happens
on Win2000 and XP with various flavors of SP's using Framework 1.1
SP1.

TlbImp.exe exists in the Framework SDK bin directory and can be
executed from the Visual Studio command-line tool with no
qualification.

I've chatted with other developers over the phone and they
add COM references with no problem. While seeking a solution I've
made clean installs of Win2000 and XP, reinstalled Framework from
my prerequistite disk, and reinstalled VS a number of times with
identical results.

On searching these groups I've found a couple others (over the last
couple years) who've had the same problem, but I've never seen a
solution.

MS has a KB article 883608 that discusses a scenario that generates
the same error message, but doesn't seem to apply in my case.

Any help?
Thanks,
--J.


User submitted from AEWNET (http://www.aewnet.com/)

Nov 22 '05 #6
I was having the exact same problem. I couldn't add COM references through VS, but I could run tlbimp.exe from the command prompt even though VS said that it couldn't find it.

I reformatted, and everything worked again.. until... I installled Office Professional 2003. After that, VS couldn't find tlbimp again. I uninstalled Office, VS finds tlbimp.

I am guessing that one of the components of Office is conflicting with tlbimp inside of the GAC.

If anyone else is having this problem, try uninstalling Office, and share your results.

--Michael F.

User submitted from AEWNET (http://www.aewnet.com/)
Nov 22 '05 #7
jwen
1
take look at http://dallas.sark.com/SarkBlog/cbol...9/29/2156.aspx

It seems that your real problem is permissions. If you created a shortcut on your desktop for VS.NET and the target has a mapped directory path - even if it is a local drive - there will be problems using any of the programs in the \sdk\bin folder.

I was having the same problem when I created a shorcut on my desktop and started using it instead fo using the Visual Studio icon in the Programs menu. For some reason, when the shortcut was created, it created a target value with a drive mapping rather than an explicit c:\ drive.

I altered the shortcut properties target to point to the explicit local drive - not a mapped path. It works as it should. Hope this helps.

J.
Mar 1 '06 #8

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

6 posts views Thread by jemmaq99 | last post: by
5 posts views Thread by Mads Peter Nymand | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.