05-14-2012 06:40 AM
I'm using ISE Design Suite 14.1 (windows 7, 32 bit) and an error appears:
"Environment variable 'TEMP' not defined or points at a non-existant directory or a non-writable directory. Please define it to a directory location for temporary files."
I've created C:\TEMP directory but the problem still exists.
What can I do?
Solved! Go to Solution.
05-15-2012 06:24 AM
First google result:
You may want to check first... you likely already have TEMP and TMP variables, but they may not be pointing to a good location that you're trying to accomplish.
05-15-2012 10:57 AM
Yes, I have already TEMP and TMP variables and they point to "%USERPROFILE%\AppData\Local\Temp" as indicated in the tutorial "How to Add, Remove or Edit Environment variables in Windows 7?", so I think I havo to do something in ISE.
05-16-2012 02:55 PM
The problem has been fixed. Kaspersky had sent two files in quarentine. Yesterday they was returned to be restored and ISE was started to run well.
05-21-2012 11:22 AM
Could you tell us which files Kaspersky quarantined?
We are having the same problem, and we're running Kaspersky KES8 but I am not seeing anything in the quarantine.
08-10-2012 06:14 PM
This has been plaguing me for come time, but I think I have found the cause and the solution.
The environment I have is Windows XP SP3. I run Kaspersky AV but do not believe that is at all involved in the matter.
I have been running into this during implementation using ISE 13.4. Sometimes ISE would stop in translate, sometimes it would stop in place & route. And sometimes it would (after rebooting the machine) run to completion.
One thing that seemed to help for a week or so was to run regedit and in
change forceguest to 0.
But today that failed to help. forceguest was 0 but I simply could not run ISE to completion.
What did seem to solve it was to run a registry cleaner (I use and recommend Advanced System Optimizer 3 Registry Cleaner from SysTweak. It's not free but I believe you get what you pay for.) Make sure that all of the registry scan settings are turned on, particularly "Deep Scan." This found some problems involving C:\temp! After cleaning the registry the problem (at least for now) went away.
I also have a /system/ environment variable TEMP = C:\TEMP.
Hope this helps!