Bad major version number error

I'm trying to run the HelloWorld program in Linux. I can compile ("javac HelloWorld.java"), but when I try to run the program, using "java HelloWorld", i got the following error message:
Error loading class HelloWorld: Bad major version number
Any idea of what's wrong?

well, i found the problem. i had installed an old java version and forgot to delete it. i was using jdk 1.1 and i didn't notice it. just deleted the old version and everything went fine. thanks, m_srini ! :-)

Similar Messages

Java.lang.ClassFormatError: Bad major version number

Hi friends,
I am using JWS2.0(trial version). I have uploaded class files into servlet (and respective packages), every thing was working fine. one fine day i started getting the 404 - file not found error(JWS not yet expired). I uninstalled the jws, j2sdk1.4.0, jre1.4.0 but with no result.
I even formated the system and loaded all again. But still i am getting the same problem.
The servlet is the simple HelloWorld servlet.
Through the SunExample its working fine. But the uploaded servlet is not getting recognised.
Here is the ErrorLog
[Tue Feb 22 17:26:29 GMT+05:30 2005] ClassLoaderFactory Error: Can not find Class : Hello [ ClassNotFoundException ]
[Tue Feb 22 17:26:31 GMT+05:30 2005] ClassLoaderError: (com.sun.server.loader.JarClassLoader@17d67e:\servlets) ERROR: Unable to load class local class Hello
[Tue Feb 22 17:26:31 GMT+05:30 2005] java.lang.ClassFormatError: Bad major version number
at java.lang.ClassLoader.defineClass(ClassLoader.java:219)
at com.sun.server.loader.ServletClassLoader.callDefineClass(ServletClassLoader.jav a:726)
at com.sun.server.loader.ServletClassLoader.checkAndDefineClass(ServletClassLoader .java:620)
at com.sun.server.loader.DirectoryClassLoader.getClassFromLocalDir(Compiled Code)
at com.sun.

Try re-compiling the Servlet. Make sure that the JDK version used to recompile is <= the version used to run the server (if you are using a higher jdk to compile the servlet, maybe Java 5.x, then you are to run, maybe Java 1.4.x, then use the -target option of javac to target the lower release...)

Bad major version number! Help please ;-)

I have been writing applets using the Forte 3.0 sdk.
I don't as yet use Swing, but rather the standard AWT elements.
These applets work fine in IE 5, but when I try to view them in Netscape Communicator 4.79, the applet fails to appear and I see the following error message "Applet Editor Error:java.lang.ClassFormatError: Bad major version number"
I have searched the net and this is some advice I found: "The javac by default compiles for 1.2 compatible vm's. To compile an application to be compatible for both 1.1 and 1.2 vm's use:
javac -target 1.1 foo.java"
I'm guessing Netscape isn't 1.2 compatble, despite that the java plugins for 1.4.0 are enabled ( I have checked.).
So my question is:
How do I force 1.1 compatability in the Forte IDE?
I have looked through all the options and cannot find any switches for compatability.
I'm not using command-line so I can't directly add -target 1.1
Thank you in advance.

In Forte go to menu Project->Settings. Open Compiler Types->External Compilation, there you have a property called "External Compiler", click on the value and there you can edit the arguments that are sent to the compiler...
//Anders =)

Major version number mismatch warning ?

Flatform : RedHat Linux7.1
Program : j2sdk-1_4_0-linux-i386.bin
I have this error after installing jdk1.4.0 and typing 'javac' :
===========================
Warning: Major version number mismatch.
Warning: Minor version number mismatch.
Warning: Major version number mismatch.
Warning: Minor version number mismatch.
Warning: Major version number mismatch.
Warning: Minor version number mismatch.
Warning: Major version number mismatch.
repeat...
Why this error do occur?
How can I complete jdk1.4 installing?

I'm getting the same warning as well. I recently upgraded from Red Hat 7.1 -> 7.2 and have j2sdk1.4.0.
I get the following warnings when I actually run programs:
Warning! Major version number mismatch.
Warning! Minor version number mismatch.
Did you ever find any resolution? I'll keep looking & if I find something, I'll post it here.
Thanks-
[email protected]

SSL "SSL3_GET_RECORD:wrong version number" error using Mail

I have set up an SSL proxy and I am trying to send a message through it to my mail server.
The proxy's log shows a "SSL3GETRECORD:wrong version number" error whenever Mail tries to send a SSL message.
I have been told that this error means that the proxy's certificate is using SSL3 but Mail is using a different version of SSL.
Does anyone know what version of SSL Mail uses, or how to change it to use version 3?
Thanks,
James.

