registration of COM dlls fails in dynamic clearcase views

registration of COM dlls fails in dynamic clearcase views

• Scott Ferrett

  Thanks Alin,

  Sorry that I answear so late, I got a lot of things to do...

  You were right. I found a third-party dll that was cousing the problem.

  He was compiled with VS2003.

  Vasile.

  
  
  

• Peter607

  Vasile,

  "MSVCR72D.dll" - I have no idea which version of VS requires this dll. As far as I remember, VS2003 uses MSVCRT71, and VS2005 definitely uses MSVCR80. To my knowledge, VS2003 supports ATL projects and doesn't need MSVCR72.dll. I don't know what Msvcr72 is. As far as I know VS2003 SP1 (which may or may not use MSVCR72) was not released yet. According with http://msdn.microsoft.com/vstudio/support/servicing/sp1_vs03/default.aspx, it will be released at least 2 days from now, or later. Are you running some beta/pre-release version of VS2003 SP1 on the machine that may have installed this dll and cause other problems In that case I'd talk with VC/VCLibraries guys, and probably uninstall the pre-release software...

  Bernd,

  the error message "This application could not be started, because the application configuration is not correct. You should reinstall the application to solve the problem." means that one of the Side-By-Side dlls specified in the application's manifest cannot be found (most likely something wrong with your .NET Frameworks install or with VC Libraries SxS install). This definitely is not a source control problem. I'd look either on disk for an <application>.config file or use a resource viewer and look in dll's resources for the RT_MANIFEST section and try to identify the dependency that cannot be satisfied by checking with the dlls installed in C:\WINDOWS\WinSxS\ and the policies from C:\WINDOWS\WinSxS\Policies. If you have installed pre-release versions of VS, especially from different VBLs, the application configuration may be messed up. I'd try to reinstall VS2005, and if this doesn't fix the problem I'd take this up with VCLib/.NetFrameworks guys, or call Microsoft Product support.

  Alin

  
  

