Submit My Question - Recent Questions - Recent Answer
Msdn Tech >> Software Development for Windows Vista >> Windows Workflow Foundation

build failure

Hi,

I run into the following problem building my project using WWF Beta 2:

After the first successful build, it isn't possible to build the solution again. Build ends with an error, not described in detail.

are there any ideas about soving this problem?

Best regards, Andreas

this is the output of the build process:

Build started: Project: Diagnostics, Configuration: Debug Any CPU

Diagnostics -> D:\_work\S3\src\S3.root\S3\Tools\Diagnostics\bin\Debug\Upper.S3.Diagnostics.dll

Build started: Project: NHibernate.Generics, Configuration: Debug Any CPU

NHibernate.Generics -> D:\_work\S3\src\S3.root\S3\Tools\NHibernate\NHibernate.Generics\bin\Debug\NHibernate.Generics.dll

Build started: Project: Core, Configuration: Debug Any CPU

Core -> D:\_work\S3\src\S3.root\S3\Core\bin\Debug\Upper.S3.Core.dll

Build started: Project: DataObjects, Configuration: Debug Any CPU

DataObjects -> D:\_work\S3\src\S3.root\S3\DataObjects\bin\Debug\Upper.S3.DataObjects.dll

Build started: Project: WorkflowRuntime, Configuration: Debug Any CPU

WorkflowRuntime -> D:\_work\S3\src\S3.root\S3\Server\Workflow\WorkflowRuntime\bin\Debug\Upper.S3.Server.Workflow.WorkflowRuntime.dll

Build started: Project: Common, Configuration: Debug Any CPU

Common -> D:\_work\S3\src\S3.root\S3\BusinessLogic\Common\bin\Debug\Upper.S3.BusinessLogic.Common.dll

Build started: Project: EventProcessor, Configuration: Debug Any CPU

EventProcessor -> D:\_work\S3\src\S3.root\S3\BusinessLogic\EventProcessor\bin\Debug\Upper.S3.BusinessLogic.EventProcessor.dll

Build started: Project: TestBase, Configuration: Debug Any CPU

TestBase -> D:\_work\S3\src\S3.root\S3\UnitTests\TestBase\bin\Debug\UPPER.S3.TestBase.dll

Build started: Project: CoreActivities, Configuration: Debug Any CPU

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Csc.exe /noconfig /nowarn:1701,1702 /warn:4 /define:DEBUG;TRACE /reference:..\..\..\lib\NHibernate.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Data.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Design.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Drawing.Design.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Drawing.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Transactions.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Web.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Web.Services.dll /reference:"C:\Programme\Reference Assemblies\Microsoft\WinFx\v3.0\System.Workflow.Activities.dll" /reference:"C:\Programme\Reference Assemblies\Microsoft\WinFx\v3.0\System.Workflow.ComponentModel.dll" /reference:"C:\Programme\Reference Assemblies\Microsoft\WinFx\v3.0\System.Workflow.Runtime.dll" /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Xml.dll /reference:D:\_work\S3\src\S3.root\S3\BusinessLogic\EventProcessor\bin\Debug\Upper.S3.BusinessLogic.EventProcessor.dll /reference:D:\_work\S3\src\S3.root\S3\Core\bin\Debug\Upper.S3.Core.dll /reference:D:\_work\S3\src\S3.root\S3\DataObjects\bin\Debug\Upper.S3.DataObjects.dll /debug+ /debug:full /optimize- /out:obj\Debug\Upper.S3.Server.Workflow.CoreActivities.dll /target:library GenericEventActivity.cs Properties\AssemblyInfo.cs Properties\Settings.Designer.cs "C:\Dokumente und Einstellungen\gue\Lokale Einstellungen\Temp\fgs3hrxi.cs"

Compile complete -- 0 errors, 0 warnings

CoreActivities -> D:\_work\S3\src\S3.root\S3\Server\Workflow\CoreActivities\bin\Debug\Upper.S3.Server.Workflow.CoreActivities.dll

Build started: Project: WorkflowLibrary.Test, Configuration: Debug Any CPU

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Csc.exe /noconfig /nowarn:1701,1702 /warn:4 /define:DEBUG;TRACE /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Data.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Design.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Drawing.Design.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Drawing.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Transactions.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Web.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Web.Services.dll /reference:"C:\Programme\Reference Assemblies\Microsoft\WinFx\v3.0\System.Workflow.Activities.dll" /reference:"C:\Programme\Reference Assemblies\Microsoft\WinFx\v3.0\System.Workflow.ComponentModel.dll" /reference:"C:\Programme\Reference Assemblies\Microsoft\WinFx\v3.0\System.Workflow.Runtime.dll" /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Xml.dll /reference:D:\_work\S3\src\S3.root\S3\BusinessLogic\EventProcessor\bin\Debug\Upper.S3.BusinessLogic.EventProcessor.dll /reference:D:\_work\S3\src\S3.root\S3\Server\Workflow\CoreActivities\bin\Debug\Upper.S3.Server.Workflow.CoreActivities.dll /debug+ /debug:full /optimize- /out:obj\Debug\Upper.S3.Server.Workflow.WorkflowLibary.Test.dll /resource:obj\Debug\Upper.S3.Server.Workflow.Libary.Test.WfGenericEventActivityTest.layout /target:library Properties\AssemblyInfo.cs WfGenericEventActivityTest.xoml.cs "C:\Dokumente und Einstellungen\gue\Lokale Einstellungen\Temp\qtbc48fy.cs"