That's peculiar. Sounds like you're experiencing issues communicating over SSL somewhere.
Can you share some details with me? Feel free to ping me at andrl {at} microsoft.com
Some things that'll help troubleshoot:
- When and where are you seeing the error? Please provide a stack trace if you have one.
- Is your host behind a proxy that has https disabled? Is this running on Azure or somewhere else?
- What version of openssl, node.js, and documentdb client are you running?
* To find the version of openssl - run "openssl version" in a terminal.
* To find the version of node.js - run "node -v" in a terminal.
* To find the version of documentdb client - look inside the package.json for your project.

Incrementing major version of configuration

When I create a new version of an existing configuration in RON the program increments minor version number of the configuration, e.g. 1.2 -> 1.3 -> 1.4 etc. But if I want the major version number to be incremented, e.g. 1.4 -> 2.0, how can I make that happen? In Configuration Properties window the field showing version seems to be always in read-only state, so I cannot use that but is there any other way to do what I need? Actually there is quite analogous problem with files in my private workarea. How to increment major version number of a file?
Risto Nieminen

Risto,
That's one limitation that's rather hard to work around. You have two options:
(1) Manually specify the version number EVERY time you check in an object. This is not a very sensible solution unless you can be sure every developer will abide by this standard without fail. You can't easily add a version number after the object has been checked in.
(2) Don't ascribe any significance to the generated version numbers. Don't use the generated version numbers as release numbers, for example. Instead, name your configurations for the external release numbers, e.g. RELEASE_2_4_1 for release 2.4.1.

Help Updates Doesn't upgrade major version to 2014, only applies minor version updates

I have Adobe Creative Cloud for OS X deployed to many machines using CCP and Casper and I have now set up AUSST.
On one test machine, I opened one CC application and went to Help > Updates and installed all available updates. It appears to only install minor version number updates, not Major version number upgrades, so my machine is not on CC 2014.
Is this expected behaviour? Should I now be on 2014, or do I need to build a new package using CCP for 2014?
If I need to build a new package, what do I do regarding the existing installations? DO i need to remove all those components first?
Thanks,
Alan.

Alan,
This, like it or not, is the world of CC 2014. They are new versions -- upgrades rather than updates. The pre-CC 2014 versions can be installed alongside the new versions without a problem. They will need to be uninstalled individually if you don't want them lying around. And sadly, unlike the CS suites, there is no single uninstaller that will remove all the unwanted CC applications. They need to be removed one-by-one.
We should let one of the Adobe moderators vet this response, but this is my understanding and experience.
Ric

Java error message - Bad version number in .class file

I get the error noted below in Safari, Firefox, and Chrome when I try to view java containing web pages.
Specifically this page: http://aviationweather.gov/adds/tafs/java/
My Java Preferences are as follows
My OS is 10.5.8
Thanks!
Java Plug-in 1.6.0_26
Using JRE version 1.5.0_30-b03-389-9M3425 Java HotSpot(TM) Client VM
User home directory = /Users/ernest
c:   clear console window
f:   finalize objects on finalization queue
g:   garbage collect
h:   display this help message
l:   dump classloader list
m:   print memory usage
o:   trigger logging
q:   hide console
r:   reload policy configuration
s:   dump system and deployment properties
t:   dump thread list
v:   dump thread stack
x:   clear classloader cache
0-5: set trace level to <n>
java.lang.UnsupportedClassVersionError: Bad version number in .class file
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:676)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
    at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja va:25)
    at java.lang.reflect.Method.invoke(Method.java:592)
    at sun.plugin2.applet.Plugin2ClassLoader.defineClassHelper(Plugin2ClassLoader.java :1014)
    at sun.plugin2.applet.Plugin2ClassLoader.access$100(Plugin2ClassLoader.java:69)
    at sun.plugin2.applet.Plugin2ClassLoader$2.run(Plugin2ClassLoader.java:991)
    at java.security.AccessController.doPrivileged(Native Method)
    at sun.plugin2.applet.Plugin2ClassLoader.findClassHelper(Plugin2ClassLoader.java:9 55)
    at sun.plugin2.applet.Applet2ClassLoader.findClass(Applet2ClassLoader.java:134)
    at sun.plugin2.applet.Plugin2ClassLoader.loadClass0(Plugin2ClassLoader.java:250)
    at sun.plugin2.applet.Plugin2ClassLoader.loadClass(Plugin2ClassLoader.java:180)
    at sun.plugin2.applet.Plugin2ClassLoader.loadClass(Plugin2ClassLoader.java:161)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
    at sun.plugin2.applet.Plugin2ClassLoader.loadCode(Plugin2ClassLoader.java:675)
    at sun.plugin2.applet.Plugin2Manager.createApplet(Plugin2Manager.java:3046)
    at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Plugin2Manager.ja va:1498)
    at java.lang.Thread.run(Thread.java:655)
