x Want to participate? Join the group to interact
  • State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 139 subscribers
  • Views 289 views
  • Users 0 members are here
Browse Forums
Announcements
237
topics
29
replies
General Discussion
5k
topics
13k
replies
Sage Data & Analytics
56
topics
95
replies
Sage Enterprise Intelligence
210
topics
416
replies
Sage Intelligence Reporting
121
topics
322
replies
DeepakN

web scheduler - Error on Load properties from configuration manager

SUGGESTED
Posted By

Hi Guys,

Hope you can help with this, we are trying to install Web-Scheduler 2023 U1 (graphQL version) as a brand new install. We have gone through all the pre-requisites including creating self signed certificate and installing latest sage services and the install goes though without errors until we get this message:

We have tried browsing directly from IIS, but get the following error:

we have restarted server, tried different browsers, ports etc, with no luck. Any ideas on this?

  • 0
    SUGGESTED

    Hello Deepakn,

      You shouldn't really be using self-signed certificates as they are not supported and this is one of the reasons why but lets ignore that for now and assume this is a one-off demo system where it doesn't make sense to pay a certificate authority.

    As a first step I'd check:

    1) Does your certificate have a subject alternative name in addition to the subject? For example, I have *.example.com as my subject and in the subject alternative name of example.com and *.example.com. If not recreate it

    2) Beyond being placed in your personal certificate store, Is your self-signed certificate recognized as valid in your certificate chain?

  • 0 in reply to Dylan Connor

    Thanks Dylan! 

    We seem to have got around the problem (for now) still using a self signed certificate. We can now connect however only via Edge :) Chrome still returns the same issue so not really fixed.

    I think you are right regarding the certificate not be recognized as being valid...will keep checking.

  • 0

    Hi,

    In my case, he solution was uninstalling the following

    Microsoft .NET Core 3.1.26 - Windows Server Hosting

    Microsoft .NET Core 5.0.17 - Windows Server Hosting

    Microsoft .NET Core 6.0.6 - Windows Server Hosting

    Restart IIS and Retry the connection.

    Else, before launching the setup, unistall these components.

*Community Hub is the new name for Sage City