Problems with Java or the server?

Error: can not find main class or can not find jvm.dll

This article applies to:

  • Platform(s): Windows 7, Vista, Windows XP, Windows 2000, Windows 2003
  • Java version(s): 6.0

SYMPTOMS

During Java installation process error message dialog box displays

can not find main class

or

can not find jvm.dll

CAUSE

  1. Corrupt registry entries for Java
  2. Corrupt deployment.properties file for the Java

SOLUTION

Please follow the steps below for resolving this issue.

  1. Remove any traces of the failed Java installation by uninstalling Java.
  2. Download and install the Windows offline installer package.

MORE TECHNICAL INFORMATION

Deployment Configuration File and Properties, Coreranch.com - Error: Could not find the main class. Program will exit.

Source: java.com

The server won't launch on PC which has Java JRE 64-bit (x64 platform)

Java JRE 64-bit (x64 platform) is not supported by the server. Download Remote PC Server v1.0x Full (with bundled JRE) or download and install Java JRE 32-bit (x86 platform).

Error: JRE was not found

First JRE 64-bit is not supported. Install JRE 32-bit.

JRE Not Found

1st SOLUTION

  1. Go to the Control Panel.
  2. Double-click the icon Java Control Panel to open it.
  3. Select "Java" tab.
  4. Click on View in Java Application Runtime Settings.
  5. Appears a window with Java machines that you have in your PC and the folder where you've got your JRE. Change the path to 32-bit JRE (in my case to "C:\Program Files (x86)\Java\jre6\bin\javaw.exe" or simpler path "C:\Program Files (x86)\Java\jre6\". NOT "C:\Program Files\Java\jre6\", it's the 64-bit version of JRE).

There will always be at least one entry. It will be the most recently installed JRE; i.e., the JRE associated with the Java Control Panel.

2nd SOLUTION

  1. Go to "C:\Users\(your user)\AppData\Roaming".
  2. Delete the folder Remote PC Server.
  3. Run Remote PC Server application normally from your desktop shortcut.
  4. It will prompt you to specify the location of Java JRE.
  5. Click Browse, then go to (this is important) C:\Program Files (x86)\Java\jre6\ (note: go to (x86) folder, not to the x64 one).
  6. Choose it and click OK, the server will give an error at System Tray area, ignore it and close the server from there.
  7. Right click the shortcut of the program on the desktop -> Properties -> Compatibility -> mark on Run as administrator -> click OK.

MORE TECHNICAL INFORMATION

Java Control Panel, How do I set or change the PATH system variable?, How do I enable the latest Java version on my Windows system?

Preference error: Configuration file can not be written

Preference error: Configuration file can not be written.

Run the application as Administrator (right-click on .exe or .jar executable file -> Run as Administrator or right-click on .exe or .jar executable file -> Properties -> Compatibility -> mark on Run as administrator -> click OK). The program can not create or modify his files because it's not permitted through strict Windows system policy.

Videotutorial

The server won't launch on PC which has Toshiba Bluetooth stack

java.lang.UnsatisfiedLinkError: com.intel.bluetooth.BluetoothStackToshiba.getLibraryVersion()
...

Toshiba Bluetooth stack isn't compatible with Bluecove library (app's library for Bluetooth).

MORE TECHNICAL INFORMATION

bluecove.org, [BlueCove-users] TOSHIBA Bluetooth stack support

The server opens with Nokia Ovi Suite

Right-click on Remote PC Server.jar in Windows Explorer -> Properties -> Change Opens with to Java(TM) Platform SE binary.

Source: onyxbits.de - I extracted the JAR file, but cannot find an executable file

The server won't launch on PC which has BlueSoleil Bluetooth stack

Exception in thread "main" java.lang.UnsatisfiedLinkError:
com.intel.bluetooth.BluetoothStackBlueSoleil.getLibraryVersion()
...

or

Error: IOEXception - Can't create Service [General fail]

Can't create Service [General fail]

BlueSoleil support is incomplete in BlueCove library (BlueCove supported stacks). Try different versions of IVT Bluesoleil: thread on this issue.