Link to home
Start Free TrialLog in
Avatar of mmichaels1970
mmichaels1970

asked on

New Blackberry Enterprise Server Express Installation - Administration Service Logon

I'm attempting to install BESx 5.0 sp1 for Exchange on a non-exchange server.  The installation process seems to have completed successfully.  However, when I attempt to log on to the Administration Service web page, I get an error that: "The browser session has timed out.  Please log in again.".

I tried installing BESx to use AD authentication and BES authentication.  Both with the same result.

I was told by my wireless service rep that my version of Blackberry Professional Server (installed on another machine) was being discontinued.  So I figured this would be a good time to install a fresh copy of BESX and then use the transport agent to move the user accounts over.

I'm attaching a screen shot and a log file.  Can somebody help me figure out where I'm going wrong?
bb1.jpg
MYLOG.txt
ASKER CERTIFIED SOLUTION
Avatar of digitap
digitap
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of mmichaels1970
mmichaels1970

ASKER

Hi digitap.  The link you provided appears to be broken.  However, I see what you're getting at.  I suspected IIS earlier and tried simply stopping the service to see if that might help.

The Admin guide I  have appears to be a little different than the one you are referencing.  Probably because it's been modified for SP1.  So page 327 refers to "Instant Messaging".  I'll look through the guide more thoroughly to see if I can learn more about the port assignments.

In the meantime, I'm going to remove BESx entirely.  Then, I'll try to remove IIS as well before doing a reinstall.    That's something I can accomplish while picking through the manual.
Also...

In reference to:

"Notice the last line in your log file:

[com.rim.bes.bas.commands.securitymanager.SecurityLogin] [INFO] [BBAS-1006] {unknown} Logged in user admin"

I agree and noticed that as well.  That's what makes this problem even more frustrating for me.  It appears I'm very close to having this thing going.
Tried installing BESx with IIS removed and get:

javax.servlet.ServletException: org.apache.hivemind.ApplicationRuntimeException: Could not create the Command object com.rim.bes.bas.command.CommandException: CommandException SYSTEM: javax.naming.NameNotFoundException: ejb not bound: javax.naming.NameNotFoundException: ejb not bound
      org.apache.tapestry.services.impl.WebRequestServicerPipelineBridge.service(WebRequestServicerPipelineBridge.java:60)
      $ServletRequestServicer_127486229c5.service($ServletRequestServicer_127486229c5.java)
      org.apache.tapestry.request.DecodedRequestInjector.service(DecodedRequestInjector.java:55)
      $ServletRequestServicerFilter_127486229c1.service($ServletRequestServicerFilter_127486229c1.java)
      $ServletRequestServicer_127486229c7.service($ServletRequestServicer_127486229c7.java)
      org.apache.tapestry.multipart.MultipartDecoderFilter.service(MultipartDecoderFilter.java:52)
      $ServletRequestServicerFilter_127486229bf.service($ServletRequestServicerFilter_127486229bf.java)
      $ServletRequestServicer_127486229c7.service($ServletRequestServicer_127486229c7.java)
      org.apache.tapestry.services.impl.SetupRequestEncoding.service(SetupRequestEncoding.java:53)
      $ServletRequestServicerFilter_127486229c3.service($ServletRequestServicerFilter_127486229c3.java)
      $ServletRequestServicer_127486229c7.service($ServletRequestServicer_127486229c7.java)
      $ServletRequestServicer_127486228ad.service($ServletRequestServicer_127486228ad.java)
      org.apache.tapestry.ApplicationServlet.doService(ApplicationServlet.java:123)
      org.apache.tapestry.ApplicationServlet.doGet(ApplicationServlet.java:79)
      javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
      javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
      com.rim.bes.bas.web.common.ResponseHeadersFilter.doFilter(ResponseHeadersFilter.java:85)
      org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
I restarted the server and the apache errors disappeared and I was left with a normal logon screen.  Installation of BESx with IIS removed from the server results in the same Browser time out error originally reported.  So this doesn't appear to be an apache/IIS conflict.
I'm shooting in the dark here.  What version of Java do you have installed?  You might try uninstalling it and reinstalling with the latest version.
I have Java 6.0.180 (Version 6 update 18) which I think is the latest.  I'm wondering if my version  is too new and some sorts of functions that java used to support aren't there anymore.  That's my shot in the dark.

Also, this is a Microsoft Virtual Machine.  I'm going to try to install BESx on a "normal" non-virtual server to see if it  makes a difference.
Re: java, that's a possibility.  Look up the system requirements for BES and see if they list the version.  Apps using old versions of Java is a VERY common problem.

I'd try the java trail first, then the physical server.
ok.  The app requirement that shows up on install of BESx is 6.0.150 (version 6 update 15).  I'll remove 18 from my server and make sure I install 15.
Ok...let me know if that fixes it.
Removed all versions of Java and let the BESx installation program install java for me.  Problem remains:   browser session has timed out.

I'm going to proceed to installation on a non-virtual machine.
ok...sorry for the trouble.
I have successfully installed it in a virtual environment with no issues and cannot help you with that issue, but you did say you wanted to use the transporter when it is running.  You cannot use the transporter with the express version.

From the Blackberry support site:
BlackBerry Enterprise Server Express version 5.0 SP1 does not support upgrades or migration to or from any other product line.

The BlackBerry Enterprise Transporter is not supported for use with BlackBerry Enterprise Server Express version 5.0 SP1.

