[anderscooter]

We have six servers 5.0.2 with administration service running on them, using DNS round robin. We can only login to the administration service on the singleton or using the url of the singleton. Otherwise we get an invalid username or password.

[freakinvibe]

But if you have a pool name in DNS, and you hit any of the six servers, you should be automatically redirected to a working server. This is how it works for us (having two BAS servers). We are using single sign-on, though, so we never have to login.

Have you made sure that the 6 servers can freely communicate with each other via UDP/TCP and no Windows firewall is blocking needed ports?

[anderscooter]

All the individual servers have an individual IP and are also in the DNS pool name, both in forward and reverse DNS. We are using TCP and there isnt a firewall on the server enabled or between the servers. We are using AD authentication but not single sign on. If I restart the admin service on one of the servers that is not the singleton AD authentication will work for a short time then stop, but it will always work on the singleton.

[freakinvibe]

What is the exact URL you use for your login page?

[anderscooter]

'https://besadmin.domain.domain.com/webconsole/login'

[freakinvibe]

That seems to be right.

Have you checked the BBAS-AS logs on the servers that don't work. They might indicate the reason why the login fails.

[anderscooter]

I just tried to login and then checked the log. There is nothing new showing from the last hour.

[BlackBerryBESMatt]

Blackberry/com/btsc KB19436
I've run into this problem before, but it was with 2 BES. This is what got both of them logging in with no conflicts.

Task 1 - Backup existing configuration files to a different location

Stop all BlackBerry Administration Service services on all BlackBerry Administration Service nodes in the cluster.
Copy the file bas-object-versioning-cache-service.xml from C:\Program Files\Research In Motion\BlackBerry Enterprise Server\BAS\server\default\deploy\ to a different directory (e.g. Desktop).
Copy the file cluster-service.xml from C:\Program Files\Research In Motion\BlackBerry Enterprise Server\BAS\jboss\ejb\server\default\deploy\ to a different directory (e.g., Desktop).
Note: If you simply rename the files and leave in their original location, the modifications below will not work.

Task 2 - Edit the configuration files

Modify both attached files below, so that the TCPPING initial_hosts match the environment:
Replace BAShost2, BASHost3 etc. with the name of the other BlackBerry Administration Service nodes within the cluster.
The node order must be the same on every BlackBerry Administration Service node in the cluster.
Note: The simplest way to achieve this is to ensure after the BlackBerry Administration Service hostnames are customized, copy and replace the two customized xml files across all BlackBerry Administration Service nodes. This will ensure the order of the hosts is maintained.

Place the modified bas-object-versioning-cache-service.xml file into the following location on all BlackBerry Administration Service nodes:
C:\Program Files\Research In Motion\BlackBerry Enterprise Server\BAS\server\default\deploy\bas-object-versioning-cache-service.xml

Place the modified cluster-service.xml file in the following location on all BlackBerry Administration Service nodes:
C:\Program Files\Research In Motion\BlackBerry Enterprise Server\BAS\jboss\ejb\server\default\deploy\cluster-service.xml

Task 3 - Start all BlackBerry Administration Service nodes

Start the BlackBerry Administration Service services on only one BlackBerry Administration Service node (the first BlackBerry Administration Service node to come online will be considered the singleton and responsible for IT policy reconciliation and other critical singleton specific tasks).
Wait 7 to 10 minutes before starting the BlackBerry Administration Service services on the second BlackBerry Administration Service node.
Continue waiting 7 to 10 minutes before starting each successive BlackBerry Administration Service node.
Task 4 - Verify BlackBerry Administration Service Node Functionality

Attempt to login to each BlackBerry Administration Service node in the cluster using the hostname of the BlackBerry Administration Service node.
Verify that the login page is displayed.
Verify that the Microsoft® Active Directory® or BlackBerry Administration Service login completes successfully.
Attempt to login to the BlackBerry Administration Service console by accessing the BlackBerry Administration Service pool name (if round robin Domain Name System (DNS) is set up).
Verify that the login page is displayed.
Verify that the Microsoft Active Directory or BlackBerry Administration Service login completes successfully.

[anderscooter]

The servers are in a different order on all 6 and it says num_initial_members="2". I assume I change this to 6?

[anderscooter]

I tried the KB19436 and it didn't work, I didn't change the initial members, and had to restore the backups.