This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- FlexNet Publisher
- :
- FlexNet Publisher Forum
- :
- xmlsign Problem
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 01, 2014
01:10 PM
xmlsign Problem
Hello,
When going through setting up for trusted storage, there are steps for defining the trusted configuration with fileTrustedConfigIn.xml
I can do the tcencrypt step to generate theTrustedConfigOut.xml and the KeyFile.xml.
However when I try the step:
xmlsign -a ../ActivationSettings/publisher.xml \
-iTrustedConfigOut.xml \
-oTrustedConfigOut.xml
I get the message "OS error code 0x00000000"
What is this error? My publisherID matches in publisher.xml and TrustedConfigIn.xml so that is not the problem.
Any help would be appreciated, thank you.
When going through setting up for trusted storage, there are steps for defining the trusted configuration with file
I can do the tcencrypt step to generate the
However when I try the step:
xmlsign -a ../ActivationSettings/publisher.xml \
-i
-o
I get the message "OS error code 0x00000000"
What is this error? My publisherID matches in publisher.xml and TrustedConfigIn.xml so that is not the problem.
Any help would be appreciated, thank you.
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 26, 2015
10:39 AM
Hello,
I got the same problem both on Windows and Linux. Does anybody know what the problem is ?
Thanks
I got the same problem both on Windows and Linux. Does anybody know what the problem is ?
Thanks
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 26, 2015
11:03 AM
If I remember correctly, I contacted Flexera support directly and they told me the publisherID they gave me was incorrect and had to issue a new one.
