# DS2.1.1 (Suite 2.3.7) Doesn't work

**URL:** <https://forum.sierrawireless.com/t/ds2-1-1-suite-2-3-7-doesnt-work/5610>\
**Category:** Development tools\
**Created:** [May 17, 2012, 6:15pm UTC](https://forum.sierrawireless.com/t/ds2-1-1-suite-2-3-7-doesnt-work/5610 "2012-05-17T18:15:06Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![awneil](https://avatars.discourse-cdn.com/v4/letter/a/49beb7/32.png) [@awneil](https://forum.sierrawireless.com/u/awneil)\
**Post date:** [May 17, 2012, 6:15pm UTC](https://forum.sierrawireless.com/t/ds2-1-1-suite-2-3-7-doesnt-work/5610/1 "2012-05-17T18:15:06Z")

</div>

I just installed the full Framework 2.3.7 from the Full Installer.

On Windows XP Pro + SP3

There were no errors or warnings from the installation.

Developer Studio does not start:

> [@](#):
>
> !SESSION 2012-05-17 19:05:57.859 -----------------------------------------------  
> eclipse.buildId=unknown  
> java.version=1.6.0\_31  
> java.vendor=Sun Microsystems Inc.  
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en\_GB  
> Command-line arguments: -os win32 -ws win32 -arch x86 -data @noDefault
> 
> !ENTRY com.swi.tm.core 4 0 2012-05-17 19:05:59.921  
> !MESSAGE FrameworkEvent ERROR  
> !STACK 0  
> org.osgi.framework.BundleException: The bundle “com.swi.tm.core\_1.3.0.201205041047-R9458 [2]” could not be resolved. Reason: Missing Constraint: Require-Bundle: org.eclipse.core.runtime; bundle-version=“[3.7.0,4.0.0)”  
> at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1327)  
> at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1311)  
> at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:323)  
> at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:389)  
> at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1131)  
> at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)  
> at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)  
> at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)  
> at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)  
> at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438)  
> at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1)  
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)  
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> 
> !ENTRY org.eclipse.osgi 4 0 2012-05-17 19:05:59.921  
> !MESSAGE Bundle initial@reference:file:plugins/com.swi.tm.core\_1.3.0.201205041047-R9458.jar/ was not resolved.

… and so it goes on… ☹

What’s up ❓

