Vivotek CC9381-HV streaming problem.
AnsweredHi,
I did an update on an good working and connected Vivotek camera (CC9381-HV).
Update from 0100 to 0222 and yes rebooted the camera and reset the camera to factory default, but still nno connection possible. this is the error i recived:
Confirming server availability.
OK
Confirming camera is accessible.
OK
Confirming target camera provides media stream.
FAILED: Camera request "CreateProfile" failed with error "Fault info. Reason: A profile with the token ProfileToken already exists. (media1). Additional: SOAP-ENV:Sender. Sub info: "http://www.onvif.org/ver10/error":InvalidArgVal. ". Please try to reboot the camera, then restore factory defaults on the web-page. Finally, try to update firmware. If the problem persists, please contact support.
Diagnostics complete
I hope you can help me out with this one.
-
Hi @...,
Please follow the steps as described below:
-
Remove the device from the system.
-
Stop the mediaserver application and paste the resource_data.json file in the following LINK at the following location:
-
For Windows: C:\Program Files\Network Optix\Nx Witness\MediaServer
For Linux: /opt/networkoptix/mediaserver/bin/ -
Now start the mediaserver application again.
-
Add the device again.
To stop and start the media server, please do it as follows:
For Windows: Open the task manager, select tab ‘Services’ find the mediaserver application, right-click and select; Stop or Start
For Linux: Open the terminal (Ctrl+Alt+T) and enter the following command; sudo service networkoptix-mediaserver restart.
After this, the request should be fulfilled.
Please confirm, and we will add it to a future patch.0 -
-
Hi @...,
Just checking in to make sure you received our response as it has been a while since we have heard from you. Please let us know if you still need help by responding to this message.
0 -
Hi @...,
We have not heard back from you in a while, so we are going to assume your question has been answered and set this topic to 'Answered'.Be aware that since we did not receive feedback that this 'fix' won't be added to future patches or releases.
0
Please sign in to leave a comment.
Comments
3 comments