Upgraded to 1.4.4 and now build fails

10 views
Skip to first unread message

Dustin Norman

unread,
Jun 1, 2009, 4:29:19 PM6/1/09
to ccnet-user
I upgraded this morning to 1.4.4 from 1.4.3 and now my builds are
failing with the following error:

MSBUILD : error MSB1021: Cannot create an instance of the logger.
Could not load file or assembly 'C:\\Documents and Settings\\build\
\Local Settings\\Application Data\\assembly\\dl3\\L4LPPRCO.WLA\
\A45BEZVR.NAV\\0f2e8763\\bcf52c7d_28e2c901\
\ThoughtWorks.CruiseControl.MsBuild.dll' or one of its dependencies.
The given assembly name or codebase was invalid. (Exception from
HRESULT: 0x80131047)
Switch: C:\Documents and Settings\build\Local Settings\Application Data
\assembly\dl3\L4LPPRCO.WLA\A45BEZVR.NAV
\0f2e8763\bcf52c7d_28e2c901\ThoughtWorks.CruiseControl.MsBuild.dll;D:
\Builds\Classic\Logs\Ontake\msbuild-results.xml

I have ThoughtWorks.CruiseControl.msBuild.dll in my CruiseControl.NET
\server directory but it definitely is not at the path listed in the
error message. What do I have to do to fix this?

Thanks,
Dustin

Craig Sutherland

unread,
Jun 1, 2009, 4:35:13 PM6/1/09
to ccnet-user
Can you send us your ccnet.config that is using this? Or at least the
relevant part of the config.


Craig

Dustin Norman

unread,
Jun 1, 2009, 4:40:22 PM6/1/09
to ccnet-user
Here are the tasks for the build:

<tasks>
<msbuild>
<executable>$(msbuildPath)</executable>
<workingDirectory>$(classicOntakeBuildPath)</workingDirectory>
<projectFile>SetupBuild.proj</projectFile>
<targets>Build</targets>
<buildArgs>/nologo /noconsolelogger /p:SvnPath=&quot;$(svnPath)
&quot;;SvnCertsReposUrl=$(svnCertsOntakeReposUrl)</buildArgs>
<timeout>600</timeout>
<description>Preparing build environment</description>
</msbuild>
<msbuild>
<executable>$(msbuildPath)</executable>
<workingDirectory>$(classicOntakeBuildPath)</workingDirectory>
<projectFile>BuildAll.proj</projectFile>
<targets>Build</targets>
<buildArgs>/nologo /noconsolelogger /p:DBDocumentorPath=&quot;$
(dbDocumentorPath)&quot;;LatestAAMKitPath=&quot;$
(latestAAMOntakeKitPath)
&quot;;KitProjectName=Ontake;PreReleaseBuild=False</buildArgs>
<timeout>7200</timeout>
<description>Building agent, server and media</description>
</msbuild>
<msbuild>
<executable>$(msbuildPath)</executable>
<workingDirectory>$(classicOntakeBuildPath)</workingDirectory>
<projectFile>PostBuild.proj</projectFile>
<targets>Build</targets>
<buildArgs>/nologo /noconsolelogger /
p:BVTProjectName=&quot;Ontake&quot;</buildArgs>
<timeout>600</timeout>
<description>Performing post-build operations</description>
</msbuild>
<msbuild>
<executable>$(msbuildPath)</executable>
<workingDirectory>$(classicOntakeBuildPath)</workingDirectory>
<projectFile>TearDownBuild.proj</projectFile>
<targets>Build</targets>
<buildArgs>/nologo /noconsolelogger /p:SvnPath=&quot;$(svnPath)
&quot;</buildArgs>
<timeout>600</timeout>
<description>Tearing down build environment</description>
</msbuild>
</tasks>

The weird part is that it looks like the last task is actually
executing. Here is the log output:

