none
Deployment of renew certificate for TFS build is not working

    Question

  • We have a ClickOnce application which is pushed into TFS and we have all of our environment builds running as queued builds on the server.

    Our builds began failing for our client due to the certificate expiring and the guy that "usually fixes the problem" is out of town for the week.  (doesn't it always happen that way?)

    After a quick Google I found the location where I can redeploy the certificate and I did this.

    However I am now getting an error because I'm not the guy that "usually issues the certificate".  

    We have all of our testing builds of the client dead in the water and tomorrow's build into our staging server is dead as well due to this expired certificate.  How do I make TFS 2010 recognize my certificate as being valid for signing???

    I have looked through several threads but they are all doing a build and deploy on their own machine, not on the TFS build server.

    Tuesday, August 27, 2013 8:14 PM

Answers

  • Hi SASS_Shooter,

    Based on these description, do you use on-premise TFS2010? If yes, you can rebuild on your build agent machine and then deploy to see whether it works fine. If you don't specify a special build service account before build process, it will use the default build service account.

    If the error still occurred after you perform operations mentioned above, the issue is more related to C#. You can reopen a thread in C# forum at here for a better response. Thanks for your understanding.

    Best regards,


    <THE CONTENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS OR IMPLIED>
    Thanks
    MSDN Community Support

    Please remember to "Mark as Answer" the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.


    Thursday, August 29, 2013 3:22 AM
    Moderator

All replies

  • Hi SASS_Shooter,

    I'd like to confirm with you whether you can build success on your clent machine. Could you please make sure if it works fine on your build agent machine?

    For team build with ClickOnce application, you can refer to this article. Another option is that you can check the accont that build service depend on in build agent machine to see whether its password is expired.  

    Best regards,


    <THE CONTENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS OR IMPLIED>
    Thanks
    MSDN Community Support

    Please remember to "Mark as Answer" the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.


    Wednesday, August 28, 2013 10:41 AM
    Moderator
  • It builds fine on my machine.  I am just frozen as far as being able to do a build and deploy of click once.  It does NOT build on my build server.  It throws an exception because the certificate is a different person from the original person.  And this is killing us at the moment.  
    Wednesday, August 28, 2013 3:59 PM
  • I also looked at that article.  Did you not read anything I wrote, Kimi???  That article is a happy happy trail of building a brand new deployment of Click Once.  We have had a deployment working for almost 2 fracking years.  But the certificate expired and the person who did the last one was out of town.  I renewed the certificate and all hell has broken loose.  Now we cannot deploy ANYWHERE!!!!
    Wednesday, August 28, 2013 4:04 PM
  • Hi SASS_Shooter,

    Based on these description, do you use on-premise TFS2010? If yes, you can rebuild on your build agent machine and then deploy to see whether it works fine. If you don't specify a special build service account before build process, it will use the default build service account.

    If the error still occurred after you perform operations mentioned above, the issue is more related to C#. You can reopen a thread in C# forum at here for a better response. Thanks for your understanding.

    Best regards,


    <THE CONTENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS OR IMPLIED>
    Thanks
    MSDN Community Support

    Please remember to "Mark as Answer" the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.


    Thursday, August 29, 2013 3:22 AM
    Moderator