Clickonce - Unable to Sign Application

Hot Topic

How: Layout Managers in .Net like Java
Advice on binding enum to combobox then casting back
How can I select all items from a ListBox quickly?
Child Form
Accessing to a menuitem on parentform from a childform in C#
How to execute console application in Windows Form?
ListView sorting
ActiveX control
Question about threading Forms
Form Refresh Question

Windows Forms

Drag & Drop Reorder of Row
Variabels
On a DataGridView control, is it possible to ...
"The terrarium server is experiencing temporary difficulties. This is probably why you are not receiving any animals. Please bear with us while we get the issue resolved."
OCR Component
IDE Designer unable to display forms containing user controls
Adding menu to treeview nodes
Capture KeyPresses with one control, but handle them with another
Mouse button issues
Basic Question on Properties returning a class

Clickonce - Unable to Sign Application

Error    1    Cannot publish because a project failed to build.        1    1    PMtool2
Error    2    SignTool reported an error 'Failed to sign bin\Debug\PMtool2.publish\\setup.exe. '.    PMtool2

I get these errors when I try to publish this to any location.
I have an Authenticode Cert for application signing installed, and it sees it and all it's details correctly from what I can tell.
I get no build errors at all when just building the application normally.

I've searched the help files, and online, and can't seem to find anything that matches this. Anyone have any ideas

This is with the full release version of VS 2005 of course, just in case.

Answer this question

Clickonce - Unable to Sign Application

  • Peter V

    David, would you be able to see if you can use a vs commandline tool called SignTool.exe directly ("SignTool.exe Signwizard" ) to sign the app on that machine with the communcation manager installed/configured  That would help eliminate VS and bring in the right folks.  If you run Signtool and it errors, please provide that error information as well. 

    Also, I just tried installing the communication manager and was not able to repro.  however my machine  does not have any of the wireless devices that is required to fully test.  At what point do you see the conflict occur Did just installing the manager cause the problem for you

    Thanks!
    Robert Schoen (MS Visual Basic QA)

     

  • Patrick Cournoyer

    That is good information.  Thanks! Stay tuned.

  • jketola

    Awesome!  I will followup with our Click Once folks monday and see what we can find out about this repro on our side!

    Robert Schoen (MS Visual Basic QA)

  • Scott Ritter

    Same Results with the 5.1.10DL version as well.

    Just a note, that might help your guys locate the error faster. This software installs it's own LSP elements on top of the network stack. Might be a decent place to start.

    I'll check back on this thread middle of next week to see if you need any further information.

  • fwpi

    Are you saying that if you create a brand new app (a simple win app) and just publish (Publishing will generate a test cert for you automaticaly) by right clicking on the project node in the solution explorer that this fails with the same error

    Have you been able to publish a click once app from this machine in the past or is this your first attempt

    Robert Schoen (MS Visual Basic QA)

  • programmer2005

    Glad that you figured it out!

    Can you send me a link to information related to this software   It would be good to have this information on our radar to help folks out in the future...and maybe we can track down on our end what the issue is.

    Robert Schoen (MS Visual Basic QA)

  • thirdq

    On the "bad" machine - view the certificate via the Signing page (right click on the project in the solution explorer and select properties - then change to signing tab) by clicking the "view details" button of the cert that you are trying to use.  Change to the  "Certificate Path" tab of this dialog, what does the "Certificate Status" say at the bottom

    Robert Schoen (MS Visual Basic QA)

  • Chernichkin Stanislav

    Even tried making a brand new application that was just a ok window, and get the same erorrs. Still looking for any help on this.

  • Siddharth Fadnis

    Guys,

    I am struck with a similar error and I don't have the cingular software that David was talking about installed on my machine. Do we have a list of all the softwares that might potentially impact the ClickOnce feature Or is there some kind of patch that I need to run to make sure that I can publish the smart client projects

    Thank you,
    - Krishna

  • yayah_1

    http://www.cingular.com/midtolarge/communicationmgr

    I was using the 5.1.04DL version of the software, and if you need I can supply a cached copy of that version, as their site has been updated with 5.1.10DL (which I will be testing if this error still resides with that version of the software).

  • George Kondiles

    Now I'm really baffled, using the test cert, or my authenticode cert on another machine with the same code works fine. I re-installed the certs on this machine and it still fails.

    I'll try re-installed VS, but past that I'm at a loss right now.

  • Sun - By - Night

    After failing with this same error using even the temporary test cert's the VS 2005 generates, aquired a Brand New authenticode Cert that expires Nov 2006 to try this with, and it generates the same error.

  • aak165842

    I believe this error is typically due to a certificate being expired.  Can you verify

    Robert Schoen (MS Visual Basic QA)

  • Eric2002

    Hi Robert, thanks for your attention to this.

    It would appear that a Cellular Data Card Software I had installed on this machine was somehow interfering with it's ability to publish correctly, although I could not tell you why.

    I removed the software on a hunch, and after that, all my code signs correctly.

    At least that might explain why the error was so generic.
  • Clickonce - Unable to Sign Application
Answer this question