topic Re: Beta 10: Build Solution fails in ArcObjects SDK Questions

Build Solution fails

JochenManegold — Tue, 17 Nov 2009 14:52:04 GMT

I have a installation of ArcGIS Desktop 9.4 and the ArcObjects SDK on a Windows Server 2008 R2 (64 bit). I generated in Visual Studio 2008 a Desktop Class Library from the ESRI Templates and generated a Command based on BaseCommand. If I compile the solution (for the x86 platform), an error occures:
"The command "esriRegasm.exe "C:\Data\jm\JMLib1\JMLib1\bin\x86\Debug\JMLib1.dll" /v 9.4 /p Desktop /s" exited with code -1."
If I run the esriRegasm from the CommandLine - or using the context menu in the explorer - esriRegasm fails with: "Registration failed. Could not write to disk". My account is in the Administrator Group.

run Visual Studio as administrator

JochenManegold — Thu, 19 Nov 2009 08:58:43 GMT

start Visual Studio 2008 with the command "run as administrator" - then it works fine

Re: Beta 10: Build Solution fails

JohnFell — Thu, 23 Sep 2010 19:09:56 GMT

I tried running the application as an Administrator but I still get this error as well. Has this happened to anyone else?

Re: Beta 10: Build Solution fails

EagerIp — Sat, 25 Sep 2010 00:52:44 GMT

Check to see if you have the right permission to write to \Program Files\Common Files\ArcGIS\Desktop10.0\Configuration\CATID. Use "Program Files (x86)" if it is a 64-bit OS.

Re: Beta 10: Build Solution fails

JohnFell — Mon, 27 Sep 2010 17:30:00 GMT

The permissions are at full control for my login. The properties dialog for this folder states that it is "Read Only (Only applies to files in folder)". See attached screenshot. Still getting error in VS2010.

Re: Beta 10: Build Solution fails

JohnFell — Mon, 27 Sep 2010 17:50:54 GMT

Here is the output when I execute esriRegasm.exe from the command line while adding the '/e' flag.

**********************************

ESRIRegAsm::Register
Command line: "I:\FELLJ\FellJGIS\Projects\Development\dotNETProjects\NewFindTo
ol\NewFindAcctTool\NewFindAcctTool\bin\Debug\NewFindAcctTool.dll" /e /p:Desktop
/s

Registry Capture On.
Registering managed library...
Managed Exception: Could not load file or assembly 'file:///i:\FELLJ\FellJGIS\
Projects\development\dotnetprojects\newfindtool\newfindaccttool\newfindaccttool\
bin\Debug\newfindaccttool.dll' or one of its dependencies. Operation is not supp
orted. (Exception from HRESULT: 0x80131515)
Registry Capture Off.

Operation Failed
0032C1E8

**********************************

Press Enter to continue...

Re: Beta 10: Build Solution fails

EagerIp — Mon, 27 Sep 2010 23:10:47 GMT

Hi fellj,

I see now that your error is different than the original post.

See if you can try to debug it with the troubleshooting suggestion posted on 2/2/2010 in the following thread http://forums.arcgis.com/threads/1162-Beta-10-Issue-with-ESRIRegAsm?p=4267#post4267.

The goal is to attach esriRegasm.exe to step into your code and see if it throws any useful information during debugging.

Re: Beta 10: Build Solution fails

JohnFell — Tue, 28 Sep 2010 11:53:39 GMT

I've made the suggested change to the esriRegasm.exe.config file but nothing has changed. I still get the following error when I try to Clean, Build, or Debug the solution.

The command "esriRegasm.exe "NewFindAcctTool.dll" /p:Desktop /s" exited with code -1.

See attached esriRegasm.exe.config file snapshot.

Re: Beta 10: Build Solution fails

RichardWatson — Tue, 28 Sep 2010 15:08:40 GMT

It looks like your assembly/DLL is failing to load.