Exception: java.lang.UnsupportedClassVersionError: Bad version number in .class file

Hi, thank you for the reply. However, java is definitely enabled on my computer, on all my browsers. In fact, if I go to the SUN website and run the java test, I get that all is OK.
I think it may have something to do with the .class (maybe in .jar-file) compiled with a higher version of java than the virtual machine trying to run it.
The example I found (google search) is .class-file that is compiled with JDK 6 and I am trying to run it with 1.4 JVM.
There is some software error going on somewhere... but I do not know enough to fix it.
Many thanks for all your help

[ERROR CODE DPL.DS.5107] problem when deploying an app (Bad version number)

Dear colleagues,
please find attached a Java exception trace, where I tried to deploy a sample application to my CE 7.1 (only Java version).
I use JDK version 1.6.0_06: do you know this problem? Do you have any hints?
Compatibility level is put to "6.0": I read only about problems related to JDK 1.5.xx versions.
The consequence is that the component cannot be deployed sucessfully.
Kind regards,
Daniel
[ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 7584050:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5107] Exception during initial start of application de.dkoller/instantdlv~ear in container webservices_container.
        at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.makeStartInitially(StartInitiallyTransaction.java:195)
        at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:143)
        at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:419)
        at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyGlobal(StartTransaction.java:449)
        at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:437)
        at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:178)
        at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:419)
        at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:444)
        at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:334)
        at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
        at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:248)
        at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:389)
        at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3387)
        at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3373)
        at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3276)
        at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3249)
        at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
        at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
        at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
        at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
        at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
        at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
        at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
        at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
        at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
        at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
        at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
        at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
        at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
        at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
        at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
        at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
        at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872)
        at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
        at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
        at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
        at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
Caused by: java.lang.UnsupportedClassVersionError: Bad version number in .class file
        at java.lang.ClassLoader.defineClass1(Native Method)
        at java.lang.ClassLoader.defineClass(ClassLoader.java:654)
        at com.sap.engine.boot.loader.ResourceMultiParentClassLoader.loadClassLocal(ResourceMultiParentClassLoader.java:198)
        at com.sap.engine.boot.loader.MultiParentClassLoader.findClassInLoaderGraph(MultiParentClassLoader.java:302)
        at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:256)
        at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:228)
        at com.sap.engine.services.webservices.server.deploy.ws.WSInitialStartProcess.generateJAXWSFramework(WSInitialStartProcess.java:265)
        at com.sap.engine.services.webservices.server.deploy.ws.WSInitialStartProcess.generateJAXWSFramework(WSInitialStartProcess.java:220)
        at com.sap.engine.services.webservices.server.deploy.ws.WSInitialStartProcess.execute(WSInitialStartProcess.java:140)
        at com.sap.engine.services.webservices.server.deploy.WSBaseAbstractDProcess.makeProcess(WSBaseAbstractDProcess.java:316)
        at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.makeStartInitially(WebServicesDeployManager.java:687)
        at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.makeStartInitially(StartInitiallyTransaction.java:182)
        ... 36 more

This forum is for the Sun Java System Web Server, not the Sun Java System Application Server. You will likely have better success by posting your question to the Application Server forum(s) at:
http://forum.java.sun.com/category.jspa?categoryID=109

JDBC error : UnsupportedClassVersionError:Bad version number in .class file

Hi All,
I am currently working with PI 7.1 on an Idoc ->XI->JDBC scenario. The DB being used in our case is SQL 2008. We have successfully installed the JDBC driver provided by MS. When the message reached the JDBC the following error is listed in RWB.
JDBC Message processing failed, due to Error when attempting to get processing resources: com.sap.aii.af.lib.util.concurrent.ResourcePoolException: Unable to create new pooled resource: DriverManagerException: Can not establish connection:: UnsupportedClassVersionError: Bad version number in .class file
We tried reinstalling the JDBC drivers as well , but to no avail.. .
Any idea on why this could happen ?
Regards,
Sandeep

