Subscriber Discussion

Problems Installing Milestone Recording Server As A Failover

UM
Undisclosed Manufacturer #1
•Dec 17, 2018

I am currently installing Milestone Corporate 2018 R3 (12.3a) for a customer, and have run into an issue.

The servers are all running Windows Server 2012.  The servers are not yet joined to a domain, they are currently being staged as a Workgroup.  All of the servers have a unique user account with the same username and password that is added to the local Administrators group, and all servers currently have that user account logged in.

I am installing Milestone Corporate in a distributed architecture, where the primary components are all installed on a dedicated Management Server, the Recording Server component on a separate server, and the Recording Server installed as a Failover installed on a third server.

The problem occurs when I go to install the Recorder Server component as a Failover.  I get prompted for the Name/IP of the Recorder Server and the Name/IP of the Management Server, where I am specifying IP Address, and when I go to start the install, I get an error message that states "Failed to Connect, Check the User Name and Password".  A basic review of the log shows references to the same issue "UserNamePasswordException".

Note : All other components installed without issue on the other servers.

I found a reference on the MS Knowledge Base with a similar issue, but no real resolution other that a statement that a later version resolved this: 

https://supportcommunity.milestonesys.com/s/article/cannot-install-a-Failover-Server-on-XProtect-2017-R1-error-1603?language=en_US

Please note that I do have this open as a case with Milestone Support, however,  I am trying to expedite the resolution of this issue as it has now caused a significant bottleneck in my staging time line, and I have had success in the past getting answers on IPVM in a very timely manner.  I am hoping for the same this go round.  Thank you in advance!

Avatar
Sean Patton
•Dec 17, 2018

UM1,

I am trying a couple things out on our Milestone Servers, but do not have any valuable input/feedback for you at this time. I have also reached out to a Milestone technical resource to see if they have any suggestions.

UM
Undisclosed Manufacturer #1
•Dec 17, 2018

Thank you very much Sean!

AB
Alexander Bakke
•Dec 17, 2018

Hello.

 

Try to have the XProtect Managment Server service run as the same Windows account that you are using to install (and later run) the Failover server.

The Failover server component requires more privileges than a normal Recording server.

 

(2)
UM
Undisclosed Manufacturer #1
•Dec 17, 2018

Hello,  and thank you for your time. 

I have all services running under the same User Account which has been added as an Administrator to each server, however,  I still get the same error when attempting to install the Failover recording server.

 

AB
Alexander Bakke
•Dec 17, 2018

You're welcome.

What about the information in this link?

https://supportcommunity.milestonesys.com/s/question/0D50O000049u3J3SAI/failover-installation-failed?language=en_US

UM
Undisclosed Manufacturer #1
•Dec 17, 2018
In reply to Alexander Bakke

Thanks so much Alexander!  It was something in the link from the Support Community link that triggered the correction.  The time/date was not synchronized between the two servers!  Doh!

 

AB
Alexander Bakke
•Dec 17, 2018
In reply to Undisclosed Manufacturer #1

Thank you for the feedback. 

I remember I had issues myself when setting this up, but I didn't recall exactly how I solved it.

If you ask me I think the installer should be able to inform of the incorrect credentials without cancelling the entire install, but I guess that can be feedback for later versions.

(1)
Avatar
Josh Hendricks
•Dec 17, 2018
Milestone Systems

During install of the Failover recording server it should only ask for the name/IP of the Management Server - you should never have to enter info about other recording servers on the Failover Server as any of that configuration will be done in Management Client.

Are you logged into Windows as the custom local user account you created on all machines? The installer is probably trying to validate the connection to the management server and that might fail in a workgroup environment unless you're logged in under that account.

You might also consider directly adding that user account to your Administrators role in Management Client - although if it is a member of the local administrators group on the Management Server it should in theory not be needed.

(1)
UM
Undisclosed Manufacturer #1
•Dec 17, 2018

Thank you very much for taking the time to follow up Joshua!  I was able to resolve the issue based on earlier feedback from Alexander.

 

New discussion

Ask questions and get answers to your physical security questions from IPVM team members and fellow subscribers.

Newest discussions