OK, I think I've resolved it, but not 100% sure what did it. so what seems to be happening is that Milestone is telling the remote client to connect to it's NAT IP instead of the external IP. When I access the system from the internet ( What I see come back in my browser is "waiting for 192.168.0.10:8081". and they use the same port as the iOS app!
however, I am unable to get the Milestone client app or web client working. On the internet, pointing to my home router via DynDNS, I can get the Milestone Mobile App working on my iOS device. I can get all clients and services working when pointed to the local IP of the box. On the local network, everything works fine.
On my home router I forwarded ports 8080 (the one I used for Milestone's primary install as port 80 was in use on the machine), 8081 (mobile http) and 8081 (secure http) to the box running Milestone. I also downloaded and installed Milestone Mobile server components. It is working really well other than a very frustrating problem so I'm wondering if anyone here has any ideas.Īt install time, Milestone gives the option of specifying an internal and external IP address.
I installed the software with the 30 day trial license, onto a spare Windows Home Server I had around (basically Windows Server 2003). The end of the latest Database log shows archiving progressing with the note that “Maximum size limit (819200 MB) reached for bank!” So apparently these errors were blocking archiving.So, in an effort to move away from my buggy Synology setup I have been giving Milestone XProtect Express a shot. The good news is that the archiving function started working again MediaDatabase is back to just over 800GB of space used. Unfortunately, recent historical footage for the Alley camera is not available. After restarting the Recording Server, the cache was rebuilt and Alley camera recording resumed: Solutionįinally I followed the advice (for a somewhat different problem) in this post: with Recording Server stopped, in the root of the live disk’s E:\MediaDatabase folder, I deleted archive_cache.xml and cache.xml.
Stopping and starting recording did not re-activate the camera. The Recording tab for that camera confirms the error: Sure enough, recording has stopped on that camera:
One of the messages mentions the alley camera.
End of inner exception stack trace -Īt (String tableName, String bankDirectory, String description, String group)Īt (Guid deviceId, String tableName, TableOption tableOption, String tableDescription, String tableDataGroupName, String mediaDataType, Boolean manuall圜ontrolCommitSequence, RawDbChannel channel)Īt (Guid deviceId, String tableName, String tableDescription, String tableDataGroupName, String mediaDataType, RawDbChannel channel)Īt () : Failed to create table -> : Failed to create table -> : Error opening table '22c63e5d-b218-4e62-bf00-2faf95c15b4a'!, Error opening table '22c63e5d-b218-4e62-bf00-2faf95c15b4a'!, Error opening table!, Expansion timeslice is not valid! -> : NmDatabase::CmClientTable::Open (line Client/ClientTable.cpp, 264): Error opening table '22c63e5d-b218-4e62-bf00-2faf95c15b4a'! -> : NmDatabase::CmServerClient::OpenTable (line Server/ServerClient.cpp, 944): Error opening table '22c63e5d-b218-4e62-bf00-2faf95c15b4a'! -> : NmDatabase::CmTable::Open (line Core/Table.cpp, 419): Error opening table! -> : NmDatabase::CmTableColumn::ExpandTimeSlice (line Core/TableColumn.cpp, 1915): Expansion timeslice is not valid!