BlackBerry Forums Support Community               

Closed Thread
 
LinkBack Thread Tools
Old 10-14-2010, 12:29 PM   #1 (permalink)
New Member
 
Join Date: Oct 2010
Model: 8800
PIN: N/A
Carrier: Rogers
Posts: 6
Post Thanks: 0
Thanked 0 Times in 0 Posts
Exclamation BES Web Administration Service not working

Please Login to Remove!

Ive successfully installed BES as well as MSSQL2008R2

Both are configured and communicate correctly.

But when I attempt to connect to the Web Administration Service, It shows "Page cannot be displayed".

As far as I know, BES itself is working fine, all the services are running and it is communicating with the database. However without access to the Admin Panel, I cannot configure the BES Server.

When exploring around the BES folder, I Noticed a license for Apache, so I assume it has a built in Webserver. However, I cannot see Apache running under services, which is why Im assuming that there is no webserver configured. I went ahead and installed IIS, but that didnt seem to solve the problem.

What are my options? Can I just "point" BES Admin server to use IIS? If so, where can I find the interface (.php or .aspx files I assume) to administer the configuration?

Edit : I just found the BAS-AS_err Logs

Quote:
Error encountered while starting server: com.microsoft.sqlserver.jdbc.SQLServerException: The connection to the named instance has failed. Error: java.net.SocketTimeoutException: Receive timed out.
java.lang.RuntimeException: com.microsoft.sqlserver.jdbc.SQLServerException: The connection to the named instance has failed. Error: java.net.SocketTimeoutException: Receive timed out.
at com.rim.bes.bas.system.DirectDatabaseAccessor.getC onnection(DirectDatabaseAccessor.java:107)
at com.rim.bes.bas.system.TransportProtocolConfigurat or.configureTransportProtocols(TransportProtocolCo nfigurator.java:193)
at com.rim.bes.bas.system.BASMain.initialize(BASMain. java:1354)
at com.rim.bes.bas.system.BASMain.main(BASMain.java:1 065)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The connection to the named instance has failed. Error: java.net.SocketTimeoutException: Receive timed out.
at com.microsoft.sqlserver.jdbc.SQLServerException.ma keFromDriverError(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.g etInstancePort(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.c onnect(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerDriver.conne ct(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at com.rim.bes.bas.system.DirectDatabaseAccessor.getC onnection(DirectDatabaseAccessor.java:78)
Im not sure what its telling me. I see that its attempting to connect to an SQL Server and failing, even though BES itself has no problems (Tested with the test connection).

Last edited by rboelens : 10-14-2010 at 12:37 PM.
Offline  
Old 10-14-2010, 12:41 PM   #2 (permalink)
Thumbs Must Hurt
 
Join Date: Jun 2008
Location: Canada
Model: 8110
PIN: N/A
Carrier: A crappy one aka. Rogers
Posts: 96
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Did you install BES 5.0 SP2?

BlackBerry - BlackBerry Enterprise Server Compatibility


What account are running the BAS services? Local system, BESAdmin

Have you checked the Windows Application logs (Event Viewer) or BAS-AS logs?
Offline  
Old 10-14-2010, 12:44 PM   #3 (permalink)
Thumbs Must Hurt
 
Join Date: Jun 2008
Location: Canada
Model: 8110
PIN: N/A
Carrier: A crappy one aka. Rogers
Posts: 96
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Sounds like the SQL Browsing service may not be running.

You should make sure TCP/IP and named pipes are enabled in SQL Manager for the SQL instance the BES database is associated with.
Offline  
Old 10-14-2010, 12:50 PM   #4 (permalink)
New Member
 
Join Date: Oct 2010
Model: 8800
PIN: N/A
Carrier: Rogers
Posts: 6
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

SQL Browsing Service was enabled, and both TCP/IP and Named Pipes were enabled already.

As stated earlier, BES can connect to SQL (Ive confirmed this with the "Test SQL Connectivity" button in the BES Server Configuration tool. It just seems that BAS will not connect. BAS Services is run by BESAdmin. BES Compatability Matrix Seems to support my software.

Server 2008 R2
SQL 2008 x64 Express SP1

The above exerpt was from the BAS-AS_err logs

Edit : When attempting to run "Run" batch file, It states
Quote:
JAVA_HOME is not set. Unexpected results may occur.
Set JAVA_HOME to the directory of your local JDK to avoid this message
Im gonna update Windows 2008 to SP2 in the meanwhile

Last edited by rboelens : 10-14-2010 at 02:01 PM.
Offline  
Old 10-14-2010, 01:23 PM   #5 (permalink)
Thumbs Must Hurt
 
Join Date: Jun 2008
Location: Canada
Model: 8110
PIN: N/A
Carrier: A crappy one aka. Rogers
Posts: 96
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Update to BES 5.0 SP2?
Offline  
Old 10-14-2010, 02:01 PM   #6 (permalink)
New Member
 
Join Date: Oct 2010
Model: 8800
PIN: N/A
Carrier: Rogers
Posts: 6
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Im using 5.0.2

I assume the ".2" means SP2?
I cannot seem to find a service pack download from the Blackberry website.

I ment Updating Windows to SP2 earlier. (Fixed previous post)

Is there any way to tell if the webserver is up and running?
I dont see apache listed in the services list

Last edited by rboelens : 10-14-2010 at 02:04 PM.
Offline  
Old 10-14-2010, 02:17 PM   #7 (permalink)
Thumbs Must Hurt
 
Join Date: Jun 2008
Location: Canada
Model: 8110
PIN: N/A
Carrier: A crappy one aka. Rogers
Posts: 96
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Re: Apache webserver...I don't believe that's how apache is used by BES.

I think you may need to increase the BAS-AS logging level to see all the errors. Be warned...increasing the logging level will give you a lot more info but it should allow you to find a more specific errors. Searching BTSC with log snips should eventually help you find the right article but it may take a while.

That being said, sometimes you can simply re-install BAS in an attempt to resolve similar issues. Remember, Back up, Back up, Back up!!!
Offline  
Old 10-14-2010, 02:27 PM   #8 (permalink)
New Member
 
Join Date: Oct 2010
Model: 8800
PIN: N/A
Carrier: Rogers
Posts: 6
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

How do I increase the logging level?

Ive attempted a reinstall, but for some reason every time I run the Install now, it gives errors during the splash preloader screen.

According to what ive read online, BES uses Apache Coyote, in lieu of IIS.

I have IIS Up, and it is functioning, is there a way to configure BES to use IIS instead of Apache once its already been installed with apache?

Last edited by rboelens : 10-14-2010 at 02:28 PM.
Offline  
Old 10-14-2010, 02:37 PM   #9 (permalink)
Thumbs Must Hurt
 
Join Date: Jun 2008
Location: Canada
Model: 8110
PIN: N/A
Carrier: A crappy one aka. Rogers
Posts: 96
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Steps to increase logging level should be within KB00765-How to change the log levels for BlackBerry Enterprise Server components

As for using IIS instead of Apache, I would assume no. BAS is so finicky it would take very little to disrupt it as it is. If you are unable to re-install...that would suggest to me like there may be a bigger problem. Is a clean re-install out of the question? or is this BES in production?
Offline  
Old 10-14-2010, 02:44 PM   #10 (permalink)
New Member
 
Join Date: Oct 2010
Model: 8800
PIN: N/A
Carrier: Rogers
Posts: 6
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Its not in production yet.
A clean install would take another 2-3 days with updates/software + Configuration.
I would prefer to fix this, rather than clean install, and Im not quite convinced that a fresh install would fix the issue either.

Ill try and increase the logging level and attempt to give you more detailed results.

Edit : Problem

Quote:
BlackBerry Enterprise Server 5.0 :
To change the logging level for a specific BlackBerry server component, complete the following steps::

1.Log in to the BlackBerry Administration Service console. <-- Thats my problem in the first place
Edit : Another Log file that I found (Webserver logs)

Quote:
Oct 14, 2010 1:00:38 PM org.apache.catalina.startup.Embedded start
INFO: Starting tomcat server
Oct 14, 2010 1:00:39 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.18
Oct 14, 2010 1:00:41 PM org.apache.catalina.startup.ContextConfig defaultWebConfig
INFO: No default web.xml
Oct 14, 2010 1:00:42 PM org.apache.catalina.core.ApplicationContext log
INFO: AdministrationController (Status):init
Oct 14, 2010 1:00:42 PM org.apache.catalina.core.ApplicationContext log
INFO: C:\Program Files (x86)\Research In Motion\BlackBerry Enterprise Server\MDS\Servers\Instance
Oct 14, 2010 1:00:43 PM org.apache.catalina.startup.ContextConfig defaultWebConfig
INFO: No default web.xml
Oct 14, 2010 2:35:47 PM org.apache.catalina.startup.Embedded start
INFO: Starting tomcat server
Oct 14, 2010 2:35:48 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.18
Oct 14, 2010 2:35:48 PM org.apache.catalina.startup.ContextConfig defaultWebConfig
INFO: No default web.xml
Oct 14, 2010 2:35:49 PM org.apache.catalina.core.ApplicationContext log
INFO: AdministrationController (Status):init
Oct 14, 2010 2:35:49 PM org.apache.catalina.core.ApplicationContext log
INFO: C:\Program Files (x86)\Research In Motion\BlackBerry Enterprise Server\MDS\Servers\Instance
Oct 14, 2010 2:35:50 PM org.apache.catalina.startup.ContextConfig defaultWebConfig
INFO: No default web.xml
I hope this helps.
I was mistaken about it using Apache Coyote, it appears to be using Apache Catalina or Tomcat

Last edited by rboelens : 10-14-2010 at 04:39 PM.
Offline  
Old 10-26-2010, 03:56 PM   #11 (permalink)
New Member
 
Join Date: Oct 2010
Model: 8800
PIN: N/A
Carrier: Rogers
Posts: 6
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

It would appear the issue lay with the Apache build being used by 5.0.2 (Catalina).

It would appear that the initial installation and configuration did not set the SQL Pointers for the Apache server to the configured SQL Server.

We blew away the image and restarted using 5.0.1 and are now able to successfuly configure and access the Web Administration Service.

It appears that the Coyote Build (5.0.1) is working.

Issue Solved, I suppose.
I would have liked to be able to use the latest version, rather than being forced to downgrade due to poor software, but I guess I dont really have a choice.
Offline  
Closed Thread


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On





Copyright 2004-2014 BlackBerryForums.com.
The names RIM and BlackBerry are registered Trademarks of BlackBerry Inc.