solution to unresolved external symbol _com_issue_error _bstr_t::_bstr_t
LNK2019: unresolved external symbol “void __stdcall _com_issue_error(long)” (?_com_issue_error@@YGXJ@Z) referenced in function “public: __thiscall _bstr_t::_bstr_t(unsigned short const *)” (??0_bstr_t@@QAE@PBG@Z)
I despise this error. Every time I write a new ATL or WTL app, and don’t use COM much in it, I get this.
I then plow for 10 minutes throuh newsgroups to get it figured.
So, hopefully Google will pick this text up and make the solution shorter for other people.
SOLUTION: #include <comdef.h>
Ben says that If #include comdef.h does not fix the unresolved externals, then make sure you are also linking against comsupp.lib
Ben says that If #include comdef.h does not fix the unresolved externals, then make sure you are also linking against comsupp.lib
I'm Ohad Eder-Pressman, a San-Francisco based Founder & Software-Hacker. Currently I am the CEO of
Hi!
Tnx. It really helped
BTW. It happens also with _variant_t
Definately helpful. Thanks.
WOW.. man it really worked!!! Three times cheers to you buddy ..
Thanks. quick and to the point.
Thanks
Really thanks !!! That was an amazing help
Thanks!
Exactly what I needed to know.
Thankyou!
Thanks, this helped loads.
EXCELLENT, thanks for the help!
(PS. You might want to turn on comment reviews to avoid the spam.
)
Cool Beans! Thanks!
Ohad, thank you for this! It is indeed the first Google hit. Please update it as follows: If #include comdef.h does not fix the unresolved externals, then make sure you are also linking against comsupp.lib. That fixed it for me.
Haha! Thanks a lot!
I got 15 of those when I now recompiled my project after a lot of changes. Found you via Google!
At risk of repeating everyone else – thanks a lot – the evil compiler error is dead – hurrah!
Thanks man, its really helpful
i was searching for a long time for the conversion..
Cheers,
Rabindra
adding comsupp.lib worked for me w/o adding #include comdef.h
THANKS !
Google did indeed take me right to this answer. Thanks!
Google did its job!
Thans a lot!
Thank you very much!
Even now, 2 years after its original date – this post continues to help lost souls on the Internet. Thanks!
Thank you! Thank you! Thank you!!!
Thank you! You saved the day
many many thanks!!
you + google = problem solved!!
Many thanks
Thank you. It really helped
)
Thank you! Very needed solution!
Great thanks!!!
Thanks a bunch….Really really appriciate. It make my day and saved my hair!!!!!
Thanks a lot!!!
It really helped! Thanks!
Thnk you very much. It really help a lot. Exact and short, makes it much more valuable. Have a nice day
Thanks a lot
Proved to be really helpful. Especially when you are distressed and see nothing bright in front of you….this useful tip has shown me life.
Thanks a lot my dear friend.
thanks!
Yesss! Thank you very much for saving my time!
It didn’t solve it for me. But I did figure it out.
I had to add this to my sources file.
USE_VCCOM=1
Thanks a ton!
Dude, you are awesome!
Hi. I want to use _bstr_t and I have #include and I added comsupp.lib to the library list and I still get this error.
The build is driven by a vcproj so we don’t use “sources” files. The moment I invoke _bstr_t this error results. Is there any solution?
Hi That’s #include comdef above, somehow the posting omitted the string comdef, maybe due to the greater than/less than characters.
Thanx
when i include
an error occur it is ‘internal compiler error’
Thanks, dude, it is great concise post.
thanks! it helps a lot, IT is the solution to the problem that we had in our work with compiling a specific dll file. (we are NOT programmers)
You saved me. Thanks!