Problems with 2024.3

Hi Marcus,

You can use the following support article to resolve this issue.  Use the web client to get the init code for the rich client on remote workstations.
https://support.solarwinds.com/SuccessCenter/s/article/How-to-register-the-ARM-clients

Please open a support ticket if you need more assistance.  There were a lot of changes with the latest ARM release so we're still catching up on support documentation.

As I mentioned in my post: my web client does not have the "settings -> connection security" entry. So I can't get any init code from there. so how do I register my rich client? Ah and BTW. the automatic update of the collectors doesn't work anymore. We have to manually update all of our collectors.

You need to log in to the Web client with an admin-level user to see Settings > Connection Security 

There are some instances where the collectors will not update automatically.

If you still have issues, please open a support case.

Logged in with an admin account. No Settings > Connection Security. Opening a support case is not the best idea.

2024.3 is a mess

In the meantime the problem has been fixed. We had to tweak the mainXXXXX.js file in the grantma wwwroot folder. I think most people with 8MAN license are affected.

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.