I am having trouble in testing a Midlet. I am using j2me sdk 3, the Midlet builds successfully, but when i try to run it, it fails and it shows the following message in the log:
Failed to connect to device {0}!
Reason:
Emulator {0} terminated while waiting for it to register!
I had the same problem. On the next system restart there where message about runMidlet crash due to DEP (Data Execution Prevention).
After turning off DEP all started to work perfect.
In case it could help, it was on Win2003, Java ME SDK 3.0.
UPDATE:
I advise to turn off DEP for all programs (it is "Turn on DEP for essential Windows programs and services only" option).
In my case turning off DEP for single runMidlet.exe had only temporary effect.
See also Java ME SDK Team blog entry on this
You probably need to increase the debugger timeout value. I work in WTK 2.5.x so I'm not sure where this setting is exposed (are you on Netbeans?) in version 3.0.
Somewhat out-of-date instructions for Eclipse and Netbeans.
Just go to tools/java platform, select the CLDC Framework blah blah blah and Click refresh.
If you are using Linux as your operating system just you need to type the command 'setenforce permissive' in the terminal.It will solve the issue.
Rishabh
Aside from the DEP issue mentioned in other answers, there is a useful list of solutions to common problems here.
Related
I have been having problems with my Windows 10 (for example my localhost:8000). So I started looking for an answer, and it looks like the good old IIS is causing this issue, maybe because it's not enable in the turn Windows features on/off. SO in theory it should be a piece of cake right? Well when I click next I get the following message:
Windows couldn't complete the requested changes.
The function attempted to use a name that is reserved for use by another transaction. Error code: 0x80071A90
I read somewhere that it may be related to the .NET Framework, I have Framework 3.5 and 4.6 installed. I have tried all possible combinations, enable both of them, disable both, only one, everything! Not real information around regarding the Error code either.
Does it have something to do with the version of Windows that I have? Which is Windows Home. Is there any other way to make it work? Thank you in advance for your input.
As this is one of the first hits when you search for that error message posting solution here...
If you get this error when trying to "Turn Windows features on or off" in Windows 10 - make sure to disable Antivirus program.
Culprit for me was Avast.
To disable Avast right click on the icon in task-bar -> Avast shields control -> Disable until computer is restarted.
After Avast was disabled I had no problems with adding new features.
I've just downloaded Eclipse on elementary OS and attempted to launch it. After doing so, I saw the loading screen for a few seconds before it disappeared and left me with the desktop. Since then, my computer (an old Dell with 4GB of RAM and an Intel Core Duo) has been very unresponsive and the disk activity indicator is almost constantly lit up. I've been looking at the desktop for around 30 minutes now! How can I solve this problem and launch Eclipse?
EDIT: Running eclipse -clean from the command line produces the following error: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized.
First, you might review your installation steps. If nothing is obviously wrong, check the following:
check for any error logs
check that you're using the proper Java version
make sure that there's enough memory allocated for Eclipse (see the eclipse.ini file)
as a last resort, try reinstalling it
See also the following guide for installing on Elementary OS: how to install
If that's not working submit more details of your specific problems.
NOTE: You may have to find the right Java and install it "by hand" rather than relying upon the distribution's package manager. You can "point" Eclipse at the right Java by editing the .ini file.
Some related links are as follows:
a similar symptom related to multiple screens and/or corrupt workspace
General trouble-shooting related to your issue and symptoms
When I run the program in j2me the emulator is not run and show that code what is mean? here the code.
C:\Documents and Settings\admintrator\My Documents\JavaMESDKProjects\MobileApplication4\nbproject\build-impl.xml:629: Execution failed with error code 1.
BUILD FAILED (total time: 2 minutes 1 second)
Seems that you do not have J2ME SDK installed on your computer.
Download it and install on your computer.
After that specify the location of installed J2ME SDK in your Netbeans project "Platform" settings.
Also make sure that Java/bin folder, where javac.exe located is specified in the system PATH environment variable.
I also experiencing this problem using sun wirless toolkit but my solution to this problem is somewhat irrational. When I'm going to run the application I disabling all my network adapter, LAN, WLAN even Bluetooth if you have but still I don't think that it will solve everything. You can try to do this if you wish but not suggesting the best way to do.
and thank you for your time.
I am using Titanium Appcelerator to write an app for Android, and as compared to Windows, where the emulator was quite stable, in Linux I get the following symptoms:
emulator restart with no reason, sometimes after a runtime error, sometimes right after launching my app, and sometimes just right after booting completely after being launched
emulator informs that "process $1 is not responding", where $1 is generally the system process, but sometimes may be acore, or the calendar. This may happen while installing my app on the emulator, right after loading it, or right after unlocking the screen.
As it is easy to imagine, testing code like this can be quite difficult, so I was wondering, has anyone else stumbled upon this problem, and/or know how it could be solved?
Thank you very much in advance, and pls let me know of any info I should provide.
Leo
You should verify that the emulator is working fine without Appcelerator first. Definitely update to the latest SDK (r8) and create a new emulator AVD and see if the problem is there without Appcelerator.
I think I found a solution, but I don't claim it is universally valid: I just erased the virtual device created under Titanium, changed the project file for it to use SDK 1.4.2, and had it launched again under 1.4.2. It certainly didn't build my app, but at least it created a new virtual device, which I use now to build against 1.5.0, working like a charm so far.
Thanks again Manfred for pointing me in the right direction!
(I'm re-posting this message since I signed up as a user now)
I just installed Visual Studio 6 (SP5) on a Vista Enterprise machine. Had some problems but I think it’s set up alright.
The problem is my VC++ 6 application fails when trying to host an ActiveX. I was able to compile it ok, though got a warning message from Vista about the rc.exe (“This program has known compatibility issues” ).
When I debugged it I saw that my class that derives from CAxDialogImpl fails on its Create() method. The same application worked just fine on XP!
Is there a known compatibility issue there?
Some tech info: I saw that CAxDialogImpl::Create() (I pass NULL here) calls AtlAxCreateDialogA, which in turn calls CreateDialogIndirectParamA which throws a general exception.
Thanks a lot, Erik
PS -
1. I am Admin on my machine. OS is 32 bit.
2. I know that VS6 is not supported on Vista but I had no choice since I ran into troubles trying to migrate it to VS 2008.
OK.
Found the reason and the solution.
It appears to be a DEP compatibility issue.
It was hard to locate since when the application failed no exception / message shown.
The problem was caused due to old ATL components used in the my dll.
Old versions of ATL generate machine code at runtime and then attempt to execute this code from pages of memory that were not marked as executable, thus causing a DEP violation if hardware-enforced DEP is enabled.
The difference between my XP machine and the vista machine was actually in the DEP operation - the DEP on the vista is hardware-based, which caused the problem.
Also, I had COM applications using the same dll and working fine, however .Net applications were failing because they were created with the DEP compatibility flag.
The solution was to remove the DEP compatibility flag from the .Net applications.
Cheers,
Erik
PS - two links were very helpful:
http://support.microsoft.com/kb/948468
How to make my program DEP-compatible?