Hi,
I’m working with version 2017 R3. Several live cameras are configured and seem to work well. When running SmartClient and pressing the record button on a camera view, recording seems to start correctly, and the status indeed shows it records.
However, when running the sample VideoViewer, selecting the same camera, and pressing the record button (which triggers the StartRecordingCommand message), nothing seems to happen, and no error is raised
More info:
Logged in as administrator
RuleSystem.log shows the following in the time of sending StartRecordingCommand message
2018-05-06 23:32:43.698+03:00 [ 53] INFO - RuleProcessor starting to execute rule action. Rule: fa2f8209-8d9b-4580-a6eb-17e58c99a610 (Default Record on Request Rule); ActionName: VideoOS.Recorder.RuleActions.DeviceRecordingRuleAction
2018-05-06 23:32:43.698+03:00 [ 53] INFO - DeviceRecordingRuleAction trigged, Executing action. recordingState=True sourceRuleId=fa2f8209-8d9b-4580-a6eb-17e58c99a610 sourceId=e8bd6cee-1119-4296-ba91-e3803e2c591e
Can you help me identify the problem?
Thank you
In c-code XProtect there is a rule named “Default Record on Request Rule”, if this rule is not enabled recording will not be done when using the functionality from the VideoViewer sample. My guess is that you have the rule disabled.
If the rule is completely missing make a rule like -
--
Perform an action on Request Start Recording
from External
start recording immediately on the devices from metadata
Perform stop action on Request Stop Recording
from External
stop recording immediately
--
When you have an administrator role user the issue explained in the thread below does not fit, but I would like to mention it so that you are aware..
https://developer.milestonesys.com/s/question/0D50O000042P1U7SAK/sendmessage-controlstartrecordingcommand-does-not-work-with-non-admin-user
Thank you for the response.
Just checked the value of this rule. It is there, and is already marked as ‘Active’
Is there any other log I can check to see why command is not accepted?
The MIP log might have something -
“[C:\ProgramData\Milestone\MIPSDK\MIP20180509.log](file:C:/ProgramData/Milestone/MIPSDK/MIP20180509.log)” (MIP[YYYYMMDD] log file name reflects the date)
If Audit Log -‘Enable user access logging’ is on you should be able to see the events in the Audit Log in the Management Client.
On a broader note there could be something in the debug logs for event server, recording server or management server -
[C:\ProgramData\Milestone\XProtect](file:C:/ProgramData/Milestone/XProtect) Event Server\logs
[C:\ProgramData\Milestone\XProtect](file:C:/ProgramData/Milestone/XProtect) Recording Server\Logs
[C:\ProgramData\Milestone\XProtect](file:C:/ProgramData/Milestone/XProtect) Management Server\Logs
Thank you
I did not see any notable comments in the described logs. None did even mention receiving the command request
Will consider re-installing the server, and update if it works