Orchestrator 2022 Web Console

David Kohler 0 Reputation points
2023-08-01T22:45:42.3066667+00:00

Greetings fellow SCORCHers!

I have a new fresh install, and have hit a wall with the web console. I have installed CU1, and the hot-fix after that.

When I go to the console, using either localhost, or FQDN, on the local server, or FQDN from other systems, I authenticate, then Active jobs and Completed jobs is blank, and "Folders and Runbooks" is stuck loading.

Using developer tools in the browser I see the following:

SyntaxError: Unexpected end of JSON input at JSON.parse (<anonymous>) at XMLHttpRequest.st (http://scorch01.contoso.com:82/main.ed82a97a3ae28433.js:1:548775)

"Http failure during parsing for http://scorch01.contoso.com:81/api/folders"

I have tried reinstalling the Web Console, and Web API

Any guidance would be greatly appreciated.

Dave

System Center Orchestrator
System Center Orchestrator
A family of System Center products that provide an automation platform for orchestrating and integrating both Microsoft and non-Microsoft IT tools.
214 questions
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. XinGuo-MSFT 14,386 Reputation points
    2023-08-04T07:39:34.1666667+00:00

    Hi,

    Here are some steps you can take to troubleshoot and resolve the issue:

    1. Check SCORCH and IIS Logs: First, review the SCORCH and IIS logs to look for any specific error messages or warnings related to the web console. The logs may provide more detailed information about what's causing the problem.
    2. Check Web Console Configuration: Ensure that the Web Console is properly configured to connect to the correct Orchestrator server and API endpoint. Check the web.config file of the Web Console and make sure the <Orchestrator> section contains the correct information, including the server name, port, and credentials.
    3. Clear Browser Cache: Sometimes, caching issues in the browser can cause problems. Try clearing your browser cache and cookies and then reload the web console to see if that resolves the issue.
    4. Check the Application Event Log for the WebAPI
    0 comments
  2. Stefan Horz 3,461 Reputation points
    2023-08-04T13:55:54.85+00:00

    Hi,

    does opening http://scorch01.contoso.com:81/$odata in browser work?

    If yes make sure the URL for WebConsole is listed in in "C:\Program Files\Microsoft System Center\Orchestrator\WebApi\web.config".

    Regards,

    Stefan

    0 comments
  3. David Kohler 0 Reputation points
    2023-08-04T13:58:58.5933333+00:00

    The fix was to grant the service account the db-owner role for the database. It had the one highlighted in yellow. I added db_owner, and the console started working.
    User's image

    0 comments