Workflow manager Service Bus 407 error

After installing and configuring Workflow Manager on SharePoint 2013 farm I am able to create workflows in SP Designer in 2013 and publish them on the server with no errors. New workflows do show up in the application, but will not run. I found
the indication in ULS that something went wrong 
Workflow revision number mismatch! Current workflow store revision is 13 and workflow host scope has revision 0
Operational event viewer logs on the Workflow Manager Host showing up these events:
Log Name: Microsoft-Workflow/Operational
Source: Microsoft-Workflow
Date: 5/2/2014 2:00:31 PM
Event ID: 22
Task Category: (65512)
Level: Warning
Keywords: Dispatcher,Management
User: domain\user
Computer: FQDN
Description:
Service Bus exception swallowed at location ServiceBusNamespaceListener.GetSessionAndStateWithRetryAsyncResult.HandleException. System.UnauthorizedAccessException: The token provider was unable to provide a security token while accessing 'https://fqdn:9355/WorkflowDefaultNamespace/$STS/Windows/'. Token provider returned message: ''. ---> System.IdentityModel.Tokens.SecurityTokenException: The token provider was unable to provide a security token while accessing 'https://FQDN:9355/WorkflowDefaultNamespace/$STS/Windows/'. Token provider returned message: ''. ---> System.Net.WebException: The remote server returned an error: (407) Proxy Authentication Required.
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at System.Net.HttpWebRequest.GetRequestStream()
at Microsoft.ServiceBus.TokenProviderHelper.GetWindowsAccessTokenCore(IEnumerator`1 stsUris, Func`2 uriBuilder, String requestToken, TimeSpan timeout, DateTime& expiresIn)
--- End of inner exception stack trace ---
at Microsoft.ServiceBus.TokenProviderHelper.ThrowException(Uri requestUri, WebException exception)
at Microsoft.ServiceBus.TokenProviderHelper.GetWindowsAccessTokenCore(IEnumerator`1 stsUris, Func`2 uriBuilder, String requestToken, TimeSpan timeout, DateTime& expiresIn)
at Microsoft.ServiceBus.WindowsTokenProvider.OnBeginGetToken(String appliesTo, String action, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.TokenProvider.GetTokenAsyncResult..ctor(TokenProvider tokenProvider, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.TokenProvider.BeginGetToken(String appliesTo, String action, Boolean bypassCache, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.TokenProviderUtility.GetMessagingToken(ITokenProvider tokenProvider, Uri baseAddress, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout)
--- End of inner exception stack trace ---
Server stack trace:
at Microsoft.ServiceBus.TokenProviderUtility.GetMessagingToken(ITokenProvider tokenProvider, Uri baseAddress, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.GetAuthorizationHeader(String action)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.CreateWcfMessageInternal(String action, Object body, Boolean includeToken)
at Microsoft.ServiceBus.Messaging.Sbmp.AcceptMessageSessionForNamespaceAsyncResult..ctor(SbmpMessagingFactory messagingFactory, ReceiveMode receiveMode, Int32 prefetchCount, CreateControlLinkSettings controlLinkSettings, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessagingFactory.OnBeginAcceptMessageSession(ReceiveMode receiveMode, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.Messaging.MessagingFactory.AcceptMessageSessionAsyncResult.<GetAsyncSteps>b__29(AcceptMessageSessionAsyncResult thisPtr, TimeSpan t, AsyncCallback c, Object s)
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.EnumerateSteps(CurrentThreadType state)
Exception rethrown at [0]:
at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Workflow.Dispatcher.ServiceBusNamespaceListener.GetSessionAndStateWithRetryAsyncResult.EndAsyncResult(IAsyncResult result)
at Microsoft.Workflow.Common.BackoffRetryAsyncResult.IsolateWithRetry(IAsyncResult result)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Workflow" Guid="{B2885F6E-231C-43FF-BBEA-7516148FF6FE}" />
<EventID>22</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>65512</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000210</Keywords>
<TimeCreated SystemTime="2014-05-02T18:00:31.600519200Z" />
<EventRecordID>323735</EventRecordID>
<Correlation ActivityID="{C756E6D1-A7DC-4DA5-BA9D-D38DFD199CBC}" />
<Execution ProcessID="4084" ThreadID="4112" />
<Channel>Microsoft-Workflow/Operational</Channel>
<Computer>FQDN</Computer>
<Security UserID="S-1-5-21-436374069-1326574676-725345543-5309" />
</System>
<EventData>
<Data Name="location">ServiceBusNamespaceListener.GetSessionAndStateWithRetryAsyncResult.HandleException</Data>
<Data Name="exception">System.UnauthorizedAccessException: The token provider was unable to provide a security token while accessing 'https://********************:9355/WorkflowDefaultNamespace/$STS/Windows/'. Token provider returned message: ''. ---&gt; System.IdentityModel.Tokens.SecurityTokenException: The token provider was unable to provide a security token while accessing 'https://****************:9355/WorkflowDefaultNamespace/$STS/Windows/'. Token provider returned message: ''. ---&gt; System.Net.WebException: The remote server returned an error: (407) Proxy Authentication Required.
at System.Net.HttpWebRequest.GetRequestStream(TransportContext&amp; context)
at System.Net.HttpWebRequest.GetRequestStream()
at Microsoft.ServiceBus.TokenProviderHelper.GetWindowsAccessTokenCore(IEnumerator`1 stsUris, Func`2 uriBuilder, String requestToken, TimeSpan timeout, DateTime&amp; expiresIn)
--- End of inner exception stack trace ---
at Microsoft.ServiceBus.TokenProviderHelper.ThrowException(Uri requestUri, WebException exception)
at Microsoft.ServiceBus.TokenProviderHelper.GetWindowsAccessTokenCore(IEnumerator`1 stsUris, Func`2 uriBuilder, String requestToken, TimeSpan timeout, DateTime&amp; expiresIn)
at Microsoft.ServiceBus.WindowsTokenProvider.OnBeginGetToken(String appliesTo, String action, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.TokenProvider.GetTokenAsyncResult..ctor(TokenProvider tokenProvider, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.TokenProvider.BeginGetToken(String appliesTo, String action, Boolean bypassCache, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.TokenProviderUtility.GetMessagingToken(ITokenProvider tokenProvider, Uri baseAddress, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout)
--- End of inner exception stack trace ---
Server stack trace:
at Microsoft.ServiceBus.TokenProviderUtility.GetMessagingToken(ITokenProvider tokenProvider, Uri baseAddress, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.GetAuthorizationHeader(String action)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.CreateWcfMessageInternal(String action, Object body, Boolean includeToken)
at Microsoft.ServiceBus.Messaging.Sbmp.AcceptMessageSessionForNamespaceAsyncResult..ctor(SbmpMessagingFactory messagingFactory, ReceiveMode receiveMode, Int32 prefetchCount, CreateControlLinkSettings controlLinkSettings, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessagingFactory.OnBeginAcceptMessageSession(ReceiveMode receiveMode, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.Messaging.MessagingFactory.AcceptMessageSessionAsyncResult.&lt;GetAsyncSteps&gt;b__29(AcceptMessageSessionAsyncResult thisPtr, TimeSpan t, AsyncCallback c, Object s)
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.EnumerateSteps(CurrentThreadType state)
Exception rethrown at [0]:
at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Workflow.Dispatcher.ServiceBusNamespaceListener.GetSessionAndStateWithRetryAsyncResult.EndAsyncResult(IAsyncResult result)
at Microsoft.Workflow.Common.BackoffRetryAsyncResult.IsolateWithRetry(IAsyncResult result)</Data>
</EventData>
</Event>
no proxy is configured on the system and gateway address is accurate.

are you accessing the site from your local machine or on the server? also could you please tell us if your sharepoint server and Client
are on same domain.  Looks Like Token services having the issue.
As i saw you are using the SSL, check the below post may help.
http://social.technet.microsoft.com/wiki/contents/articles/13708.installing-workflow-manager-failed-with-could-not-establish-trust-relationship-for-the-ssltls-secure-channel.aspx
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Similar Messages

  • Timeout while configuring workflow manager (service bus services are stuck on strarting)

    Hello,
    I cant finish workflow manager configuration. help me please.
    I tried:
    1) leave the farm (Workflow manager configuration), delete databases, create new farm with default settings - it creates SB&WF farms and on 3d stage I get timeout error.
    2) leave the farm, delete databases, delete workflow manager and service bus software, install it again, create new farm with defaults - the same result.
    3) leave the farm, delete databases, get powershell commands for "create new farm with default settings", run it step by step - same result.
    there are generated powershell commands:
     New-SBFarm -SBFarmDBConnectionString '... ManagementDB con string ...' -InternalPortRangeStart 9000 -TcpPort 9354 -MessageBrokerPort 9356 -RunAsAccount 'domain\acc' -AdminGroup 'BUILTIN\Administrators' -GatewayDBConnectionString '... gateway con string
    ...' -CertificateAutoGenerationKey $SBCertificateAutoGenerationKey -MessageContainerDBConnectionString '... message container con string ...' -Verbose;
    New-WFFarm -WFFarmDBConnectionString '... WF managementDB con string ...' -RunAsAccount 'domain\acc' -AdminGroup 'BUILTIN\Administrators' -HttpsPort 12290 -HttpPort 12291 -InstanceDBConnectionString '... WF instanceDB con string ...' -ResourceDBConnectionString
    '... wf resourceDB con string ...' -CertificateAutoGenerationKey $WFCertAutoGenerationKey -Verbose;
    Add-SBHost -SBFarmDBConnectionString '... ManagementDB con string ...' -RunAsPassword $SBRunAsPassword -EnableFirewallRules $true -CertificateAutoGenerationKey $SBCertificateAutoGenerationKey -Verbose;
    I don't see any errors in event log, only timeout error in setup log.
    Service bus gateway service is started successfully, Service bus message broker is stuck starting.

    dmadelung, thank you for your message.
    the problem was with ports. 9000 port was used already. moving to different ports resolved the problem

  • Workflow Manager service in Error state after Dec14 CU install

    After installing Dec 14 CU and updating the WF farm to CU2 I tried to run the cmdlets as per here -
    https://technet.microsoft.com/en-us/library/dn133867.aspx?f=255&MSPPError=-2147217396
    $credential = [System.Net.CredentialCache]::DefaultNetworkCredentials
    $site = Get-SPSite https://teams.sharepoint.com
    $proxy = Get-SPWorkflowServiceApplicationProxy
    $svcAddress = $proxy.GetWorkflowServiceAddress($site)
    Copy-SPActivitiesToWorkflowService -WorkflowServiceAddress $svcAddress -Credential $credential -Force $true
    This errors:
    Copy-SPActivitiesToWorkflowService : An internal error occured. For more details, please see the server logs. Client
    ActivityId : cb2a40af-2c50-4e5c-8ac2-c5436c351b89.
    At line:1 char:1
    + Copy-SPActivitiesToWorkflowService -WorkflowServiceAddress $svcAddress -Credenti ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidData: (Microsoft.Share...WorkflowService:CopySPActivitiesToWorkflowService) [Copy
       -SPActivitiesToWorkflowService], InternalServerException
        + FullyQualifiedErrorId : Microsoft.SharePoint.WorkflowServices.PowerShell.CopySPActivitiesToWorkflowService
    I then ran get-WFFarmstatus on the WF server (3 in the farm) and see that the service is stopped on all the WF servers with a warning:
    WFserver1      WorkflowServiceBackend                                                 
    Stopped
    WARNING: Endpoint https://WFserver1:12290/ is not responding: The remote server returned anerror: (500) Internal Server Error.
    WFserver1      WorkflowServiceFrontEnd                                                
    Stopped
    Checked the underlying services and IIS on the 3 WF servers and these are all now started but the WF service cannot be started:
    net start WorkflowServiceBackend
    The Workflow Manager Backend service is starting.
    The Workflow Manager Backend service could not be started.
    A system error has occurred.
    System error 1067 has occurred.
    The process terminated unexpectedly.
    The WF operational logs show this:
    Unhandled exception in AppDomain:
    Microsoft.Workflow.Common.FatalException: An unrecoverable error occurred. For
    diagnostic purposes, this English message is associated with the failure: 'A
    required Workflow Manager configuration
    'WorkflowServiceScopeSnapshotProcessBatchSize' is not present. Please add this
    configuration value.'. ---> System.IO.InvalidDataException: A required
    Workflow Manager configuration 'WorkflowServiceScopeSnapshotProcessBatchSize'
    is not present. Please add this configuration value. <o:p></o:p>
    at
    Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result) <o:p></o:p>
    at
    Microsoft.Workflow.Service.WorkflowServiceBackendHost.OnStartCompleted(IAsyncResult
    result) <o:p></o:p>
    There is a suggested fix for this here -
    http://www.guideushow.com/sharepoint/solved-workflowservicescopesnapshotprocessbatchsize-is-not-present/
    (http://www.guideushow.com/sharepoint/solved-workflowservicescopesnapshotprocessbatchsize-is-not-present/)
    <o:p></o:p>
    I’d like to at least get some feedback as to whether this is safe/supported (MS doesn’t like
    any tinkering with the DBs…) – or whether we should go down the uninstall/reinstall
    the Workflow farm route  - thanks
    J

    Hi,
    For your issue, try to provid EXECUTE permission for role "WFServiceOperators".
    Add Workflow service account as “WFServiceOperators” into the database. Here are the steps to apply permissions:
    Open the Query Window and Select the database “WFInstanceManagementDB”
    Write the following line of script:
    GRANT EXECUTE TO WFServiceoperators
    Hit Execute.
    Repeat the steps for database “WFResourceManagementDB”
    Here are similar issue posts, you can use as a reference:
    https://social.msdn.microsoft.com/Forums/office/en-US/351b72e1-1664-43c5-8c2b-ffb307bef38e/cant-access-workflow-status-page-after-workflow-manager-cu2?forum=sharepointadmin
    https://social.msdn.microsoft.com/forums/azure/en-US/054d2a58-8847-4a6a-b1ab-05a79f49fe65/workflow-manager-cumulative-update-february-error?forum=wflmgr
    Best Regards,
    Lisa Chen
    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
    [email protected]

  • Error in Grid Control: Setup - Management Services and Repository - error

    Hi, sometimes , in our grid control, we could see in
    Setup -> Management Services and Repository -> errors, the following error
    OMS failover: Error in OMS status collection. ORA-20233: Invalid Target=Management Services and Repository or Metric=Management_Servlet_Status (validate_target_metric)
    How can I correct this ?
    We are in 10.2.0.5 ( with 3 management servers )
    thanks for your help
    regards,

    See the metalink note 388280.1,4487966 for solution.
    Hope this helps,
    Regards
    Click here to [ Restore and recover OCR|http://www.oracleracexpert.com/2009/08/restore-and-recover-ocr-from-backup.html]
    Click here to [Replace and repair OCR|http://www.oracleracexpert.com/2009/09/how-to-move-or-replace-and-repair-ocr.html]
    Click here to [Backup and Recover VOTE|http://www.oracleracexpert.com/2009/08/voting-disk-backup-and-recovery.htmll]
    http://www.oracleracexpert.com

  • Workflow manager 1.0 : runtime error 400 running Add-WFHost "The api-version in the query string is not supported"

    Installing Workflow Manager 1.0 for SharePoint Server 2013 SP1 everything is fine until the last step of the configuration and last powershell command : 
    Add-WFHost -WFFarmDBConnectionString 'myconnectionstring' -RunAsPassword $WFRunAsPassword -EnableFirewallRules $true -SBClientConfiguration $SBClientConfiguration -CertificateAutoGenerationKey $WFCertAutoGenerationKey -Verbose;
    gives me the following error : 
    Add-WFHost : 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'..TrackingId:412684e3-3539-468e-91e6-17838c6eaa55_GS
    P,TimeStamp:04/04/2014 12:54:11
    At line:1 char:1
    Can't find anything about this subject except this
    thread which does not help me that much in SharePoint dev env ...
    Removing workflow manager 1.0 and service bus (leave the farm using wizzard, remove binaries and databases) does not help.
    Who already faces this issue and how can I try to resolve it ?
    Best regards !
    Alexandre DAVID

    The API version is hardcoded in Microsoft.ServiceBus.dll, which ships as part of the Service Bus. Each version of this lib has a different string.
    If you install workflow manager 1.0, here are the pre-requisites:
    .NET Framework 4 Platform Update 3 or .NET Framework 4.5
    Service Bus 1.0
    Workflow Client 1.0
    PowerShell 3.0
    The following are the pre-requisites to configure Workflow Manager 1.0
    Instance of SQL Server 2008 R2 SP1, SQL Server Express 2008 R2 SP1, or SQL Server 2012.
    TCP/IP connections or named pipes must be configured in SQL Server.
    Windows Firewall must be enabled. [Windows Firewall is Off on target server]
    Ports 12290 and 12291 must be available.
    Here are the reference for installing and configuring Workflow Manager 1.0:
    http://lennytech.wordpress.com/2013/06/02/installing-workflow-manager-1-0/
    http://lennytech.wordpress.com/2013/06/02/configuring-workflow-manager-1-0/
    http://social.technet.microsoft.com/Forums/en-US/c74507fb-ac2d-405f-b19c-2712b1055708/workflow-manager-10-configuration-service-bus-for-windows-server-the-api-version-is-not?forum=sharepointadmin

  • Workflow Manager Cumulative Update (February) error

    Hi,
    I've downloaded and installed
    Workflow Manager 1.0 Cumulative Update and
    Service Bus 1.0 Cumulative Update. But after installing the updates, I can't access the Library workflow settings page. I'm getting unexpected error. Then after investigating the workflow manager log in event viewer, I've found the following error messages:
    The asynchronous operation has completed with an exception. Exception message is: System.Data.SqlClient.SqlException (0x80131904): The EXECUTE permission was denied on the object 'InsertTrackingAndStatus', database 'DEV_WFInstanceManagementDB', schema 'dbo'.
       at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
       at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
       at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
       at System.Data.SqlClient.SqlCommand.CompleteAsyncExecuteReader()
       at System.Data.SqlClient.SqlCommand.EndExecuteNonQueryInternal(IAsyncResult asyncResult)
       at System.Data.SqlClient.SqlCommand.EndExecuteNonQuery(IAsyncResult asyncResult)
       at Microsoft.Workflow.Management.ExecuteNonQueryAsyncResult.OnEndExecuteSql(IAsyncResult result)
       at Microsoft.Workflow.Management.ExecuteSqlAsyncResult.EndAsyncResult(IAsyncResult result)
       at Microsoft.Workflow.Common.BackoffRetryAsyncResult.IsolateWithRetry(IAsyncResult result)
       at Microsoft.Workflow.Common.AsyncResult.AsyncCompletionWrapperCallback(IAsyncResult result)
    ClientConnectionId:2f93882a-8d4c-440d-a3ff-0bd9d1682ad2.
    The issue I've found in my Dev environment with Windows Server 2008 R2 SP 1. This is standalone SharePoint farm with DC, SQL Server and SharePoint all installed in the same server. One workaround I have found that if I add the WF user as dbo to the database
    as well as  'WFServiceOperators' then the error disappear.
    Thanks,
    Sohel Rana
    http://ranaictiu-technicalblog.blogspot.com

    I ran the provided SQL script on our Workflow Manager databases. I commented out the EXEC line and added a 'PRINT @Cmd'. This allowed me to view the actual commands the script would execute. These commands were generated:
    GRANT EXECUTE ON [AddDbUserToRole] TO [WFServiceOperators]
    GRANT EXECUTE ON [AddLoginAndUser] TO [WFServiceOperators]
    GRANT EXECUTE ON [AddUserToServiceAdmins] TO [WFServiceOperators]
    GRANT EXECUTE ON [AddUserToServiceOperators] TO [WFServiceOperators]
    GRANT CONTROL, REFERENCES ON TYPE::[DebugTraceRecordValues] TO [WFServiceOperators]
    GRANT EXECUTE ON [DeleteExpiredInstances] TO [WFServiceOperators]
    GRANT EXECUTE ON [DeleteInstances] TO [WFServiceOperators]
    GRANT EXECUTE ON [DeleteInstancesByScopeId] TO [WFServiceOperators]
    GRANT EXECUTE ON [DeleteSystemInstances] TO [WFServiceOperators]
    GRANT CONTROL, REFERENCES ON TYPE::[EntityIds] TO [WFServiceOperators]
    GRANT CONTROL, REFERENCES ON TYPE::[EntityNames] TO [WFServiceOperators]
    GRANT EXECUTE ON [FormatNTGroupName] TO [WFServiceOperators]
    GRANT EXECUTE ON [GetDebugTraces] TO [WFServiceOperators]
    GRANT EXECUTE ON [GetInstanceCount] TO [WFServiceOperators]
    GRANT EXECUTE ON [GetInstanceDebugTraces] TO [WFServiceOperators]
    GRANT EXECUTE ON [GetInstanceDebugTracesByWorkflowId] TO [WFServiceOperators]
    GRANT EXECUTE ON [GetInstanceMetadata] TO [WFServiceOperators]
    GRANT EXECUTE ON [GetInstances] TO [WFServiceOperators]
    GRANT EXECUTE ON [GetInstancesById] TO [WFServiceOperators]
    GRANT EXECUTE ON [GetInstancesByWorkflowId] TO [WFServiceOperators]
    GRANT EXECUTE ON [GetInstanceStatusHistory] TO [WFServiceOperators]
    GRANT EXECUTE ON [GetInstanceStatusHistoryRecordsByWorkflowId] TO [WFServiceOperators]
    GRANT EXECUTE ON [GetInstancesToRestore] TO [WFServiceOperators]
    GRANT EXECUTE ON [GetInstanceTelemetryData] TO [WFServiceOperators]
    GRANT EXECUTE ON [GetMappedVariables] TO [WFServiceOperators]
    GRANT EXECUTE ON [GetStatusHistory] TO [WFServiceOperators]
    GRANT EXECUTE ON [GetStillReferencedWorkflows] TO [WFServiceOperators]
    GRANT EXECUTE ON [GetStoreVersion] TO [WFServiceOperators]
    GRANT EXECUTE ON [GetSystemInstances] TO [WFServiceOperators]
    GRANT EXECUTE ON [GetUpdatedInstances] TO [WFServiceOperators]
    GRANT CONTROL, REFERENCES ON TYPE::[Guids] TO [WFServiceOperators]
    GRANT EXECUTE ON [HasPermissionToPerform] TO [WFServiceOperators]
    GRANT EXECUTE ON [InsertInstanceDebugTraceRecords] TO [WFServiceOperators]
    GRANT EXECUTE ON [InsertInstanceStatusHistoryRecords] TO [WFServiceOperators]
    GRANT EXECUTE ON [InsertNotStartedInstanceRecord] TO [WFServiceOperators]
    GRANT EXECUTE ON [InsertTrackingAndStatus] TO [WFServiceOperators]
    GRANT CONTROL, REFERENCES ON TYPE::[InstanceStatusValues] TO [WFServiceOperators]
    GRANT CONTROL, REFERENCES ON TYPE::[MetadataValues] TO [WFServiceOperators]
    GRANT CONTROL, REFERENCES ON TYPE::[MetadataValuesWithInstanceId] TO [WFServiceOperators]
    GRANT EXECUTE ON [OnInstanceEndedWithStatusDetail] TO [WFServiceOperators]
    GRANT EXECUTE ON [OverrideTrackingAndStatus] TO [WFServiceOperators]
    GRANT EXECUTE ON [ResetInstancesToNotStarted] TO [WFServiceOperators]
    GRANT CONTROL, REFERENCES ON TYPE::[StatusHistoryRecordValues] TO [WFServiceOperators]
    GRANT CONTROL, REFERENCES ON TYPE::[TrackingRecordValues] TO [WFServiceOperators]
    GRANT EXECUTE ON [UpdateInstanceWorkflowStatus] TO [WFServiceOperators]
    GRANT CONTROL, REFERENCES ON TYPE::[Variables] TO [WFServiceOperators]
    GRANT CONTROL, REFERENCES ON TYPE::[WorkflowIds] TO [WFServiceOperators]
    I ran the script against both 'WFInstanceManagementDB' and 'WFResourceManagementDB'. I also ran it against 'WFManagementDB', but the script didn't generate any GRANT commands for that database.
    So I enabled the EXEC command and reran the script against both databases. Almost immediately I could see a drop in CPU utilization on our workflow server. Also the errors disappeared from the Event Log. To be safe I also rebooted the server.
    This seems to have fixed our problem. I'd still like to have an official KB article or update for this problem, though.

  • Workflow Manager with Project Server error Exception Starting Workflow: The value for column _WORKFLOW_INSTANCE_UID_ in table _WorkflowInstance_ is DBNull

    Hello,
    The project server workflows were running fine on my servers (2 App and 2 WFE). suddenly workflows are not working anymore.
    and I am getting the below error:
    DBNull.. Trace: at Microsoft.Office.Project.Server.Schema.WorkflowDataSet.WorkflowInstanceRow.get_WORKFLOW_INSTANCE_UID() at Microsoft.Office.Project.Server.BusinessLayer.Workflow.StartWorkflow(Guid projectGuid, Guid enterpriseProjectTypeUid, Boolean
    isNewProject, Guid previousEntepriseProjectTypeUid, Boolean skipStage, Guid stageToSkipTo):
    WorkflowExceptionStartingWorkflow (35115). Details: id='35115' name='WorkflowExceptionStartingWorkflow' uid='047a6f2d-8a44-e411-8bf4-0050568b37eb'.
    I checked all DBs; all running fine. Also I tried to re-register the workflow with my site collection. but nothing worked.
    Any suggestions?
    Twitter : @MShoubaki | http://jo.linkedin.com/in/mshoubaki

    Hi Mohammad, 
    I was able to resolve my issue by installing KB2880963.  I did not have any of the other updates mentioned installed, but it did resolve the issue. 
    Note: I did need to restart my servers.  
    See Below from
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/b189e4b8-bb9e-4ade-a3d5-cd2e0f90e93f/workflow-not-working-after-installing-service-pack-1-and-patches?forum=sharepointadmin 
    Here is
    the security update which you will need to install.
    Update 2880963 for SharePoint Server 2013
    http://support.microsoft.com/kb/2880963
    Chcek the link for details.
    http://expertsharepoint.blogspot.de/2014/08/workflow-not-working-after-installing.html

  • Workflow Manager for SP2013. The remote server returned an error: (500) Internal Server Error.

    I am *almost* all the way through provisioning my on premise SP 2013 farm for SharePoint 2013 Workflows.  Workflow manager is installed alongside Service Bus.  Workflow Manager client is installed on the SP servers.  I built a new simple list-based
    workflow in SP Designer 2013, saved it, and published it without any errors.  However, when I go back to the list in my portal and try to run the workflow, I get the "Sorry, something went wrong" page, and the logs say this:
    05/15/2013 12:41:05.07  w3wp.exe (0x071C)                        0x085C SharePoint Foundation        
     Runtime                        tkau Unexpected System.Net.WebException: The remote server returned an error: (500) Internal Server
    Error.    at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)     at Microsoft.Workflow.Client.HttpGetResponseAsyncResult`1.End(IAsyncResult result)     at Microsoft.Workflow.Client.ClientHelpers.SendRequest[T](HttpWebRequest
    request, T content) 27be1b9c-f990-f096-34a8-7ac8816bc7a5
    05/15/2013 12:41:05.08  w3wp.exe (0x071C)                        0x085C SharePoint Foundation        
     General                        ajlz0 High     Getting Error Message for Exception System.Web.HttpUnhandledException
    (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> Microsoft.Workflow.Client.InternalServerException: Exception thrown from the data layer. For more details, please see the server logs. HTTP headers received from the server
    - ActivityId: 0c03f692-8153-43a7-bed5-096214b06168. NodeId: VM22. Scope: /SharePoint/default/d386fdc7-ea7b-4d46-9a39-5c114096eef8/f203a564-e83a-47a3-b11b-e432ac1e6dab. Client ActivityId : 27be1b9c-f990-f096-34a8-7ac8816bc7a5. ---> System.Net.WebException:
    The remote server returned an error: (500) Internal Server Error.     at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)     at Microsoft.Workflow.Client.HttpGetResponseAsyncResult`1.End(... 27be1b9c-f990-f096-34a8-7ac8816bc7a5
    05/15/2013 12:41:05.08* w3wp.exe (0x071C)                        0x085C SharePoint Foundation        
     General                        ajlz0 High     ...IAsyncResult result)     at Microsoft.Workflow.Client.ClientHelpers.SendRequest[T](HttpWebRequest
    request, T content)     --- End of inner exception stack trace ---     at Microsoft.Workflow.Client.ClientHelpers.SendRequest[T](HttpWebRequest request, T content)     at Microsoft.Workflow.Client.InstanceManager.GetInternal(Int32
    skip, Int32 count, String workflowName, WorkflowInstanceStatus workflowStatus, IDictionary`2 activationMetadataFilter)     at Microsoft.SharePoint.WorkflowServices.FabricWorkflowInstanceProvider.EnumerateByMonitoringParameter(Guid monitoringParameter,
    Int32 offset, Int32 count, Boolean checkPermissions)     at Microsoft.SharePoint.WorkflowServices.FabricWorkflowInstanceProvider.EnumerateInstancesForListItem(Guid listId, Int32 itemId, Int32 offset)     at Microsoft.Sh... 27be1b9c-f990-f096-34a8-7ac8816bc7a5
    05/15/2013 12:41:05.08* w3wp.exe (0x071C)                        0x085C SharePoint Foundation        
     General                        ajlz0 High     ...arePoint.WorkflowServices.FabricWorkflowInstanceProvider.EnumerateInstancesForListItem(Guid
    listId, Int32 itemId)     at Microsoft.SharePoint.WorkflowServices.ApplicationPages.WorkflowPageBase.ConstructStatusArraysWF4(ArrayList running, ArrayList completed, Boolean onlyMyWorkflows)     at Microsoft.SharePoint.WorkflowServices.ApplicationPages.WorkflowPage.ConstructStatusArrays()    
    at Microsoft.SharePoint.WorkflowServices.ApplicationPages.WorkflowPage.OnLoad(EventArgs e)     at System.Web.UI.Control.LoadRecursive()     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint,
    Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.HandleError(Exception e)     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStages... 27be1b9c-f990-f096-34a8-7ac8816bc7a5
    05/15/2013 12:41:05.08* w3wp.exe (0x071C)                        0x085C SharePoint Foundation        
     General                        ajlz0 High     ...AfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest(Boolean
    includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest()     at System.Web.UI.Page.ProcessRequest(HttpContext context)     at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()    
    at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) 27be1b9c-f990-f096-34a8-7ac8816bc7a5
    05/15/2013 12:41:05.08  w3wp.exe (0x071C)                        0x085C SharePoint Foundation        
     General                        aat87 Monitorable   27be1b9c-f990-f096-34a8-7ac8816bc7a5
    Some sort of "general server error" returns a 500 code, but I can't tell from this what the problem(s) might be. Has anyone seen this before?
    Thanks.

    Go to the server running Workflow Manager and open the Event Viewer; Applications and Services Logs; Microsoft-Workflow; Operational; and look for the underlying error.  In our case, the CU for Workflow Manager did something to the SQL permissions and
    we ended up using the workaraound described here:
    http://social.msdn.microsoft.com/Forums/windowsazure/en-US/054d2a58-8847-4a6a-b1ab-05a79f49fe65/workflow-manager-cumulative-update-february-error?forum=wflmgr
    Joe

  • Errors when pairing Workflow Manager 1.0 with Sharepoint 2013 or trying to run C# samples to directly communicate with workflow manager

    When I try with Register-SPWorkflowService for SP2013 integration or run C# samples for workflow manager 1.0 I get
    "The  remote server returned an error: (404) Not found".
    With C# sample code runs,
    Scope '/$Activities' was not found.  HTTP headers received from the server - ActivityId: e268765f-9d95-47ed-81fd-c4b38f40bfe0. NodeId: XXXX. Scope: /$Activities/...
    The inner exception is:
    The remote server returned an error: (404) Not Found.
    We have got stuck here for a couple of days and...
    The workflow server runs on a dedicated machine than the SQL server for workflow farm DBs...
    I found one similar complain for the pre-release versions of the workflow and service bus etc.
    Help please...
    muharrem
    Muharrem

    Hi,I had already done disableloopbackcheck and it did not matter.No problem with creating scopes (using powershell) but pairing fails anyway.Here is the config from a local explorer connection to the HTTPS port:(And following it, you may see the result of
    a scope enumerator script)
    <?xml version="1.0"?>
    <ScopeInfo xmlns="http://schemas.microsoft.com/workflow/2012/xaml/activities" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
    <ChildScopeCount>3</ChildScopeCount>
    <DefaultWorkflowConfiguration/>
    <Description>For / sample only</Description>
    <LastModified>2013-11-08T21:22:00.967</LastModified>
    <LastRevised>2013-11-08T00:04:31.88</LastRevised>
    <Path>/</Path>
    <SecurityConfigurations>
    <ScopedSecurityConfiguration i:type="WindowsSecurityConfiguration">
    <Name>Microsoft.Workflow.Management.Security.WindowsSecurityConfiguration</Name>
    <WorkflowAdminGroupName>altemis\WorkflowAdmins</WorkflowAdminGroupName>
    </ScopedSecurityConfiguration>
    </SecurityConfigurations><
    Status>Active</Status>
    </ScopeInfo>
    PS C:\Shared> C:\Shared\WF Script-Enumaret Scopes.ps1
    Name:
    Path: /
    Status: Active
    User Comments: For / sample only
    Parent: None
    Children: 3
    Exception calling "GetChildScopes" with "0" argument(s): "Scope '/$ChildScopes' was not found.  HTTP headers received from 
    the server - ActivityId: 616224db-0321-450a-92ef-f03384c008a2. NodeId: ALTEMIS-SVR02. Scope: /$ChildScopes. Client 
    ActivityId : 649dba85-dc89-0002-d9bf-9d6489dcce01."
    At C:\Shared\WF Script-Enumaret Scopes.ps1:21 char:9
    +         $manager.GetChildScopes() | % { WriteScopeInfo $scopeUri $_.Path $scope. ...
    +         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
        + FullyQualifiedErrorId : ScopeNotFoundException
    Muharrem

  • Profile Manager Service stopped "error reading settings"

    Hello to all.
    from yesterday we are not be able to start the Profile Manager Service.
    Multiple errors occured on the server while reading settings message.
    The log of the Profile manager gives us the below
    Feb 14 10:16:48 elserverx.elhsa.gr ProfileManager[208] <Info>: Completed in 624ms (View: 0, DB: 3) | 200 OK [https://elserverx.elhsa.gr/magic/do_magic]
    Feb 14 10:17:43 elserverx.elhsa.gr ruby[204] <Error>: Check-in to the service com.apple.system.opendirectoryd.api failed. This is likely because you have either unloaded the job or the MachService has the ResetAtClose attribute specified in the launchd.plist. If present, this attribute should be removed.
    Feb 14 10:17:43 elserverx.elhsa.gr ruby[204] <Error>: error communicating with opendirectoryd: Connection invalid
    Feb 14 10:17:43 elserverx.elhsa.gr ruby[207] <Error>: Check-in to the service com.apple.system.opendirectoryd.api failed. This is likely because you have either unloaded the job or the MachService has the ResetAtClose attribute specified in the launchd.plist. If present, this attribute should be removed.
    Feb 14 10:17:43 elserverx.elhsa.gr ruby[207] <Error>: error communicating with opendirectoryd: Connection invalid
    Feb 14 10:17:43 elserverx.elhsa.gr ruby[203] <Error>: Check-in to the service com.apple.system.opendirectoryd.api failed. This is likely because you have either unloaded the job or the MachService has the ResetAtClose attribute specified in the launchd.plist. If present, this attribute should be removed.
    Feb 14 10:17:43 elserverx.elhsa.gr ruby[203] <Error>: error communicating with opendirectoryd: Connection invalid
    Feb 14 10:17:43 elserverx.elhsa.gr ruby[206] <Error>: Check-in to the service com.apple.system.opendirectoryd.api failed. This is likely because you have either unloaded the job or the MachService has the ResetAtClose attribute specified in the launchd.plist. If present, this attribute should be removed.
    Feb 14 10:17:43 elserverx.elhsa.gr ruby[206] <Error>: error communicating with opendirectoryd: Connection invalid
    Feb 14 10:17:43 elserverx.elhsa.gr ruby[208] <Error>: Check-in to the service com.apple.system.opendirectoryd.api failed. This is likely because you have either unloaded the job or the MachService has the ResetAtClose attribute specified in the launchd.plist. If present, this attribute should be removed.
    Feb 14 10:17:43 elserverx.elhsa.gr ruby[208] <Error>: error communicating with opendirectoryd: Connection invalid
    and the open directory log gives us the below
    2013-02-14 12:06:28.963252 EET - Discovered configuration for node name '/Search' at path '/Library/Preferences/OpenDirectory/Configurations//Search.plist'
    2013-02-14 12:06:28.963265 EET - Registered node with name '/Search'
    2013-02-14 12:06:32.443127 EET - Discovered configuration for node name '/LDAPv3/127.0.0.1' at path '/Library/Preferences/OpenDirectory/Configurations/LDAPv3/127.0.0.1.plist'
    2013-02-14 12:06:32.443197 EET - Registered subnode with name '/LDAPv3/127.0.0.1'
    2013-02-14 12:06:32.445031 EET - Loaded bundle at path '/System/Library/OpenDirectory/Modules/legacy.bundle'
    2013-02-14 12:06:32.447440 EET - Loaded bundle at path '/System/Library/OpenDirectory/Modules/search.bundle'
    2013-02-14 12:06:32.452261 EET - Loaded bundle at path '/System/Library/OpenDirectory/Modules/PlistFile.bundle'
    2013-02-14 12:06:32.454005 EET - Loaded bundle at path '/System/Library/OpenDirectory/Modules/FDESupport.bundle'
    2013-02-14 12:06:32.474804 EET - Loaded bundle at path '/System/Library/OpenDirectory/Modules/ConfigurationProfiles.bundle'
    2013-02-14 12:06:32.475597 EET - Registered subnode with name '/Local/Default'
    2013-02-14 12:06:33.449683 EET - '/Search' has registered, loading additional services
    2013-02-14 12:06:33.449695 EET - Initialize augmentation support
    2013-02-14 12:06:33.453505 EET - Loaded bundle at path '/System/Library/OpenDirectory/Modules/SystemCache.bundle'
    2013-02-14 12:06:33.456591 EET - Loaded bundle at path '/System/Library/OpenDirectory/Modules/ldap.bundle'
    2013-02-14 12:06:33.461349 EET - Successfully registered for Kernel identity service requests
    2013-02-14 12:06:33.461365 EET - Adjusting kernel ID cache (100 -> 250) and membership cache (100 -> 500)
    2013-02-14 12:06:35.539007 EET - Loaded bundle at path '/System/Library/OpenDirectory/Modules/AppleODClientLDAP.bundle'
    2013-02-14 12:06:35.541877 EET - Loaded bundle at path '/System/Library/OpenDirectory/Modules/AppleODClientPWS.bundle'
    2013-02-14 12:06:38.368985 EET - 28.20 - Client: opendirectoryd, UID: 0, EUID: 0, GID: 0, EGID: 0
    2013-02-14 12:06:38.368985 EET - 28.20, Module: AppleODClientLDAP - unable to create LDAP connection context - no server specified
    2013-02-14 12:06:38.368992 EET - 28.20 - Client: opendirectoryd, UID: 0, EUID: 0, GID: 0, EGID: 0
    2013-02-14 12:06:38.368992 EET - 28.20, Module: AppleODClientLDAP - unable to open connection to LDAP server - unable to create connection context
    2013-02-14 12:06:43.535973 EET - Loaded bundle at path '/System/Library/OpenDirectory/Modules/configure.bundle'
    2013-02-14 12:06:43.537082 EET - Loaded bundle at path '/System/Library/OpenDirectory/Modules/keychain.bundle'
    2013-02-14 12:06:43.545959 EET - Loaded bundle at path '/System/Library/OpenDirectory/Modules/ActiveDirectory.bundle
    Can you please help us with this.
    Any ideas????
    Thank you

    We have just faced similar issue - did you manage to find any solution?

  • Facing some problem while configuring Workflow Manager 1.0.

    Hi,
    I am facing some problem while configuring Workflow Manager 1.0. in my farm.
    Scenario is,
    I have installed and configured workflow manager in my farm, it was working well with no issue. But one of team member played with AD and deleted Farm administrator's entry from AD by mistake. So suddenly workflows get affected and stopped working. 
    Then I added administrator entry in AD, uninstalled the Workflow Manager and installed it again. But now while configuring workflow manager I am facing some issues that "Failure to adding user in BUILTIN\Administrative group. Please add it manually" 
    And after sometime it shows another error message that, "Starting service Service Bus Massage broken failed: Timed out has expired, the operation has not been completed" 
    If I go for services then "Service bus Message broker" service is not running properly (Its status is just showing "Starting")  and don't starts.
    I have also added the user in BUILTIN\Administrator, IIS_IUSER, WSS_WPG group of the machine from computer manager - user and groups. 
    Also given permission to databases, and assign role of sysadmin and dbcreator to user
    I also tried following steps    
        1) Stop all services associated to workflows
        2) Uninstalled workflow manager
        3) Deleted all databases associated with workflows
        4) Installed workflow manager and tried to configure.
    But showing same error. 
    If I use another SharePoint server farm to configure workflows, there I am not getting first error of adding user to BUILTIN\Administrator group. but second error remains same.
    We having SQL server and Active directory at another machine and FARM at another machine, if I use local admin for configuration of the workflows (as local admin can start any services) but entry of local admin is not Active directory so can not assign SQL's
    sysadmin, and dbcreator role to local admin.
    I am attaching snapshot of error for better understanding.
    Your help will be very precious to me. 
    Thanks,
    Rajesh
    Rajesh Agravat

    Rajesh
    Check to see what the service accounts are being used for these Workflow Manager 1.0 services:
    Service Bus Message Broker
    Service Bus Gateway
    Workflow Manager Backend
    All of these should be running and your workflow service account should be running all of these.  If any are still configured under the old service account, they'll need to be updated.  Next, check to see what service accounts have access to the
    Workflow Manager 1.0 databases:
    SbGatewayDatabase
    SbManagement
    SbMessageContainer
    WFInstanceManagement
    WFManagement
    WFResourceManagement
    The Workflow Manager service account should be mapped as the DBO for all of these.  if any are still configured under the old service account, they'll need to be updated.
    Given the complete loss of the original workflow service account, and the resultant impact on security configuration throughout the workflow farm, I would recommend performing a re-installation.  Do it thus:
    Launch Workflow Manager Configuration Wizard
    Select the Leave Workflow Manager Farm
    Stop all workflow services (see above list)
    Repeat steps 1-3 for each instance of Workflow Manager 1.0 Server installed.
    Delete all Workflow Manager databases (see above list).
    reboot.
    Start new installation.

  • Workflow Manager 1.0 configuration- Specified RunAs account is invalid

    Hello - I am trying to install and configure Workflow manager 1.0. As part of workflow manager configuration specifying the user id in
    Configure Service Account  section throwing error as "Specified RunAs account is invalid".
    I tried different ways and means suggested in forums and KBs - but I think it is unable to validate the user in Active Directory. Our Active Directory is AD 2003 functional level and wondering it has any issues with Workflow manager 1.0?
    Here are the environment details:
    WF Machine: Windows Server 2008 R2 SP1
    AD: Active Directory 2003
    Workflow Manager 1.0 installed and also applied the below latest workflow and service bus hotfixes.
    http://support.microsoft.com/kb/2799754; 
    http://support.microsoft.com/kb/2799752
    Also moved the service account to the default OU=Users container in AD as specified in below forum but no luck.
    http://social.msdn.microsoft.com/Forums/en-US/servbus/thread/3d803e15-606a-4f06-96fe-97c23ad3c01a
    I am not sure where the issue is wondering if any one has run into similar issue. Appreciate any feedback.

    Thanks for your response.
    No it still didnt work, we right clicked the users OU, provided read permissions on it directly not from any groups. as well as for computers OU.
    For me it is not showing invalid user, but wizard crashes as soon as we enter the service account details in the wizard. may be since the solution you are providing is not working for me.
    http://social.technet.microsoft.com/Forums/office/en-US/d70662fc-8e10-4862-975d-e441bf9c32f0/what-permission-does-the-service-account-requires-on-ad-for-the-workflow-manager-10-to-be?forum=sharepointadmin
    However we had one other test account which has full control on many areas is able to pass thru in this wizard with out crashing.
    We arent able to get the same permissions applied for prod account as it isnt right to simply take elevated permissions full control on AD Objects.
    Windows/AD team is looking for specific permission which this workflow manager requires to provide access.
    I dont see this documented with microsoft Either.
    SQL DB creation ability, Domain Account, Farm admin - is the criteria i believe.

  • Unable to find the User Named Account Name@Domain Name while Configuring Workflow Manager

    Hi,
    I have installed Work Flow Manager,Service Bus and its Cumulative Updates.
    While Configuring Workflow Manger using Workflow Manager configuration wizard i am getting the error while creating a Service Bus Namespace.
    I have provided the Service Accounts for both Workflow Manager and Service Bus as Domain\Account instead of
    Account@Domain.
    While looking in to the Power Shell scripts that are poupulated by the GUI i have identified that
    Account@Domain is appended to the ManageUsers switch while creating a Service Bus Namespace and the GUI configuration is failing.
        New-SBNamespace -Name 'WorkflowDefaultNamespace' -AddressingScheme 'Path' -ManageUsers 'Domain\Account','Account@Domain' -Verbose;
    So i need to modify the Powershell script as below and need to run the Powershell scripts for configuring Workflow Manager.
    Is this a bug in GUI Workflow Configuration Wizard or am i doing something wrong.
    Please help.
        New-SBNamespace -Name 'WorkflowDefaultNamespace' -AddressingScheme 'Path' -ManageUsers 'Domain\Account' -Verbose;
    Scripts Populated from GUI modified for Making it working:
    # To be run in Workflow Manager PowerShell console that has both Workflow Manager and Service Bus installed.
    # Create new SB Farm
    $SBCertificateAutoGenerationKey = ConvertTo-SecureString -AsPlainText  -Force  -String 'Run As Password' -Verbose;
    New-SBFarm -SBFarmDBConnectionString 'Data Source=Server Name;Initial Catalog=SbManagementDB;Integrated Security=True;Encrypt=False' -InternalPortRangeStart 9000 -TcpPort 9354 -MessageBrokerPort 9356 -RunAsAccount 'Domain\Account' -AdminGroup 'Domain\Domain
    Group' -GatewayDBConnectionString 'Data Source=Server Name;Initial Catalog=SbGatewayDatabase;Integrated Security=True;Encrypt=False' -CertificateAutoGenerationKey $SBCertificateAutoGenerationKey -MessageContainerDBConnectionString 'Data Source=Server Name;Initial
    Catalog=SBMessageContainer01;Integrated Security=True;Encrypt=False' -Verbose;
    # To be run in Workflow Manager PowerShell console that has both Workflow Manager and Service Bus installed.
    # Create new WF Farm
    $WFCertAutoGenerationKey = ConvertTo-SecureString -AsPlainText  -Force  -String 'Run As Password' -Verbose;
    New-WFFarm -WFFarmDBConnectionString 'Data Source=Server Name;Initial Catalog=WFManagementDB;Integrated Security=True;Encrypt=False' -RunAsAccount 'Domain\Account' -AdminGroup 'Domain\Domain Group' -HttpsPort 12290 -HttpPort 12291 -InstanceDBConnectionString
    'Data Source=Server Name;Initial Catalog=WFInstanceManagementDB;Integrated Security=True;Encrypt=False' -ResourceDBConnectionString 'Data Source=Server Name;Initial Catalog=WFResourceManagementDB;Integrated Security=True;Encrypt=False' -CertificateAutoGenerationKey
    $WFCertAutoGenerationKey -Verbose;
    # Add SB Host
    $SBRunAsPassword = ConvertTo-SecureString -AsPlainText  -Force  -String 'Run As Password' -Verbose;
    Add-SBHost -SBFarmDBConnectionString 'Data Source=Server Name;Initial Catalog=SbManagementDB;Integrated Security=True;Encrypt=False' -RunAsPassword $SBRunAsPassword -EnableFirewallRules $true -CertificateAutoGenerationKey $SBCertificateAutoGenerationKey -Verbose;
    Try
        # Create new SB Namespace
        New-SBNamespace -Name 'WorkflowDefaultNamespace' -AddressingScheme 'Path' -ManageUsers 'Domain\Account' -Verbose;
        Start-Sleep -s 90
    Catch [system.InvalidOperationException]
    # Get SB Client Configuration
    $SBClientConfiguration = Get-SBClientConfiguration -Namespaces 'WorkflowDefaultNamespace' -Verbose;
    # Add WF Host
    $WFRunAsPassword = ConvertTo-SecureString -AsPlainText  -Force  -String 'Run As Password' -Verbose;
    Add-WFHost -WFFarmDBConnectionString 'Data Source=Server Name;Initial Catalog=WFManagementDB;Integrated Security=True;Encrypt=False' -RunAsPassword $WFRunAsPassword -EnableFirewallRules $true -SBClientConfiguration $SBClientConfiguration -EnableHttpPort 
    -CertificateAutoGenerationKey $WFCertAutoGenerationKey -Verbose;
    Thanks, Vijay Arockiasamy

    Hi Vijay
    uninstall this and install the one labeled Refresh 1
    Kind Regards,
    John Naguib
    Senior Consultant
    John Naguib Blog
    John Naguib Twitter
    Please remember to mark this as answered if it helped you

  • Workflow Manager 1.0 will install but NOT configure.

    Hello everyone,
         I have successfully installed Workflow Manager 1.0 (and its prerequisites) on my Server 2008 R2 SP1 machine
    that is hosting Sharepoint 2013.  I attempt to go into the Workflow Manager Configuration.  That comes up and asks me if I want to Create new farm with Default Settings, New Farm with custom settings, or existing farm.  I've tried both Default
    settings AND Custom settings.
        When the configuration wizard comes up, I attempt to fill out the necessary information.  It seems to connect
    to the SQL server without a problem.  I only run into an issue when setting the USER ID.  The program totally freezes up and force closes. 
        I have verified that the USERID is in the correct format and tried multiple different formats.  The problem
    is that the moment I move the cursor from the USERID field to ANY other field, the program force closes.  I'm not able to hit submit, I'm not able to change any other options.  The moment USERID is manipulated or the cursor LEAVES the USERID field,
    the program force closes.  It won't even allow me to put in a password before it force closes.
         Customer domain is running in Windows Server 2003 Enterprise Edittion SP2.
    Any ideas?
    Thank you very much!
    I have copied the errors from event viewer below:
    APPLICATION ERROR
    Faulting application name: Microsoft.Workflow.Deployment.ConfigWizard.exe, version: 1.0.20922.0, time stamp: 0x505e1b30
    Faulting module name: KERNELBASE.dll, version: 6.1.7601.17965, time stamp: 0x506dcae6
    Exception code: 0xe0434352
    Fault offset: 0x000000000000bccd
    Faulting process id: 0x17f8
    Faulting application start time: 0x01cddee198ece72e
    Faulting application path: C:\Program Files\Workflow Manager\1.0\Microsoft.Workflow.Deployment.ConfigWizard.exe
    Faulting module path: C:\Windows\system32\KERNELBASE.dll
    Report Id: 22ab8b69-4ad5-11e2-af8f-005056965915
    .NET Runtime Error
    Application: Microsoft.Workflow.Deployment.ConfigWizard.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.Runtime.InteropServices.COMException
    Stack:
       at System.DirectoryServices.AccountManagement.PrincipalContext.DoLDAPDirectoryInitNoContainer()
       at System.DirectoryServices.AccountManagement.PrincipalContext.DoDomainInit()
       at System.DirectoryServices.AccountManagement.PrincipalContext.Initialize()
       at System.DirectoryServices.AccountManagement.PrincipalContext.get_QueryCtx()
       at System.DirectoryServices.AccountManagement.Principal.FindByIdentityWithTypeHelper(System.DirectoryServices.AccountManagement.PrincipalContext, System.Type, System.Nullable`1<System.DirectoryServices.AccountManagement.IdentityType>, System.String,
    System.DateTime)
       at System.DirectoryServices.AccountManagement.UserPrincipal.FindByIdentity(System.DirectoryServices.AccountManagement.PrincipalContext, System.String)
       at Microsoft.ServiceBus.Commands.Common.SecurityHelper.IsUserValid(System.DirectoryServices.AccountManagement.PrincipalContext, System.String)
       at Microsoft.ServiceBus.Commands.Common.SecurityHelper.IsDomainUserValid(System.String, System.String)
       at Microsoft.ServiceBus.Commands.Common.ValidateUserAttribute.Validate(System.String)
       at Microsoft.Deployment.ConfigWizard.UICommon.AccountDetailsViewModel.ValidateDomainUser()
       at Microsoft.Deployment.ConfigWizard.UICommon.AccountDetailsControl.UserIdTextBox_LostFocus(System.Object, System.Windows.RoutedEventArgs)
       at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)
       at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs)
       at System.Windows.Controls.Primitives.TextBoxBase.OnLostFocus(System.Windows.RoutedEventArgs)
       at System.Windows.UIElement.IsFocused_Changed(System.Windows.DependencyObject, System.Windows.DependencyPropertyChangedEventArgs)
       at System.Windows.DependencyObject.OnPropertyChanged(System.Windows.DependencyPropertyChangedEventArgs)
       at System.Windows.FrameworkElement.OnPropertyChanged(System.Windows.DependencyPropertyChangedEventArgs)
       at System.Windows.Controls.TextBox.OnPropertyChanged(System.Windows.DependencyPropertyChangedEventArgs)
       at System.Windows.DependencyObject.NotifyPropertyChange(System.Windows.DependencyPropertyChangedEventArgs)
       at System.Windows.DependencyObject.UpdateEffectiveValue(System.Windows.EntryIndex, System.Windows.DependencyProperty, System.Windows.PropertyMetadata, System.Windows.EffectiveValueEntry, System.Windows.EffectiveValueEntry ByRef, Boolean, Boolean,
    System.Windows.OperationType)
       at System.Windows.DependencyObject.ClearValueCommon(System.Windows.EntryIndex, System.Windows.DependencyProperty, System.Windows.PropertyMetadata)
       at System.Windows.DependencyObject.ClearValue(System.Windows.DependencyPropertyKey)
       at System.Windows.Input.FocusManager.OnFocusedElementChanged(System.Windows.DependencyObject, System.Windows.DependencyPropertyChangedEventArgs)
       at System.Windows.DependencyObject.OnPropertyChanged(System.Windows.DependencyPropertyChangedEventArgs)
       at System.Windows.FrameworkElement.OnPropertyChanged(System.Windows.DependencyPropertyChangedEventArgs)
       at System.Windows.DependencyObject.NotifyPropertyChange(System.Windows.DependencyPropertyChangedEventArgs)
       at System.Windows.DependencyObject.UpdateEffectiveValue(System.Windows.EntryIndex, System.Windows.DependencyProperty, System.Windows.PropertyMetadata, System.Windows.EffectiveValueEntry, System.Windows.EffectiveValueEntry ByRef, Boolean, Boolean,
    System.Windows.OperationType)
       at System.Windows.DependencyObject.SetValueCommon(System.Windows.DependencyProperty, System.Object, System.Windows.PropertyMetadata, Boolean, Boolean, System.Windows.OperationType, Boolean)
       at System.Windows.DependencyObject.SetValue(System.Windows.DependencyProperty, System.Object)
       at System.Windows.FrameworkElement.OnGotKeyboardFocus(System.Object, System.Windows.Input.KeyboardFocusChangedEventArgs)
       at System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object)
       at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)
       at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs)
       at System.Windows.UIElement.RaiseTrustedEvent(System.Windows.RoutedEventArgs)
       at System.Windows.Input.InputManager.ProcessStagingArea()
       at System.Windows.Input.KeyboardDevice.ChangeFocus(System.Windows.DependencyObject, Int32)
       at System.Windows.Input.KeyboardDevice.Focus(System.Windows.DependencyObject, Boolean, Boolean, Boolean)
       at System.Windows.Input.KeyboardDevice.Focus(System.Windows.IInputElement)
       at System.Windows.UIElement.Focus()
       at System.Windows.Input.KeyboardNavigation.Navigate(System.Windows.DependencyObject, System.Windows.Input.TraversalRequest, System.Windows.Input.ModifierKeys, System.Windows.DependencyObject)
       at System.Windows.Input.KeyboardNavigation.Navigate(System.Windows.DependencyObject, System.Windows.Input.Key, System.Windows.Input.ModifierKeys)
       at System.Windows.Input.KeyboardNavigation.ProcessInput(System.Windows.Input.InputEventArgs)
       at System.Windows.Input.InputManager.RaiseProcessInputEventHandlers(System.Windows.Input.ProcessInputEventHandler, System.Windows.Input.ProcessInputEventArgs)
       at System.Windows.Input.InputManager.ProcessStagingArea()
       at System.Windows.Input.InputManager.ProcessInput(System.Windows.Input.InputEventArgs)
       at System.Windows.Interop.HwndKeyboardInputProvider.ReportInput(IntPtr, System.Windows.Input.InputMode, Int32, System.Windows.Input.RawKeyboardActions, Int32, Boolean, Boolean, Int32)
       at System.Windows.Interop.HwndKeyboardInputProvider.ProcessKeyAction(System.Windows.Interop.MSG ByRef, Boolean ByRef)
       at System.Windows.Interop.HwndSource.CriticalTranslateAccelerator(System.Windows.Interop.MSG ByRef, System.Windows.Input.ModifierKeys)
       at System.Windows.Interop.HwndSource.OnPreprocessMessage(System.Object)
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
       at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
       at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
       at System.Windows.Threading.Dispatcher.Invoke(System.Windows.Threading.DispatcherPriority, System.Delegate, System.Object)
       at System.Windows.Interop.HwndSource.OnPreprocessMessageThunk(System.Windows.Interop.MSG ByRef, Boolean ByRef)
       at System.Windows.Interop.ComponentDispatcherThread.RaiseThreadMessage(System.Windows.Interop.MSG ByRef)
       at System.Windows.Threading.Dispatcher.TranslateAndDispatchMessage(System.Windows.Interop.MSG ByRef)
       at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
       at System.Windows.Application.RunInternal(System.Windows.Window)
       at System.Windows.Application.Run()
       at Microsoft.Workflow.Deployment.ConfigWizard.App.Main()

    Hi Scott, 
    Thank you very much.. Now I am able to run wizard.. but at the end of wizard step I am getting below error
    [Info] [1/23/2014 5:48:47 PM]: Endpoint=sb://MSPAPPS.psu.edu.sa/WorkflowDefaultNamespace;StsEndpoint=https://MSPAPPS.psu.edu.sa:9355/WorkflowDefaultNamespace;RuntimePort=9354;ManagementPort=9355
    [Info] [1/23/2014 5:48:47 PM]: Processing completed
    [Verbose] [1/23/2014 5:48:47 PM]: Validating input and configuration parameters.
    [Verbose] [1/23/2014 5:48:49 PM]: Installing auto-generated certificate.
    [Progress] [1/23/2014 5:48:49 PM]: Installing auto-generated certificate.
    [Verbose] [1/23/2014 5:48:51 PM]: Granting 'Log on as Service' privilege to the RunAs account.
    [Progress] [1/23/2014 5:48:51 PM]: Granting 'Log on as Service' privilege to the RunAs account.
    [Verbose] [1/23/2014 5:48:52 PM]: Workflow Manager configuration starting.
    [Progress] [1/23/2014 5:48:52 PM]: Workflow Manager configuration starting.
    [Verbose] [1/23/2014 5:48:55 PM]: Configuring Workflow Manager runtime settings.
    [Progress] [1/23/2014 5:48:55 PM]: Configuring Workflow Manager runtime settings.
    [Error] [1/23/2014 5:48:55 PM]: System.Management.Automation.CmdletInvocationException: The token provider was unable to provide a security token while accessing 'https://mspapps.psu.edu.sa:9355/WorkflowDefaultNamespace/$STS/Windows/'. Token provider returned
    message: 'The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.'. ---> System.UnauthorizedAccessException: The token provider was unable to provide a security token while accessing 'https://mspapps.psu.edu.sa:9355/WorkflowDefaultNamespace/$STS/Windows/'.
    Token provider returned message: 'The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.'. ---> System.IdentityModel.Tokens.SecurityTokenException: The token provider was unable to provide a security
    token while accessing 'https://mspapps.psu.edu.sa:9355/WorkflowDefaultNamespace/$STS/Windows/'. Token provider returned message: 'The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.'. ---> System.Net.WebException:
    The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.
       at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
       at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
       at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
       at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
       at System.Net.ConnectStream.WriteHeaders(Boolean async)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
       at System.Net.HttpWebRequest.GetRequestStream()
       at Microsoft.ServiceBus.TokenProviderHelper.GetWindowsAccessTokenCore(IEnumerator`1 stsUris, Func`2 uriBuilder, String requestToken, TimeSpan timeout, DateTime& expiresIn)
       --- End of inner exception stack trace ---
       at Microsoft.ServiceBus.TokenProviderHelper.ThrowException(Uri requestUri, WebException exception)
       at Microsoft.ServiceBus.TokenProviderHelper.GetWindowsAccessTokenCore(IEnumerator`1 stsUris, Func`2 uriBuilder, String requestToken, TimeSpan timeout, DateTime& expiresIn)
       at Microsoft.ServiceBus.WindowsTokenProvider.OnBeginGetWebToken(String appliesTo, String action, TimeSpan timeout, AsyncCallback callback, Object state)
       at Microsoft.ServiceBus.TokenProvider.GetWebTokenAsyncResult..ctor(TokenProvider tokenProvider, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout, AsyncCallback callback, Object state)
       at Microsoft.ServiceBus.TokenProvider.BeginGetWebToken(String appliesTo, String action, Boolean bypassCache, TimeSpan timeout, AsyncCallback callback, Object state)
       at Microsoft.ServiceBus.TokenProviderUtility.GetMessagingWebToken(ITokenProvider tokenProvider, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout)
       --- End of inner exception stack trace ---
    Server stack trace: 
       at Microsoft.ServiceBus.TokenProviderUtility.GetMessagingWebToken(ITokenProvider tokenProvider, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout)
       at Microsoft.ServiceBus.Messaging.HttpWebRequestExtensions.AddAuthorizationHeader(HttpWebRequest request, ITokenProvider tokenProvider, Uri baseAddress, String action)
       at Microsoft.ServiceBus.Messaging.ServiceBusResourceOperations.GetAsyncResult`1.<GetAsyncSteps>d__11.MoveNext()
       at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.EnumerateSteps(CurrentThreadType state)
       at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.Start()
    Exception rethrown at [0]: 
       at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
       at Microsoft.ServiceBus.NamespaceManager.OnEndTopicExists(IAsyncResult result)
       at Microsoft.ServiceBus.NamespaceManager.TopicExists(String path)
       at Microsoft.Workflow.Deployment.Commands.WorkflowServiceConfigHelper.SetWFRuntimeSettings(String resourceDBConnectionString, String config)
       at Microsoft.Workflow.Deployment.Commands.AddWFHost.CallWFRuntimeSettings(Service wfserviceInfo, String unencryptedResourceConnectionString)
       --- End of inner exception stack trace ---
       at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
       at Microsoft.Workflow.Deployment.ConfigWizard.CommandletHelper.InvokePowershell(Command command, Action`3 updateProgress)
       at Microsoft.Workflow.Deployment.ConfigWizard.ProgressPageViewModel.AddWFNode(FarmCreationModel model, Boolean isFirstCommand)

  • Oracle Service Bus configuration project deployment problem

    I cannot deploy the "OSB30 Book Conf" configuration project to the server. "The specified domain path is not a valid Oracle Service Bus domain" error appears. Where is the domain path specified? Where can I get know which paths are valid Oracle Service Bus domains?
    I am using OSB 10.3.1, WebLogic server 10.3, Oracle Workshop for WebLogic 10.3 running on RHEL4.
    Thank you.

    Your first message about "THE SPECIFIED DOMAIN PATH IS NOT A VALID ORACLE SERVICE BUS DOMAIN" is the most annoyingly stupid message and wasted days of my time when I was trying to script the creation of an OSB domain.
    The way Workshop decides that a domain is a valid OSB domain or not is by checking the config.xml for the prescense of "lib/kernel.ear" - if that's not EXACTLY like that, that it decides its not a valid domain.
    If you look in the config.xml, you must have an entry like
    <app-deployment>
    <name>XBus Kernel</name>
    <target>AdminServer</target>
    <module-type>ear</module-type>
    <source-path>C:\osb1031\osb_10.3/lib/kernelEar</source-path>
    and not something like this
    <app-deployment>
    <name>XBus Kernel</name>
    <target>AdminServer</target>
    <module-type>ear</module-type>
    <source-path>c:\domains\user_projects\applications\MyESB11g/kernelEar</source-path>
    It's all to do with the path you choose for the applications when creating the domain and there's a bug raised for it. Sounds like you're working anyway.
    Pete

Maybe you are looking for