lelle1 Absent Member.
Absent Member.
2519 views

Error 1024

Hi,

we are doing a PoC for a customer thats interested in file reporter for OES, setup went fine.
We got nameresesolution working (slp and hostfile) but we do get a error trying to send scans, both file and trustees
This is what ends up in the log file on the enginee, nothing much on client. I have checked that client runs

Dispatching permission scan for target \\CLUSTER-XXX-SERVER\XXX, scan ID 9...
2018-03-11 21:56:52 3600 5 0005 624 2100 SSC: Dispatching permission scan for target \\CLUSTER-YYY-SERVER\YYY, scan ID 10...
2018-03-11 21:56:52 3600 3 0005 624 2096 SSC: Failed to dispatch scan for target \\CLUSTER-XXX-SERVER\XXX, result: 1024.
2018-03-11 21:56:52 3600 3 0005 624 2100 SSC: Failed to dispatch scan for target \\CLUSTER-YYY-SERVER\YYY, result: 1024.
2018-03-11 21:56:52 3600 8 8010 624 2096 SQL: SQL Processing SQL query: 'SELECT retry_count FROM srs.scans WHERE id = ?', Param 0 (): 9
2018-03-11 21:56:52 3600 8 8010 624 2100 SQL: SQL Processing SQL query: 'SELECT retry_count FROM srs.scans WHERE id = ?', Param 0 (): 10
2018-03-11 21:56:52 3600 8 8010 624 2112 SQL: SQL Processing SQL query: 'DELETE FROM srs.scan_active_tasks WHERE id=?', Param 0 (): 14
2018-03-11 21:56:52 3600 8 8010 624 2096 SQL: SQL Processing SQL query: 'SELECT * FROM srs.scan_policies WHERE id=?', Param 0 (): 1
2018-03-11 21:56:52 3600 5 0005 624 2096 SSC: Scheduling retry for scan 9, retry interval 900, try 0 of 3.
2018-03-11 21:56:52 3600 7 800c 624 2096 Sched: Attempted to Register ScanSchedulerService Scheduled Task [32], Result = 0.
2018-03-11 21:56:52 3600 8 800c 624 3556 Sched, ST: Acquired Maintenance Semaphore. Dormant for 45006 ms, nTimeout was 233000 ms.
2018-03-11 21:56:52 3600 7 800c 624 3556 Sched, ST: Next on the queue AgentManagerService Scheduled Task 2 will be executed Sunday, March 11, 2018 22:00:00 (188 seconds from now).
2018-03-11 21:56:52 3600 8 8010 624 2100 SQL: SQL Processing SQL query: 'SELECT * FROM srs.scan_policies WHERE id=?', Param 0 (): 1
2018-03-11 21:56:52 3600 5 0005 624 2100 SSC: Scheduling retry for scan 10, retry interval 900, try 0 of 3.
2018-03-11 21:56:52 3600 7 800c 624 2100 Sched: Attempted to Register ScanSchedulerService Scheduled Task [33], Result = 0.
2018-03-11 21:56:52 3600 8 800c 624 3556 Sched, ST: Acquired Maintenance Semaphore. Dormant for 0 ms, nTimeout was 188000 ms.
2018-03-11 21:56:52 3600 7 800c 624 3556 Sched, ST: Next on the queue AgentManagerService Scheduled Task 2 will be executed Sunday, March 11, 2018 22:00:00 (188 seconds from now).
2018-03-11 21:56:52 3600 8 8010 624 2096 SQL: SQL Processing SQL query: 'UPDATE srs.scans SET agent_name=NULL, scan_start_time=NULL, retry_count = retry_count + 1, next_retry_time=srs.timet_to_datetime(?), status_code=?, error_string=?, progress_status=-2 WHERE id = ?', Param 0 (): 1520806260, Param 1 (): 1024, Param 2 (): No agent available for delegation., Param 3 (): 9
2018-03-11 21:56:52 3600 8 8010 624 2100 SQL: SQL Processing SQL query: 'UPDATE srs.scans SET agent_name=NULL, scan_start_time=NULL, retry_count = retry_count + 1, next_retry_time=srs.timet_to_datetime(?), status_code=?, error_string=?, progress_status=-2 WHERE id = ?', Param 0 (): 1520806260, Param 1 (): 1024, Param 2 (): No agent available for delegation., Param 3 (): 10
2018-03-11 21:56:52 3600 8 8010 624 2108 SQL: SQL Processing SQL stored procedure: 'srs.add_notification_entry', Param 0 (notification_timet): '1520801812', Param 1 (target): '{A8E7469A-C9B6-45C4-9E8D-9A46E7A8B6C9}', Param 2 (type): '2', Param 3 (severity): '1', Param 4 (status_code): '1024', Param 5 (destination_type): '1', Param 6 (subject): 'Scan Failure', Param 7 (message): 'The scheduled permissions scan (Scan ID 9) for storage path \\CLUSTER-XXX-SERVER\XXX was unable to complete. No agent is available for the specified storage path.There are 3 retry attempts remaining. The next attempt will be made in 4448 seconds.'
2018-03-11 21:56:52 3600 8 8010 624 2104 SQL: SQL Processing SQL stored procedure: 'srs.add_notification_entry', Param 0 (notification_timet): '1520801812', Param 1 (target): '{A8E7469A-C9B6-45C4-9E8D-9A46E7A8B6C9}', Param 2 (type): '2', Param 3 (severity): '1', Param 4 (status_code): '1024', Param 5 (destination_type): '1', Param 6 (subject): 'Scan Failure', Param 7 (message): 'The scheduled permissions scan (Scan ID 10) for storage path \\CLUSTER-YYY-SERVER\YYY was unable to complete. No agent is available for the specified storage path.There are 3 retry attempts remaining. The next attempt will be made in 4448 seconds.'