<msbuild startTime="05/29/2009 17:12:54" elapsedTime="00:00:15"
success="true">
<project name="Build" file="D:\Builds\Classic\BuildSource\Ontake
\Source\Build\TearDownBuild.proj" success="true">
<target name="Build" success="true">
<message level="high"><![CDATA[Restoring certs directory from
buildparts repository]]></message>
<message level="high"><![CDATA[rename D:\Builds\Classic
\BuildSource\Ontake\Source\BuildParts\certs certs_secure]]></message>
<message level="high"><![CDATA[rename D:\Builds\Classic
\BuildSource\Ontake\Source\BuildParts\certs_back certs]]></message>
<message level="high"><![CDATA["C:\Program Files\CollabNet
Subversion\svn.exe" commit ..\ --message "Updated build numbers, etc."
--non-interactive --no-auth-cache]]></message>
<message level="high"><![CDATA[Sending Source\Agent
\FbMonitor\Properties\AssemblyInfo.cs]]></message>
<message level="high"><![CDATA[Sending Source\Agent
\Include\buildver.h]]></message>
<message level="high"><![CDATA[Sending Source\Agent
\Receiver\EdgeSightEPAgent.xml]]></message>
<message level="high"><![CDATA[Sending Source\Agent
\Receiver\EdgeSightEPAgentx64.xml]]></message>
<message level="high"><![CDATA[Sending Source\Common
\include\common_buildver.h]]></message>
<message level="high"><![CDATA[Sending Source\Server
\Citrix.SystemMonitoring.EdgeSight\Common\CoreAssemblyInfo.cs]]></
message>
<message level="high"><![CDATA[Sending Source\Server
\Include\buildver.h]]></message>
<message level="high"><![CDATA[Sending Source\Server
\Install\WixSource\pages.wxs]]></message>
<message level="high"><![CDATA[Sending Source\Server\SQL
\Schema\full_schema.sql]]></message>
<message level="high"><![CDATA[Transmitting file data .........]]
></message>
<message level="high"><![CDATA[Committed revision 978.]]></
message>
<message level="high"><![CDATA[Unmapping W:]]></message>
<message level="high"><![CDATA[subst W: /D]]></message>
<message level="high"><![CDATA[Unmapping X:]]></message>
<message level="high"><![CDATA[subst X: /D]]></message>
</target>
</project>
</msbuild>MSBUILD : error MSB1021: Cannot create an instance of the
logger. Could not load file or assembly 'C:\\Documents and Settings\
\build\\Local Settings\\Application Data\\assembly\\dl3\\L4LPPRCO.WLA\
\A45BEZVR.NAV\\0f2e8763\\bcf52c7d_28e2c901\
\ThoughtWorks.CruiseControl.MsBuild.dll' or one of its dependencies.
The given assembly name or codebase was invalid. (Exception from
HRESULT: 0x80131047)
Switch: C:\Documents and Settings\build\Local Settings\Application Data
\assembly\dl3\L4LPPRCO.WLA\A45BEZVR.NAV
\0f2e8763\bcf52c7d_28e2c901\ThoughtWorks.CruiseControl.MsBuild.dll;D:
\Builds\Classic\Logs\Ontake\msbuild-results.xml

But it doesn't look like any of the other tasks ran. Very, very
weird.

Thanks,
Dustin
> > Dustin- Hide quoted text -
>
> - Show quoted text -

Craig & Sammi Sutherland

unread,
Jun 1, 2009, 4:51:11 PM6/1/09
to ccnet...@googlegroups.com
Hi Dustin,

I think you've found a bug in CC.NET. We do have one thing that you can try
as a work-around. Can you try adding a logger element to the msbuild tasks,
like follows:


<msbuild>
<executable>$(msbuildPath)</executable>
<workingDirectory>$(classicOntakeBuildPath)</workingDirectory>
<projectFile>SetupBuild.proj</projectFile>
<targets>Build</targets>
<buildArgs>/nologo /noconsolelogger /p:SvnPath=&quot;$(svnPath)
&quot;;SvnCertsReposUrl=$(svnCertsOntakeReposUrl)</buildArgs>
<timeout>600</timeout>
<description>Preparing build environment</description>

<logger>C:\Program
Files\CruiseControl.NET\Server\ThoughtWorks.CruiseControl.MsBuild.dll</logge
r>
</msbuild>

You'll need to make sure the directory is the directory you installed CC.NET
to.

I'll also raise this as an issue so it gets fixed.


Craig

Dustin Norman

unread,
Jun 1, 2009, 5:04:22 PM6/1/09
to ccnet-user
I've temporarily rolled back to 1.4.3 as I've got an important build
coming up. Once it's done I'll give 1.4.4 a try again with your
workaround.

Thanks,
Dustin

On Jun 1, 4:51 pm, "Craig & Sammi Sutherland"
<cj.sutherl...@xtra.co.nz> wrote:
> Hi Dustin,
>
> I think you've found a bug in CC.NET. We do have one thing that you can try
> as a work-around. Can you try adding a logger element to the msbuild tasks,
> like follows:
>       <msbuild>
>         <executable>$(msbuildPath)</executable>
>         <workingDirectory>$(classicOntakeBuildPath)</workingDirectory>
>         <projectFile>SetupBuild.proj</projectFile>
>         <targets>Build</targets>
>         <buildArgs>/nologo /noconsolelogger /p:SvnPath=&quot;$(svnPath)
> &quot;;SvnCertsReposUrl=$(svnCertsOntakeReposUrl)</buildArgs>
>         <timeout>600</timeout>
>         <description>Preparing build environment</description>
>         <logger>C:\Program
> Files\CruiseControl.NET\Server\ThoughtWorks.CruiseControl.MsBuild.dll</logg­e
> > - Show quoted text -- Hide quoted text -

awesthusing

unread,
Jun 2, 2009, 1:25:29 PM6/2/09
to ccnet-user
I ran into this same problem when upgrading from 1.4.3 to 1.4.4. When
I added the logger node as described above, my build worked just fine.

Michael Schall

unread,
Jun 2, 2009, 2:25:36 PM6/2/09
to ccnet...@googlegroups.com
I also had the issue and it was fixed by adding logger node.

Maybe this needs to be put in the release notes?
Reply all
Reply to author
Forward
0 new messages