05-01-2012 01:53 AM
I too am having issues getting our UDS system up and running. I did a two server install with the Core & Console Service both running on the internal LAN and the Communication service in our DMZ. My SSL cert is from Verisign and I have it loaded on both the DMZ and Internal servers.
When I launch the mobile fusion app on an iOS device or an Android device I have the same problem. I type in the public name of our communication server and click next and immediately get an error. The error is just the generic "Your device cannot be activated at this time. Contact your administrator."
I contacted tech support and after 4 hours, was finally told that our installation was corrupt (which I don't believe was true) and that I had to rebuild the system from scratch. So, 2 days and many wasted hours later here I am, with 2 freshly built servers, and the exact same problem I originally had. Any guidance anyone could give would be great. I am at a lose at this point. If I go to the public URL or internal URL for my two servers I am presented with a blank white page that shows my Verisign cert and says it is a trusted site. So I think I have my SSL certs installed properly. On my Android device, the error I get is slightly different as follows:
Certificate not trusted
The security certificate for this server is not trusted. Do you want to continue?
If I click Yes, I get a message saying verifying server for about 5 seconds and than a message that says "Activate error".
I mailed the certificate to myself on both the iPhone and Droid and installed the cert on both but still get the same result.
05-02-2012 12:10 PM
You will have to look at your Communication log to determine why this failure is occuring. With a distributed install with multiple attempted installations I would check this KB: http://www.blackberry.com/btsc/KB31093
05-02-2012 10:39 PM
I am able to say that I have similar issues as well but I was able to activate a Droid 2 today on our UDS but still cannot activate an iOS device.
My setup is different as all services are running on the internal server and we utilize our load balancer. The result with an iOS device is the same. And I have spent countless hours working with a tech at RIM who watched our install so we know it was set up EXACTLY as the documents outlined which are **bleep**.
05-04-2012 09:55 AM
I have spent the last few weeks on calls with BB support and still have a call in on a Mobile Fusion Studio issue (not integrating my UDS domain into it) but have finally gotten everything else up and running. My setup has the core module and console services installed on my internal LAN, and the communication module on a machine in the DMZ.
I'm going to start from the basics on my install so I apologize now if it seems like I'm sounding too basic on what I go over.
From the begining, I made sure all the ports were opened on my firewall (internally and externally) and that I had an externally accessible A record for my UDS box on my DMZ. This includes all the ports 8081 back to the UDS box on my local LAN.
After ports were setup and tested, I kicked off the install for the core module and console services on the machine on my local lan. I followed the install/admin guide and basically went from there. For the later install I did (the one that was finally 100% clean) I followed the install guide and went from there. After the Core and Console services were installed, I moved to the UDS box in my DMZ for the communication module. I setup my CSR to upload to a third party CA, got my cert and continued on with the installation as per the documentation. One thing I did notice in one of the installations I did, is that you need to verify all the certificates are pulled over from UDS box with the core module installed.. One of my installs was getting cert issues, but it was due to the fact that I had installed UDS several times on my internal net, and the certs got mixed up, and I had to manually import them to my DMZ box. If you have all the firewall rules open from your DMZ box to the internal lan and only do a single install, you will not have this issue.
Once I had both installs up, I went into UDS on the internal LAN box and setup my APN. This can be a bit flaky, if you do it in IE, so I would recommend (as per the documentation) to use chrome/safari, or even firefox worked ok. One thing I noticed with the APN, is (if you are using IE or firefox) you do not want to save the certificate to your machine right off the bat. You want to create the APN, and then log back into the site, and copy the APN directly from the site. Not doing this, ended up creating a bogus file which messed up one of my installations altogether. Once you install the APN into your cert store, make sure to give read access to authenticated users or you will end up having permission issues while trying to activate devices. Once this part is completed, you are pretty much good to go assuming all the above are set. I'm sorry this isn't the most descriptive installation procedure, but I will try to write something up a bit better as soon as time permits. In a nutshell, I followed the documentation and had a few issues which I was able to iron out... although I still have a few pending issues, at least I can test devices and activate them... Just need to figure out why a few policies aren't working right with android devices, and the other UDS issue..
05-04-2012 12:07 PM
I am more then happy to try the information below as it pertains to the APN. However, my question to you is this..
How do you download the APN from the UDS Admin console after you have installed it? I completed all of my work with Chrome b/c IE is not called Internet Exploder for nothing!
I am able to activate a Droid device through UDS without any issues outside of the recognition of a trusted certificate. I just need to get my bloody iPhones working.
05-30-2012 04:25 PM
I am having this same issue, and it is becoming frustrating. I have a simpler set up. I have one server running UDS. I've checked and as best I can tell my certificate matches the web address I'm attempting to put into the iOS device (casewise).
I found if I connect to my network via VPN I get the error immediately. If I'm not connected to the VPN it at least takes some time to try before giving me this same error. I don't have any Android devices to try.
Any ideas would be greatly appreciated.
05-31-2012 01:01 PM
My question is this... Are you running through any sort of load balancer? My issue appears to be directly related to the Net Scaler used in our environment. We have to update our version in order to resolve the problem. Larger projects on our radar has taken away from completing the update and testing.
Also, I would suggest working with BlackBerry support. There support group finally figured out the issue for us after we provided logs showing that a Droid would activate but an iOS device would not.
02-06-2013 05:33 AM
I am unable to activate Android device on my UDS. After typing organization's server name and tapping Next and entering uesrname and password, it gives the error invalid username/password on device. I dont know which log files should i check for errors and what are these errors.
I just installed UDS and this is my first device to be activated.