Hi Mallikarjun,
Are you getting this error for only specific channel or all channels?
If you are getting this for all channels check your drivers of they are installed correctly....
if it is for specific channel then try increasing JDBC thread count and in restart the channel...
Regards,
Naveen

Bad version number on Mac, but not PC

I have a java applet that works fine in Windows. It works fine on Macs as long as I compile it with JDK 1.5. However, once I compile it with JDK 1.6 it loads in Windows, but it doesn't load at all in Mac OSX. I've tried compiling it with javac using -target 1.5 -source 1.5 and -target 1.4 -source 1.4 but no luck.
None of the computers I have tested on have JRE version lower than 1.5. The Mac I tested it on has JRE 1.5.16. I've also tested it on Ubuntu with JRE 1.5, which didn't work, and 1.6, which did work.
Here is the error from appletviewer in Mac:
appletviewer testprogram2.html
2008-10-16 16:17:22.269 appletviewer[436:10b] _CFGetHostUUIDString: unable to determine UUID for host. Error: 35
2008-10-16 16:17:22.546 appletviewer[436:e13] _CFGetHostUUIDString: unable to determine UUID for host. Error: 35
2008-10-16 16:17:22.812 appletviewer[436:613] _CFGetHostUUIDString: unable to determine UUID for host. Error: 35
Warning: Can't read AppletViewer properties file: /Users/miahx/.hotjava/properties Using defaults.
java.lang.UnsupportedClassVersionError: Bad version number in .class file
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:675)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at sun.applet.AppletClassLoader.findClass(AppletClassLoader.java:177)
at java.lang.ClassLoader.loadClass(ClassLoader.java:316)
at sun.applet.AppletClassLoader.loadClass(AppletClassLoader.java:119)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at sun.applet.AppletClassLoader.loadCode(AppletClassLoader.java:605)
at sun.applet.AppletPanel.createApplet(AppletPanel.java:723)
at sun.applet.AppletPanel.runLoader(AppletPanel.java:652)
at sun.applet.AppletPanel.run(AppletPanel.java:326)
at java.lang.Thread.run(Thread.java:613)
It looks like there is still a version compatibility problem, but from researching this error, just adding the -target and -source java versions when compiling should fix it. Maybe I'm going about this all wrong?
Any ideas?
Edited by: nikkorizz on Oct 16, 2008 2:23 PM
Edited by: nikkorizz on Oct 16, 2008 2:52 PM

