02-12-2013 01:01 PM
We have been using BES for years, and we have also successfully installed the BDS & Studio components of BES 10 (of course on another server). But no matter how hard we're, we cannot get UDS working. After installation, we always get the error: "An error occurred. The site might be temporarily unavailable. Click OK to attempt to return to the login page.".
First, we installed USD on the same server as BDS & Studio, following the known BB KB article on port changes.
When we faced the login error after the installation, we followed all advice from BB KB and Support Forums (SSL certificate and Core web site binding in IIS, IIS Application Pool settings and recycle, installation with a local admin account that has the right to logon as a service and as a batch job), but with no luck.
We then setup a brand new, clean virtual machine to setup UDS on its one, separated from the BDS & Studio server. But again after the installation the same error, and we could not login.
We even did a third try, setting up another clean virtual server (this time a "vanilla" Windows installation from the Microsoft Volume Licensing media, not using our usual VMware server template, to be sure that there was no Windows setting in the template that could be preventing UDS from working), and even used the previous (SP2) version of UDS (and not the one that came with BES10, to make sure that there was nothing wrong with the BES10 version). But again, we cannot login after the installation finishes (claiming) successfully. And even after upgrading it to the BES10 version, we were once more unable to login.
So... what could be preventing us from logging on to a brand new UDS installation on a brand new, clean and uncustomized Windows server (and another two installations before that)??? We were so eager to test UDS, and we have dedicated so much effort in the last days, that it's completely disappointing to end up with three separate server installations and not one of them functional
- Windows Server 2008 R2 SP1 x64
- SQL Server 2008 R2 Express (Installed automatically by UDS setup).
- All the Java & .NET installations performed by UDS setup (except for .NET 4, which is always requested by the setup and we install manually).
- Computer joined to a domain. Account used is a local admin, and has the right to logon as service and batch. Windows Services & IIS Application Pool use with this account.
- DNS working fine. Network connectivity working fine (connection to SRP, access to Internet, connectivity to the local SQL installation etc).
Solved! Go to Solution.
02-13-2013 11:37 AM
I just tried to login again, to capture fresh logs
The UCore log (in csv format) is large and I don't know what to look for. Any suggestions?
Here is the BAC log (real server name changed to server.domain.com). I did get the 503 error when I tested opening the Core URL in a browser, but I thought this was normal since I wasn't sending a proper request through the browser to the web service.
Feb 13 18:29:11 [UwpLogger] [INFO ] [http-8443-4] : (AbstractEntityCache.java:49) : Entity Trace: Authorize called for default:admin
Feb 13 18:29:11 [UwpLogger] [INFO ] [http-8443-4] : (AbstractEntityDao.java:74) : Dao Trace: Authorize called for default:admin
Feb 13 18:29:11 [UwpLogger] [INFO ] [http-8443-4] : (AbstractEntityDao.java:74) : Dao Trace: MakeRestCall called for com.rim.mdm.dao.entity.Authentication using method GET using URI https://server.domain.com:8081/dm/auth with profile default:admin
Feb 13 18:29:11 [RestTemplate] [WARN ] [http-8443-4] : GET request for "https://server.domain.com:8081/dm/auth" resulted in 503 (Service Unavailable); invoking error handler
Feb 13 18:29:11 [UwpLogger] [INFO ] [http-8443-4] : (AbstractEntityDao.java:74) : Dao Trace: Handling exception for REST call: 503 Service Unavailable using URI https://server.domain.com:8081/dm/auth
Feb 13 18:29:11 [UwpLogger] [INFO ] [http-8443-4] : (LoginController.java:311) : AuditLog 'Failure' notice from 'login' performing 'action' for 'login with username admin' doing 'fail to login' with problem '503 Service Unavailable using URI https://server.domain.com:8081/dm/auth'. Logged from (LoginController.java:311).
02-13-2013 12:09 PM
Are all of the components of UDS including the COMM installed? You will see the versions in the CORE log when it starts up.
You will see all the versions of components that register starting with the CORE by looking for Configuration deployment Core component registered at host.
If it doesn't detect that all compenents are installed and at the proper version you will see the error Configuration deployments are invalid and you will get the 503 service not available error when trying to login.
02-13-2013 01:09 PM
Actually... we never installed the Communications Component on any of our installations, because we planned to install it on another server in the DMZ. But after the Core & Console installation was finished on the first server, we attempted to login, saw the login error and started troubleshooting and re-installing again and again, without ever getting to install the Comm on the second server!
I will install the Communications Component as soon as possible in the DMZ and hope this fixes the problem
02-14-2013 08:27 AM
You were right Login was sucessful as soon as we installed the Communication Module in the DMZ and setup the firewall rules to allow communication between Core and Comm.
I have accepted your answer as solution to the problem.
Thank you for your help!