Hi,

I have done this hundreds of times before on other servers and I'm doing it the exactly same way everywhere, but on some servers this just doesnt work. So I'm trying to figure out why and what I'll have to do to make it work.

Usually when I am to save the application and deployment manifests I can either use an existing .pfx-file from earlier ClickOnces, or create a new.pfx by pressing the "New"-button.
But on some servers nothing happens when I try to save the new .pfx-file.

When the Signing Options window appears for the manifest I simply press the "New"-button and the "Save As"-window lets me choose the name and place for the file. So far so good, but whenI press the "Save"-button I get back to the Signing Options with no certificate created.
Usually the certificate will be created and chosen when doing this, but not on some servers.

If I create a key like this on another server and copy the .pfx-file into this one I can choose it normally and everything works - but creating a new one doesn't.

Hi Ziern,

What are the OS versions on those servers that have the problem you describe?

I open the MageUI.exe in the ildasm tool and navigate to the Mage > Mage.SignOnSave > btnNewKeyFile_Click node. Double clicking this node opens a window to show the IL of this method. I see that the codejust uses the System.IO.FileStream class to save the new created certificate file to the disk.

Check on those problematic servers to see if the newly created certificate files are saved on the specified path or not.

In addition, you should ensure the application has the permission to write in the path you specified.

Sincerely,
Linda Liu

Hi Linda,

Thank you for the reply.
The OS version is Winows Server 2008, and to me it seems it only happens on that OS.

The certificate file is not created at allwhen I try to create it as I described earlier. Simply, nothing happens.
On the servers where there is no problem the certificate is created and the path to it is written in the textbox. But on these servers no certificate gets created and no path is written in the textbox after I click the Save-button.

There should be no permission problems, I even added full rights to "Everyone" to test it temporarily.

/Z

I recently got this problem again on a Virtual XP machine that I've been using as a workaround. (I create the signing keys on this machine instead of the servers on which I can't create one.)

I've been able to create the signing keys on this virtual XP machine up until I chose to install some Windows Updates. After I had installed the updates I got the same problem as before (read earlier posts).
Since my virtual XP machine was lacking alot of updates I can't really tell which update that caused it, but I am suspecting that it has something to do with .NET 3.5. But it could be anything really.

So I performed a system restore on the vitual XP, and after that I can now create the signing keys again.


Is it the .NET 3.5 update that makes this happen, or is it something else?