Do you want to connect to this server?īetter create a dedicated restricted Windows user account for mobile app usage and add it to AXIS Camera Station. Wrong certificate: The server certificate has changed and we don't know if you are communicating with. The following error messages are shown in the mobile app: Mobile app cannot login to the AXIS Camera Station server If none of the above helps, escalate the issue to AXIS Support. Unicast via RTSP, tunneled via HTTP: axrtsp Windows Media Player is used for verifying that all required components used by AXIS Camera Station are installed on the computer. Unicast via RTSP: axrtsp:///axis-media/media.amp Unicast via RTP: axrtpu:///axis-media/media.amp (Make sure to enter the actual IP of the camera in each command): Try to open a video stream from Windows Media Player with the methods below. See the Windows Media Downloads page.Ĭheck if windows media player is fully installed.
Windows Server 2003, suggest the customer to install Windows Media Format SDK. Windows Server 20, see this FAQ for more information. Windows Server 2016: install version with Desktop Experience. Windows Server OS, make sure the Desktop Experience is installed. No video stream can be played in AXIS Camera Station although other functions work fine.
Health check on any network deice (switch/router/network adapter/cable) in use between cameras, server and client.Ĭannot update device firmware through AXIS Camera Station Make sure no other bandwidth consuming application is running at the same time.Įnough bandwidth / Remote or local network
Make sure no other CPU/RAM consuming application is running at the same time.Ībnormal bandwidth usage corresponding to the same time as the issue. Stream with same profile or lower resolution.Ībnormal CPU/RAM usage corresponding to the same time as the issue. Many different streams being used from the same camera, especially high resolution.Ĭould be a problem especially for some M-Line cameras. Other VMS client than AXIS Camera Station connected to the camera.ĭisconnect the camera from the other client and restart it.
Virtual Machine is not supported for the client.Īsk the customer for their typical use case. With dedicated graphic card, see Hardware Guidelines. With internal graphic card, no more than two monitors per graphic card is recommended. Try to run the client on a dedicated computer.
Verify that the graphic card’s or network adapter’s driver is up to date.Ĭheck on the manufacture’s website if the driver is the latest for this OS.Ĭlient and Server running on the same machine. I use 600 as a test, I would like to use a more reasonable 240 in practise.Open the DirextX Diagnostic Tool (search for dxdiag on the computer). The Internet opinion seems divided on this issue. I have tried creating the AutoStartDelay entry as both a REG_SZ and a REG_DWORD as Which is described as doing what I would like it to do, however my attempts to set the delay to 600 seconds instead of 120 seems not to make any difference to the delay time. I have read about a registry setting HKLM\SYSTEM\CurrentControlSet\Control\AutoStartDelay
However, I would like to start some services after a service has collected data from a serial comms line, which takes 180 seconds on this large installation I am working on. It is hard to accurately time the delay, but it seems to agree with the documentation that 120 seconds after the last autostart service starts. I have changed the services from "Autostart" to "Autostart (Delayed)" and now see that my services are starting after the otherĪutoStart services.
I am trying to increase the delay for some of my services on a Windows Server 2012 Standard Edition system.