12-21-2012 06:32 PM
I'm trying to install BB Push Service SDK 1.1.0-1, but the installer always stops at the inital screen after the extraction.
Running Windows 7 on VMware Fusion
Java JDK 6 is installed
Have set JAVA_HOME and added JAVA_HOME/bin to PATH
Is the installer creating a logfile?
Are there any other requirements beside of JDK 6?
I downloaded the Push Service SDK again and reinstalled the JDK 6.
I've already installed successfully the SDK on an other VM, but can't find any differences why the installer isn't working in this VM.
Solved! Go to Solution.
12-21-2012 07:18 PM
The installer will make a log file but that's when it's actually doing the install.
You said it freezes on the initial screen? Which screen is that? The one that prompts you where you want to install the SDK?
12-21-2012 07:23 PM
I can see the inital screen with the progressbar, this screen disappears and the installers is closed.
What's the location of the log file?
12-21-2012 07:49 PM
The logging only happens when you've finished passing through the steps on the installer and it starts the actual install itself.
I wonder why it would just close the installer on its own. Maybe a VM thing? Not entirely sure.
12-21-2012 07:59 PM
Had the same idea, so I tested the installation on a second Mac.
The failed installations were Win7/64Bit using Bootcamp and VMware Fusion 5.
The successful installation was Win7/64Bit using Bootcamp and VMware Fusion 4.
Where does the installer store the extracted data? Maybe it helps to delete these files?
Can I use the linux version on a Mac?
12-21-2012 08:33 PM
You could give the Linux installer a shot on your Mac, but my guess would be that it might not work.
A Mac-specific installer is coming in the near future by the way.
An alternative is to just download the raw distribution files themselves from here:
See the "Alternatively, download the high-level and low-level APIs as raw archive files" section.
You would just get the Linux archive file and download it to your Mac.
The main difference between the installer and using the archive files directly is that the installer offers the ability to deploy the high-level samples we provide with Apache Tomcat. (Tomcat is not part of the SDK itself by the way. It's just for showing the samples.)
12-21-2012 08:46 PM
Also, as a work around you can take the successfully installed Push SDK directory zip it up and move it over to the non working VM. There are two environment variables you'll need to manually set on the Vm for BPSS_HOME and TOMCAT_HOME. There may also be a BPSS_VERSION.
12-21-2012 08:52 PM