Release management

Hi ,
I am supposed to create these procedures through program .Anyone please give me the program to create the PO release strategy & Purchase Requisition release strategy.
Thanks

Hi Akhil,
Thanks for your post.
I reproduced this scenario in my RM 2013 Update 4 environment, and received the same result.
For this scenario, please submit it to Microsoft Connect Feedback portal at:
https://connect.microsoft.com/VisualStudio. Microsoft engineers will evaluate it seriously.
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.

Similar Messages

  • Deployer Installation: Failed to validate Release Management Server for Team Foundation Server 2013

    Attempting to install the deployer on a machine and getting the below error.  Not sure what that means, out of turn error or what actually occurs at this step, validating release management server,  during the configuration piece.  The user,
    that we set for the service was validated fine.  The user is an service account in the TFS RM Server, is  an admin on the local box as well.
    I am able to get into the TFS RM Server through the client just fine. I can hit the TFS RM UI just fine as well.
    Curious what would not allow the deployer to complete as mentioned below.
    Any help is appreciated.
    I, 2013/12/16, 14:46:26.521, Validated account to use as identity for Release Management Services.
    I, 2013/12/16, 14:46:26.521, Validating Release Management Server for Team Foundation Server 2013...
    E, 2013/12/16, 14:46:30.905, Received Exception : Microsoft.TeamFoundation.Release.CommonConfiguration.ConfigurationException: Failed to validate Release Management Server for Team Foundation Server 2013.
       at Microsoft.TeamFoundation.Release.CommonConfiguration.DeployerConfigurationManager.ValidateServerUrl()
       at Microsoft.TeamFoundation.Release.CommonConfiguration.DeployerConfigurationManager.ValidateAndConfigure(DeployerConfigUpdatePack updatePack, DelegateStatusUpdate statusListener)
       at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
    I, 2013/12/16, 14:46:30.905, Work completed for GetConfiguration() call : got out of turn error
    E, 2013/12/16, 14:46:30.905, Failed to validate Release Management Server for Team Foundation Server 2013.

    Hi Kpdn, 
    Thanks for your post.
    All your participation and support are very important to build such harmonious/ pleasant / learning environment for MSDN community.
    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.

  • Problems setting up release management

    Hi I am running into problems in setting up Microsoft Release Management. I have 2 domains. My tfs (separate server), release management server and release management client (both on single physical server) are in domain1 and deployer is in domain2 in Azure
    VM. I am using a VPN tunnel to connect release management server, release management client and deployer. They connect with each other nicely. The problem comes when I add reference to tfs in release management client. TFS fails to verify. Now
    the user I am using to connect has Make requests on behalf of
    others' permissions so that is not the issue. I get TF400324 error. I even used wireshark to troubleshoot but it looks as if release management
    client is not even trying to connect. I can access tfs url via web browser with vpn connected from machine on which release management client is running. when  Now if I disconnect the vpn and try to verify tfs from release
    management client it works. Does release management client supports connecting via ipv6 tunnel?

    Hi abhijitdamle,
    I'd like to know how do you connecting via ipv6 tunnel, and when you get the error(without vpn connection?) . If your machine can be access via HTTP/HTTPS, then RM client can also be connected. For your situation, seems you got the
    issue resolved after using vpn.
    If you have other concerns about the error, you can also check the methods below to see if it works for you:
    1. Check the permission of the user account you use, make sure it has the permission of "make requests on behalf of others"
    2. Clean team foundation cache on your RM client machine
    3. Check the team project collection url to ensure it's input correctly, or use the solution on this
    page
    Best regards,

  • Release management with Azure and Visual Studio Online (Cloud TFS)

    What strategy would you use to manage the releasing of versioned software to Azure cloud services (web and worker roles)? We are not looking for continuous integration. We are using Visual Studio 2013 and Visual Studio Online (Cloud TFS).
    At one point, we were releasing straight from Visual Studio using the Azure Cloud Project Publish tool. This is really bad practice in my opinion as you can never be sure what you are really releasing. Additionally, there is no automated control on the labeling
    or branching of code, or the running of unit tests and code analysis checks.
    Next, we employed Release builds on Visual Studio Online. Before deployment, one would edit the appropriate Build Definition (whether it be for Test or Production by and filling in the code label (under the "Get Version" build property) that is to
    be released. This would then get the appropriate code (by the label specified), build it, and release it to whatever cloud service is specified in the targeted Cloud Project profile (this is using the AzureContinuousDeployment.11.xaml template).
    There is still a degree of manual intervention involved. Also, the fact that a version of code is built every time before it is released is not ideal (as far as I understand it would be better if it was packaged once).
    Microsoft Release Management tools
    look ideal for the job, but are not supported with Visual Studio Online.
    Is there a better way of handling our releases?

    /waves hand.. These are not the tools you seek. You are looking for continuous integration.
    Although CI has the word continuous in there, it does not mean "all the time, every checkin". It can easily refer only to those bits you want to release - -and the way to tell the system which bits you want released is to merge them to a Releases
    branch.
    If you do this, not only do you get all the joy of controlled CI, but you guarantee what you release is exactly what is controlled in your SCM - under the Releases branch, preferably tagged or otherwise noted as a particular release. That means you can also
    rollback to a previous release by simply reverting to a previous release in your SCM!
    Of course you don't have to let it happen automatically, you can set it up to build 'continually' and then remove the check on the SCM to see if any changes have been committed. You can replace this with the manual build button.

  • Unable to Create Website using "Create Web Site" action component in Release Management

    Hi Team,
    I am trying to use Release Management to Deploy my Website along with DB in staging servers.
    I have set-up 2 Staging Servers SIT & UAT Both 2012 Servers with IIS 8.5 Configured.
    Defined Release Path and Release template.
    Deployment Sequence is something like this : 
    Deployment Sequence - Server Name - Create Folder - XCopy - Create Website - Configure Website
    Build is successful, drops the output to Output folder and RM gets initiated with it's work.
    It creates folders as mentioned in the "Create Folder" activity.
    It copies the whole content from _PublishedWebsites to the mentioned location.
    It gets stuck with the "Create Website" step.
    Initially I have provided details as follows : 
    AppPoolName
    IsPreloadEnabled
    IsAutoStart
    SiteName FabrikamSIT
    PortNumber 80
    PhysicalPath c:\FabrikamRM\WebSite\SIT 
    Later, I tried providing 
    AppPoolName DefaultAppPool
    IsPreloadEnabled 1
    IsAutoStart 1
    SiteName FabrikamSIT
    PortNumber 80
    PhysicalPath c:\FabrikamRM\WebSite\SIT 
    Then also no luck.
    Deployment gets rejected and the error that you can see when you hover the mouse is : 
    Task failed with the exit code -2146232576".
    No much info available with this eror code in net also.
    Any help in getting this simple site created is highly appreciated.
    Thanking you in advance,
    Regards,
    TFS Queries

    Hi,
    For the deployment sequence, you might need add the action of "create application pool" before creating a website.
    Another method is check whether the build output can be deployed manually. If yes, then you can trobleshoot the problem in your deployment sequence and parameters. You can create the website manually and deploy your build output to the website. If you have
    any other concerns about the deployment, you can also open a new thread in IIS forum for a better response.
    If the issue persists, please elaborate more details about your scenario with sceenshots.
    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.

  • How best we can use the Rollback and RollbackAlways mechanism in Visual Studio Release Management Template

    Hello All,
    We need a clarification on Rollback and RollbackAlways in Release template.
    We checked a scenario for Rollback and RollbackAlways:
    In Release Template, we have the first activity as “Configure Application Pool” and then followed by a rollback action of “Create Application Pool”
    and “Create Web Site” then followed by "Code Deployment" via TFS build.
    We tested with 2 scenario’s:
    With App Pool and Web Site already existing: when triggered the build, configure
    app pool succeeded, then Rollback action was skipped (as previous action was successful), finally deploy the code executed (code deployed) and build got succeeded.
    Deleted App Pool and Web Site: when triggered the build, configure app pool failed (as no app pool existed), Rollback action executed (as previous action failed) – created app pool and web site then finally
    deploy the code executed (code deployed)
    But build failed (Error: Configure app pool action failed).
    Ideally the build should succeed as the roll back action got executed and code deployed successfully.
    Please correct us if our understanding is wrong.
    Also, Kindly let us know how best we can use the Rollback and RollbackAlways mechanism in Release Management
    Looking forward for your positive response.
    Thanks in advance.
    Regards,

    Hi Shashank,
    Rollback Always runs if any of the actions in the template failed. Rollback will run if action just above rollback fails or if any of the actions below the Rollback fails.
    Article here (http://www.incyclesoftware.com/2014/03/understanding-rollbacks-release-management/) clearly explains how Rollback and Rollback
    Always work.
    I think you come across this issue since you are using build to do the "code deployment" action. You should use the release template to do that. 
    As far as I know you cannot use Rollback to achieve condition check (App pool exist in your case) action.
    For this you can create your own Power Shell component (which checks if the app pool exist and is not create it) and add it as a tool in RM server (RM Server Inventory).
    Another option is you can follow the workaround in below thread "Answer" quoted below. That is execute Remove app pool regardless if it exist or not (which does not fail) and then create app pool.
    I was able to get it working by removing the app pool which does not fail if it doesn't exist. Removing then creating seems the long way around but it works.
    Flow:
    Remove Application Pool
    Create Application Pool
    https://social.msdn.microsoft.com/Forums/en-US/43bf21c8-e233-4e58-a5a8-2592b78bc466/vs-2013-release-management-create-application-pool-fails-if-it-already-exists?forum=tfsbuild
    Cheers!
    Chaminda

  • Anyone experience with Oracle Release Management?

    Hi,
    I don't know in which forum to post this, but Order Management seems to be most appropriate.
    I am looking for someone with experience in Oracle Release Management. We are an Automotive company and a couple of our customers use EDI and we have many repeating orders / schedules. We don't have EDI set up yet, that's planned for later. We were wondering if it makes sense to start using Release Management. What we have in mind is to use the Release Workbench to enter Order Schedules faster than in OE/OM.
    However, even after reading the implementation & user manual this is still very unclear to me... What features are worth to be used with and without EDI etc. How does it fit in the whole concept and what benefits it can bring.
    I am looking for someone who has experience in this area and is willing to share some knowledge. Anyone here from companies that use this module?
    Btw., we are using eBusiness Suite 11i (11.5.10.2) and have Order Management and a couple of other modules heavily used.
    Thanks,
    David.

    Well your question is from a few years back, but I am still curious if you had any answers? If so would you be so kind to share those with me? I am currently more or less in a same position. We want to use Release Management to prefent of releasing orders when a customer is beyond his forecast, but I have no idea if we can do it with this module.
    Thanks: Pum van der Lit

  • Release Management Server/Client clarification

    Hi there,
    I am using TFS 2010 and i would like some assistance in regards to what i would like to do please.
    At my place of work we have a Build server, call it Server A which has a controller and 2 build agents. It builds my projects and outputs them in a drop folder on that server.
    Firstly, can i use my existing custom build template to allow others to trigger a build via the Release Management Client tool?
    The existing custom template i am using builds all the projects in the solution and then generates several *.MSI files at the end. I use this template in all of my Build Definitions.
    Secondly, Do i have to install the Release Management Client tool and Deployment Agent on the Build server as well?Correct me if i am wrong because i read that if you want to do automated deployment i have to do this.
    Thirdly, am i allowed to use custom scripts, executable side by side with the Deployment Agent. The reason i ask that is at some point i would like to extend the process so that once the build has finished, i can install it on Server B. Is this possible?
    Lastly, do i have to install Visual Studio 2013 on the build server for Release Management Server to work correctly?
    If you have any questions on the above please let me know.
    Thanks,

    Hi IndusKing,  
    Thanks for your reply.
    If your build definition using the ReleaseDefaultTemplate.xaml template, and you want only to build the solution(needn’t to trigger release template), you can set the
    Release Build = False in build definition>>Process>>Release.
    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.
    So if i understand correctly i can either use the ReleaseDefaultTemplate.xaml in all my build definitions or i can modify my existing template to use the Release Template functionality e.g Release Build = False.
    As far as I know RM Client not support trigger TFS build definition. You can install the VS on your RM Client machine, then trigger build definition in Team Explorer, or trigger the build definition by execute TfsBuild
    Start command line.
    Are you saying that RM client can only deploy finished finished builds?

  • Release Management and Dsc - How to queue a build when a release is in progress?

    I have VSO and Release Management 2013.4 working and deploying to Azure vm's via DSC
    The build profile is set to trigger on commit to the Git repo and the release template is set to be triggered on successful build from TFS
    However if a developer commits in quick succession the resultant builds cause releases to overlap in RM? - this causes some of the releases to fail with a DSC error ("the consistency check or pull cmdlet is in progress....")
    Is there a way to force RM to prevent concurrent releases?  (based on the same release template and build profile)

    Thats correct - in this instance its VSO as source control and using the hosted release management to attempt to deploy to azure vms
    And yes build takes about 5 minutes but the release template can take up to 15 minutes to run - this means that a second build can cause the same release template to run again (its set to trigger on build)
    Error log from RM
    xception Message: New deployment is not allowed as an another deployment is in progress. Retry the deployment after sometime. (type OperationFailedException)
    Exception Stack Trace: at Microsoft.TeamFoundation.Release.EnvironmentProvider.Azure.Implementation.AzureDeploymentProvider.ReadDeploymentResponse(DeploymentResponse response)
    at Microsoft.TeamFoundation.Release.EnvironmentProvider.Azure.Implementation.AzureDeploymentProvider.DownloadBuilds(DeploymentMachineSpecification deploymentMachineSpecification, AzureStorageSpecification azureStorageSpecification)
    at Microsoft.TeamFoundation.Release.EnvironmentProvider.Azure.Implementation.AzureDeploymentProvider.RunScript(String scriptPath, String configurationPath, MachineSpecification machine, StorageSpecification storage, Dictionary`2 configurationVariables)
    at Microsoft.TeamFoundation.Release.Tasks.DeployDsc.Execute(DscComponentParametersV2 dscComponentParameters, AzureStorage azureStorage, String[] dnsNameAndUpdatedWinRmPort, String userName, String password, String dscScriptPath, String dscConfigurationPath, Boolean skipCACheck)
    at Microsoft.TeamFoundation.Release.Automation.Tasks.DeployDscTask.DscExecute(DscComponentParametersV2 dscComponentParameters, AzureStorage azureStorage, String[] dnsNameAndUpdatedWinRmPort, String userName, String password, String dscScriptPath, String dscConfigurationPath, Boolean skipCACheck)
    at Microsoft.TeamFoundation.Release.Automation.Tasks.DeployDscTask.DscDeploy(AzureStorage azureStorage, DscComponentParametersV2 dscComponentParameters, String userName, String password, String dscScriptPath, String dscConfigurationPath, String skipCACheck)
    at Microsoft.TeamFoundation.Release.Automation.Tasks.DeployDscTask.Execute(IAutomationContext context)
    at Microsoft.TeamFoundation.Release.DistributedTask.TaskProcessor.TaskExecutor.Execute(TaskExecutionContext context)

  • Release Management for Visual Studio & Windows Forms Projects

    Is Microsoft's new Release Management (RM) tool a viable option for Windows Forms applications that utilize ClickOnce for installation? 
    It seems all of the examples I have seen for RM center around web based applications.  I intend to have TFS build the application, RM pick up the bits from a drop location and create 5 unique ClickOnce installers (using PowerShell & Mage.exe). Initially,
    each of the 5 unique ClickOnce installers would differ only in app.config files.  I though RM would be a nice fit since I can let it handle customizing the app.config for each of the 5 installers.

    Hi BWKDev, 
    Thanks for your post.
    If you can deploy your project using PowerShell script, I think 
    you can create the release template to copy your build output(include deploy PS script file) to deployment agent machine, and execute the deploy PS script using PS script execute component to deploy your project.
    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.

  • Release Management and Azure Hosted Build Agents

    Good day,
    I configured Release Management as follows:
    http://intovsts.net/2014/11/06/connect-visual-studio-release-management-to-visual-studio-online-and-microsoft-azure/
    In this material mentioned that it is for VS Online (which I don't use)... However, I can't get it to work with Hosted Build Agent in Azure. When I try to release I get error
    "Exception Message: The directory name is invalid (type Win32Exception)"
    What actually mean that Release Management Client is not installed on the Build Agent.
    Is it so, that I can't use Release Management with Hosted Build Controller/Agent? What other options to drive test Release Management w/o full TFS installation are available?
    Looking forward for your answers! Thank you in advance!

    Hi Voron81, 
    Thanks for your post.
    You’re using On-premise TFS Server(TFS 2013 Update 4) rather than the VSO? If yes and you installed the RM Server, you should install the RM Client on your On-premise build agent machine.
    For which software installed on hosted build server, please refer to the information in this article:
    http://listofsoftwareontfshostedbuildserver.azurewebsites.net/.
    If you want use your VSO account as RM Server to deploy to Azure, please refer to the solution this article:
    http://www.visualstudio.com/get-started/deploy-to-azure-vs.
    For how to use the VSO account as RM Server, please refer to the steps in this article:
    http://www.visualstudio.com/get-started/manage-your-release-vs.
    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.

  • Visual Studio Online / Release Management Email Notifications

    We use Visual Studio Online and not a local TFS instance. Additionally we want to / ARE using the Release Management service.  But, we are having difficulties configuring the Email notifications within Release Management.    We have steps
    configured  for email notification on step approval.  BUT we are not getting any of these notifications and the Releases get stuck waiting during these steps.  And only if by sheer dumb luck the user logs into his/her Release Management window
    do they see that they have pending approvals...
    What do we need to do in order to get these approvals flowing?
    Thanks in advance!

    Hi,
    Thank you for reaching out to us. I am currently researching to gather more information with regards to your request. I shall revert back to you with an update at the earliest. Sincerely appreciate your patience.
    Regards,
    Nithin Rathnakar

  • How to obtain the Management Certificate Key for using Azure with Release Managment

    In the "Release Management" app in administration --> Manage Azure one must provide a "Management Certificate Key".
    I have created a self-signed cert and uploaded it to Azure Portal --> Settings --> Management certificates
    How do I get the key?
    Thanks ))

    Hi Atwater and Sons,
    when you look at the blog post paragraph four you find a link
    Download the settings file from the Azure portal to get your subscription ID and Management Certificate key.
    After you have downloaded the file, open the file with Notepad.
    You will find everything there - except the storage Account Name:
    <PublishData>
    <PublishProfile
    SchemaVersion="2.0"
    PublishMethod="AzureServiceManagementAPI">
    <Subscription
    ServiceManagementUrl="***"
    Id="***"
    Name="***"
    ManagementCertificate="***" />
    </PublishProfile>
    Copy the Id and the ManagementCertificate and past them into RM (Manage Azure)
    Your Storage Account Name: Blog Post Paragraph four
    Go here to get the name of an existing storage account or add
    a new storage account using the Azure portal.
    Regards,
    Daniel

  • Release Management fails to locate log file

    Hi,
    I'm using Visual Studio Release Management to deploy MSI packages.
    When I try to "View Log" I get the following error:
    There was an error while reading the log: Could not find file 'C:\Users\zzzzzz\AppData\Local\Temp\RM\T\RM\xxxxxx\201503051135578722385-6\__Installer__.log'.
    And the step reports Success when it should have reported an error (The MSI returns an error).
    Any idea why the log is not generated?
    Thanks,
    Gilad

    Hi Gilad,
    You can check whether you can find the log in the path. If the log not exist, you can do a new release and check the log after doployment.
    I'd like to know the error details about MSI. If the deployment succeed, then the release can be taken as successful.
    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.

  • Is it possible to do Continuous deployment for azure cloud services(website,web and worker roles) using VSO Release management?

    Hi,
    I am trying to do continuous deployment using visual studio online and release management for Azure cloud services. But not able to find the way to do it(with the help of different blogs, those are describing using VM only).
    I tried using Release management visual studio extension also. But no Luck.
    Please help me if it is possible to do continuous deployment using release management.
    Thanks,
    Phani

    Hi,
     Please refer to the following Forum Thread with similar question which has been answered. Let us know if this helps.
     https://social.msdn.microsoft.com/Forums/en-US/9d8322f6-36e5-4cca-a982-d420d34d2072/realease-management-deployment-to-azure-websites-webworker-roles?forum=tfsbuild
    Regards,
    Nithin Rathnakar

  • Error in TFS Release Management Server after Upgrading to Update 3

    Some weird and unexplained error logged in InRelease aka (Release Management) server event log after upgrading Release Management Update 1 to update 3.
    Below error started getting logged only after upgrading to Update 3.
    Even though we started the Inrelease Server and all agents but no luck.
    Any immediate help would be much helpful.
    ----------------------------------- EVENT LOG ERROR ------------------------------------
    Timestamp: 12/15/2014 10:22:18 AM
    Message: 'LambdaValue>' is not of type 'ServerActivity'. When loading this instance you must ensure that the activity with name 'LambdaValue>' implements
    'ServerActivity'.: \r\n\r\n at
    System.Activities.ActivityInstance.System.Activities.Runtime.ActivityInstanceMap.IActivityReference.Load(Activity activity, ActivityInstanceMap instanceMap) at System.Activities.Runtime.ActivityInstanceMap.InstanceList.Load(Activity activity, ActivityInstanceMap
    instanceMap) at System.Activities.Runtime.ActivityInstanceMap.LoadActivityTree(Activity rootActivity, ActivityInstance rootInstance, List1
    secondaryRootInstances, ActivityExecutor executor) at System.Activities.Runtime.ActivityExecutor.OnDeserialized(Activity workflow, WorkflowInstance workflowInstance) at System.Activities.Hosting.WorkflowInstance.InitializeCore(IDictionary2 workflowArgumentValues,
    IList1
    workflowExecutionProperties) at System.Activities.Hosting.WorkflowInstance.Initialize(Object deserializedRuntimeState, DynamicUpdateMap updateMap) at System.Activities.WorkflowApplication.LoadCore(DynamicUpdateMap updateMap, TimeoutHelper timeoutHelper, Boolean
    loadAny, IDictionary2 values) at System.Activities.WorkflowApplication.Load(Guid instanceId, TimeSpan timeout) at System.Activities.WorkflowApplication.Load(Guid instanceId) at Microsoft.TeamFoundation.Release.ServiceProcessor.Processor.WorkflowInstance.WorkflowInstanceCacheSingleton.<.cctor>b__1(WorkflowApplication
    app, Guid id) at
    Microsoft.TeamFoundation.Release.ServiceProcessor.Processor.WorkflowInstance.WorkflowInstanceCache.CreateApplicationInCache(CreateParameters createParameters, Guid id) at Microsoft.TeamFoundation.Release.ServiceProcessor.Processor.WorkflowInstance.WorkflowInstanceCache.GetInstance(CreateParameters
    createParameters, Guid id) at Microsoft.TeamFoundation.Release.ServiceProcessor.Processor.WorkflowInstance.CachedWorkflowInstanceLoader.GetInstance(DeploymentLog log, CreateParameters createParams) at Microsoft.TeamFoundation.Release.ServiceProcessor.Processor.DeploymentControllerServiceProcessor.ContinueDeploymentWithFinalComponentState(DeploymentLog
    log) at Microsoft.TeamFoundation.Release.ServiceProcessor.Processor.DeploymentControllerServiceProcessor.ContinueDeployment(String log)
    Category: General
    Priority: -1
    EventId: 0
    Severity: Error
    Title:
    Machine: **********
    Application Domain: /LM/W3SVC/1/ROOT-1-130630102320068767
    Process Id: 6628
    Process Name: C:\Windows\SysWOW64\inetsrv\w3wp.exe
    Win32 Thread Id: 1344
    Thread Name:
    Extended Properties:

    Dear Charles-Li,
    Thank you so much for your reply.
    we started using  Release Management Update 1  and it was worked perfectly fine.  then we move to upgrade existing Release Management(server,
    Database and agent) with Update 3, which we did, and its working fine  except lots of error as mentioned in above thread, are getting logged in server event log at regular interval till now(3-4 errors every second).
    even though lots of error are getting logged but we are not facing any issue while using Release Management with update 3.
    But i am bit curious to know out reason for getting those error.
    <<clean
    the cache folder and restrat Release Management and try again>>
    already tried but no luck.
    Thanks!!

Maybe you are looking for