Welcome, Guest. Please login or register.
November 21, 2007, 06:30:03 AM
Home Help Search Login Register
News: Check out the Collanos Blog at http://blog.collanos.com.

+  Collanos Workplace User Forum
|-+  Product Support
| |-+  Technical Support (English)
| | |-+  Updated to the newest Version: Can not start Workspace
« previous next »
Pages: [1] Print
Author Topic: Updated to the newest Version: Can not start Workspace  (Read 56 times)
mcwyrsch
Newbie
*
Posts: 7


View Profile
« on: November 10, 2007, 03:17:39 PM »

Help!

Where can I send the logfile?

Cheers
Michael
Logged
mcwyrsch
Newbie
*
Posts: 7


View Profile
« Reply #1 on: November 10, 2007, 03:22:24 PM »

Here is the logfile (part one):
!SESSION 2007-11-10 14:50:19.531 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.5.0_12
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_CH
Command-line arguments:  -os win32 -ws win32 -arch x86 -clean

!ENTRY org.eclipse.update.configurator 4 0 2007-11-10 14:50:30.937
!MESSAGE
!STACK 0
org.osgi.framework.BundleException: State change in progress for bundle "initial@reference:file:plugins/org.eclipse.update.configurator_3.2.100.v20070615.jar/" by thread "Start Level Event Dispatcher".
at org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1141)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:524)
at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1148)
at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.suspendBundle(PackageAdminImpl.java:275)
at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.processDelta(PackageAdminImpl.java:398)
at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.doResolveBundles(PackageAdminImpl.java:219)
at org.eclipse.osgi.framework.internal.core.PackageAdminImpl$1.run(PackageAdminImpl.java:164)
at java.lang.Thread.run(Unknown Source)
Caused by: org.eclipse.osgi.framework.internal.core.AbstractBundle$BundleStatusException
... 8 more
Root exception:
org.eclipse.osgi.framework.internal.core.AbstractBundle$BundleStatusException
at org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1141)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:524)
at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1148)
at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.suspendBundle(PackageAdminImpl.java:275)
at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.processDelta(PackageAdminImpl.java:398)
at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.doResolveBundles(PackageAdminImpl.java:219)
at org.eclipse.osgi.framework.internal.core.PackageAdminImpl$1.run(PackageAdminImpl.java:164)
at java.lang.Thread.run(Unknown Source)

!ENTRY org.eclipse.osgi 2 1 2007-11-10 14:50:51.718
!MESSAGE NLS unused message: ok in: org.eclipse.core.internal.runtime.messages
Logged
vev
Newbie
*
Posts: 10


View Profile
« Reply #2 on: November 14, 2007, 07:05:01 PM »

Could you please tell which kind of install did you use? Commonly you could use such scenarios:
1) Launch the installer, pass the welcome screen and see the screen proposing to "Update existing Collanos instance" or "Install another instance" -> Choose "Update..." -> Proceed to the end of installation.
2) Launch the installer, pass the welcome screen and see the screen proposing to "Update existing Collanos instance" or "Install another instance" -> Choose "Install another..." -> Choose "Standard Install" -> Proceed to the end of installation.
3) Launch the installer, pass the welcome screen and see the screen proposing to "Update existing Collanos instance" or "Install another instance" -> Choose "Install another..." -> Choose "Custom Install" -> Proceed to the end of installation.
4) Launch the installer, pass the welcome screen and see the screen proposing to choose "Standard Install" or "Custom Install" -> Choose "Standard Install" -> Proceed to the end of installation.
5) Launch the installer, pass the welcome screen and see the screen proposing to choose "Standard Install" or "Custom Install" -> Choose "Custom Install" -> Proceed to the end of installation.

It would also be great to see the whole .log file
Thanks in advance for information.
Logged
admin
Administrator
Jr. Member
*****
Posts: 52


View Profile
« Reply #3 on: November 14, 2007, 07:13:14 PM »

You can send the log file to: support <AT> collanos <DOT> com. Thanks.
Logged
Pages: [1] Print 
« previous next »
Jump to:  


Login with username, password and session length

Powered by MySQL Powered by PHP Powered by SMF 1.1.4 | SMF © 2006-2007, Simple Machines LLC Valid XHTML 1.0! Valid CSS!