You can debug this using the Microsoft Fusion Log Viewer utility, i.e. fuslogvw. Run the utility from the Visual Studio Command Prompt. Make sure to set a Custom Log Location and set it to a directory which exists. What you want to see is binds that fail. The way that assemblies are located in .NET is complex:(

If this is too much, then try to use the free Reflector utility from Red-Gate. What you want to do is to expand the dependencies in order to find those that have load issues. In the unmanaged world this was done using the Depends utility.

Re: Beta 10: Build Solution fails

JohnFell — Tue, 28 Sep 2010 15:28:58 GMT

I've followed the suggestion to use the "fuslogvw" utility using the Microsoft Visual Studios 2010 command prompt. As I made an attempt to build the solution the following information was written to the log:

*** Assembly Binder Log Entry (9/28/2010 @ 11:22:46 AM) ***

The operation failed.
Bind result: hr = 0x80070002. The system cannot find the file specified.

Assembly manager loaded from: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Running under executable C:\Program Files\Common Files\ArcGIS\bin\ESRIRegAsm.exe
--- A detailed error log follows.

=== Pre-bind state information ===
LOG: User = DCAD\FellJ
LOG: DisplayName = msvcm90, Version=9.0.30729.4974, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
(Fully-specified)
LOG: Appbase = file:///C:/Program Files/Common Files/ArcGIS/bin/
LOG: Initial PrivatePath = NULL
LOG: Dynamic Base = NULL
LOG: Cache Base = NULL
LOG: AppName = ESRIRegAsm.exe
Calling assembly : (Unknown).
===
LOG: This bind starts in default load context.
LOG: Using application configuration file: C:\Program Files\Common Files\ArcGIS\bin\ESRIRegAsm.exe.Config
LOG: Using host configuration file:
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v4.0.30319\config\machine.config.
LOG: Post-policy reference: msvcm90, Version=9.0.30729.4974, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
LOG: GAC Lookup was unsuccessful.
LOG: Attempting download of new URL file:///C:/Program Files/Common Files/ArcGIS/bin/msvcm90.DLL.
LOG: Attempting download of new URL file:///C:/Program Files/Common Files/ArcGIS/bin/msvcm90/msvcm90.DLL.
LOG: Attempting download of new URL file:///C:/Program Files/Common Files/ArcGIS/bin/msvcm90.EXE.
LOG: Attempting download of new URL file:///C:/Program Files/Common Files/ArcGIS/bin/msvcm90/msvcm90.EXE.
LOG: All probing URLs attempted and failed.

With my limited experience in developing .NET applications I cannot interpret these results. What does this tell us?

Thanks for your help.

Re: Beta 10: Build Solution fails

EagerIp — Sat, 11 Dec 2021 17:33:09 GMT

The link I posted troubleshoots two slightly different problems. The one I'd like you to try is to attach esriRegasm.exe to debug through your project using Visual Studio.

OK. The /e option doesn't give a lot of information. Can you try to debug if the error stems from any of the ComRegisterFunction() inside the failed assembly? You can do so by setting esriRegasm.exe as the debugging external program in Visual Studio. (And it is better if you remove or comment out the BeforeClean/AfterBuild xml from the project file before debugging.)

Under Start Action
------------------
Start external program:
C:\Program Files\Common Files\ArcGIS\bin\ESRIRegAsm.exe

or on a 64 bit OS
C:\Program Files (x86)\Common Files\ArcGIS\bin\ESRIRegAsm.exe

Under Start Options
-------------------
Command line arguments:
"NewFindAcctTool.dll" /p:Desktop /e

Working directory:
{directory of the NewFindAcctTool.dll}

Tips on commenting out BeforeBuild/AfterBuild

Right-click the project in Solution Explorer and choose Unload Project.

After project is unloaded, right-click it again and choose "Edit NewFindAcctTool.xxproj"

The project file will be displayed in raw text format. Locate the following xml section near the bottom of the project file and comment it out (i.e. wrap them between ). Save changes and reload to start debugging.

<Target Name="BeforeClean">
  <Exec
    WorkingDirectory="$(CommonProgramFiles)\ArcGIS\bin"
    Command="esriRegasm.exe &quot;$(TargetPath)&quot; /p:Desktop /u /s"
    Condition="Exists('$(TargetPath)')"/>
</Target>
<Target Name="AfterBuild">
  <Exec
    WorkingDirectory="$(CommonProgramFiles)\ArcGIS\bin"
    Command="esriRegasm.exe &quot;$(TargetPath)&quot; /p:Desktop /s"/>
</Target>

Re: Beta 10: Build Solution fails

JohnFell — Tue, 28 Sep 2010 18:15:06 GMT

I attempted the suggested debugging procedures and got the following result:

**********************************

ESRIRegAsm::Register
Command line: "NewFindAcctTool.dll" /p:Desktop /e

Registry Capture On.
Registering managed library...
Managed Exception: Could not load file or assembly 'file:///I:\FELLJ\FellJGIS\
Projects\Development\dotNETProjects\NewFindTool\NewFindAcctTool\NewFindAcctTool\
bin\Debug\newfindaccttool.dll' or one of its dependencies. Operation is not supp
orted. (Exception from HRESULT: 0x80131515)
Registry Capture Off.

Operation Failed
003B6388

**********************************

Press Enter to continue...

Thank you for your ideas on this issue. Hopefully we can get it figured out. I am using source control using Team Foundation Server. Not sure if that makes a difference.

Re: Beta 10: Build Solution fails

RichardWatson — Tue, 28 Sep 2010 20:36:42 GMT

I see the same fuslogvw message that you do yet EsriRegAsm works for me.

My only other suggestion is as follows:
1) Open Project in Visual Studio and specify the file EsriRegAsm.exe
2) Specify the command line arguments that you need in the project properties
3) In the Debug/Exceptions menu break when any CLR exceptions are thrown

Run it. Hopefully, you will see the problem. I am thinking that it might be related to the registration logic you have in the underlying assembly? If that does not help then I am out of ideas.

Re: Beta 10: Build Solution fails

JohnFell — Wed, 29 Sep 2010 19:12:37 GMT

The build is now working properly. I had the project on a mapped network drive. Once I copied the solution and it's folder to my local machine (C:\Microsoft Visual Studios 2010\Projects) it built fine. Thanks to all for your efforts.

Re: Beta 10: Build Solution fails

MikeDavies — Thu, 17 Feb 2011 13:48:56 GMT

I know it's a long time ago, but here's a fix to allow us to used share drives:

Edit C:\Program Files (x86)\Common Files\ArcGIS\bin\ESRIRegAsm.exe.config

and add

<loadFromRemoteSources enabled="true" />

before
</runtime>

Mike.