I think I’ve been following your blog since you first wrote about joining Avanade. I’m also an Avanadeer up in Montreal, Canada. Just wanted to send my greetings and congratulations on getting your certification.

Take care,

Brian

Solution (for me at least) was to download the Sharepoint server 2007 sdk and after installing doing a devenv /resetsettings in visual studio commandprompt.

Cheers

I have the same problem as bob z described above.
I have built a system in vmware as described in the article
http://www.pptspaces.com/sharepointreporterblog/Lists/Posts/Post.aspx?ID=28
If that is familiar to you.

I am logged in as administrator and the processes are running in the same account.

Visual Studio 2008 sp1
MOSS server sp1
Windows server 2003 R2 (latest sp)
I’ve created a simple workflow and pressed f5.

Shown in the output:

—— Build started: Project: SharePointWorkflow2, Configuration: Debug Any CPU ——
c:\WINDOWS\Microsoft.NET\Framework\v3.5\Csc.exe /noconfig /nowarn:1701,1702 /errorreport:prompt /warn:4 /define:DEBUG;TRACE /reference:”C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\ISAPI\Microsoft.Office.Workflow.Tasks.dll” /reference:”C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\ISAPI\Microsoft.SharePoint.dll” /reference:”C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\ISAPI\Microsoft.SharePoint.Search.dll” /reference:”C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\ISAPI\Microsoft.SharePoint.WorkflowActions.dll” /reference:”C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5\System.Core.dll” /reference:”C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5\System.Data.DataSetExtensions.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:\Program Files\Reference Assemblies\Microsoft\Framework\v3.0\System.Workflow.Activities.dll” /reference:”C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.0\System.Workflow.ComponentModel.dll” /reference:”C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.0\System.Workflow.Runtime.dll” /reference:c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Xml.dll /reference:”C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5\System.Xml.Linq.dll” /debug+ /debug:full /filealign:512 /keyfile:key.snk /optimize- /out:obj\Debug\SharePointWorkflow2.dll /target:library Properties\AssemblyInfo.cs Workflow1.cs Workflow1.designer.cs Properties\Settings.Designer.cs “C:\Documents and Settings\Administrator\Local Settings\Temp\xodwbvvg.cs”

Compile complete — 0 errors, 0 warnings
SharePointWorkflow2 -> C:\Projects\SharePointWorkflow2\SharePointWorkflow2\bin\Debug\SharePointWorkflow2.dll
—— Deploy started: Project: SharePointWorkflow2, Configuration: Debug Any CPU ——
Successfully installed this assembly into the global assembly cache: SharePointWorkflow2.dll.
Successfully restarted Internet Information Services (IIS).
Successfully copied workflow.xml to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\FEATURES\SharePointWorkflow2\workflow.xml.
Successfully copied feature.xml to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\FEATURES\SharePointWorkflow2\feature.xml.
Failed to install the workflow template to Microsoft Office SharePoint Server.
Access denied.
Failed to deploy the workflow template to Microsoft Office SharePoint Server.
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========

Somewhere someone made the off-hand remark that it migth be different templates for moss and wss and that the templates in visual studio was incorrect. Giving me the error.

However I do not know how to verify that and I cant find my way back to that comment.

Any suggestion is appreciated.

Regards

Greger

For the record, as soon as I switched to Virtual PC and reconfigured, sample task workflow deployed as advertised.

I have no idea what led to initial problem but I had tried several times with several examples on Virtual Box. You lose some and you win one.

Regards.

http://alexcnichols.wordpress.com/2008/07/31/sharepoint-guidance-first-release/

There is some guidance for simple SharePoint workflows in this release.

I did nothing to debug settings. I haven’t tried a stsadm command yet. I am running Visual Studio as the virtual machine administrator.

I’ve found that the virtual machine where I was working was no longer letting me even access the SharePoint Central Admin which leads me to believe the vm was hosed somehow. (Central admin appeared to be up in IIS.) It could also be the virtual machine software I used (Virtual Box) was the issue.

I am presently creating a new virtual machine (with MS Virtual PC) with Windows Server 2003, Visual Studio 2008 and of course MOSS. I am running Visual Studio as administrator and I will try again to do the workflow sample for tasks that I found at rshelton.com.

The Visual Studio 2008 method of moving workflows appeals to me because it appears to take care of all the moving and activating, but I guess the downside is when it fails, it’s a little harder to figure out.

I will leave you another note after trying the process with my new setup. Regards.

A couple questions:
Are you setting the SharePoint Debug Settings to install the workflow to a local SharePoint site?
Are you able to run STSADM commands without getting Access Denied errors from the command prompt using this account?
Are you running Visual Studio as Administrator? Could be a Vista UAC issue.

The web.config should not need a safe control entry if the workflow dll is in the GAC.