Workflow Error in the E-Rec

Dear All,
        I am using the workflow  WS51800008 for the approval Requisition...
When i am triggering the workflow from the Manager id, it got triggered and it end up with the error in the Task TS51807979 saying "WEBSERVICE method PROCESSDIALOG cannot be executed".
Earlier it didnt got triggered, so i applied the Note 746709 to trigger the workflow.
Can anyone help me to sort this problem.
Thanks
Yogesh

Hi Yogesh,
So you try to execute the task from the R/3 inbox. This is probably the reason why it gives the error.
You should search this forum and SDN for configuring the UWL, as this task probably can only be executed from the UWL.
Regards,
Martin

Similar Messages

  • Failed to start workflow. The workflow cannot access the item that it has been applied to.

    I have a quick question for you and it would be great if you can answer me on this.
    I'm working through SharePoint Workflow issue (developed using Nintex) that started recently where people are getting workflow error and I don't see issues if I submit it myself. Current error. - "Failed to start workflow. The workflow cannot access
    the item that it has been applied to."
    I haven't made any major changes to Workflow except for changing email notification content and publishing it. My question is, do I need to publish the rest of the workflows too that are associated to the list after I publish changes of one workflow? Looks
    like users have required permissions to submit the form. Please let me know how to get rid of this error.
    smith

    Hi Smithspd,
    According to your description, my understanding is that your users got a workflow error, and the workflow is created by Nintex.
    For SharePoint Designer workflow, once we do any change in a workflow, we need to re-publish the workflow.
    For your issue, I suggest you re-publish the workflow, compare the result.
    In addition, as your workflow is created by Nintex and this forum is for SharePoint Designer, I suggest you ask Nintex support or forum for better help.  Thanks for your understanding.
    Best Regards,
    Wendy
    Wendy Li
    TechNet Community Support

  • Sharepoint 2013: Workflow Error , while trying to publish a Sharepoint 2013 Workflow, from the Sharepoint Designer 2013

    I don't know what might be wrong but I have tried everything possible I suppose. 
    Configuration: 1 App Server SharePoint Standard 2013 + SQL Server. On App Server, I have installed Workflow Manager as well.
    Installed Sharepoint Designer 2013 on my laptop. 
    Before I was able to publish the workflows, but now it refuses, thwroing me the following error:
    System.InvalidOperationException: Operation failed with error Microsoft.Workflow.Client.WorkflowCommunicationException: The request was aborted: The request was canceled. Client ActivityId : ac85cf9c-053a-e0db-1f47-608050559d31. ---> System.Net.WebException:
    The request was aborted: The request was canceled. ---> System.ServiceModel.CommunicationException: There was an error reading from the pipe: The pipe has been ended. (109, 0x6d). ---> System.IO.PipeException: There was an error reading from
    What I have tried so far:
    a. Re-installed Workflow, Service Bus, Windows Fabric, Sharepoint Designer... no luck
    b. Run the configuration script... -Force enabled... no luck
    c. Remove WF Manager, SB, etc... Deleted all WF and sb Databases from SQL, and re-installed all icluding updates... no luck
    d. Tried to run services using Farm account, still no luck.
    e. All services on the Server are running as well
    f. The workflow is checked that it is associated with the site collection.
    I don't know what else to try... seems like I am experiencing unique issue here... please help!

    One last thing I can suggest - In case if you have installed CU Update for WF manager 1.0 and service bus. Some time that creates problem, [Please take backup before make any changes] -
    - Clear everything, WF config , SharePoint WF setting, un register WF from SP , You can delete and recreate WF service Apps
    - IISreset at WF and SP server
    - Uninstall CU update for Workflow manager 1.0 and Service Bus from WF server [Control Panel - Programs - Update], you can delete all update installed
    - ReStart WF server
    - Reconfigure WF manager , Test WF sites , should return XML
    Get-WFFarm | ft HttpPort
    - Reconfigure WF at SP , Make sure should have enough free memory
    Register-SPWorkflowService –SPSite "http://SPsite/" –WorkflowHostUri "http://WFServer:12291" –AllowOAuthHttp
    http or https , depend on your configuration
    And retest from SPD again.
    Good luck:)
    Thanks
    Ganesh Jat [My Blog |
    LinkedIn | Twitter ]
    Please click 'Mark As Answer' if a post solves your problem or 'Vote As Helpful' if it was useful.

  • Workflow Error Message: System Account - The Workflow could not set Content Approval Status

    This is the first time I try an approval workflow. I am using a template in MS Word and assigned an approval workflow to it. The approval workflow is only going to one person in this case.
    When I start the work flow the following 3 error messages show up:
    Workflow Error Message: System Account - The Workflow could not set Content Approval Status. Enable content moderation for this list and run the workflow again.
    Workflow Error Message: System Account - The e-mail message cannot be sent. Make sure the e-mail has a valid recipient.
    Workflow Error Message: System Account - The e-mail message cannot be sent. Make sure the outgoing e-mail settings for the server are configured correctly.
    Thank you for your kind guidance.

    Hi,
    For the first error: Did you set Content Approval in the workflow?  If so, see if you have it in the versioning settings of the list settings.
    For the second error: double check your recipient is set up as being valid.  Did you type in the email address or is it referring to a people picker field?  also, make sure that in the workflow for the email that you actually populated it in the
    To: field.
    for the third error: I suspect that either your farm is not configured for email.  Or, this error is a knock on from the second error.  If you get the second error rectified it may clear this error.  If not then double check the email settings
    for your farm.
    Johnathan Lightfoot

  • When I try to execute any workflow I get the error "Something went wrong.."

    Hello,
    Last weekend I updated the servers farm and I executed "SharePoint 2013 products configuration wizard" But I had an error and the wizard showed this: Conpleted configuration settings will not be rolled back.
    From this moment when I try to execute any workflow in one of my site collections I always get the error "something went wrong.." Then I was checking the logs and I saw this:
    04/08/2015 08:12:18.82  w3wp.exe (0x1318)                        0x2070 SharePoint Foundation        
     General                        8nca Medium   Application error when access /_layouts/15/IniWrkflIP.aspx, Error=Requested
    registry access is not allowed.   at Microsoft.Win32.RegistryKey.OpenSubKey(String name, Boolean writable)     at Microsoft.Win32.Registry.GetValue(String keyName, String valueName, Object defaultValue)    
    at Microsoft.Office.InfoPath.Server.Util.UrlManager.<>c__DisplayClass1.<OpenFileNameMap>b__0()     at Microsoft.Office.Server.Security.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)     at Microsoft.Office.InfoPath.Server.Util.UrlManager.OpenFileNameMap()    
    at Microsoft.Office.InfoPath.Server.Util.UrlManager..cctor() 539dfa9c-f4fc-b08b-bdb7-dca4cb91a7b5
    04/08/2015 08:12:18.82  w3wp.exe (0x1318)                        0x2070 SharePoint Foundation        
     Runtime                        6616 Critical Requested registry access is not allowed. 539dfa9c-f4fc-b08b-bdb7-dca4cb91a7b5
    04/08/2015 08:12:18.82  w3wp.exe (0x1318)                        0x2070 SharePoint Foundation        
     General                        ajlz0 High     Getting Error Message for Exception System.TypeInitializationException:
    The type initializer for 'Microsoft.Office.InfoPath.Server.Util.UrlManager' threw an exception. ---> System.Security.SecurityException: Requested registry access is not allowed.     at Microsoft.Win32.RegistryKey.OpenSubKey(String name,
    Boolean writable)     at Microsoft.Win32.Registry.GetValue(String keyName, String valueName, Object defaultValue)     at Microsoft.Office.InfoPath.Server.Util.UrlManager.<>c__DisplayClass1.<OpenFileNameMap>b__0()    
    at Microsoft.Office.Server.Security.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)     at Microsoft.Office.InfoPath.Server.Util.UrlManager.OpenFileNameMap()     at Microsoft.Office.InfoPath.Server.Util.UrlManager..cctor()    
    --- End of inner exception stack tra... 539dfa9c-f4fc-b08b-bdb7-dca4cb91a7b5
    04/08/2015 08:12:18.82* w3wp.exe (0x1318)                        0x2070 SharePoint Foundation        
     General                        ajlz0 High     ...ce ---     at Microsoft.Office.InfoPath.Server.Util.UrlManager.GetConverterGeneratedFilePath(ConverterGeneratedFile
    file, Document document)     at Microsoft.Office.InfoPath.Server.SolutionLifetime.ScriptIncludes.RenderCssLinksToHeader(Control ctrl, Document document, Boolean ribbonEnabled, Boolean isDisplayMode)     at Microsoft.Office.InfoPath.Server.Controls.XmlFormView.TryToAddCssLinksToHeader()    
    at Microsoft.Office.InfoPath.Server.Controls.XmlFormView.OnDataBindHelper()     at Microsoft.Office.InfoPath.Server.Controls.XmlFormView.OnDataBinding(EventArgs e)     at System.Web.UI.WebControls.WebParts.Part.DataBind()    
    at System.Web.UI.Control.DataBindChildren()     at System.Web.UI.Control.DataBind(Boolean raiseOnDataBinding)     at System.Web.UI.Control.DataBindChildren()     at Sy... 539dfa9c-f4fc-b08b-bdb7-dca4cb91a7b5
    04/08/2015 08:12:18.82* w3wp.exe (0x1318)                        0x2070 SharePoint Foundation        
     General                        ajlz0 High     ...stem.Web.UI.Control.DataBind(Boolean raiseOnDataBinding)    
    at System.Web.UI.Control.DataBindChildren()     at System.Web.UI.Control.DataBind(Boolean raiseOnDataBinding)     at System.Web.UI.Control.DataBindChildren()     at System.Web.UI.Control.DataBind(Boolean
    raiseOnDataBinding)     at System.Web.UI.Control.DataBindChildren()     at System.Web.UI.Control.DataBind(Boolean raiseOnDataBinding)     at System.Web.UI.Control.DataBindChildren()    
    at System.Web.UI.Control.DataBind(Boolean raiseOnDataBinding)     at Microsoft.Office.Workflow.IniWrkflIPPage.LoadFromWorkflowAssociation()     at Microsoft.Office.Workflow.IniWrkflIPPage.OnLoad(EventArgs ea)    
    at System.Web.UI.Control.LoadRecursive()     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean inc... 539dfa9c-f4fc-b08b-bdb7-dca4cb91a7b5
    04/08/2015 08:12:18.82* w3wp.exe (0x1318)                        0x2070 SharePoint Foundation        
     General                        ajlz0 High     ...ludeStagesAfterAsyncPoint)     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) 539dfa9c-f4fc-b08b-bdb7-dca4cb91a7b5
    But I cannot find any solution.
    Please Help!

    Hello,
    After some troubleshooting finally I opened a case to Microsoft, finally we solved the error:
    I cleared the configuration cache:
    http://blogs.msdn.com/b/jamesway/archive/2011/05/23/sharepoint-2010-clearing-the-configuration-cache.aspx
    With this I could execute the wizard without any problem and the problem was solved.
    But if with this the problem is not fix, Apart from that, you can check this:
    Apparently, Microsoft change the number version of the SP1, then if you have the first sp1 versión, you will have problems with the wizard because is looking for the newer version.
    The first SP1 number version was:
    15.0.4569.1506
    The currently SP1 version is:
    15.0.4571.1502
    You can check your versión with this script:
    http://blogs.technet.com/b/stefan_gossner/archive/2015/04/20/powershell-script-to-display-version-info-for-sharepoint-product-and-language-packs.aspx
    Finally if you have the first version the solution is download SP1 again (newer) and install it again (it is not necessary unistall the currently SP1) When you finish, try to execute wizard again and everything will work fine.
    Hope this helps!

  • Error opening the workflow WS04200009

    Hi all,
    I am trying to open the ESS leave request workflow WS04200009 from eiter swdd ot from PFTS but it gives me the following error:
    Workflow definition 'WS04200009' not in version '0000'
    Message no. WD401
    Diagnosis
    The workflow definition with the ID WS04200009 in version 0000 could not be read from the database.
    System Response
    The call to the Workflow Builder had to be cancelled.
    Procedure
    Refer to your workflow system administrator.
    Please tell me what could be wrong???
    Thanks

    Have you checked OSS for applicable notes?
    I know you have not checked this forum to see if this question has already been answered, because I know it has. So perhaps you should try those two appraches first?
    Not that I mind you giving people the opportunity to earn some additional points, but it is boring to read the same questions over and over again. And I also think that out of respect for other people's time, and the community guidelines, you ought to at least search the forum before posting your question.

  • Unable to determine the value of component  ''! Workflow error, please help

    Hi All:
        I am getting the error "Unable to determine the value of component  ''" and workflows are not getting processed. I found OSS notes 879100 related to this issue but I am new to workflow and not sure where to start from! Here is the notes description:
    The workflow WS20500025 ('Service Connection Order Processing') encounters an error directly after being started. The following error messages are displayed in the workflow log:
    SWP102: Error at start of an IF branch
    WL821: Work item 000000100012: Object FLOWITEM method EXECUTE cannot be executed
    SWF_RUN535: Error '9' when calling service 'SO_OBJECT_SEND'
    SWF_RUN534: Problems occurred when generating a mail
    WL863: Notification of completion cannot be generated
    SWF_EXP_001073: Unable to determine the value of component 'QUOTATION'
    SWF_EXP_001072: Error in the evaluation of expression '<???>' for item 1
    SWF_RLS_001101: Operator 'GT': The value of the left operand cannot be determined
    SWP085: Error when starting work item 000000100012
    SWP010: Error when evaluating the IF condition for node 0000000075
    Other terms
    Service connection processing, service connection workflow
    Reason and Prerequisites
    This is due to a program error.
    The checks in the workflow Basis have been made stricter. A query of the type 'Quotation.number > 0' now causes an error if the container element 'Quotation' is not set. This is always the case if the workflow is is running without quotation prcessing, for instance.
    Solution
    The error is corrected in the next Support Package.
    If you want to implement the corrections manually in your system, change the condition in step 000075 of workflow WS20500025 as follows:
        &IS-U: Kundenangebot& EX
    and &IS-U: Kundenangebot.Verkaufsbeleg& > 0
    Save and activate the workflow.
    I am new to workflow and not sure where to start from! Could someone please help me with this? Rewards assured.
    Thanks.
    Mithun

    ANy ideas? Please help me if anyone knows the answer.
    Thanks.
    Mithun

  • Error in the workflow which executes background synchronous webservice task

    Hi,
    I am very new to SAP Workflows. I created a workflow with one activity step in it. The activity step actually executes a task TS77000300 (synchronous calculation - its an SAP task). When I test it. I get an error "Error when starting the service" with exception 8987, area SWF_HTTP and message 125 - Object WEBSERVICE method PROCESSBATCH cannot be executed.
    I checked in WF_EXTSRV tcode, there is an entry for the background synchronous webservice task.
    I checked in SWLWPTSSID table, there is an mapping between task-id and service id from WF_EXT SRV.
    I am not sure where its going wrong. Any help resolving this issue is appreciated. Thanks a lot.
    Regards,
    Raja

    Gurprit/All
    Thanks Gurprit for the direction.
    Even if I execute the the workflow( WS77000647 from SAP). The first step invokes Process Dialog which asks for three numbers and two operands. When I input all the input params and click calculate button, the second step which is actually the background synchronous task, results in the same error in the workflow log and in the Process Dialog page browser it says "Entries sent for calculation" with the same input screen.
    Am I missing anything here to run background synchronous task? Any help regarding this is appreciated.
    Thanks & Regards,
    Raja

  • Something went wrong. To try again, reload the page and then start the workflow, error on starting a workflow

    i have already create a custom workflow with sharepoint designer and checked for error and it seem fine. i published it on my document library so apprear the first issue : the column that contain the name of my workflow apprear and the link to start my workflow(contain
    the name of my first stap) doesn't appear. the second problem is that when i tried to start the workflow manually on a specific document i get an alert : Something went wrong. To try again, reload the
    page and then start the workflow
    i tried : -restart service bus message broker -restart service bus gateway -recycle workflowMgntpool -flushed the dsn resolver cache and the problem still occure
    on uls log viewer it seems to be an error on w3wp.exe process
    the workflow history is empty

    Hi Mokhtar,
    For your first issue, when you publish a workflow to your document library, only after you start the workflow, then the link to go on the workflow(contain the name of the workflow stage) will appear.
    For your second issue, my understanding is that you got an error when you manually start a SharePoint Designer 2013 Workflow.
    Please go to Administrative Tools->Services, make sure the following services are started.
    Workflow Manager Backend
    Service Bus Message Broker
    Service Bus Gateway
    Windows Fabric Host Service
    Here are similar posts for you as a reference:
    https://social.msdn.microsoft.com/Forums/office/en-US/12f8ae26-6889-4227-a3fc-dd29a38230a6/something-went-wrong-to-try-again-reload-the-page-and-then-start-the-workflow?forum=sharepointcustomization
    http://community.office365.com/en-us/f/154/t/277480.aspx
    If the issue still exists, please check Event Viewer to check more information about this issue.
    http://msdn.microsoft.com/en-us/library/jj193526(v=azure.10).aspx
    I hope this helps.
    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 running the expiration action and The workflow is no longer available

    I make a content type expiration policy with action is run a workflow. When the jobs run a have this error in the evnt viewer
    Error running the expiration action on item http://xxxxx/xxx/New.docx.
    Error:  System.InvalidOperationException: The workflow with id=xxxx is no longer available.
       at Microsoft.Office.RecordsManagement.PolicyFeatures.WorkflowExpirationAction.RunExpirationWithPostActions(SPListItem item, XmlNode parametersData, DateTime expireDate)
       at Microsoft.Office.RecordsManagement.PolicyFeatures.BaseExpirationAction.Microsoft.Office.RecordsManagement.PolicyFeatures.IExpirationActionWithPostActions.OnExpirationWithPostActions(SPListItem item, XmlNode parametersData, DateTime expireDate)
       at Microsoft.Office.RecordsManagement.PolicyFeatures.ExpirationTask.ExpirationActionData.RunExpirationAction(SPListItem item, DateTime expireDate)
       at Microsoft.Office.RecordsManagement.PolicyFeatures.ExpirationTask.<>c__DisplayClass19.<ProcessExpiredItems>b__17(SPListItem item)
       at Microsoft.Office.Server.Utilities.MonitoredScopeWrapper.RunWithMonitoredScope(Action code)
       at Microsoft.Office.Server.Utilities.ContentIterator.ProcessItem(SPListItem item, Boolean fIncludeFolderItems, MonitoredScopeWrapper monitoredScopeWrapper, ItemProcessor itemProcessor, ItemProcessorErrorCallout errorCallout)

    Hi,
    We have not heard from you in a couple of days.
    Please post back at your convenience if we can assist further.
    Best Regards,
    Lisa Chen
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Lisa Chen
    TechNet Community Support

  • The error about the workflow

    Hi,my experts:
       SRM5.0 ,ECS,
    In my case ,I want  implement the spending limit workflow to replace the one-step and two-step approval workflows. I  want my worflow like this:Output limit not exceeded - start 0-step-approval workflow;Output limit exceeded - start 1-step-approval workflow;
    I config the workflow like this:
      1、Deactivate the event linkage for the workflowsWS10000129 (one-step approval)、 WS10000031 (two-step approval)、 WS10000060 (0-step approval).
      2、Activate the event linkage for the workflow WS10000276 (spending limit);
    3、condition for workflow :
              WS10000276:ReqtCovRequest.TotalValue>ReqtCovRequest.SpendingLimitofRequester
                      WS10000060:ReqtCovRequest.TotalValue <= ReqtCovRequest.SpendingLimitofRequester
    4、PPOMA_BBP  :EMPLOYEE -output limit:100 usd.
                                                         - SLAPPROVER :USMANAGER
    Now,When I one shopping cart with value 80 usd,But the SC  still need to be approvaled by MANAGER.I want to know why?
      BR!Thanx!
    Alex

    Hi,
    I think it is not an error.
    Go to BBP_PD and check which workflow template is started.
    Go to SWO1 transaction, and enter Business Object BUS2121 and select test.
    Select create instance and give SC number. You can check the value of ReqtCovRequest.TotalValue and ReqtCovRequest.SpendingLimitofRequester.
    Go to SWD_COND and check the start condition.
    Regards,
    Masa

  • Error updating the process object in MSS workflow...

    Hi All,
    I copied the standard workflow 'WS18900010' and triggered the same in backend. In this the first step is to approve the form. I set the agent as WF Initiator for this step. Now I approved the form. But the workitem went into error giving the error message 'ERROR UPDATING THE PROCESS OBJECT'.
    What could be the reason for this?
    If the originator of request and approver of request is same(just for testing purpose), then may dis also result into above error?
    Please suggest.
    Guddan

    Hello,
    Please maintain this 'CL_HRASR00_POBJ_WF_EXIT' in the workflow exit for the specific task and also at the workflow header level.
    Execute the process and if still error occurs, check for HCM P&F authorization  and if it is fine, then check if the case settings are maintained correctly.
    you can find the case configuration in HCM P&F help docu.
    hope this helps.
    Best Regards
    Saujanya

  • Workflow erroring with ORA-06512 on the Reserve document activity

    Hi
    Can anyone help? We have a intermittent problem where the workflow for a requisition or PO errors with the following:-
    An Error occurred in the following Workflow.
    Item Type = POAPPRV
    Item Key = 101931-203179
    User Key =3096034
    Error Name = -6512
    Error Message = ORA-06512: at line
    Error Stack =
    Wf_Engine_Util.Function_Call(PO_REQAPPROVAL_ACTION.RESERVE_DOC, POAPPRV, 101931-203179, 101776, RUN)
    Activity Id = 101776
    Activity Label = DOC_RESERVE_PROCESS:RESERVE_DOCUMENT
    Result Code = #EXCEPTION
    Notification Id =
    Assigned User =
    It can be moved on by retrying the worklfow but we are getting alot of these and some of our POs are time critical which is getting missed by the time we have realised we have an error.
    We are currently on 11.5.10.2 and DB version 10.2.0.4 and we use RAC with 2 database teirs and 3 application teirs.
    Regards
    Ruth

    Hi Srini
    We have had a SR open from the start of March at a serverity 2 and its got nowhere. They say unless they can get a trace of it happening they cant do anything and since the problem is intermittent and not reproducable thats impossible to get as we have 800 users and between 300 to 400 pos being created a day.
    I am hoping that maybe someone may have an idea of a direction i can look at on the forum as we are pulling our hair out.
    Regards
    Ruth

  • PLSQL Clob Document in Oracle Apps Workflow throwing "Numeric or value Error " in the Notification Body

    I’m Using PLSQL Clob Document for printing data in HTML table format in the Notification Body,even PL/SQL Clob variable is capable of storing data up to 4gb ,when I’m trying to print the data greater than 32767bytes (32kb) it is throwing error “Numeric or value Error” .Please help me out to print data >32kb in the notification using document type attribute in oracle workflow.Appreciated for the Solution.
    Thanks,
    Kishore.

    Please see if these docs help.
    How to Write CLOB Data > 32K Out to a File? (Doc ID 358641.1)
    How To Write Out Multiple Clob Fields > 32k To A File in 4K chunks? (Doc ID 358781.1)
    Thanks,
    Hussein

  • Error MSB3073: The command exited with code -1

    I am getting this error while deploying the biztalk project from visual studio using Deployment Framework for Biztalk (BTDF).
    Please guide me what needs to be done. Here's the code :-
    <?xml version="1.0" encoding="utf-8"?>
    <!--
    Deployment Framework for BizTalk
    Copyright (C) 2008-14 Thomas F. Abraham, 2004-08 Scott Colestock
    -->
    <Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003" DefaultTargets="Installer" ToolsVersion="4.0">
    <PropertyGroup>
    <Configuration Condition="'$(Configuration)' == ''">Debug</Configuration>
    <Platform Condition="'$(Platform)' == ''">x86</Platform>
    <SchemaVersion>1.0</SchemaVersion>
    <ProjectName>HelloWorld</ProjectName>
    <ProjectVersion>1.0</ProjectVersion>
    <IncludeOrchestrations>False</IncludeOrchestrations>
    <IncludeTransforms>False</IncludeTransforms>
    <IncludeSSO>True</IncludeSSO>
    <UsingMasterBindings>True</UsingMasterBindings>
    <RequireXmlPreprocessDirectives>False</RequireXmlPreprocessDirectives>
    <ApplyXmlEscape>True</ApplyXmlEscape>
    <SkipIISReset>True</SkipIISReset>
    </PropertyGroup>
    <PropertyGroup>
    <!-- Properties related to building an MSI for server deployments -->
    <!-- BizTalk App Version Upgrade -->
    <!-- For each new product release to be deployed to your BizTalk servers: -->
    <!-- 1) Increment ProductVersion -->
    <!-- 2) Generate a new GUID and update ProductId with the new GUID -->
    <!-- This allows the new MSI to automatically uninstall (not undeploy!) the old MSI and install the new one. -->
    <ProductVersion>1.0.0</ProductVersion>
    <ProductId>084986b1-d675-4383-b0ed-da2e3f4e3998</ProductId>
    <!-- BizTalk App Version Upgrade -->
    <ProductName>HelloWorld for BizTalk</ProductName>
    <Manufacturer>Deployment Framework User</Manufacturer>
    <PackageDescription>HelloWorld</PackageDescription>
    <PackageComments>HelloWorld</PackageComments>
    <!-- NEVER change the ProductUpgradeCode. -->
    <ProductUpgradeCode>4975288c-1b94-4d42-868b-f166cdc02224</ProductUpgradeCode>
    </PropertyGroup>
    <!-- Under TFS Team Build, set CustomizableOutDir property to true in TFS 2005/2008/2010 UpgradeTemplate. -->
    <!-- With a workflow build, copy the default template then modify the MSBuild task for the solution build. Set OutDir to blank and -->
    <!-- CommandLineArguments to String.Format("/p:SkipInvalidConfigurations=true;TeamBuildOutDir=""{0}"" {1}", BinariesDirectory, MSBuildArguments). -->
    <PropertyGroup Condition="'$(Configuration)' == 'Debug'">
    <DeploymentFrameworkTargetsPath>$(MSBuildExtensionsPath)\DeploymentFrameworkForBizTalk\5.0\</DeploymentFrameworkTargetsPath>
    <OutputPath Condition="'$(TeamBuildOutDir)' == ''">bin\Debug\</OutputPath>
    <OutputPath Condition="'$(TeamBuildOutDir)' != ''">$(TeamBuildOutDir)</OutputPath>
    <DeployPDBsToGac>false</DeployPDBsToGac>
    </PropertyGroup>
    <PropertyGroup Condition="'$(Configuration)' == 'Release'">
    <DeploymentFrameworkTargetsPath>$(MSBuildExtensionsPath)\DeploymentFrameworkForBizTalk\5.0\</DeploymentFrameworkTargetsPath>
    <OutputPath Condition="'$(TeamBuildOutDir)' == ''">bin\Release\</OutputPath>
    <OutputPath Condition="'$(TeamBuildOutDir)' != ''">$(TeamBuildOutDir)</OutputPath>
    <DeployPDBsToGac>false</DeployPDBsToGac>
    </PropertyGroup>
    <PropertyGroup Condition="'$(Configuration)' == 'Server'">
    <DeploymentFrameworkTargetsPath>Framework\</DeploymentFrameworkTargetsPath>
    <!-- Get our PDBs into the GAC so we get file/line number information in stack traces. -->
    <DeployPDBsToGac>true</DeployPDBsToGac>
    </PropertyGroup>
    <ItemGroup>
    <PropsFromEnvSettings Include="SsoAppUserGroup;SsoAppAdminGroup" />
    </ItemGroup>
    <!-- !!! TODO !!! -->
    <!-- Add ItemGroup elements that contain one or more Schemas, Orchestrations, Transforms, etc. elements that describe -->
    <!-- the specific artifacts in your solution that need to be deployed. Use IntelliSense as a guide. -->
    <ItemGroup>
    <Schemas Include="HelloWorld.dll">
    <LocationPath>..\$(ProjectName)\bin\$(Configuration)</LocationPath>
    </Schemas>
    </ItemGroup>
    <!-- !!! TODO !!! -->
    <Import Project="$(DeploymentFrameworkTargetsPath)BizTalkDeploymentFramework.targets" />
    <!--
    The Deployment Framework automatically packages most files into the server install MSI.
    However, if there are special folders that you need to include in the MSI, you can
    copy them to the folder $(RedistDir) in the CustomRedist target.
    To include individual files, add an ItemGroup with AdditionalFiles elements.
    -->
    <Target Name="CustomRedist">
    </Target>
    </Project>
    Error :-
    Starting build...
    C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe "C:\BTDF\Walkthrough1\HelloWorld.Deployment\Deployment.btdfproj" /nologo /t:Deploy /p:Configuration=Debug
    Build started 08-04-2015 17:43:51.
    Project "C:\BTDF\Walkthrough1\HelloWorld.Deployment\Deployment.btdfproj" on node 1 (Deploy target(s)).
    SetModeDeploy:
    DEPLOYING APPLICATION TO BIZTALK...
    SetWinVer:
    Running on Windows V62
    Detected IIS 7
    Detected 64-bit OS
    GetSoftwarePaths:
    Using .NET Framework Install Path 'C:\Windows\Microsoft.NET\Framework\v4.0.30319'.
    Using BizTalk Install Path 'C:\Program Files (x86)\Microsoft BizTalk Server 2013\'.
    Using Deployment Framework Install Path 'C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\'.
    Using Deployment Framework Tools Path 'C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools'.
    Using BizTalk ESB Toolkit Install Path 'C:\Program Files (x86)\Microsoft BizTalk ESB Toolkit\'.
    ExportSettings:
    "C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools\EnvironmentSettingsExporter.exe" "C:\BTDF\Walkthrough1\HelloWorld.Deployment\EnvironmentSettings\SettingsFileGenerator.xml" "C:\BTDF\Walkthrough1\HelloWorld.Deployment\EnvironmentSettings"
    Environment Settings Spreadsheet to XML Exporter 1.6.1
    [http://EnvSettingsManager.codeplex.com]
    Copyright (C) 2007-11 Thomas F. Abraham. All Rights Reserved.
    Importing from SettingsFileGenerator.xml...
    Output format is XmlPreprocess (multi-file).
    Exporting to Exported_LocalSettings.xml...
    Exporting to Exported_DevSettings.xml...
    Exporting to Exported_TestSettings.xml...
    Exporting to Exported_ProdSettings.xml...
    Finished.
    InitSettingsFilePath:
    Using settings file C:\BTDF\Walkthrough1\HelloWorld.Deployment\EnvironmentSettings\Exported_LocalSettings.xml
    SetPropertiesFromEnvironmentSettings:
    Setting properties from environment settings file (C:\BTDF\Walkthrough1\HelloWorld.Deployment\EnvironmentSettings\Exported_LocalSettings.xml)
    Setting property to value 'BizTalk Application Users'.
    Setting property to value 'BizTalk Server Administrators'.
    InitializeAppName:
    BizTalk Application Name is HelloWorld
    PreprocessBindings:
    Checking syntax of XML file 'C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindingsMaster.xml'...
    Syntax of XML file 'C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindingsMaster.xml' appears to be valid.
    Clearing file attributes for 'PortBindings.xml'.
    "C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools\xmlpreprocess.exe" /v /c /noDirectives /i:"C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindingsMaster.xml" /o:"C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindings.xml" /d:CurDir="C:\BTDF\Walkthrough1" /s:"C:\BTDF\Walkthrough1\HelloWorld.Deployment\EnvironmentSettings\Exported_LocalSettings.xml"
    XmlPreprocess v2.0.18.0
    Copyright (c) 2004-2013 Loren M Halvorson
    XML File Preprocessor
    Settings XML file: "C:\BTDF\Walkthrough1\HelloWorld.Deployment\EnvironmentSettings\Exported_LocalSettings.xml"
    Preprocessing "C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindingsMaster.xml" to "C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindings.xml"...
    PortBindings.xml : Set the value 'HelloWorld' of 2 node(s) matching XPath '//ApplicationName'.
    "C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools\ElementTunnel.exe" /i:"C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindings.xml" /o:"C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindings.xml" /x:"C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools\adapterXPaths.txt" /encode+
    Nested XML Encoder/Decoder v5.5.100.0
    Copyright (C) 2005-2014 Scott Colestock, Tim Rayburn, Thomas F. Abraham
    XML encodes/decodes content of element(s) by XPath. Applies escaping rules such
    as &gt; for '<'. Namespace decls, PIs, etc. of nested XML are not preserved.
    XPaths : 16
    Transformed Nodes : 0
    Empty Nodes (skipped) : 3
    No Transform Req'd (skipped) : 3
    Total Matched Nodes : 6
    Complete - output file has been saved.
    Checking syntax of XML file 'C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindings.xml'...
    Syntax of XML file 'C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindings.xml' appears to be valid.
    DeployFileAdapterPhysicalPaths:
    Configuring FILE adapter physical paths from binding file PortBindings.xml...
    Processing FILE adapter physical paths (Send)...
    Setting up path 'C:\BTDF\Walkthrough1\Out'...
    Directory already exists.
    Granted 'BUILTIN\Users' Full Access permissions.
    Processing FILE adapter physical paths (Receive)...
    Setting up path 'C:\BTDF\Walkthrough1\In'...
    Directory already exists.
    Granted 'BUILTIN\Users' Full Access permissions.
    TerminateServiceInstancesConditional:
    Attempting to terminate all service instances for BizTalk app 'HelloWorld'...
    Terminated 0 service instances for BizTalk app 'HelloWorld'.
    VerifyBizTalkAppExists:
    Checking for existence of BizTalk application 'HelloWorld'...
    Did not find BizTalk application 'HelloWorld'.
    DeployAppDefinition:
    BTSTask.exe AddApp -ApplicationName:"HelloWorld" -Description:"HelloWorld"
    Microsoft (R) BizTalk Application Deployment Utility Version 3.10.229.0
    Copyright (c) 2013 Microsoft Corporation. All rights reserved.
    Information: Adding new BizTalk application "HelloWorld" to configuration database (server="BDDBESBWMV01", database="BizTalkMgmtDb")...
    Information: Added application "HelloWorld".
    Command succeeded with 0 errors, 0 warnings.
    UndeploySchemas:
    Adding assembly name 'HelloWorld, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1a3b87e04e203d0f' to item group.
    "C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools\gacutil.exe" /u "HelloWorld, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1a3b87e04e203d0f"
    Microsoft (R) .NET Global Assembly Cache Utility. Version 4.0.30319.1
    Copyright (c) Microsoft Corporation. All rights reserved.
    Number of assemblies uninstalled = 0
    Number of failures = 0
    DeploySchemas:
    BTSTask.exe AddResource -Type:BizTalkAssembly -Source:"..\HelloWorld\bin\Debug\HelloWorld.dll" -ApplicationName:"HelloWorld" -Options:GacOnAdd,GacOnImport,GacOnInstall
    Microsoft (R) BizTalk Application Deployment Utility Version 3.10.229.0
    Copyright (c) 2013 Microsoft Corporation. All rights reserved.
    Information: Adding resource (-Type="System.BizTalk:BizTalkAssembly" -Luid="HelloWorld, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1a3b87e04e203d0f") to application "HelloWorld"...
    Serialized BizTalk assembly "HelloWorld, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1a3b87e04e203d0f" from "..\HelloWorld\bin\Debug\HelloWorld.dll".
    Information: Validating resources (count=1)...
    * Validating resource (-Type="System.BizTalk:BizTalkAssembly" -Luid="HelloWorld, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1a3b87e04e203d0f")...
    Information: Performing change requests...
    Information: Calling BeginTypeChangeRequest for all selected resource types...
    PerformingBeginChangeRequest
    Adding resource (-Type="System.BizTalk:BizTalkAssembly" -Luid="HelloWorld, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1a3b87e04e203d0f") to store.
    Information: * Performing change request on type "System.BizTalk:BizTalkAssembly" (count=1)...
    Information: Deploy server="BDDBESBWMV01" database="BizTalkMgmtDb" assembly="C:\Users\dopdevbiztalkadmin1\AppData\Local\Temp\BT\PID9536\BizTalkAssembly\4b4a4387187988d2dc55c72b16113199\HelloWorld.dll"
    Information: Installed the "C:\Users\dopdevbiztalkadmin1\AppData\Local\Temp\BT\PID9536\BizTalkAssembly\4b4a4387187988d2dc55c72b16113199\HelloWorld.dll" assembly into the Global Assembly Cache. (force=True)
    Information: Deploy operation succeeded.
    Information: Deploy server="BDDBESBWMV01" database="BizTalkMgmtDb" assembly="C:\Users\dopdevbiztalkadmin1\AppData\Local\Temp\BT\PID9536\BizTalkAssembly\4b4a4387187988d2dc55c72b16113199\HelloWorld.dll"
    Saved schema "Microsoft.Samples.BizTalk.HelloWorld.POSchema, HelloWorld, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1a3b87e04e203d0f".
    Saved schema "Microsoft.Samples.BizTalk.HelloWorld.InvoiceSchema, HelloWorld, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1a3b87e04e203d0f".
    Saved map "Microsoft.Samples.BizTalk.HelloWorld.POToInvoice".
    Saved message type "Microsoft.Samples.BizTalk.HelloWorld.POMessageType".
    Saved message type "Microsoft.Samples.BizTalk.HelloWorld.InvoiceMessageType".
    Saved port type "Microsoft.Samples.BizTalk.HelloWorld.ReceivePOPortType".
    Saved port type "Microsoft.Samples.BizTalk.HelloWorld.SendInvoicePortType".
    Saved orchestration "Microsoft.Samples.BizTalk.HelloWorld.HelloSchedule".
    Saved schema "Microsoft.Samples.BizTalk.HelloWorld.POSchema, HelloWorld, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1a3b87e04e203d0f".
    Saved schema "Microsoft.Samples.BizTalk.HelloWorld.InvoiceSchema, HelloWorld, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1a3b87e04e203d0f".
    Saved map "Microsoft.Samples.BizTalk.HelloWorld.POToInvoice".
    Saved message type "Microsoft.Samples.BizTalk.HelloWorld.POMessageType".
    Saved message type "Microsoft.Samples.BizTalk.HelloWorld.InvoiceMessageType".
    Saved port type "Microsoft.Samples.BizTalk.HelloWorld.ReceivePOPortType".
    Saved port type "Microsoft.Samples.BizTalk.HelloWorld.SendInvoicePortType".
    Saved orchestration "Microsoft.Samples.BizTalk.HelloWorld.HelloSchedule".
    Information: Installed the "C:\Users\dopdevbiztalkadmin1\AppData\Local\Temp\BT\PID9536\BizTalkAssembly\4b4a4387187988d2dc55c72b16113199\HelloWorld.dll" assembly into the Global Assembly Cache. (force=True)
    Information: Deploy operation succeeded.
    Information: Deployed the following 1 BizTalk assemblies:
    HelloWorld.dll
    EXEC : warning : If any of the assemblies were previously loaded by a Host Instance, it may be necessary to restart the Host Instance for changes to take effect. [C:\BTDF\Walkthrough1\HelloWorld.Deployment\Deployment.btdfproj]
    Information: Commit the change requests...
    * Performing EndTypeChangeRequest for resource type "System.BizTalk:BizTalkAssembly".
    Command succeeded with 0 errors, 0 warnings.
    DeploySharedAssemblies:
    Deploying additional assemblies to GAC...
    "C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools\gacutil.exe" /f /i "C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools\SSOSettingsFileReader.dll"
    Microsoft (R) .NET Global Assembly Cache Utility. Version 4.0.30319.1
    Copyright (c) Microsoft Corporation. All rights reserved.
    Assembly successfully added to the cache
    Finished deploying additional assemblies to GAC.
    ImportBindings:
    Copying file from "C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindings.xml" to "C:\BTDF\Walkthrough1\HelloWorld.Deployment\HelloWorld_PortBindings.xml".
    BTSTask.exe AddResource -Type:BizTalkBinding -Overwrite -Source:"C:\BTDF\Walkthrough1\HelloWorld.Deployment\HelloWorld_PortBindings.xml" -ApplicationName:"HelloWorld"
    Microsoft (R) BizTalk Application Deployment Utility Version 3.10.229.0
    Copyright (c) 2013 Microsoft Corporation. All rights reserved.
    Information: Adding resource (-Type="System.BizTalk:BizTalkBinding" -Luid="HelloWorld_PortBindings.xml") to application "HelloWorld"...
    Information: Validating resources (count=1)...
    * Validating resource (-Type="System.BizTalk:BizTalkBinding" -Luid="HelloWorld_PortBindings.xml")...
    Information: Performing change requests...
    Information: Calling BeginTypeChangeRequest for all selected resource types...
    PerformingBeginChangeRequest
    Updating resource (-Type="System.BizTalk:BizTalkBinding" -Luid="HelloWorld_PortBindings.xml") in store.
    Information: * Performing change request on type "System.BizTalk:BizTalkBinding" (count=1)...
    Information: Commit the change requests...
    * Performing EndTypeChangeRequest for resource type "System.BizTalk:BizTalkBinding".
    Command succeeded with 0 errors, 0 warnings.
    Deleting file "C:\BTDF\Walkthrough1\HelloWorld.Deployment\HelloWorld_PortBindings.xml".
    BTSTask.exe ImportBindings -Source:"C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindings.xml" -ApplicationName:"HelloWorld"
    Microsoft (R) BizTalk Application Deployment Utility Version 3.10.229.0
    Copyright (c) 2013 Microsoft Corporation. All rights reserved.
    Information: Importing bindings "C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindings.xml" into application "HelloWorld" in BizTalk configuration database (server="BDDBESBWMV01", database="BizTalkMgmtDb")...
    Information: Imported application "HelloWorld" bindings.
    Command succeeded with 0 errors, 0 warnings.
    DeploySSO:
    "C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools\SSOSettingsFileImport.exe" "HelloWorld" /settingsFile:"C:\BTDF\Walkthrough1\HelloWorld.Deployment\EnvironmentSettings\Exported_LocalSettings.xml" /userGroupName:"BizTalk Application Users" /adminGroupName:"BizTalk Server Administrators"
    Error persisting to SSO:
    System.Runtime.InteropServices.COMException (0xC0002A18): The format of the account name is not valid. Domain accounts must include the domain name. Local accounts must not include a domain or computer name.
    at Microsoft.BizTalk.SSOClient.Interop.ISSOAdmin.CreateApplication(String applicationName, String description, String contactInfo, String userGroupName, String adminGroupName, Int32 flags, Int32 numFields)
    at SSOSettingsFileManager.SSOHelper.CreateApp(String appName, String userGroup, String adminGroup)
    at SSOSettingsFileManager.SettingsFileImport.SaveSettingsToSSO(String affiliateAppName, String inSettings, String userGroupName, String adminGroupName)
    at SSOSettingsFileManager.SettingsFileImport.Main(String[] args)
    C:\Program Files (x86)\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1701,5): error MSB3073: The command ""C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools\SSOSettingsFileImport.exe" "HelloWorld" /settingsFile:"C:\BTDF\Walkthrough1\HelloWorld.Deployment\EnvironmentSettings\Exported_LocalSettings.xml" /userGroupName:"BizTalk Application Users" /adminGroupName:"BizTalk Server Administrators"" exited with code -1. [C:\BTDF\Walkthrough1\HelloWorld.Deployment\Deployment.btdfproj]
    Done Building Project "C:\BTDF\Walkthrough1\HelloWorld.Deployment\Deployment.btdfproj" (Deploy target(s)) -- FAILED.
    Build FAILED.
    "C:\BTDF\Walkthrough1\HelloWorld.Deployment\Deployment.btdfproj" (Deploy target) (1) ->
    (DeploySchemas target) ->
    EXEC : warning : If any of the assemblies were previously loaded by a Host Instance, it may be necessary to restart the Host Instance for changes to take effect. [C:\BTDF\Walkthrough1\HelloWorld.Deployment\Deployment.btdfproj]
    "C:\BTDF\Walkthrough1\HelloWorld.Deployment\Deployment.btdfproj" (Deploy target) (1) ->
    (DeploySSO target) ->
    C:\Program Files (x86)\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1701,5): error MSB3073: The command ""C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools\SSOSettingsFileImport.exe" "HelloWorld" /settingsFile:"C:\BTDF\Walkthrough1\HelloWorld.Deployment\EnvironmentSettings\Exported_LocalSettings.xml" /userGroupName:"BizTalk Application Users" /adminGroupName:"BizTalk Server Administrators"" exited with code -1. [C:\BTDF\Walkthrough1\HelloWorld.Deployment\Deployment.btdfproj]
    1 Warning(s)
    1 Error(s)
    Time Elapsed 00:00:54.94

    Hi Pratibha,
    Thank you for posting in MSND forum.
    Since
    this forum is to discuss: Visual Studio WPF/SL Designer, Visual Studio Guidance Automation Toolkit, Developer Documentation and Help System, and Visual Studio Editor.
    Based
    on your issue, since it is related to the Deployment Framework for Biztalk (BTDF), so I suggest you could consult this issue directly to this Deployment Framework for Biztalk (BTDF) website:
    https://biztalkdeployment.codeplex.com/discussions , you will get better support.
    Thanks for your understanding.
    Best Regards,
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

Maybe you are looking for