New SCORCH 2019 installation. RunBook runs for ever

Question

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

Answer 1

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

Answer 2

Thanks Andreas!

Since the RunBook is developed and tested in my development environment I didnt think that the problem could be related to the RunBook. But you are right, information is always useful. I dont use any IP:s, only build my own in powershell. This RunBook creates a Collection in MEMCM and is a part of a larger Main RunBook using Invoke RunBook. Could it be that I have missed something when I imported the RunBook? Its actually the first time I try export/import RunBooks

The script in .Net activity

#-- Orchestrator Published Data or Global Variables ----------------------------------------------------------------------------------  
$SiteCode = "Populated by Initialize Data"  
$Collection_Name = "Populated by Initialize Data"  
$Limiting_Collection = "Populated by Initialize Data"  
  
  
  
#Load Configuration Manager PowerShell Module  
import-module ($Env:SMS_ADMIN_UI_PATH.Substring(0,$Env:SMS_ADMIN_UI_PATH.Length-5) + '\ConfigurationManager.psd1')  
$SiteCode = $SiteCode + ":"   
set-location $SiteCode  
  
 Try  
{  
    # Check if Collection allready exist, if not create.  
    $New_Collection_Exist = Get-CMCollection -Name $Collection_Name  
    If ($New_Collection_Exist -eq $null)  
    {  
        New-CMCollection -CollectionType Device -LimitingCollectionName $Limiting_Collection  -Name $Collection_Name    
        $New_Collection_Exist = Get-CMCollection -Name $Collection_Name  
        If($New_Collection_Exist -eq $null)  
        {  
            $New_Collection_Exist = "False"  
            $Success = "False"    
        }  
        Else  
        {  
            $New_Collection_Exist = "True"   
            $Success = "True"    
        }  
    }  
    Else  
    {  
        # Collection allready exist ----------------------------------------  
        $Success = "False"    
    }  
}  
  
Catch  
{  
    $ErrorMessage = $Error.Exception.Message  
    $ErrorPosition = $Error.InvocationInfo.PositionMessage  
    $Success = "False"      
}  
# Data output so Orchestrator can read them into Databus ------------------  
$ErrorMessage  
$ErrorPosition  
$Success  

Answer 3

I created a new RunBook as you suggested and I got the same result, RunBook runs forever and no logs in Designer. But when I try my Collection RunBook via RunBook Tester it actually works perfect and creates a new collection in MEMCM.

Thank you Andreas, I have to remember to use that tool next time I get an error.

So, perhaps we have narrowed the error to webservice somehowe I guess. I am not sure but I think that the webservice will send its request to the database and RunBook server would check if there is a job there.

Is there a way to check if RunBook server actually are running the RunBook or if its just in the Designer that shows a green arrow for the RunBook?

Any suggestions on how to proceed?

Answer 4

Hi,

make sure "Orchestrator Runbook Service" is started and running.

Regards,
Stefan

Answer 5

Hi Stefan!

I must apologize for not checking such a fundamental thing. And of course, you where right the service are not started. But will not start, not even after a reboot. Unspecified error . Windows event logs dont say anything more. Any suggestions on how to solve this?