Error using miabuild.exe with MSBuild & Task Scheduler

danvy · Post by **danvy** » Wed Jun 10, 2009 7:44 am

MichaelNesmith wrote:Why not just let the build tool receive window messages?

This workaround is totally unacceptable : We can't have someone logon after each reboot, and we do not use to have pending sessions on servers.
I'm sure we can expect a new release from a company like Installaware, not a quick an dirty trick

dawidp · Post by **dawidp** » Wed Jun 10, 2009 7:19 pm

I'm having the same problem integrating miabuild 9 with TeamBuild. Here's the code we use.

Code: Select all

<Target Name="AfterCompile">
    <Exec Command='"D:\\Program Files\\InstallAware\\InstallAware 9\\miabuild.exe" "$(SolutionRoot)\\TestApp.mpr" /r /o="$(DropLocation)\\$(BuildNumber)\\Setup"' ContinueOnError="false" />
</Target>

Looks like we're going back to using version 8.

Dawid

Chris Miller · Post by **Chris Miller** » Thu Jun 11, 2009 10:38 am

I use FinalBuilder Server so our developement can remotely start the jobs. The miabuild.exe needs to be runnable from a service account and not require an interactive desktop session.

I'm going tg to hold off on upgrading to version 9 of InstallAware until this is resolved. Leaving a console session running is not an option available for me.

kwco · Post by **kwco** » Thu Jun 11, 2009 12:03 pm

I'm going to hold off on upgrading to version 9 of InstallAware until this is resolved.

You may have to stick with 8 permanently. When I contacted support I was told that this behavior was deliberately added by design.

cjoyce · Post by **cjoyce** » Mon Jun 15, 2009 4:38 pm

This is really disappointing. There is a golden rule in software that you never take away features in an upgrade. This is just impractical for automated builds like ours with CC.NET. Please do your user community a favor and fix this asap! Our builds are crippled by this.

MichaelNesmith · Post by **MichaelNesmith** » Mon Jun 15, 2009 5:36 pm

Could someone please provide concise instructions to reproduce this issue with an easy to install automated build software, so R&D can take a look at this?

AH-NP · Post by **AH-NP** » Tue Jun 16, 2009 4:21 am

Could someone please provide concise instructions to reproduce this issue with an easy to install automated build software, so R&D can take a look at this?

Hi,

Here is our configuration:

We’ve got a windows server 2003.
On this server we have:
- Finalbuilder server 6
- Finalbuilder 6
- Installaware 9.03 Studio

From a web page we connect to finalbuilder server.
This web page got links to launch finalbuilder scripts.

My finalbuilder script calls miabuild.exe to create setups.
There is an option to do this with finalbuilder.

Before we upgrade to IA9, no account were logged on our windows server 2003.

After the upgrade, we’ve had and error on miabuild.exe :
Output from D:\\Program Files\\InstallAware\\InstallAware 9\\miabuild.exe
InstallAware Command Line Build Utility
ERROR: Not implemented

Action Failed
D:\\Program Files\\InstallAware\\InstallAware 9\\miabuild.exe returned : 3

The workaround for this is to :
Turn on the Desktop Interaction option on the FinalBuilder Server 6 Build Service
Stay logged on the server with an administrator account.

Thanks

AH-NP

nb : you can download finalbuilder trial version here :
http://www.finalbuilder.com/download.aspx

MichaelNesmith · Post by **MichaelNesmith** » Tue Jun 16, 2009 9:50 am

R&D is uploading a new build which should resolve this issue.

cjoyce · Post by **cjoyce** » Tue Jun 16, 2009 9:52 am

Here are instruction for reproducing in CC.NET:

1. Download and install Cruise Control .NET:
http://confluence.public.thoughtworks.o ... T/Download

2. Edit ccnet.config in C:\\CruiseControl.NET\\server to look like the following:

<cruisecontrol>
<project name="Test Installer" webURL="http://<server>/ccnet">
<tasks>
<exec>
<executable>miabuild.exe</executable>
<baseDirectory>C:\\Program Files\\InstallAware\\InstallAware 9</baseDirectory>
<buildArgs>"c:\\dev\\Installs\\Test.mpr"</buildArgs>
<successExitCodes>0</successExitCodes>
<buildTimeoutSeconds>3600</buildTimeoutSeconds>
</exec>
</tasks>
<triggers>
<scheduleTrigger time="22:00" />
</triggers>
<publishers>
<merge>
<files>
</files>
</merge>
<xmllogger logDir="log" />
</publishers>
</project>
</cruisecontrol>

3. From the CC.NET tray or http://<server>/ccnet request a build of the project. You'll see the build fails.

4. Go look in your C:\\CruiseControl.NET\\server and you'll see a folder was created for your test project. Look in its Artifacts\\Log folder for an XML log file. You'll see that msibuild.exe returned "ERROR: Not implemented".

MichaelNesmith · Post by **MichaelNesmith** » Tue Jun 16, 2009 9:57 am

Thanks. BTW, for now, no more effort for reproduction is necessary.

R&D is uploading a new build which should resolve this issue.

You will let us know if it still does not work, of course

AH-NP · Post by **AH-NP** » Tue Jun 16, 2009 11:42 am

R&D is uploading a new build which should resolve this issue

Thanks a lot !

Do you now when the upgrade will be available ?

Thanks

AH-NP

MichaelNesmith · Post by **MichaelNesmith** » Tue Jun 16, 2009 8:34 pm

We are hoping by Wednesday this week, pending final testing. Unfortunately a new issue was discovered with our integration process that pushed back the release by one more day

AH-NP · Post by **AH-NP** » Wed Jun 17, 2009 3:40 am

Ok

Can you post here when the release will be available ?

Thanks

AH-NP

Chris Miller · Post by **Chris Miller** » Wed Jun 17, 2009 9:45 am

MichaelNesmith wrote:We are hoping by Wednesday this week, pending final testing. Unfortunately a new issue was discovered with our integration process that pushed back the release by one more day

Thanks for the updated information and thank you for making this change in the functionality with miabuild.exe.

MichaelNesmith · Post by **MichaelNesmith** » Wed Jun 17, 2009 12:06 pm

9.04 is live - please try now!