@Mauro , can you share the alert details?  I want to see if it mentions any log files.  We might be able to get more out of the timestamp.  I would assume EVMgrS.log, thoughg want to see if there’s more.

Hi Mike

The alert is quite vague.
I’ve checked the logs and can’t see any references to this alert.
I’ll keep investigating so long.

 

Can you click on the Warning or Level 2 link to get further?

I’m pretty sure you can click further for the details (and if not, that’s a CMR we need to make ).

Hi Mike

Those two links take you to the CVLT Documentation sight so unfortunately give no info.

These are the two links.
The second one is broken.

https://documentation.commvault.com/11.24/expert/8091_setting_strength_requirements_for_user_passwords.html

http://documentation.commvault.com/additionalsetting/details?name=passwordComplexityLevel

Sounds like we need a CMR (or just more info).  Can you open a support case and see a) where this is listed and b) if we can get a CMR to add this to that dashboard/report?

Otherwise, it’s not really that useful 

Thanks Mike.

I’ll do that now.
What is the process to open a CMR for something like this? Seeing this affects all customers I have, I wouldn’t be able to log it to any specific one and I believe a CMR does carry a cost?

No cost for a CMR (a CCR is where you commit to something which is done via your Account rep).

You should be able to open a support case under any customer, then once dev accepts the CMR, ask that all of your CCIDs get added to it.

This way you can view it in the Command Center console.

Hi @Mike Struening 

So it turns out that this error is resolved with a registry key on the Commserve.
Once added or modified to 3, the error is cleared. I tested an account and at 11 characters it gives you an error, so it is working properly.

 

https://documentation.commvault.com/additionalsetting/details?name=passwordComplexityLevel

Thanks again.

Regards,
Mauro

@Mauro , I appreciate you sharing!!  I’ll mark this as the Best Answer for all posterity!

Thanks, buddy!

Only a pleasure. It seems that link that was broken is now working which has that info on the registry key.
Very handy.