Is there any further context that appears before or after this error message?
(Ensure the "-v" command line option is used to produce verbose output, in case that gives any further details beyond what you are already seeing.)
(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)
That error smells like it might occur if bad command line options are provided. What is the full command line you are using?
(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)
So I assume the screenshot shared earlier was generated when using the "-v" command line option, but that option isn't shown in the command line above.
I should have been clearer that the "-v" option needs a number (specifying a verbosity level) after it - and if a number was not specified, that would explain the error you saw in that case. But it wouldn't explain the error seen when the "-v" option is not used.
Can you share a screenshot showing the exact full command used (including details such as exactly where spaces are and are not specified) and the full output it generates (obviously with sensitive details obscured)?
NB. An "IndexOutOfRangeException" from the CommandLineProcessor.Initialize function like shown in the screenshot indicates that a command line option where it expects to find a value following the option didn't have a value specified.
(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)
(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)
So I'm confused at what you're seeing. 🙂 There is no error shown in this screenshot. Has the problem stopped happening? Or if it is still occurring, where are you seeing the error?
(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)
So the command line with "-v" at the end is failing due to no number following the option.
The other command lines are not obviously showing any failure. So I'm guess I'm not sure what problem you are seeking input from the Community on here. Is there still an issue that is concerning you?
(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)
From what you're reporting now, the system.indexoutofrangeexception that is the focus of your question in this thread seems to be no longer be occurring.
I don't know exactly what output to expect from this agent. But unless an error is reported, I would assume that the agent is running OK until/unless you observe some kind of anomaly.
(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)
