Error message points to the old file structure when I type 'java' at the cmd prompt; CLASSPATH is updated - classpath

After I re-named my JDK folder and deleted a JRE folder (I actually had to kill a process in order to delete the folder) then I edited the system variables accordingly but I'm getting error messages when I type in 'javac' or 'java' even when %classpath% shows the updated values.
Is there a hidden system variable that is still holding the older value? How can folder I get ride of the old pointer to jre folder? Is this because I ended a java process earlier in order to be able to delete the JRE folder? If so, how can I fix it now?
Thank you so much in advance for helping me out.
This is copied from the command window:
C:\jdk1.7>java
Error: could not open `C:\Program Files\Java\jre7\lib\i386\jvm.cfg'
C:\jdk1.7>javac
'javac' is not recognized as an internal or external command,
operable program or batch file.
C:\jdk1.7>echo %classpath%
.;C:\jdk1.7\bin;C:\jdk1.7\lib;C:\jdk1.7\jre\bin;C:\ANT\lib;C:\ANT\bin;c:\documen
ts and settings\homayoon\my documents\selenium tutorial\;
C:\jdk1.7>

If you renamed the folder manually, there will be a lot of registry entries that point to the old name.
Change them with RegEdit; or, faster, reinstall Java.

Related

Kotlin compiling from command line

I need to compile some Kotlin files and run them as described at Kotlin documentation
However, my command line keeps saying this:
C:\Users\name\Documents\Projec\Kotlin>kotlinc
'kotlinc' is not recognized as an internal or external command,
operable program or batch file.
I am a 64-bit Windows 7 user.
So I downloaded the latest version of the compiler (1.0.6 ATM) and extracted the files into my Program Files folder.
My variable path is set like this:
PATH=C:\Program Files\Java\jdk1.8.0_101\bin; C:\Program Files\kotlinc\bin;C:\Program Files (x86)\Android\android-sdk\platform-tools;
At this point I have no idea, I tried two versions of the compiler and tried changing the path variable few times.
Any help appreciated.
Windows PATH is semicolon-delimited; white space is not trimmed.
You need to remove the space between ; and C:\Program Files\kotlinc\bin\ in order for the directory to be added correctly to PATH.

xcopy is not recognized as an internal or external command, operable program or batch file

I have a problem using 'xcopy' command.
I'm building a C# project with msbuild. At the end of the build, a batch file is called to copy my assemblies from Debug/Release to some other folders.
Here is the problem, my build fail and the error log is 'xcopy is not recognized as an internal or external command, operable program or batch file'.
The path is correctly set, xcopy do works from a windows command line and from the visual studio command line (the one set with the project environment).
I tried to set the path in the batch file but it doesn't help.
Any suggestion?
I'm using windows 7
Cheers :)
I encountered the same problem.
It seems to be a problem with the path environment variable within Visual Studio.
When I added a "path" statement to the beginning of my build event, it produced the following output:
PATH=
This seems to indicate that the path is empty within the VS build environment.
When I specify the full path to xcopy like this, the problem went away:
%systemroot%\System32\xcopy ...
I'm not sure what caused Visual Studio to lose it's path.
Set Environment variable PATH = %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\
This is not a problem with Windows 7 or 8. It's actually a problem with applications that update environment variables such as PATH.
The PATH is stored in the Registry as an "Expandable string value" (REG_EXPAND_SZ), but a lot of applications write it back to the Registry as a "String Value" (REG_SZ). If your path contains anything like %SYSTEMROOT%, this will not be expanded into C:\Windows (or whatever yours is) if the path is stored in a REG_SZ.
The fix is simply to edit your path manually from the control panel. You need to make a change (eg add a ; to the end of the path) and then apply it. This will fix up your path in the Registry to be a REG_EXPAND_SZ.
(Go to the System Control Panel and select Advanced System Settings. Edit the Path Environment variable in the lower box, and that should fix it.
You can tell whether your path is broken in this way by opening a command prompt and typing PATH. Your path will be listed. If you can see anything enclosed in % % then your path is not being expanded.
It happened to me after I updated one of my Visual Studio extensions, during which Visual Studio was closed and reopened by the updater. I could no longer properly build my project. I closed Visual Studio and reopened it and the problem went away.
I just experienced this for the first time with a batch file I use to copy an Access front-end app to the user's local machines. Their environment is a mix of Windows 7 & 8 and 32-64 bit machines. I noticed that the xcopy.exe was both in the System32 and the SysWOW64 folders and I wondered if there was some conflict. So -- I copied the xcopy.exe into the folder where the batch file resides and it now seems to be working. Just thought I'd share this.
Eileen
I also had a problem with xcopy (same error message) - with a very simple batch program that I use to backup files to a removable drive. Have been using that program for at least 5 years with never a problem. Then yesterday xcopy is unknown to Win7. The replacement of xcopy with %systemroot%\System32\xcopy at each instance solved the problem. Very strange.
Go to environment variable and correct PATh including ; in last.
It will work, this is not at all related to OS or Technology.
It's working for me, Not even need to restart OS, Just open new command prompt.
[Fixed for me]
After adding the correct paths to "Path" environmental variable it still doesn't work (for cmd and VisualStudio) (even after restarting the PC).
The problem was in broken register parameter:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment]
ParameterName=PATHEXT
I had the value .wlua;.|exe. Maybe was broken after installing something.
Everything works again after changing it to:
.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
Hope this helps if nothing other works.

Eclipse: How to get full filepath from error "Failed to load JNI shared library"?

Something has gone wrong with my java set-up on my computer, obviously, but I can't figure out what it is until I get some more info.
When I try to run Eclipse, it give me an error:
Failed to load the JNI shared library "C:\Eclipse\1234\tools\jdk1.5.0_14\bin\..\jre\bin\client\jvm.dll"
I want to know how to find out what the rest of that filepath is. "\bin..\jre\" doesn't help me much. I suspect that it's 2 paths concatenated, but I'm not sure.
I've tried running Eclipse from the command line, but the error shows up only in the popup window.
Also, where does the JNI path get set, anyway?
I've looked at my JAVA_HOME environment variable, but it only contains "C:\Program Files\Java\jre7\bin".
This JNI-path-corruption... thing happened after I ran an installer -- nope, no uninstaller :(
C:\Eclipse\1234\tools\jdk1.5.0_14\bin\..\jre\bin\client\jvm.dll
I want to know how to find out what the rest of that filepath is. "\bin..\jre\" doesn't help me much. I suspect that it's 2 paths concatenated, but I'm not sure.
That is the full path. On all file systems that I've used ".." indicates the parent directory (i.e. up one directory). So the path refers to:
C:\Eclipse\1234\tools\jdk1.5.0_14\jre\bin\client\jvm.dll
As for how eclipse has decided on trying to use this path, I'm not sure.
your JAVA_HOME settings are wrong , as JAVA_HOME should point to the directory just above bin , and in the bin directory java executable files e.g. java.exe , javac.exe , appletviewer.exe must exist.
For example, if on my computer java.exe is in D:\JAVA7\bin directory my JAVA_HOME will be D:\JAVA7

How to set workspace in eclipse to a directory that has space in it?

In my code, i get the workspace directory and then create a temporary file in it. However, my workspace directory has space in it:
C:\Documents and Settings\F1QB\Workspace
When my code reads this, it throws an error saying that it cannot find the directory. Now, i read that i should use a directory with no spaces in it. But, since i am working on my company's machine, I don't have admin access. So, this is the only directory i can use.
I tried switch workspace option and gave %20 instead of the space. But, eclipse throws an error on restart. It says:
The folder C:\Documents%20and%20Settings\F1QB\.metadata is read only.
Is there any workaround for this problem? Thanks for the help in advance
Try c:\Docume~1\F1QB\Workspace that usually works for long file and directory names.

eclipse window not opened when i am trying to click eclipse.exe

When i am trying to open eclipse exe file , window is not opened , why this is happened , previously it is working fine but today it is not opened any changes i need to do?it will help full if any one gave quick fix .
thanks
Ramana
(The OP ramana solved it by uninstalling and re-installing Java, but below is another potential cause)
Check if your PATH hasn't changed somehow: see Java Tips: “Adventure” in resolving the Java error “Error occurred during initialization of VM”
Running Java.exe produce error in other directories (since the SDK’s bin is added to path.)
However running in it’s bin directory, it runs fine.
In the case of the ips mentioned before, the issue was:
The good news is that it is nothing supernatural or magical image but the bad news is that the Windows directory is the “protagonist” image.
From file search, it can be concluded that somehow certain mischievous program is copying some crucial java files into Windows directory which are stored in path, and so unless the java’s bin is the foremost in the path, one will bound to get the error.
The error occurs because java.exe or other Java executable expect some support files and directories to be found but obviously could not find it in Windows directory.
Running the java.exe in its bin directory will not produce error because Windows will use the current directory to which the file is run first before searching for it in the path.
That might not be the case for you, but that could still be related to a PATH issue.