• Rodney Mathis

  I doubt it's one of the executable coming with VS8 that is dependent on VS2003 dlls. In particular, the command line you quoted it's from cl compiler - cl.exe uses MSVCRT80 (see this with "depends.exe "C:\Program Files\Microsoft Visual Studio 8\VC\bin\cl.exe")

  To me, it seems more plausible that other tool you use during build (possible during a post-build step, or custom build rule), is causing the problem. So, look for detailed error log in build.html or try using msbuild /v:diag from command line, and see which dll registration was invoked by the build just before displaying the error message.

  I don't know what DICALLBACK is, but it is not something that came with VisualStudio. Merrely using the include folder in the command line of CL.exe does not produce that error. If you're sure that registration of dicallback.dll (as a post-build step) is causing the "error PRJ0019: A tool returned an error code from "Performing registration"" you'll need to contact the product support for whoever application distributed dicallback.dll.

  Alin

  
  

• kMatsupy

  Hi Bernd,

  I don't think your error has anything to do with source control integration or VSS.

  The "PRJ0019: A tool returned an error code from "Performing registration" message is likely displayed by the build process when the custom build step used by registration failed.

  There may be many reasons why the registration of the dll fails (no access to registry, dependency dll cannot be found and loaded, etc).

  I suspect the registration is doing "regsvr32.exe Yourdll.dll" which fails for some reason. I'd try running that commadn manually, see what error code you get, then followup from there either with the project forums or with Clearcase support.

  Alin

  
  

• Maluco

  Hello Vasile,

  did you try to allow execute rights for the user group "Others" of the clearcase VOB

  This solved the problem for me...

  Best Regards

  Bernd

  
  

• Liatush

  Hi Bernd,

  If you'll try running regsvr32 on the binary and if it will fail displaying an error code, post it to this forum and we can at least try to translate it into a more user-friendly message (hopefully it will help debugging the issue).

  I would also try depends.exe (http://www.dependencywalker.com/) on the binary that fails registration, perhaps it offers information about possible unsatisfied dependencies.

  Alin

  
  

• libarra

  Alin,

  Sorry, it was just a typing mistake, so instead of "MSVCR72D.dll" please understand "MSVCR71D.dll".

  To complete this information on the machine I have only Visual Studio 2005 Installed, release Version.

  In the solution I have more projects, by example more Com DLLS, convertion for this ones it is working fine, but in the dependencies tree comes some Com EXE that cannot be registered because they are linked with this Visual Studio 2003 dlls. I gave you the command line, there you can see the include from dicallback that it is a COM Dll and it is fine converted/registered.

  I hope this time it is more clear what the problem is.

  Thanks,

  Vasile.

  
  
  

• rahul_sabharwal

  Hello,

  thanks for your answer.

  I know that this problem does not really have something to do with source control integration in VS2005, but I didn't really know in which forum I should post...

  As I aleady mentioned, I works fine on local harddisk and in clearcase snapshot views, but it fails in dynamic clearcase views.

  Well, I think that's a good question for the clearcase support ;)

  Best Regards

  Bernd Ritter

  
  

• ramamoorthi

  Hi Alin,

  I used the depends.exe that comes with VS2005, but it didn't show any missing dependencies. But it shows a warning:

  "At least one module has an unresolved import due to a missing export function in a delay-load dependent module."

  Running regsv32 on the command line doesn't showan error code, but just a MessagBox saying:

  "LoadLibrary("UnmanagedFunctions.dll") failed - This application could not be started, because the application configuration is not correct. You should reinstall the application to solve the problem."

  (I translated the message from german; hope it is correct...)

  One of the clearcase guys here just mentioned that this is a problem of clearcase access rights. In some cases the security settings of clearcase VOBs are not applied correctly and prevent an application from running.

  This bug has already been reported to IBM but there is no fix available yet.

  A workaround is to allow execute rights for the user group "Others" of the clearcase VOB.

  Best Regards

  Bernd Ritter

  
  

• NeonICE

   

   

    Hi Guys,

    I have the same problem but I got luck to use the different computers for Visual Studio 2003 and Visual Studio 2005.

    So On on computer I have 2003 installed and there everything works fine compiling, registering and running the ATL COM Exe component.

    I just copied the project on the second computer where I had Visual Studio 2005 installed.

   I convert the project and after eliminating some errors I got at the end of the compiling the error:

    A tool returned an error code from "Performing registration"].

    So the next step was to register the component manually and I got the reason for the error:

    This application has failed to start because MSVCR72D.dll was not found.Reinstalling the application may fix this problem.

    I was shocked because I was not expecting that the Visual studio 8(2005) needs the Visual C runtime dlls from the Version 7(2003 Studio).

    So the question is why this happended

    Something wrong in the conversion, or just the new studio 2005 doesn't support ATL projects any more 

    Bernd please checked on your machine to see if in your case this MSVCR72D.dll it is used too.

    To be able to see all the options that i use in my project i give you here the complete command line:

    /Od /I "../../common/aoolebase" /I "../../common/DICALLBACK" /I "../common" /I "../../common" /I "../.." /I ".." /I "../../lib-3rdParty\SQL2K\Include" /D "WIN32" /D "_WINDOWS" /D "_DEBUG" /D "DBNTWIN32" /D "_VC80_UPGRADE=0x0710" /D "_ATL_DLL" /D "_MBCS" /Gm /EHsc /RTC1 /MDd /Yu"stdafx.h" /Fp"Debug\BMBUOleRessource.pch" /Fo"Debug\\" /Fd"Debug\vc80.pdb" /W4 /nologo /c /Wp64 /ZI /TP /errorReport:prompt

    Thanks and I wait your answear.

     Vasile,

     Dipl, Computer-Science.

   

   

  
  
  
• registration of COM dlls fails in dynamic clearcase views