Problem:
Obscure error message http://img66.imageshack.us/img66/6746/confusedg.png
Conditions:
IE7, SP2, latest flash/java. Only reproducible on one machine.
Observations:
Smaller than a javascript alert box, and seems to be generated when a swf on my web page loads. The dialog is modal, however, like an alert box.
Issues:
I've tried matching the configuration of the machine in question, but a recreation of the machine does not get this error. I'm not ultra-familiar with flash/flex, so is there something that flex/flash could do which would cause this error dialog to appear.
How would one even go about debugging this? It's mostly not reproducible aside from a single machine, and the circumstances which cause the error are unknown. Thoughts?
Looks like a windows dialog to me. Neither Flash/Flex or Javascript. (though one could make either look like that if they tried).
The problem could be entirely machine dependent, it could be a virus, or it could be anti-virus or add blocker thinking the flash file is a threat. My automatic backup.recovery software sometimes pops alerts like that when it's in the middle of making a backup and I download something.
I'm meandering, my point is there are far more variables than just the browser and flash versions that could be coming in to play. I know that probably doesn't help much, but hopefully I've given you a few more ideas of what to check.
When you're setting up the "mirror" of your development machine, are you sure you're installing the version of Flash with Debugging enabled?
That might have something to do with it.
Have you tried using IE developer toolbar? http://www.microsoft.com/downloads/details.aspx?familyid=e59c3964-672d-4511-bb3e-2d5e1db91038&displaylang=en
Process Explorer would help debug this by displaying the call stacks of the IE7 process. You could then look at each call stack in order to find the one displaying the message box. This will show you exactly which modules are on the stack at the time the message box is displayed.
Related
I have one program, I maintain, that was originally written in Oracle Forms 6i. A while ago I migrated it to 11g. Our users access this Oracle Forms program through their Internet Explorer browser on their Windows 7 machines.
The problem has been that the program only seems to run well for our users, when they have Java 6 Update 45, installed on their machines. Going to a newer version causes problems.
Today, I wanted to get this resolved, so I updated my PC to Java 8.31, and attempted to access my Oracle forms program using IE. (Thanks to Viewing oracle app and getting: java.lang.ClassNotFoundException: oracle.forms.engine.Main I was able to get the form running again in my web browser.)
When my form ran, I found the tab key wouldn't advance to the next field on the login dialogue box. But after I logged in the tab key worked. (The tab key initially not working is a small thing, but it has really annoyed some of our users.)
I then used several different forms. Some worked just fine, no problems. But then when I clicked a button, on one form, it would endlessly try to complete a request; to the point that I couldn't even close the web browser to stop it. (Finally I just used task manager to end my web browser’s process.) This seemed to go in line with what some of our users have reported: (when attempting to use the latest Java) that the Oracle forms application just stops working completely after a while.
Because of these issues our users want to keep Java 6 Update 45 on their machines. I know this is a major security hole, but I haven’t quite nailed down what the solution to it is.
Has anyone else had a similar issue? We're running Oracle Fusion Middleware 11; specifically Forms Services version 11.1.2.0.0
Thanks.
Well this may not be a question that needs answering after all.
I've done some more testing since asking this. Besides the login dialogue box (not responding, as it should, to the tab key) everything else works just as it should.
I still have one form that hangs; but that’s all (and it may be caused by something else). All my other forms seem to work just fine.
I talked with one of my co-workers, and I realized we really need to investigate and determine what version of Java our users really are using. They may not have used the most recent version of Java; which I used with success, today. Or some may be already on it; and that's why they aren't complaining.
At any rate more research, is needed on my part. Thanks to all who read this. If any of you have had similar experience in something like this, still feel welcome to answer/comment.
I have already asked this and was heavily downvoted. Unfortunately, I still can't solve it. I don't know what I do, but sooner or later I loose an ability to run java applets and java web start applications in all browsers.
Here is an example what is happening.
I am opening page with applets http://csis.pace.edu/~bergin/Java/applets.htm and getting the following picture:
with signs plugins were blocked. I am trying to unblock
which causes another dialog
after OK I have another
next
if clicked
And so on.
Applet doesn't run.
After dancing with PATHes, Java updates and so one, once I can have applet run. But sooner or later I will stuck in this position again.
I would like to know, is it possible to exclude this situation in principle?
I mean I don't want to disable security at all, but I mean that in case my explicit permission everything should run. Is it possible to do that?
UPDATE
First of all, I don't understand, why can't I run applet on outdated java if I want?
I am a human and robots should obey me! :)
Suppose I wish to debug my applet on old version of java, why not?
Second, there is no information about what version it thinks I have and what version it wants?
Without this information it is possible that there is just a bug in version detection mechanism.
I have multiple versions of Java in Program Files since I am a Java developer. Then how can I know which one it uses?
UPDATE 2
I have updated my Java from 1.8.0_20 to 1.8.0_25 and now situation have changed, but applets are sill impossible to run.
The proof I have "latest" java:
The proof I have added the site above to exclusions list:
The effect of applet run:
(applet not runs)
Clicking details result:
(no any details in fact)
So, what to do?
UPDATE 3
This site is not working: http://ssd.jpl.nasa.gov/sbdb.cgi?sstr=2012VP113;orb=1;cov=0;log=0;cad=0#orb
(show orbit diagram)
Reloading/restarting browser does not help.
I looked at your html source and realized you're using the .class file directly instead of wrapping it in a jar file. This is what you have:
<applet code="GSort.class" width=700 height=400>
I think applets no longer work when using .class files directly due to new security requirements. They have to be wrapped in jar files because you need to add some security settings to the meta-inf folder of the jar file. Here is how oracle recommends deploying an applet:
https://docs.oracle.com/javase/tutorial/deployment/applet/deployingApplet.html
Edit:
I tried again with adding the site url to the Java security exception list and this time I got it to work! It looks like chrome stays in memory after exiting so changing Java security doesn't affect it unless you shut down chrome completely and restart it. Easiest way is to use Internet Explorer. Try it with Internet Explorer and it should work (assuming that you still have the site added under java security exception list).
I can't figure this one out.
I have Java code that captures Webcam, it works awesome for what I need.
Issue comes along when I am trying to make an Applet out of it. I made applet, but it simply doesn't work. It doesn't create any visible errors, doesn't complain about libraries, basically nothing I can grub on to. The only thing I can see in Console log (Mac OS 10.5) is following message:
PluginProcess[10143] Process manager already initialized -- can't fully enable headless mode.
I don't have any ideas on how to fix it. Please Advise.
Thank you.
P.S: I just want to make Java Applet out of existing code so I can dump it into machine (any) and it can stream video from webcam.
https://bugzilla.mozilla.org/show_bug.cgi?id=574904#c23 says "this message is a
red herring: You always see it (using Apple/Sun's Java Plugin2) whenever any
Java applet is displayed."
I'm working on a Java webapplication. Something I did, perhaps the javascript, caused the back button of the browser to stop working (it actually just shows a thinking circle on the tab in chrome).
The problem seems to be only in chrome
I'm not sure exactly what to look for...
What can cause the browser back button not to work?
This is an open bug on Chrome. It may not have anything to do with your application: http://www.google.com/support/forum/p/Chrome/thread?tid=1893e974f696f250&hl=en
Edit:
Here's the quick link to the actual reported bug.
Are you using the location.replace method anywhere? If you're talking in general and not just in Chrome, it's the only thing I can think of that would cause the back button not to work.
See the first point here.
Other than that, and especially if it just happens on Chrome, a browser bug seems much more likely.
Sounds like it could be a server side problem. Make sure you don't have any infinite loops and limit the runtime of your script.
I am trying to run a Java webstart application which is launched from a html page. While loading I get an alert with the message "Automation server can't create object" a couple of times after which the applications starts and works fine. The alerts come up only on one of the workstations. Any pointers on where I should look?
Regards,
Dutch
try the following IE setting: "Initialize and script ActiveX control not marked as safe."
May or may not apply to your case, but there are reported problems with the JScript Runtime throwing up errors when starting up Applets or Java WebStart applications when you have specific network settings.
Every now and again, there's a Windows Update that generates such a bug and another one that follows to fix it and you'll see some of these errors. Yours might be one of these.
Usually the workaround in-between is to either:
go to IE's Network Settings and uncheck "auto detect settings" or any PAC file setting
or go to the Java control panel's Network Settings and disable "Use browser settings" or other settings to use a direct connection instead.
Obviously, that workaround is only valid if you do not have to go through a proxy...