Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 13 replies
  • Subscribers 1 subscriber
  • Views 19118 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ConfigCID.exe changes

QC

Hello all

Last week I stumbled over the recent changes in ConfigCID.exe - got a "Failed to read signing key" error (meanwhile the article on ConfigCID.exe has been amended with information on this). This will affect you if

  • you have to configure a CID on a child SUM and
  • you can't access the share from the management server

There are perhaps more changes (to expect)

Just to let you know

Christian

:36855


This thread was automatically locked due to age.
Parents
  • 0

    Hello JFC,

    this is getting confused and confusing :smileyhappy:. Normally I'd suggest starting another thread but as the issues could be related let's continue here. Trying to sort this out ...

    What does and what does not work? I have no idea whether you use one or more CIDs - could be only one which you publish with IIS, but as you mention MR I assume there are at least two. Do all clients updating from the WebCID fail?

    As an aside - are you trying to introduce a message relay (i.e. get rid of the port forwarding)?

    For any "current" SEC version the SUM should be version 1.4.2.186 and the associated ConfigCID.exe 2.0.17.0. - this is AFAIK the first one which would give you Failed to read signing key but then running the command on your server should not give you this message

    cac.pem should be in the root of the CID (i.e. in the SAVSCFXP folder) - as said, if you get the message that it could not be found it's either not there or there's a typo in the path.

    IIS is likely working correctly, the updating error could be caused by a "logical" error in the CID. The reason should be in the same ALUpdate log you posted the Cannot locate server message from - a number of lines down.

    HTH

    Christian

    :39527
Reply
  • 0

    Hello JFC,

    this is getting confused and confusing :smileyhappy:. Normally I'd suggest starting another thread but as the issues could be related let's continue here. Trying to sort this out ...

    What does and what does not work? I have no idea whether you use one or more CIDs - could be only one which you publish with IIS, but as you mention MR I assume there are at least two. Do all clients updating from the WebCID fail?

    As an aside - are you trying to introduce a message relay (i.e. get rid of the port forwarding)?

    For any "current" SEC version the SUM should be version 1.4.2.186 and the associated ConfigCID.exe 2.0.17.0. - this is AFAIK the first one which would give you Failed to read signing key but then running the command on your server should not give you this message

    cac.pem should be in the root of the CID (i.e. in the SAVSCFXP folder) - as said, if you get the message that it could not be found it's either not there or there's a typo in the path.

    IIS is likely working correctly, the updating error could be caused by a "logical" error in the CID. The reason should be in the same ALUpdate log you posted the Cannot locate server message from - a number of lines down.

    HTH

    Christian

    :39527
Children
No Data