/Lelle
2018-03-11 21:56:52 3600 8 8010 624 2108 SQL: SQL Processing SQL stored procedure: 'srs.add_notification_entry', Param 0 (notification_timet): '1520801812', Param 1 (target): '', Param 2 (type): '2', Param 3 (severity): '1', Param 4 (status_code): '1024', Param 5 (destination_type): '2', Param 6 (subject): 'Scan Failure', Param 7 (message): 'The scheduled permissions scan (Scan ID 9) for storage path \\CLUSTER-XXX-SERVER\XXX was unable to complete. No agent is available for the specified storage path.There are 3 retry attempts remaining. The next attempt will be made in 4448 seconds.'
2018-03-11 21:56:52 3600 8 8010 624 2104 SQL: SQL Processing SQL stored procedure: 'srs.add_notification_entry', Param 0 (notification_timet): '1520801812', Param 1 (target): '', Param 2 (type): '2', Param 3 (severity): '1', Param 4 (status_code): '1024', Param 5 (destination_type): '2', Param 6 (subject): 'Scan Failure', Param 7 (message): 'The scheduled permissions scan (Scan ID 10) for storage path \\CLUSTER-YYY-SERVER\YYY was unable to complete. No agent is available for the specified storage path.There are 3 retry attempts remaining. The next attempt will be made in 4448 seconds.'
0 Likes
2 Replies
Micro Focus Contributor
Micro Focus Contributor

Re: Error 1024

In the log I see the following: "No agent is available for the specified storage path"

If the agent is installed on a server, File Reporter will know that this agent will need to be used to scan this server. In this case with a Cluster volume you will need to tell the system what agent should be used to perform the scan for this scan target.

Within File Reporter webconsole go to Administration -> Agents
Select the agent that should be used to scan the cluster volumes and click "Assign Proxy Targets"
Select the Cluster volumes that need to be scanned by this agent
0 Likes
lelle1 Absent Member.
Absent Member.

Re: Error 1024

Thanks, now it's working
/Lelle
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.