To move a BlackBerry smartphone user to BlackBerry Enterprise Server Express version 5.0 SP1, the user must be removed from the existing BlackBerry Enterprise Server and then added to the BlackBerry Enterprise Server Express server.  To do this complete the following steps:

Delete the BlackBerry smartphone user account from the current BlackBerry Enterprise Server.
Back up the BlackBerry smartphone.
Perform a security wipe on the BlackBerry smartphone.
This step is required. For further information about performing a security wipe on a BlackBerry smartphone, see KB04533.
Add the BlackBerry smartphone user as a new user on the destination BlackBerry Enterprise Server Express.
Activate the BlackBerry smartphone.
For an explanation on how to activate a BlackBerry smartphone using BlackBerry Enterprise Server Express, see KB21124.

As for the other issue, I would suggest removing IIS as a first step unless you need to use it on this server for something else.  My install was successful with no IIS installed.
Hi GKalosky...thanks for your input.  I sure wish my users were ok with ActiveSync.  Thanks for saving me from wasting  my time trying to figure out why Transporter won't work.

I tried a complete removal of IIS and the problem remained.  I also removed all versions of Java and allowed the BESx install program to install them, and the problem remained.

To digitap and GKalosky:
Just ran through an installation on a non-virtual server (even with IIS installed and running) and it ran through with flying colors.  My admin web page is logging in properly and all seems well.

I guess, GKalosky, based on your experience, I can't completely conclude that BESx is not compatible in a virtual environment.  I'm going to debate now whether to let the issue go and continue on with my non-virtual server, or try to pursue the installation on the virtual server I originally intended to host the software.
What virtual environment are you using?  I believe the compatibility listing shows Hyper-V as not being compatible.

I would also suggest that even after removing IIS, that you would need to remove and reinstall BESx.
I'm using Microsoft Virtual Server 2005 R2.  I did try a complete removal and reinstallation, even deleting the config database, after removing IIS.
The old Microsoft Virtual Server 2005 R2 is not on the compatibility list.  Hyper-V is with some restrictions.  You may want to review the compatibility document:
http://na.blackberry.com/eng/support/software/server_express_ver_march_05_10.pdf
Thanks for the compatibility list link.  I took a look at the System Requirements in the Installation and Administration Guide, but didn't reference the link you provided.  So I guess I can conclude that BESx is not compatible in a Microsoft Virtual environment.

After a seemingly successful installation on another server, it appears I can do everything accept add users.  I was able to add a group, a software configuration, and a policy.  But when I try to add a user, I get no options.

Thanks for trying to help.  It's looking like this just isn't meant to be.  Please let me know if you see something obvious with this new "create user" issue.  If I can't get it done, I'll probably just purchase a new 5 user pack from my BPS and forget about it.


bb2.jpg
Did you use the same besadmin that you are running on the professional version?  If you created another service account, not necessary, did you give it all the proper rights, both on Exchange as as a local administrator on the machine that BESx is installed on?  It kind of looks like it does not have the proper authentications.
Yes I used the same besadmin.

I just stumbled upon:

http://supportforums.blackberry.com/t5/BlackBerry-Enterprise-Server/Unable-to-Create-Users/m-p/347753;jsessionid=EBFA478435795F8646F0B0DACA8025AB

where Terminal Server Application mode appears to be causing the problem.  Let me try removing that on both servers and then try a reinstall.
You probably just want remote access turned on which uses Terminal Services, but is not full application mode.  I use that on BES and all my servers for remote administration.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Ok.  Here's the lowdown on the entire issue.

First:  BESx appears to be incompatible with the Windows Virtual environment.  Installing it on a Windows Virtual machine will lead to the original reported browser error that the "session timed out".

Second:  Installing BESx on a Terminal Server (Application Mode) in a non-virtual environment also won't work.  A tell-tale sign if you get the traditional "click next when your installation is done" terminal services prompt at the beginning of your BESx installation process.  You will find that the setup application will only allow you to install as a "remote server" as opposed to a "local server".  "Local Server" will be grayed out.

I noticed this "remote server" option, but having never installed this app before, moved on to the next step.  On a subsequent run of the setup program, you are able to select "local server", so I figured this was just the process.

Once Terminal Server was removed from "Add/Remove Windows Components", and remote access was granted through Right Click "My Computer" and select "Remote", the setup application ran much differently.

Another snag that I hit on the install process was a missing CDO.dll file and an incompatible version of mapi32 on my new BES host.  This was resolved by downloading the "Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1" from Microsoft.

http://www.microsoft.com/downloads/details.aspx?FamilyID=E17E7F31-079A-43A9-BFF2-0A110307611E&displaylang=en

For a bit of good news...the Blackberry Transporter application does appear to work well with BESx 5.0 sp 1.  I transferred my own Blackberry account and I'm seamlessly receiving email and changes to my contacts are syncing immediately.
I didn' mention the CDO or MAPI issues because you did not reference those issues.  They should definitely document this better.  I am glad the transporter is working for you.
Both Experts helped lead me to the eventual solution reached in my final post.  They were patient and timely with their responses and are much appreciated!
That's great!  I'm sorry I missed the incompatible issue with BESx and virtual environments.  I should have caught that.  I'm glad you got it working!
You are too kind.  Thank you for the points!
I'd like to know how you got the BlackBerry Transporter to work with BES Express. I know it is unsupported but many users seem to have it working.