ScriptRunner Error Events

ScriptRunner & Windows Event Log related entries

Please note that an administrative PowerShell console at the ScriptRunner Service host is required to run the cmdlets of the ScriptRunnerSettings module.

Use the Get-AsrWinEvent cmdlet in the PowerShell console of the ScriptRunner service computer to receive ScriptRunner events from the Windows Event Log.

The parameters Level, MaxEvents and Oldest are allowed.

Example: Get-AsrWinEvent -Level Error, Warning -MaxEvents 5

 

The Event IDs are separated in different sections

  • 0 - Startup, Shutdown eventlog messages
  • 10 - License eventlog messages 
  • 20 - Scheduler eventlog messages 
  • 30- Loading scripts, modules, credentials 
  • Database eventlog messages
  • 40 - local database 
  • 50 - external database 
  • 60 - Connector eventlog messages 
  • 70 - WebAPI eventlog messages 
  • 80 - Query eventlog messages 
  • 90 - Various events 
  • 100 - Inbound Connector 

There are generic Errors, Warnings and Information Logs in each section.

Errors

ID

Message

5

{0} {1} received a serious error and is shutting down. Error message: {2}

7

ScriptRunner failed to run background task. The reported error was: {0}

8

ScriptRunner runtime exception: {0}

13

Error reading {0} license: {1}

15

{0} license expired. All functions have been disabled.

17

{0} License: {1}

19

{0} License ({1} Users): rejecting user '{2}'. Reason: {3}

22

ScriptRunner Scheduler: Failed to start scheduled action {0}. The reported error was: {1}

23

ScriptRunner Scheduler: Invalid schedule disabled for action {0}. The reported error was: {1}

41

ScriptRunner DbManager: Local database error: {0}. Database: {1}

45

ScriptRunner DbManager: Local database cleanup failed: {0}. Database: {1}

51

ScriptRunner DbManager: Failed to export report to the external database - element may be missing! The element is ID={0} in the local database ({1}).

52

ScriptRunner DbManager: External database error: {0}. Database: {1}

53

ScriptRunner DbManager: External database error: {0}. Database: {1}

55

ScriptRunner DbManager: Local filesystem buffer error: {0}. If the local filesystem buffer does not work, your external database may start missing reports. The local filesystem buffer is: {1}

60

ScriptRunner E-Mail Notifier: Email notification failed ({0}). Reason: {1}

60

ScriptRunner E-Mail Notifier: Email notification failed ({0}, {1}). Reason: {2}

64

ScriptRunner E-Mail Inbound Connector: Email processing failed ({0}). Reason: {1}

66

ScriptRunner Password Server Connector: Failed to connect to '{0}'. Reason: {1}

90

ScriptRunner: Error executing Action '{0}': {1}

99

ScriptRunner Service internal error (Assert error): {0}

Warnings

ID

Message

6

ScriptRunner did not start Action{0}. Reason: {1}

9

ScriptRunner Warning: {0} {1}

12

{0} Evaluation License ({1} Users). This license will expire in {2} days. {3}

18

{0} License: {1}

24

ScriptRunner Scheduler: Deferring scheduled action {0}. {1}

26

<Generic Message>

30

ScriptRunner script library status: {0} old script references and {1} old script parameter references deleted: {2}

34

ScriptRunner: {0} credentials missing in Windows Credential Manager ({1}): {2}

35

ScriptRunner: Error reading script library - file will be ignored! '{0}': {1}

36

ScriptRunner: Error reading params - file will be ignored! '{0}': {1}

39

ScriptRunner: Error reading module '{0}' - module will be ignored! {1}

44

ScriptRunner DbManager: Local database force cleanup: {0}. Database: {1}

54

ScriptRunner DbManager: There are {0} report elements queued in the local filesystem buffer, waiting for the external report database. Make sure your external database is operational and connected, so that ScriptRunner can successfully write these reports to the external database! The buffer size is limited to {1} reports; if the buffer is full, your external database may start missing reports. The local filesystem buffer is: {2}

65

ScriptRunner E-Mail Inbound Connector: Shutting down but {0} jobs may be still running: {1}

77

ScriptRunner WebAPI: {0}

80

<Generic Message>

81

Can't resolve Choice reference {0}. {1}

101

ScriptRunner {0} Connector{1}{2}: {3}

For a detailed error analysis the ScriptRunner logs can be used under <C:\ProgramData\ScriptRunner\Service\Local\Log>