After BES monitoring Remote component installed, Console wont let me login

Hi,

I have following environment:

BAS server 01 and 02
BES primary and Standby

upgraded from 5.0.1 to 5.0.2

Now i have installed on a separate Virtual Machine the BES Montiroing remote Component 5.0.1.

During installation i chose "existing database"

Then i ran 5.0.2 upgrade on it.

The console window opens fine. When I put user/pwd/domain/Active Directory it does not login

this message comes

The username, password, or domain is not correct. Please correct the entry.

while i login with same credentials in BAS console successfully.

My BAS console is opening fine. Only my newly installed and upgraded Monitoring console is not loging in.

It is 5.0.2 and i have now also deployed Maintenance Realease 2

Still not loging in....
(03/02 15:28:26:733):{Dummy-1} [db_connection_manager:__init__:100] [INFO] Database connection pool for [BMSDB] initialized. Min connections: 4. Max connections: 10. Available connections: 4
(03/02 15:28:31:15):{Dummy-1} [db_connection_manager:__init__:100] [INFO] Database connection pool for [BMSDB] initialized. Min connections: 4. Max connections: 10. Available connections: 4
(03/02 15:28:31:15):{Dummy-1} [util:attemptToConnect:71] [INFO] Successfully connected to the database
(03/02 15:28:35:171):{Dummy-1} [db_connection_manager:__init__:100] [INFO] Database connection pool for [BMSDB] initialized. Min connections: 4. Max connections: 10. Available connections: 4
(03/02 15:28:35:562):{Dummy-1} [oidutil:__init__:43] [INFO] MIBMap started
(03/02 15:28:35:562):{Dummy-1} [cycle_manager:__init__:39] [INFO] Cycle Manager startup complete
(03/02 15:28:35:578):{Dummy-1} [flow_controller:__init__:31] [INFO] Flow Controller startup complete
(03/02 15:28:35:578):{Dummy-1} [scheduler:__init__:33] [INFO] Scheduler startup complete
(03/02 15:28:35:578):{Dummy-1} [input_source_manager:__init__:24] [INFO] Input Source Manager startup complete
(03/02 15:28:35:875):{Dummy-1} [oidutil:__init__:43] [INFO] MIBMap started
(03/02 15:28:35:875):{Dummy-1} [short_request_handler:__init__:22] [INFO] Short Request Handler startup complete
(03/02 15:28:36:203):{Dummy-1} [oidutil:__init__:43] [INFO] MIBMap started
(03/02 15:28:36:203):{Dummy-1} [long_request_handler:__init__:22] [INFO] Long Request Handler startup complete
(03/02 15:28:36:203):{Dummy-1} [user_cache:__init__:24] [INFO] User Cache startup complete
(03/02 15:28:36:203):{Dummy-1}[list_manager:__init__:25] [INFO] List Manager startup complete
(03/02 15:28:36:203):{Dummy-1} [load_manager:__init__:25] [INFO] Load Manager startup complete
(03/02 15:28:36:203):{Dummy-1} [diagnostics_handler:__init__:41] [INFO] Diagnostics Handler startup complete
(03/02 15:28:36:203):{Dummy-1} [bas_handler:__init__:69] [INFO] Health Matrix Component startup complete
(03/02 15:28:36:203):{Dummy-1} [trap_receiver:__init__:59] [INFO] Trap Component startup complete
(03/02 15:28:36:203):{Dummy-1} [host_handler:__init__:37] [INFO] Host Handler startup complete
(03/02 15:28:36:233):{Dummy-1} [peer:connectToPeer:895] [ERROR] header too long
Traceback (most recent call last):
File "common\peer.pyo", line 884, in connectToPeer
File "common\peer.pyo", line 293, in __init__
File "common\peer.pyo", line 259, in get_client_socket
File "common\peer.pyo", line 240, in __get_ssl_context
File "M2Crypto\SSL\Context.pyo", line 74, in load_cert
SSLError: header too long
(03/02 15:28:36:233):{Dummy-1} [peer:connection_failed:830] [WARNING] Connection failed for (App) at (u'BMS Server and Domain.com, 55500)
(03/02 15:28:36:233):{Dummy-1} [peer:connectToPeer:895] [ERROR] bad object header
Traceback (most recent call last):
File "common\peer.pyo", line 884, in connectToPeer
File "common\peer.pyo", line 293, in __init__
File "common\peer.pyo", line 259, in get_client_socket
File "common\peer.pyo", line 240, in __get_ssl_context
File "M2Crypto\SSL\Context.pyo", line 74, in load_cert
SSLError: bad object header
(03/02 15:28:36:233):{Dummy-1} [peer:connection_failed:830] [WARNING] Connection failed for (DCS) at (u'BMS Server and Domain.com, 55502)
(03/02 15:29:06:382):{Timer Thread} [load_manager:collectMetrics:34] [INFO] Collecting load metrics
(03/02 15:29:36:414):{Timer Thread} [load_manager:collectMetrics:34] [INFO] Collecting load metrics
(03/02 15:30:06:617):{Timer Thread} [load_manager:collectMetrics:34] [INFO] Collecting load metrics
(03/02 15:30:36:617):{Timer Thread} [load_manager:collectMetrics:34] [INFO] Collecting load metrics
(03/02 15:31:06:726):{Timer Thread} [load_manager:collectMetrics:34] [INFO] Collecting load metrics
(03/02 15:31:36:726):{Timer Thread} [load_manager:collectMetrics:34] [INFO] Collecting load metrics
(03/02 15:32:07:7):{Timer Thread} [load_manager:collectMetrics:34] [INFO] Collecting load metrics
(03/02 15:32:37:7):{Timer Thread} [load_manager:collectMetrics:34] [INFO] Collecting load metrics
(03/02 15:33:07:7):{Timer Thread} [load_manager:collectMetrics:34] [INFO] Collecting load metrics
(03/02 15:33:37:7):{Timer Thread} [load_manager:collectMetrics:34] [INFO] Collecting load metrics
(03/02 15:34:07:128):{Timer Thread} [load_manager:collectMetrics:34] [INFO] Collecting load metrics

Open in new window

Also i am geting this error in the logs



(03/02 14:13:12:32):{Dummy-1} [db_connection_manager:__init__:100] [INFO] Database connection pool for [BMSDB] initialized. Min connections: 4. Max connections: 10. Available connections: 4
(03/02 14:13:12:32):{Dummy-1} [util:attemptToConnect:71] [INFO] Successfully connected to the database
(03/02 14:13:17:293):{Dummy-1} [db_connection_manager:__init__:100] [INFO] Database connection pool for [BMSDB] initialized. Min connections: 4. Max connections: 10. Available connections: 4
(03/02 14:13:21:569):{Dummy-1} [db_connection_manager:__init__:100] [INFO] Database connection pool for [BMSDB] initialized. Min connections: 4. Max connections: 10. Available connections: 4
(03/02 14:13:21:599):{Dummy-1} [dcs_util:_loadConfig:103] [INFO] Loaded config: {'target': 3400, 'max': 4000, 'delta': 14, 'msg_days': 14, 'db_name': u'BMSStoreUAT', 'pass': 100, 'threshold': 3200}
(03/02 14:13:21:599):{Thread-2} [persist:run:36] [INFO] Starting persistence agent
(03/02 14:13:21:599):{Dummy-1} [peer:connectToPeer:895] [ERROR] header too long
Traceback (most recent call last):
File "common\peer.pyo", line 884, in connectToPeer
File "common\peer.pyo", line 293, in __init__
File "common\peer.pyo", line 259, in get_client_socket
File "common\peer.pyo", line 240, in __get_ssl_context
File "M2Crypto\SSL\Context.pyo", line 74, in load_cert
SSLError: header too long
(03/02 14:13:21:599):{Dummy-1} [peer:connection_failed:830] [WARNING] Connection failed for (Engine) at (u'BMS Server and Domain.com, 55501)
(03/02 14:14:21:698):{Thread-3} [dcs_util:hasLimit:109] [INFO] DB edition: Developer Edition
(03/02 14:14:21:698):{Thread-3} [dcs_util:hasLimit:114] [INFO] No size limit for installed DB edition, checks will not be performed


What does it mean by ..... header too long ?

Open in new window

Amir4uAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rob KnightConsultantCommented:
Hi,

Make sure the user ID you are logging in with has been assigned the appropriate Administration monitoring role and then try again.

Regards,


RobMobility.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Amir4uAuthor Commented:
i have added the role "Monitoring system administrator" and " MOnitoring View Administrator" and now i get this error again which i got before upgrading BMS 5.0.2 with MR2. This error is coming after i put my user/pwed/domain. this issue is  also known to be accepted by BB official support but they claim that it is resolved when MR2 is applied.
0
Rob KnightConsultantCommented:
Hi,

I believe you need to perform these steps after MR2:

http://www.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB24346

Regards,


RobMobility.
0
Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

Amir4uAuthor Commented:
When i deploy MR2 to BMS because it was giving that login problem should I be deploying MR2 to all other BES and BAS to make all the versions same?

shall I first deploy the latest MR4 and then go for your above link ?

0
Rob KnightConsultantCommented:
Hi,

Also check windows event viewer - if there are any issues with DB connections, check permissions on the blackberry monitoring database.

Regards,


RobMobility.
0
Rob KnightConsultantCommented:
Hi,

It's only showing as an issue with MR2 - I suggest you get it to the point you know it is working and then run the MR3, MR4 etc.

All servers should be running at there same level of MR, although it generally is only a service pack which modifies SQL etc.

Regards,


RobMobility.
0
Amir4uAuthor Commented:
well i did follow this document

http://www.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB24346"
and the web.keystore was created successfully but still when i try to login it's just giving this error ....

The username, password, or domain is not correct. Please correct the entry.

I have also checked the database for rights and my user has full rights.

i tried also with BAS user i.e.

admin
pwd

and with

besadmin
pwd
domain

but still it isnt letting me in....

the installation was all smooth but i am simply wondering whats going on....
0
Amir4uAuthor Commented:
well this is a dumb question i guess but my montiroing server name is long, 15 characters, would this create a problem somehow?

could this somehow be realted to this line in the logs

(03/02 14:13:21:599):{Dummy-1} [peer:connectToPeer:895] header too long
0
Amir4uAuthor Commented:
HI

I added "MOnitoring System administrator" but did not add "Monitoring view administrator" and was just trouableshooting in all the other wrong areas...

wehn i finally added "Monitoring view administrator" only then was i able to login...

I guess it's . MY Bad ...
0
Amir4uAuthor Commented:
U rule ROB ........
0
Amir4uAuthor Commented:
shooot ...it's again not logging in .......
0
Amir4uAuthor Commented:
ok , restarted the server and now it's opening again ......donno why these mood shifts ....
0
Amir4uAuthor Commented:
still giving same prob inm my case.... opened a ticket with Black Berry support ....
0
Amir4uAuthor Commented:
BB Support told me to follow this article...

Article ID: KB23477

 

lets see what happens
....
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
BlackBerry Programming

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.