I've turned off Trusted Surface in workflow manager because I won't have any user published workflows in my environment.  Are there any ways to extend the expression translation so that it supports activities that are not part of trusted surface?

For example, I would like to use the new operator to create a request object.  Is there a way to do this without providing some sort of factory activity?

Hi, I have tried in two separate environments to create a new workflow farm and am getting the following error. I have already installed the Feb CU for both workflow manager and the service bus. I rebooted all servers after installing.

I noticed a message in the UI saying "Configuration operation failed. Please drop databases and use ‘Create a New Farm’ again." When I look in SQL Management Studio no databases have been created. The new farm wizard fails on the first step.

Any ideas on a fix for this? I am using a SQL alias on my server, would this cause any problems? When I test the connection to the DB from the wizard all tests pass.

Error:

System.Management.Automation.CmdletInvocationException: An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name.
An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name.
An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name. ---> System.Data.SqlClient.SqlException: An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name.
An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name.
An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name.в System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   в System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   в System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)в System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   в System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite)в System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)в System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   в System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   в System.Data.Linq.SqlClient.SqlProvider.Execute(Expression query, QueryInfo queryInfo, IObjectReaderFactory factory, Object[] parentArgs, Object[] userArgs, ICompiledSubQuery[] subQueries, Object lastResult)
   в System.Data.Linq.SqlClient.SqlProvider.ExecuteAll(Expression query, QueryInfo[] queryInfos, IObjectReaderFactory factory, Object[] userArguments, ICompiledSubQuery[] subQueries)
   в System.Data.Linq.SqlClient.SqlProvider.System.Data.Linq.Provider.IProvider.Execute(Expression query)
   в Microsoft.ServiceBus.Commands.Common.ServerManagementStoreDataContext.CreateServerAdministratorLogin(String loginName)
   в Microsoft.ServiceBus.Commands.Common.SecurityHelper.CreateServerAdministratorRole(String accountName, String connectionString)
   в Microsoft.ServiceBus.Commands.NewSBFarmBase.InstallManagementDB(String connectionString, String adminGroup, String runAsName)
   в Microsoft.ServiceBus.Commands.NewSBFarmBase.ProcessRecord()
   --- Конец трассировки внутреннего стека исключений ---
   в System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
   в Microsoft.Workflow.Deployment.ConfigWizard.CommandletHelper.InvokePowershell(Command command, Action`2 updateProgress)
   в Microsoft.Workflow.Deployment.ConfigWizard.ProgressPageViewModel.CreateSBFarm(FarmCreationModel model)

I am getting error during workflow manager configuration.

I have posted the error  details here, can someone guide me here

http://social.msdn.microsoft.com/Forums/en-US/sharepointadmin/thread/0a730b57-d952-4db8-8275-1f73996265d1

MCTS,MCPD Sharepoint 2010. My Blog- http://www.sharepoint-journey.com
If a post answers your question, please click "Mark As Answer" on that post and "Vote as Helpful

Environment: Server 2012 standalone dev environment (single machine farm), VS 2012 Ultimate, SP 2013.

Followed the instructions several times to install / remove / re-install WFM 1.0 and no matter I end up with the following error when I try to debug the SP solution including a project with a couple simple task assignment workflows (in a brief flash window which I managed to screen capture):

Microsoft.Workflow.TestServiceHost.exe Error: 0 : System.IO.InvalidDataException: A required Workflow Configuration 'WorkflowServiceScopeSnapshotProcessBatchSize' is not present. Please add this configuration value.

The debug window (TestServiceHost) then closes, the browser closes and in my debug window in VS the following message appears:

Microsoft.Workflow.TestServiceHost.exe Error: 0 : System.MissingMethodException: Method not found: 'Void Microsoft.Workflow.Tracing.WorkflowEventSource.UnknownIsolateHandledExceptionAction(System.String, Microsoft.Workflow.Tracing.EventTraceActivity)'.

An unhandled exception was thrown: Microsoft.Workflow: System.Threading.ThreadAbortException: Thread was being aborted.
   at System.Threading.WaitHandle.WaitMultiple(WaitHandle[] waitHandles, Int32 millisecondsTimeout, Boolean exitContext, Boolean WaitAll)
   at System.Threading.WaitHandle.WaitAny(WaitHandle[] waitHandles, Int32 millisecondsTimeout, Boolean exitContext)
   at Microsoft.Workflow.Common.IOThreadTimer.TimerManager.OnWaitCallback(Object state)
   at Microsoft.Workflow.Common.IOThreadScheduler.ScheduledOverlapped.IOCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlappedCallback)
   at Microsoft.Workflow.Common.Fx.IOCompletionThunk.UnhandledExceptionFrame(UInt32 error, UInt32 bytesRead, NativeOverlapped* nativeOverlapped)

Any help in correcting this issue is greatly appreciated. Thanks.

Hi, I've set up a new workflow farm but can't bind to sharepoint due to a warning about certificates not being trusted. 

I have exported the file from IIS manager to a .cer file, added to trusted certicate authorities but when I browse to the workflow site the certificate still seems to be untrusted. 

Any ideas what I'm missing?

Guys:

Expression translation fails with 'unknown type' errors when the workflow xaml includes either custom code or a data type that is declared in the xaml local namespace. After more hours than I care to admit of trying to find out why the types defined in AllowedTypes.xml were not being recognized I found I needed to manually edit the xaml to add the assembly reference, as shown:-

Change:

 xmlns:local="clr-namespace:<your namespace>"

To:

 xmlns:local="clr-namespace:<your namespace>;assembly=<your assembly>"

Hello,

in order to install the 26/02/2013 version of the Microsoft Office Developer Tools for Visual Studio 2012, you need to install first the Service Bus 1.0 Cumulative Update 1.

The thing is that I can not install this update, I always get an error:

DownloadManager Information: 0 : Using cached file at C:\Users\Gilles\AppData\Local\Microsoft\Web Platform Installer\installers\ServiceBusCU1\5024FF633CA537CDB1C2903F97E1244457BAEE18\ServiceBus-KB2799752-x64-EN.exe instead of downloading from http://go.microsoft.com/fwlink/?LinkId=285191&CLCID=0x409
DownloadManager Information: 0 : Starting EXE command for product 'Service Bus 1.0 Cumulative Update 1'. Commandline is: 'C:\Users\Gilles\AppData\Local\Microsoft\Web Platform Installer\installers\ServiceBusCU1\5024FF633CA537CDB1C2903F97E1244457BAEE18\ServiceBus-KB2799752-x64-EN.exe /quiet'. Process Id: 6308
DownloadManager Information: 0 : Install exit code for product 'Service Bus 1.0 Cumulative Update 1' is '-1'
DownloadManager Error: 0 : Install return code for product 'Service Bus 1.0 Cumulative Update 1' is Failure
DownloadManager Information: 0 : Product Service Bus 1.0 Cumulative Update 1 done install completed
DownloadManager Information: 0 : Increasing current install to 2

if I run C:\Users\Gilles\AppData\Local\Microsoft\Web Platform Installer\installers\ServiceBusCU1\5024FF633CA537CDB1C2903F97E1244457BAEE18\ServiceBus-KB2799752-x64-EN.exe

I get : "an unexpected internal error has occured."

I am running Windows 8.

Somebody having the same issue?

Thx

Gilles

http://gilleslauwers.wordpress.com

I installed a Sharepoint 2013 Farm and Workflow Manager 1.0.

I created a workflow with Sharepoint Designer 2013, which works fine til I add a "send email" action. When the worklfow contains a "sending email" action the worklfow cancels with

RequestorId": 3d95f396-16f9-9e6d-0000-000000000000. Details: "RequestorId": 3d95f396-16f9-9e6d-0000-000000000000. Details: An unhandled exception occurred during the execution of the workflow instance. Exception details: System.ApplicationException: HTTP 400 {"Transfer-Encoding":["chunked"],"X-SharePointHealthScore":["0"],"SPClientServiceRequestDuration":["61"],"SPRequestGuid":["3d95f396-16f9-9e6d-8c72-b133c88bf37a"],"request-id":["3d95f396-16f9-9e6d-8c72-b133c88bf37a"],"X-FRAME-OPTIONS":["SAMEORIGIN"],"MicrosoftSharePointTeamServices":["15.0.0.4420"],"X-Content-Type-Options":["nosniff"],"X-MS-InvokeApp":["1; RequireReadOnly"],"Cache-Control":["max-age=0, private"],"Date":["Mon, 15 Apr 2013 09:55:12 GMT"],"Server":["Microsoft-IIS\/7.5"],"X-AspNet-Version":["4.0.30319"],"X-Powered-By":["ASP.NET"]} bei Microsoft.Activities.Hosting.Runtime.Subroutine

Sending emails work fine under Sharepoint 2013, I added an action writing destination email address in History, which works fine.

Any ideas, suggestions, more information needed?

Thanks for help

Hi.

I have a workflow that waits for an incoming notification before running a custom code activity. Once the notification is received and the custom code is called, if the custom code activity faults with a NullReferenceException then Workflow Manager proceeds to report a number of error and critical events to the EventLog (see below) before crashing (with crash dump) and restarting. On restart, Workflow Manager attempts to resume the workflow by calling the faulting code. It will keep doing this until the crash dumps (each approx 360MB) consume all remaining disk space; at a rate of one crash dump every 45 seconds. The only way to break the cycle before disk space is exhausted is to delete the published workflow.

To rule-out any additional interaction within the code, I pared-down my custom activity to a simple "throw new NullReferenceException" in the Execute() body and got the same result.

Incidentally, the crash dumps are written to "C:\Windows\System32\%LOCALAPPDATA%\CrashDumps" which is not a location where I would expect to find crash dumps for a service.

Regards,

Phil

Event #1 (many instances):

Dispatcher encountered an unexpected exception: System.NullReferenceException: Object reference not set to an instance of an object.

   at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.SystemSuspendSessionOnFailedConfiguration(String suspensionReason)

   at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.SystemSuspendSession(String suspensionReason, SystemSuspendType suspendType)

   at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.Isolate(AsyncCompletion callback, IAsyncResult result)

   at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.Isolate(AsyncCompletion callback, IAsyncResult result)

   at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.ExceptionHandlingFrame(IAsyncResult result)

Event #2 (Critical):

Dispatcher failfast is causing the Workflow Manager backend to terminate. Exception: System.AggregateException: The dispatcher failure rate has reached 11%. InnerException is the last failure; see traces for other failures. ---> System.NullReferenceException: Object reference not set to an instance of an object.

   at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.SystemSuspendSessionOnFailedConfiguration(String suspensionReason)

   at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.SystemSuspendSession(String suspensionReason, SystemSuspendType suspendType)

   at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.Isolate(AsyncCompletion callback, IAsyncResult result)

   at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.Isolate(AsyncCompletion callback, IAsyncResult result)

   at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.ExceptionHandlingFrame(IAsyncResult result)

   --- End of inner exception stack trace ---

---> (Inner Exception #0) System.NullReferenceException: Object reference not set to an instance of an object.

   at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.SystemSuspendSessionOnFailedConfiguration(String suspensionReason)

   at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.SystemSuspendSession(String suspensionReason, SystemSuspendType suspendType)

   at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.Isolate(AsyncCompletion callback, IAsyncResult result)

   at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.Isolate(AsyncCompletion callback, IAsyncResult result)

   at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.ExceptionHandlingFrame(IAsyncResult result)<---

Event #3:

Application terminating due to FailFast. Message : An unrecoverable error occurred. For diagnostic purposes, this English message is associated with the failure: 'The dispatcher failure rate has reached 11%. InnerException is the last failure; see traces for other failures.'., Exception: System.AggregateException: The dispatcher failure rate has reached 11%. InnerException is the last failure; see traces for other failures. ---> System.NullReferenceException: Object reference not set to an instance of an object.

   at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.SystemSuspendSessionOnFailedConfiguration(String suspensionReason)

   at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.SystemSuspendSession(String suspensionReason, SystemSuspendType suspendType)

   at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.Isolate(AsyncCompletion callback, IAsyncResult result)

   at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.Isolate(AsyncCompletion callback, IAsyncResult result)

   at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.ExceptionHandlingFrame(IAsyncResult result)

   --- End of inner exception stack trace ---

---> (Inner Exception #0) System.NullReferenceException: Object reference not set to an instance of an object.

   at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.SystemSuspendSessionOnFailedConfiguration(String suspensionReason)

   at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.SystemSuspendSession(String suspensionReason, SystemSuspendType suspendType)

   at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.Isolate(AsyncCompletion callback, IAsyncResult result)

   at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.Isolate(AsyncCompletion callback, IAsyncResult result)

   at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.ExceptionHandlingFrame(IAsyncResult result)<---

.

Hi,

We are trying to decide if some future release of WFM can be used in a mission-critical high-throughput enterprise solution that we are building on top of Service Bus. Our stumbling blocks are:

1. We need workflow activation from any Service Bus subscription or queue. Right now, we have some glue code that reads from a service bus queue and calls the WFM client API, so 2 hops instead of one.

2. Even though our workflow notifications are delivered by the service bus, there is no way to access the brokered message header from the workflow (at least, we haven't found one). And I mean the whole header, not just to user properties.

3. We need to build and send a brokered message directly from an activity, to any service bus queue or topic.

It is frustrating to have WFM sitting on top of the excellent service bus, but with a half backed integration. Handling brokered messages directly from activities seems to be an obvious feature, sadly missing.

Is there a roadmap for WFM, and if so, are brokered messages activities on it?

Thanks

We are using the HttpSend in Workflow Manager to communicate with Azure Media Services REST API.

Upon posting to "https://media.windows.net/API" the Azure Media Services REST API documentation states that a 302 redirect is returned to the client with a corresponding location header pointing to a new API endpoint. We need the endpoint, but are redirected so we cannot retrieve the Location out of the response header.

We have a need to use our workflows with SharePoint 2013 and have been told that code activities are not supported within SharePoint 2013. If we could use a code activity then we could use the HttpWebRequest to work around this issue.

If code activities cannot be used in SharePoint 2013 what can we do to not be redirected?

I've installed Workflow Manager 1.0, registered it on my SharePoint farm over HTTP without any errors. But I get the message "Workflow is not connected" at workflow service status page in CA.

One thing that seems suspicious is there are 2 Workflow service application proxy for Workflow service application.

How to make it working?

Env: VS 2012, SP2013, Win2012, WFM 1.0, SB 1.0, SB CU 1, WFM CU 1, SP Tools for VS, VS Update for Office tools

I have two solutions, one which deploys lists as features as a dependency feature to my list workflow feature, one which deploys List workflows as a feature with lists pre-existing on the SP site.

The second when deployed works fine (both are simple Sequence workflows with LookupSPListItemId, LookupSPList, LookupSPListItem, SingleTask, WritetoHistory objects - the lookups are to a secondary list to retrieve data for use in the SingleTask).

The first produces a Suspended state on the workflow with the following error once it hits the LookupSPListItemId:

System.FormatException: Expected hex 0x in '{0}'. at System.Guid.GuidResult.SetFailure(ParseFailureKind failure, String failureMessageID, Object failureMessageFormatArgument) at System.Guid.TryParseGuidWithHexPrefix(String guidString, GuidResult& result) at System.Guid.TryParseGuid(String g, GuidStyles flags, GuidResult& result) at System.Guid.Parse(String input) at System.Activities.CodeActivity
InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation) 

I tried making the listinstance feature (where the lists are activated on the sp site) a dependency in the feature for the workflow feature, tried recycling the site, the app pools (all involved) and rebooting the server after a deployment, all to no avail. The first solution simply fails.

Any ideas?

when I try to publish the workflow the following error appears:

Microsoft.Workflow.Client.ActivityValidationException: Workflow XAML failed validation due to the following errors:
Cannot set unknown member 'CompositeTask.RelatedContentLinkListItemIntegerId'. HTTP headers received from the server - ActivityId: 15459ce7-8e0d-4267-aa59-cc724289e422. NodeId: TECSRVSOL02. Scope: /SharePoint/default/c8ca3a4c-bb1a-4056-b675-597fa0348916/0d4731cd-bfe2-47b6-acd2-6caa6bd45931. Client ActivityId : d753129c-27a3-10d6-8d8c-f5a6367ce7ab. ---> System.Net.WebException: The  

I tried to create another workflow and got the same error. Followed the article "Troubleshooting workflow Manager 1.0 Management and Executation" to fix and nothing again.. 

Someone can help me?

I have workflows that I want to start using with Workflow Manager, however, from what I have heard, I can't just use my regular .Net types in there.  So for example, outside of WFM, my workflows have a reference to a .Net component that has classes like Employee, Customer etc...data types.

Can I still use these, as is in WFM or do I need to somehow convert these to DynamicValue types?

STom

When using the new SharePoint 2013 Platform in Designer, I have encounter a problem where the URL for the Current Item is not being generated correctly.

I get a relative url that looks like this: Lists/ChangeNotification/1_.000

I switched to using the SharePoint 2010 Platform and get the correct Url generated to open the list item in the display form:http://sharepoint2013/Lists/ChangeNotification/DispForm.aspx?ID=1

I see that there are some updates out for the Service Bus and Workflow Manager but I didn't see any references to this bug listed in the KBs.

I am getting the following error when trying to connect to workflow manager 1.0 cumulative update 1  installed on a windows server 2012 with visual studio running the UsingWorkflowTools sample project.

Error:
 System.ArgumentException: The remote server returned an error: (400)
 Bad Request. The api-version in the query string is not supported.
 Either remove it from the Uri or use one of
 '2012-03'