Installing the ESB Toolkit v2.0 on Windows 7 Error: Operation Not Completed#

Here's an interesting one: I was installing the ESB Toolkit 2.0 on a Win 7 x86 machine the other day, and during install got an error from Visual Studio saying "The operation could not be completed.":

If you choose OK, the ESB Installer finishes with a success message, but then the Itinerary Designer doesn't work in Visual Studio (you get an error about a missing assembly when you try and add a new itinerary to a project).

There was nothing in the event log at all about this.

When I turned on MSI logging, I saw that the devenv.exe process had returned an error, but that the MSI installer was swallowing it, and continuing on.

What's odd is that I've never seen this error during install of the toolkit on Win 2008 R2 which is, in theory, the same kernel.

Note: I'm aware that the ESB Toolkit 2.0 is not officially supported on Windows 7 or 2008 R2, but that's all I have to work with at my client!

The solution is to run the installer from an elevated command prompt i.e. right-click the Command Prompt icon, select Run as Administrator. Then in the elevated command window, navigate to the folder containing your ESB msi file, and type:

msiexec /i "BizTalk ESB Toolkit 2.0-x86.msi"

I suspect the reason for this is that the installer kicks off an instance of devenv.exe to install the Itinerary Designer templates, and the devenv.exe process needs to be elevated to do this (as it updates the registry). So I suspect this is a fault with the MSI package more than anything.

Unsure if anyone else has come across this – it may also be because the Win 7 image I was using was a bit more locked down as it was on a domain and a lot of restrictive Group Policies applied.

Sunday, August 22, 2010 6:22:56 PM (GMT Daylight Time, UTC+01:00) #    Comments [2]  |  Trackback


Monday, August 23, 2010 11:00:15 AM (GMT Daylight Time, UTC+01:00)
Hi Daniel,
A blog post after nearly 2 years!! So you got round the issue for installing, but isnt it quite a risk for the client since its not supported in production ?

Btw, any plans to release the source code for XmlViewer? Pretty nifty utility and I'd like to incorporate that sort of functionality into a community utility. Pl let me know if you are ok with that and how I can get hold of the source code.

Monday, August 23, 2010 1:13:20 PM (GMT Daylight Time, UTC+01:00)
Hi Benjy! Good to hear from you - congrats on the MCS role!
Yes, 2 years is a fairly long while, I got snowed under with becoming a father, moving house, etc, and just fell off the blogging wagon... trying to get back on it now!

re. official support with R2 - I know what you're saying, but I've heard various snippets that official support for 2008 R2 will come out later this year - in any case, this is a greenfield client and we haven't yet configured any servers, so not to late to rollback to 2008 vanilla if we experience issues. The main thing is that we wanted an easy upgrade path to BTS2010 - depending on the release date of BTS2010 we might skip BTS2009. So far we've had no issues running on R2, only on Win7 - Win7 isn't an ideal dev platform, but we wanted to trial it anyway.

Re. source code for XmlViewer: of course. I've been a bit lax in releasing it.
I always wanted to go back an polish/tidy up the code, but I think I should release it as is.
The version I have is one step on, it fixes a small bug related to long file/path names.

I'll release it on here first, then look at throwing it up on CodePlex. I'll dig out the code this week.

I also have a slew of other utility programs I always intended to release.
I'll also have to trade notes with you on BizUnit 4.x as well...! :-)

Comments are closed.
All content © 2020, Daniel Probert
On this page
This site
<July 2020>
Blogroll OPML

Powered by: newtelligence dasBlog 2.3.12105.0

The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

Send mail to the author(s) E-mail

Theme design by Jelle Druyts

Pick a theme: