Problems with 2024.3

2024.3 is a mess

Hi Stephan,

I’m sorry to hear about your concerns. With the 2024.3 release, we had to implement some fundamental changes to ensure we deliver secure products. Unfortunately, this has resulted in some temporary inconveniences, which are documented here: ARM 2024.3.0.298 information
We have suggested clear workarounds for these issues and aim to provide more permanent solutions in the upcoming service release.

Been through the documents. The Exchange scan terminates abnormally and permissions can't be altered. 

Any idea what is causing this? Here is the event log. Maybe an indicator for a problem which can be resolved without opening a ticket:

[   1394|<MX-Server>|pnCollector |25052.1| 75|<DOMAIN>\SYSTEM             |pn.jobs.JobCenterImplementation         |240801| 9:37:27.041|Error      ]             JobStatus.addError(Object source, MultiLingualString error): Abnormal process termination.

We have a couple of resolutions:

1. When setting the account for exchange scan, use the same account which was used for ARM installation.

2. The other workaround involves setting up a Windows task that enables the PnJob to run with the account configured for the scan, regardless of whether the user is logged in or not.

How to configure the Windows Task Scheduler to start the PnJob

1. Open Task Scheduler:

· Press Win + R, type taskschd.msc, and press Enter.

2. Create a New Task:

· In the Actions pane on the right, click "Create Task".

3. General Tab:

· Provide a name for the task.

· Add the account used in the Exchange Scan

· Under Security options, select "Run whether user is logged on or not".

· Check "Run with highest privileges" if the job requires elevated permissions.

4. Triggers Tab:

· Click "New".

· Select "On an event" from the "Begin the task" dropdown.

· In the Log select 8MAN

· Click OK.

5. Actions Tab:

· Click "New".

· For the "Action" dropdown, select "Start a program".

· Click "Browse" and select: pnJob.exe located in C:\Program Files\SolarWinds\ARM\bin

· Click OK.

6. Conditions Tab:

· Uncheck "Start the task only if the computer is on AC power" if it's not relevant.

7. Settings Tab:

· Ensure settings like "Allow task to be run on demand" are checked.

8. Save the Task:

· Click OK, then provide your credentials when prompted.

Wow. Number 1 already solved the problem. I would have never used this account since it always was another Service Account which now does not work anymore, but only for Exchange.. Anyway, thank you.

Hi Keshav,

I have tried the workaround with the Windows Task.
Before, I got this error when I started the Exchange Scan:

Now I no longer get this error. However, 0 items are scanned:

Do you have any other idea?
If I use the account that was also used for the ARM installation, then I would have to give it additional rights, which I would like to avoid.

Kind regards

Jonas

Hi Jonas,

I understand the hesitation to provision additional rights. Please create a support ticket so we can investigate this further.

The exchange scan and making changes only works for us when the account that installed the software and runs the scan is logged in on the ARM Server :-(

The exchange scan and making changes only works for us when the account that installed the software and runs the scan is logged in on the ARM Server :-(