Compile complete -- 0 errors, 0 warnings

WorkflowLibrary.Test -> D:\_work\S3\src\S3.root\S3\UnitTests\Server\Workflow\WorkflowLibrary.Test\bin\Debug\Upper.S3.Server.Workflow.WorkflowLibary.Test.dll

Build started: Project: WorkflowRuntime.Test, Configuration: Debug Any CPU

WorkflowRuntime.Test -> D:\_work\S3\src\S3.root\S3\UnitTests\Server\Workflow\WorkflowRuntime.Test\bin\Debug\Upper.S3.Server.Workflow.Runtime.Test.dll

Build started: Project: CoreActivities.Test, Configuration: Debug Any CPU

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Csc.exe /noconfig /nowarn:1701,1702 /warn:4 /define:DEBUG;TRACE /reference:..\..\..\..\lib\NHibernate.dll /reference:..\..\..\..\lib\nunit.core.dll /reference:..\..\..\..\lib\nunit.framework.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Data.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Design.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Drawing.Design.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Drawing.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Transactions.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Web.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Web.Services.dll /reference:"C:\Programme\Reference Assemblies\Microsoft\WinFx\v3.0\System.Workflow.Activities.dll" /reference:"C:\Programme\Reference Assemblies\Microsoft\WinFx\v3.0\System.Workflow.ComponentModel.dll" /reference:"C:\Programme\Reference Assemblies\Microsoft\WinFx\v3.0\System.Workflow.Runtime.dll" /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Xml.dll /reference:D:\_work\S3\src\S3.root\S3\BusinessLogic\Common\bin\Debug\Upper.S3.BusinessLogic.Common.dll /reference:D:\_work\S3\src\S3.root\S3\BusinessLogic\EventProcessor\bin\Debug\Upper.S3.BusinessLogic.EventProcessor.dll /reference:D:\_work\S3\src\S3.root\S3\Core\bin\Debug\Upper.S3.Core.dll /reference:D:\_work\S3\src\S3.root\S3\DataObjects\bin\Debug\Upper.S3.DataObjects.dll /reference:D:\_work\S3\src\S3.root\S3\Tools\Diagnostics\bin\Debug\Upper.S3.Diagnostics.dll /reference:D:\_work\S3\src\S3.root\S3\UnitTests\Server\Workflow\WorkflowRuntime.Test\bin\Debug\Upper.S3.Server.Workflow.Runtime.Test.dll /reference:D:\_work\S3\src\S3.root\S3\UnitTests\Server\Workflow\WorkflowLibrary.Test\bin\Debug\Upper.S3.Server.Workflow.WorkflowLibary.Test.dll /reference:D:\_work\S3\src\S3.root\S3\Server\Workflow\WorkflowRuntime\bin\Debug\Upper.S3.Server.Workflow.WorkflowRuntime.dll /reference:D:\_work\S3\src\S3.root\S3\UnitTests\TestBase\bin\Debug\UPPER.S3.TestBase.dll /debug+ /debug:full /optimize- /out:obj\Debug\Upper.S3.Server.Workflow.CoreActivities.Test.dll /target:library GenericEventActivity.Test.cs Properties\AssemblyInfo.cs "C:\Dokumente und Einstellungen\gue\Lokale Einstellungen\Temp\8b30tbwh.cs"

Compile complete -- 0 errors, 0 warnings

CoreActivities.Test -> D:\_work\S3\src\S3.root\S3\UnitTests\Server\Workflow\CoreActivities.Test\bin\Debug\Upper.S3.Server.Workflow.CoreActivities.Test.dll

========== Build: 11 succeeded or up-to-date, 1 failed, 0 skipped ==========

[13642 byte] By [andreass] at [2007-12-22]
«« Proxy with webClient?
»» Shortcut keys for context menu?
# 1

Andrea,

We have seen a similar issue in the past where the build succeeds (binaries are built successfully) but reports 1 failure. What you could try is to see if the binaries are built. If they are thenyou can ignore this failure.

Could you attach the solution so that we can repro this on our side.

Thanks,

Vijay

VijaySubramani at 2007-8-30 > top of Msdn Tech,Software Development for Windows Vista,Windows Workflow Foundation...
# 2

Hi,

now we've isolated the rebuild-problem as it follows

at first: here's a download link for the hole project:

http://rome.uppernetwork.com:83/MS/S3Test_BuildFailed_LoaderExceptions.zip

The project includes only 2 projects, with 4 classes (the minimal version to reproduce the error):

SequentialWorkflow.cs -> Basis sequential workflow

StateWorkflow.cs -> Basis state workflow

