Active Roles

Export-QCWorkflow seems not to be working in ActiveRoles Synch 7.1.2

Although I had no problem exporting a QC workflow in the past (v6.9), it looks like that in a fresh installation of 7.1.2 Export-QCWorkflow returns an error, no matter what I have tried

 

Export-QCWorkflow : Object reference not set to an instance of an object.
At line:9 char:2
+     Export-QCWorkflow -Id $name -Path $file
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Export-QCWorkflow], NullReferenceException
    + FullyQualifiedErrorId : ProcessingError,ActiveRoles.SyncService.ManagementShell.Commandlets.ExportWorkflowCmdlet

 

Any ideas?

 

  • I just tested this cmdlet in my lab running Active Roles 7.2.1 and it worked as expected.

    Are you seeing the same error when exporting all Workflows or just this one?
  • All workflows. Upgraded to 7.2, same thing. Furthermore I just noticed that after upgrading, the scheduled tasks are running on schedule. They run only manually. I have started thinking that something is seriously wrong, and I should perhaps install from scratch, without keeping the database. But I hate to re-create all workflows - at least, if I could export, I would have the xml files as a guide
  • Can you export a workflow's Updating Rules? The option is under the "More" menu. Whatever is selected will be exported.

    If you do have to re-create everything from scratch, this will make it much easier.
  • Thanks for the suggestion. Yes this is true. I can export the rules, but I will still have to re-create the connections and the mappings and I am trying to avoid this. I wonder if I am the only one with this issue.
  • I just took a look at the log file and I find the following every time I try to do an export
    2018-03-13 16:23:04.6112 33 Error --> Outgoing exception ActiveRoles.SyncService.ServerCommon.ErrorHandling.SimpleErrorHandler.HandleError System.ServiceModel.CommunicationException: The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '10675199.02:48:05.4775807'. ---> System.IO.IOException: The read operation failed, see inner exception. ---> System.ServiceModel.CommunicationException: The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '10675199.02:48:05.4775807'. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
    at System.ServiceModel.Channels.SocketConnection.HandleReceiveAsyncCompleted()
    at System.ServiceModel.Channels.SocketConnection.OnReceiveAsync(Object sender, SocketAsyncEventArgs eventArgs)
    --- End of inner exception stack trace ---
    at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
    at System.ServiceModel.Channels.ConnectionStream.EndRead(IAsyncResult asyncResult)
    at System.Net.FixedSizeReader.ReadCallback(IAsyncResult transportResult)
    --- End of inner exception stack trace ---
    at System.Net.Security.NegotiateStream.EndRead(IAsyncResult asyncResult)
    at System.ServiceModel.Channels.StreamConnection.EndRead()
    --- End of inner exception stack trace ---
    at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
    at System.ServiceModel.Channels.TransportDuplexSessionChannel.EndTryReceive(IAsyncResult result, Message& message)
    at System.ServiceModel.Dispatcher.DuplexChannelBinder.EndTryReceive(IAsyncResult result, RequestContext& requestContext)
    at System.ServiceModel.Dispatcher.ErrorHandlingReceiver.EndTryReceive(IAsyncResult result, RequestContext& requestContext)