- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
05-13-2024 05:52 AM
I'm looking for a solution to this if anyone has any ideas.
The detection log lists each machine found in the OU, which indicates that the LDAPS connection is successful. However, in that same log, each machine has a message like this:
"ScanMachineTaskHandler | Execute | Error in execute for machine [FQMACHINENAME] Reason:Source array was not long enough. Check srcIndex and length, and the array's lower bounds."
The last two lines in the log are:
10/05/2024 10:00:09.377 | TasksRunner | HandleTaskRunGeneralError | Failed to invoke task: id=38,taskTypeId=1,creationTime=1715347374,status=0,inputParameters=<ActiveDirectoryListMachinesTask z:Id="1" xmlns="PIMSuiteData.Facade.CPM.Scanner" xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns:z="http://schemas.microsoft.com/2003/10/Serialization/"><SourceName z:Id="2">Active Directory</SourceName><SafeId>24</SafeId><FileNumber>3</FileNumber><LDAPPath z:Id="3">OU=[OUNAME],OU=[OUNAME],DC=[DCNAME],DC=com</LDAPPath><LDAPAddress z:Id="4">[DOMAINNAME]</LDAPAddress><DisableUsages>true</DisableUsages><ScanType>WIN</ScanType><ShouldUseLDAPS>true</ShouldUseLDAPS></ActiveDirectoryListMachinesTask>,retry=0,minStartTime=0,createdBy=[createuser],discoveryName=Windows discovery from [detection name],nextRunTime=1715349600,schedulingInfo=0 0 10 ? * 6,lastRunTime=2147483647,Consumers=i64UserObjectId=14,UserName=PasswordManager,TaskRuns=. error: Index was outside the bounds of the array.
10/05/2024 10:00:09.377 | Discovery ended. Discovery Name: Windows discovery from [detection name]
05-20-2024 07:54 AM
Hey there,
We have seen this happen when the scanner user does not have access to the folder where the account discovery logs are written to on the CPM machine. Can you check this for me and see if there are permissions issues there? If they are, adding that user to the folder should resolve them.
Thanks,
Sarah
Strategic Support
05-20-2024 07:54 AM
Hey there,
We have seen this happen when the scanner user does not have access to the folder where the account discovery logs are written to on the CPM machine. Can you check this for me and see if there are permissions issues there? If they are, adding that user to the folder should resolve them.
Thanks,
Sarah
Strategic Support
11-05-2024 11:01 AM
Happen to come across this too and the scanner user has full R/W rights to the account discovery logs folder (and the log folder above it).
I can't seem to find any other information about that error. Previously did scans didn't have a problem until last week and there have been no changes.
12-03-2024 03:15 PM
Same issue here. Also confirmed the scanner account has the appropriate permissions for the Scanner logs. It doesn't seem to be a permission issue though as many accounts are processed fine.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

