Re: regsvr32 error code 0x80004002
- From: billyard <dmetcalf@xxxxxxxxxxxxxxx>
- Date: Thu, 06 Dec 2007 22:03:09 -0500
Norman Diamond wrote:
Until yesterday I could use Visual Studio 2005 to build DLLs using ATL.
Usually Visual Studio 2005 would register the DLLs during building
(yeah, there are still reasons to be an administrator while using Visual
Studio). When it failed, I could type a regsrv32 command into a command
prompt.
Today regsvr32 gives error code 0x80004002, Interface Not Supported.
(Actual wording: インターフェースがサポートされていません)
Some MSDN searching and some Google searching yield the following
information.
Windows Update gets broken similarly. Well I didn't try Windows Update
today, I'm trying to register one of my own DLLs that only uses ATL80
and CRT80.
Visual Basic 5 contains a working version of comcat.dll version 4.71.
If I find Visual Basic 5 then I can try overwriting Windows XP SP2's
version of comcat.dll with this old version, and see if that fixes it.
When Microsoft resumes distribution of Visual Basic 5, please let me know.
Windows Server 2003 Volume Shadowing Services gets broken similarly. XP
doesn't have a UI for Volume Shadowing Services, but it has some of the
same DLLs, so I reregistered all of the DLLs that exist. Those worked.
But regsvr32 still refuses to register my DLL.
I also tried reregistering an old copy of my DLL, built two months ago
and properly registered two months ago. The error is the same, 0x80004002.
Does anyone know how to get regsvr32 working again on ATL DLLs?
I've seen this do wonders - try:
msiexec /unreg
msiexec /regserver
.
- Follow-Ups:
- Re: regsvr32 error code 0x80004002
- From: Norman Diamond
- Re: regsvr32 error code 0x80004002
- References:
- regsvr32 error code 0x80004002
- From: Norman Diamond
- regsvr32 error code 0x80004002
- Prev by Date: regsvr32 error code 0x80004002
- Next by Date: Re: Program Crashes On Exit
- Previous by thread: regsvr32 error code 0x80004002
- Next by thread: Re: regsvr32 error code 0x80004002
- Index(es):
Relevant Pages
|