The above workarounds don't work for me on Windows, the only thing that has worked for me is to set the prefs to tabbed whilst the script is running.
function tabInterface(onOff) {
if(onOff == undefined) onOff=true;
    var desc19 = new ActionDescriptor();
        var ref8 = new ActionReference();
        ref8.putProperty( charIDToTypeID('Prpr'), stringIDToTypeID('interfacePrefs') );
        ref8.putEnumerated( charIDToTypeID('capp'), charIDToTypeID('Ordn'), charIDToTypeID('Trgt') );
    desc19.putReference( charIDToTypeID('null'), ref8 );
        var desc20 = new ActionDescriptor();
        desc20.putBoolean( charIDToTypeID('EGst'), true );
        desc20.putBoolean( stringIDToTypeID('openNewDocsAsTabs'), onOff );
    desc19.putObject( charIDToTypeID('T   '), stringIDToTypeID('interfacePrefs'), desc20 );
    executeAction( charIDToTypeID('setd'), desc19, DialogModes.NO );
function isTabInterface(){
var ref = new ActionReference();
ref.putEnumerated( charIDToTypeID("capp"), charIDToTypeID("Ordn"), charIDToTypeID("Trgt") );
return executeActionGet(ref).getObjectValue(stringIDToTypeID('interfacePrefs')).getBoolean(stringIDToTypeID( 'openNewDocsAsTabs'));

[svn:bz-trunk] 17299: BLZ-555: Bad version number in . class when starting JBoss 5.x with latest BlazeDS app

Revision: 17299
Revision: 17299
Author:   [email protected]
Date:     2010-08-12 05:36:37 -0700 (Thu, 12 Aug 2010)
Log Message:
BLZ-555: Bad version number in .class when starting JBoss 5.x with latest BlazeDS app
The "testdata" package has been compiled using JDK 1.6. When you try to run on application server that uses JDK 1.5, it will give the above error. Removed this test related package from the aspectjweaver-1.6.5.jar.
Checkintests: PASS
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-555
    http://bugs.adobe.com/jira/browse/aspectjweaver-1
Modified Paths:
    blazeds/trunk/lib/spring/aspectjweaver-1.6.5.jar

andre.ramaciotti wrote:And I'm not sure if you should put that & after exec awesome. It works fine here without it.
No & after entries in .xinitrc . You've commented out the awesome entry.

How can i set the "Keep the following number of major versions" to a limit suppose 20 and then disable it from the users so that they cannot change the value?

I want to set the value of "Keep the following number of major versions" in the versiong settings of a documnet library to a limit say 20 and then disable the option from the users so that they cannot them. Is it possible thorugh some custom coding?

Hi Moumita10,
Just curious about that how the custom CSS code works in your environment if put it in the “LstSetng.aspx” page.
In my environment, it hides the "Keep the following number of major versions" setting in the “LstSetng.aspx”
page after applying the custom CSS style there.
Thanks
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

OOTB workflow gives error when user rejects in the document in publishing a major version.

Hi All,
I am using OOTB workflow with little customization with following configuration
1. Allow content approval enabled
2. Configure a workflow with following general settings true
3. Start workflow on publish of Major version only is enabled
4. workflow has following configuration enabled.
Now, when user start publishing of major version and Starts the workflow. workflow starts without any problem.
But as and when the user rejects the document it is rejected with Reject status with "Approval Status" as well as workflow status which is expected.(This is correct )
But when i look at the workflow history i can see at last line there is an Error with
An error has occurred in In [Workflow Name].
Now when user check out and check in item again and try to publish with Major version again. it gives errors that the previous version is still running.
I have trace a lot and also test with original OOTB workflow itself. it is behaving the same.
As per my findings there is problem in "Completion condition of this task process" the end task process is not being executed correctly.
I tried to end the task process with End the task process action but it is still not working.
I need some help in this issue as users are facing problems in case of rejection. I hope some one has the solution for the same.
Two things i have noticed are
1. My MS office 2010 professional plus is expired as i was using trial version
2. I have made stop inheriting tasks permission and remove all default groups as i have settings in workflow "Only allow task reception and process owner to read and edit workflow task"
3. Earlier i had also installed "Sharepoint 2010 April 2012 updates". i had also observed that (installing Sharepoint 2010 April 2012 updates) before that if user has selected "Automatically rejects the document if any participant rejected". it ends
with "rejected" status. At present it remains in inprogress and not stops with rejected status.
Can any one give me a hint what should be the problem ? Is it a problem with latest Sharepoint 2010 April 2012 updates ?
Thanks,
S. M. MANIYAR

I have done following testing.
1. The server in which i have not installed sharepoint 2010 April 2012 updates the above scenario is working fine without any problem
2. I have also observed following logs of error in server where April 2012 updates is installed.
8/28/2012 03:51:41.33 w3wp.exe (0x0F08)                       0x0A00 SharePoint Foundation
Workflow Infrastructure       88xr Unexpected WinWF Internal Error, terminating workflow Id# 8bf7fef1-c92e-4b22-a16f-480425d3adc6
08/28/2012 03:51:41.33 w3wp.exe (0x0F08)                       0x0A00 SharePoint Foundation
Workflow Infrastructure       98d4 Unexpected System.InvalidOperationException:
CompositeActivity cannot transition to 'Closed' status when there are active child context still exist for child activity.     at System.Workflow.ComponentModel.Activity.MarkClosed()     at System.Workflow.ComponentModel.ActivityExecutionContext.CloseActivity()
at Microsoft.Office.Workflow.Actions.OfficeTask.FinalClose(Object sender, EventArgs eventArgs)     at System.Workflow.ComponentModel.ActivityExecutorDelegateInfo`1.ActivityExecutorDelegateOperation.Run(IWorkflowCoreRuntime workflowCoreRuntime)
at System.Workflow.Runtime.Scheduler.Run()
Following are last two lines of workflow history.
S. M. MANIYAR

What is this error java.sql.SQLException: Bad format for number ?

Dear All,
I am reading few values from database. Then I get this error "MyError:Error : java.sql.SQLException: Bad format for number 'Sarawak' in column 6. " So what is this error referring to. I have checked the database column and its value fits according the data type. Any hints please?

I have checked the database column and its value fits according the data type.Check again. Then check again. Keep checking until you find your error. You are trying to read a string containing "Sarawak" as a number. You have "getInt(6)" or other numeric type, and the 6th column in the select statement is not numeric.

Bad major version number error

Similar Messages

Maybe you are looking for