[attachment=0]1337277958328.zip[/attachment]

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [May 21, 2012, 6:12am UTC](https://forum.sierrawireless.com/t/ds2-1-1-suite-2-3-7-doesnt-work/5610/2 "2012-05-21T06:12:09Z")

</div>

Did you install 32 bit Java Runtime Environment?

---

<div class="post-metadata">

**Author:** ![awneil](https://avatars.discourse-cdn.com/v4/letter/a/49beb7/32.png) [@awneil](https://forum.sierrawireless.com/u/awneil)\
**Post date:** [May 21, 2012, 5:48pm UTC](https://forum.sierrawireless.com/t/ds2-1-1-suite-2-3-7-doesnt-work/5610/3 "2012-05-21T17:48:05Z")

</div>

I already have DS versions 2.1.0 and earlier installed and working - so I assume the Java is OK…?

---

<div class="post-metadata">

**Author:** ![awneil](https://avatars.discourse-cdn.com/v4/letter/a/49beb7/32.png) [@awneil](https://forum.sierrawireless.com/u/awneil)\
**Post date:** [May 21, 2012, 5:49pm UTC](https://forum.sierrawireless.com/t/ds2-1-1-suite-2-3-7-doesnt-work/5610/4 "2012-05-21T17:49:05Z")

</div>

Anyhow, shouldn’t the installer have told me if Java was missing or incompatible ❓

---

<div class="post-metadata">

**Author:** ![daav](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/daav/32/2767_2.png) [@daav](https://forum.sierrawireless.com/u/daav)\
**Post date:** [May 22, 2012, 8:09am UTC](https://forum.sierrawireless.com/t/ds2-1-1-suite-2-3-7-doesnt-work/5610/5 "2012-05-22T08:09:21Z")

</div>

> [@awneil](#):
>
> Anyhow, shouldn’t the installer have told me if Java was missing or incompatible ❓

True, the installer won’t run on a 64bits VM, and checks that the VM version is correct for DS.  
Anyhow, with 2.37 Full Installer, did you make sure you’ve clicked the correct option to install DS 2.1.1 instead of 2.2.0? Indeed, the default behavior is to install latest online DS release (today: 2.2.0).  
And from what I’m reading in the log, start fails because it’s looking for components of DS 2.2.0:

> [@](#):
>
> The bundle “com.swi.tm.core\_1.3.0.201205041047-R9458 [2]” could not be resolved.

---

<div class="post-metadata">

**Author:** ![awneil](https://avatars.discourse-cdn.com/v4/letter/a/49beb7/32.png) [@awneil](https://forum.sierrawireless.com/u/awneil)\
**Post date:** [May 22, 2012, 6:15pm UTC](https://forum.sierrawireless.com/t/ds2-1-1-suite-2-3-7-doesnt-work/5610/6 "2012-05-22T18:15:31Z")

</div>

> [@daav](#):
>
> with 2.37 Full Installer, did you make sure you’ve clicked the correct option to install DS 2.1.1 instead of 2.2.0?

I didn’t see the option so, no - I didn’t check it!

> [@](#):
>
> Indeed, the default behavior is to install latest online DS release (today: 2.2.0)

So why did it not do that properly?

> [@](#):
>
> from what I’m reading in the log, start fails because it’s looking for components of DS 2.2.0

Again - why did it fail to install 2.2.0 correctly?

What’s my next step? Should I just delete it all and start again - this time taking care to explicitly install 2.1.1?

---

<div class="post-metadata">

**Author:** ![daav](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/daav/32/2767_2.png) [@daav](https://forum.sierrawireless.com/u/daav)\
**Post date:** [May 24, 2012, 8:09am UTC](https://forum.sierrawireless.com/t/ds2-1-1-suite-2-3-7-doesnt-work/5610/7 "2012-05-24T08:09:15Z")

</div>

The option I’m talking about is the “Install” group on top of software selection tree: “Latest software versions” or “This package”  
By selecting the “This package” option, it will install 2.1.1  
By the way, just made a test to install 2.2.0 with this full installer (something similar to your use case), and DS is starting correctly.  
Maybe should you make a new try…

---

<div class="post-metadata">

**Author:** ![daav](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/daav/32/2767_2.png) [@daav](https://forum.sierrawireless.com/u/daav)\
**Post date:** [May 31, 2012, 1:54pm UTC](https://forum.sierrawireless.com/t/ds2-1-1-suite-2-3-7-doesnt-work/5610/8 "2012-05-31T13:54:59Z")

</div>

After some investigation, we found the issue.  
Actually, when a former full installer (containing a former DS release) is used to install the latest online DS release, the installation will success, but DS won’t be able to launch.  
We’ll fix the bug in the next installer engine version.  
Meanwhile, the workaround is:

- If you want to install a former SDK release, please always select “This package” option of the “Install” group
- If you want to install latest software version, please use either the light installer, or install a former release (cf. first point) and then upgrade DS when the software update popup rises up.

---

<div class="post-metadata">

**Author:** ![awneil](https://avatars.discourse-cdn.com/v4/letter/a/49beb7/32.png) [@awneil](https://forum.sierrawireless.com/u/awneil)\
**Post date:** [May 31, 2012, 6:11pm UTC](https://forum.sierrawireless.com/t/ds2-1-1-suite-2-3-7-doesnt-work/5610/9 "2012-05-31T18:11:18Z")

</div>

Thanks - haven’t got around to trying it yet!