SequentialWorkflow1.cs -> derive from SequentialWorkflow

StateWorkflow1.xoml -> derive from StateWorkflow

Steps to reproduce the ?Build – Failed“ Error:

First Test:

  1. Open S3.sln in VS2005

  2. Build/Rebuild All -> Success

  3. Build/Rebuild All -> Rebuild All failed

  4. Open the workflow “StateWorkflow1.xoml” with the designer -> failed, retrieve the LoaderExceptions …

Second Test:

  1. Close the Solution

  2. Open S3.sln

  3. Open the workflow “StateWorkflow1.xoml” with the designer -> Success

  4. Build/Rebuild All -> Success

  5. Build/Rebuild All -> Success

  6. …

The behaviour is the same for StateWorkflow1 and SequentialWorkflow1.

Thanks for helping us with this problem!

Gerhard B.

(Proxy for Andreas S)

GerhardB at 2007-8-30 > top of Msdn Tech,Software Development for Windows Vista,Windows Workflow Foundation...
# 3

I would like to re-open this and see if the Workflow team has been able to isolate this bug and fix it for a current (2.2) or future version. We are experiencing this issue (Beta 2) and it is quite frustrating as we are only able to successfully build our project the first time. The second build (and all subsequent builds) results in one build failed (the workflow project) with 0 errors. The only way to make it go away is to close and re-open the solution, which only works the first time we build after re-opening the solution.

Is there any work around or item to check to stop this phantom build failure from occuring?

DavidFelker at 2007-8-30 > top of Msdn Tech,Software Development for Windows Vista,Windows Workflow Foundation...
# 4

I'm also running into a problem. It appears something in the msbuild process removes temporary files too early. this is happening inside clean virtual PCs on both beta 2 and beta 2.2. I see it happen in console mode applications and class library projects. The build process produces no binaries. Typicall error messages are:

Error 1 Compilation failed. Could not find a part of the path 'C:\Documents and Settings\bitmask\Local Settings\Temp\1\ypdd48iv.tmp'. C:\dev\workflow\...

FileMon from sysinternals shows the entire Temp\1\ directory getting whacked during the build process.

This is becoming a major frustration. If someone wants, I can send a VPC image to reproduce the problem.

ScottAllen at 2007-8-30 > top of Msdn Tech,Software Development for Windows Vista,Windows Workflow Foundation...
# 5
I have also just begin experiencing this issue. On our VPC when trying to build the application, it is unable to locate a temp directory.

Has anyone found an fix for this?

jmurray_mi at 2007-8-30 > top of Msdn Tech,Software Development for Windows Vista,Windows Workflow Foundation...
# 6
I think I found a solution to this issue, though I can't say for certain which fixed the problem.

1) I uninstalled the winFx, workflow and VS extensions from the machine.
2) I reinstalled these components which led me to the second fix (and the one I think actually worked).

3) During the reinstall I was unable to unpackage the extension for install with an error about lacmking permissions. Researching my environment variables I noticed that my global TEMP and TMP settings were for C:\Windows\Temp\.

In a desperate stab I changed these two settings to C:\Temp\. Afterward I was able to reinstall the extensions pacakge and succeeded in compiling the application.

Not sure if this will help anyone else but its worth a shot!

Jesse

jmurray_mi at 2007-8-30 > top of Msdn Tech,Software Development for Windows Vista,Windows Workflow Foundation...
# 7
Not to beat a dead horse but this happened again on my server. I can now confirm that simply changing the values of the environment variables (TEMP and TMP) fixes whatever issue is underlying this problem.

In my case I changed back from C:\Temp to C:\Windows\Temp.

jmurray_mi at 2007-8-30 > top of Msdn Tech,Software Development for Windows Vista,Windows Workflow Foundation...
# 8

I'm consistently seeing this, and changing the location of the TMP and TEMP paths doesn't seem to do the trick for me . . .

The only way I can seem to get around this is to:

1. Create a new blank SharePoint WF project.

2. Open the new project, build it - it builds OK (as you would hope for a new project !)

3. Close the project.

4. Copy the old workflow files (workflowname.cs workflowname.designer.cs) into the new project folder.

5. Open the new project again, remove the default workflow files (workflow1.cs workflow1.designer.cs) and include the new files in the project.

6. Re-build the project and it works OK.

Note, I also copy over my workflow.xml, feature.xml and install.bat so as not to lose those either ! I then remove the old project and rename the new project to be the same as the old.

This is a right headache to do everytime I see this . . . Has anyone found anything out about this yet such as the cause or a better solution ?!

Thanks,

Chris

ChrisWhite at 2007-8-30 > top of Msdn Tech,Software Development for Windows Vista,Windows Workflow Foundation...
Software Development for Windows Vista
Windows Workflow Foundation

Software Development for Windows Vista Hot Topic

Software Development for Windows Vista New Topic

Software Development for Windows Vista

Java / MSDN / Linux Tech / PHP Tech / MSDN DotNet / MSDN TECH / Health Library / Programmers Tech / visual basic Tech / Developer Tech / Ipod faqs / Msdn China Tech

Site Classified