Hi! I just finished a new SCORCH 2019 installation with Roll up 2 with no errors. Every role has its own server and database is on a SQL Hotell. Windows OS is 2016 and SQL is 2017. When I try to start a very simple RunBook from Orchestration Console just to test if setup is working, the RunBook starts but never finish not even time out or error. I can se in RunBook Designer that the RunBook is started but there are no logs there, not even when i stop the RunBook from Designer. I have a SCORCH environment in a Development domain that works perfectly setup in the same way. I would appreciate some help here, what have I missed? Best regards Mats

Hi @mats stenmark , the logs are located here: C:\ProgramData\Microsoft System Center 2012\Orchestrator\RunbookService.exe\Logs I guess you'll find something with problems to connecting to database there. Update Rollup 2 requires new SQL driver (MSOLEDBSQL). For more information, see the Microsoft OLE DB driver for SQL Server topic on the Microsoft Learn website . When it is installed run " Data Store Configuration " again. If Management Server and Runbook Server is installed on the same system check that kb4569536_managementserver_x86.exe is installed. UR2 consists of kb4569536_managementserver_x86 kb4569536_runbookdesigner_x86 and kb4569536_runbookserver_x86. If Mangement Service runs with the same account as Runbook Service I think there will be NO permission problems. Regards, Stefan

Hi @mats stenmark , If the Orchestrator Runbook service is throwing this error message while starting please check: Permissions of Runbook Service service account on the SCORCH Server Runbook Service service account is allowed and able to access the SQL database of SCORCH https://learn.microsoft.com/en-us/previous-versions/system-center/system-center-2012-r2/hh912319(v=sc.12) ---------- (If the reply was helpful please don't forget to upvote and/or accept as answer , thank you) Regards Andreas Baumgarten

New SCORCH 2019 installation. RunBook runs for ever

Accepted answer

Stefan Horz 3,461 Reputation points

2021-03-13T17:07:18.183+00:00

Hi @mats stenmark ,

the logs are located here: C:\ProgramData\Microsoft System Center 2012\Orchestrator\RunbookService.exe\Logs

I guess you'll find something with problems to connecting to database there. Update Rollup 2 requires new SQL driver (MSOLEDBSQL). For more information, see the Microsoft OLE DB driver for SQL Server topic on the Microsoft Learn website.

When it is installed run "Data Store Configuration" again.

If Management Server and Runbook Server is installed on the same system check that kb4569536_managementserver_x86.exe is installed. UR2 consists of kb4569536_managementserver_x86 kb4569536_runbookdesigner_x86 and kb4569536_runbookserver_x86.

If Mangement Service runs with the same account as Runbook Service I think there will be NO permission problems.

Regards,
Stefan
Please sign in to rate this answer.
mats stenmark 21 Reputation points

2021-03-13T20:50:02.833+00:00

Hi @Stefan Horz

The logs are showing error when i try to start the service

Blockquote

<Param>This computer was unable to communicate with the computer providing the server.</Param>
<Param></Param>
<Param>-2147467235</Param>
</Params>
</Exception>

And also
</Location>
<MsgCode>Unknown database type</MsgCode>
</Exception>

Blockquote

I did install the OLE DB driver on both servers prior to installation of Management server and RunBook server

I also did run the Data Store Configuration again without any errors. But RunBook service wont start.

I have a question about permissions during installation of SCORCH. Is it the service account that has to be Sysadmin during installation or is it the account running the setup?

Stefan Horz 3,461 Reputation points

2021-03-14T06:42:52.48+00:00

Hi @mats stenmark ,

have you executed "Data Store Configuration" also at the Runbook Server? Is Update kb4569536_runbookserver_x86 installed on the Runbook Server?
The SQL permissions are set bei the Orchestrator RTM Setup.

Regards,
Stefan

mats stenmark 21 Reputation points

2021-03-14T12:58:02.03+00:00

Hi @Stefan Horz !

For some reason I thought that "Data Store Configuration" only had to be run on Management server, but I was wrong :P. And it makes sense since RunBook Designer had access to the database since I could check RunBooks in and out and also that I could see that all imported RunBooks actually was in the database. And I guess its because Designer goes trough Management server to reach database, and I did run "Data Store Configuration" on that server. So after I run "Data Store Configuration" on RunBook server the RunBook service started perfectly and now I can run RunBooks from webservice.

Thanks Stefan, you are the best!

Best regards
Mats
Sign in to comment

New SCORCH 2019 installation. RunBook runs for ever

5 additional answers