Assessment job not started due to error: Max number of parallel assessments reached about pnpassessment HOT 12 CLOSED

I'm having the same issue :(

from pnpassessment.

@dirar / @oalfatyan : what version are you using? What's the OS you're running the assessment from? Can you try the following. Launch the assessment tool without any arguments, on the prompt you see type list and press enter. This shows the running assessments, if there are three already then you can't run more. You can wait for the existing runs to be done or stop them...or simply kill the running microsoft365-assessment.exe processes in case you don't need those runs.

from pnpassessment.

we are running the latest version 1.9.0 on windows 11, it is discovering 1181 sites and it fails immediately, is it due to a threshold by Microsoft? even changing the Thread option does not help

from pnpassessment.

and when tried to run the tool on a windows server 2019 I get this error: Assessment job not started due to error: Microsoft Graph service exception

from pnpassessment.

@oalfatyan : did grant the proper permissions for the AddInsACS run, see https://pnp.github.io/pnpassessment/addinsacs/requirements.html#permission-requirements for more details. Given you're using application permissions you need the following permissions:

• Microsoft Graph: Sites.Read.All, Application.Read.All
• SharePoint: Sites.Read.All

from pnpassessment.

The app permission is correct, also when I try to run it as interactive mode and with one site instead of tenant ...I get the same error

not sure how to proceed with this!

from pnpassessment.

@dirar : can you verify all microsoft365-assessment.exe processes are killed and then run below and share output:

from pnpassessment.

as requested

from pnpassessment.

The error has changed to the below

from pnpassessment.

can you copy the log output gathered in the folder where the exe file is and send it to [email protected]. The logs should tell us more about why you see the graph exception

from pnpassessment.

closing this one, root cause was missing Application.Read.All permission and not missing to provide the application id argument on the command line.

from pnpassessment.

@jansenbe Thank you

from pnpassessment.