Error IWAE0037E when migrating mid-sized WebLogic 8.1 project

Hi guys,
I am working on a project to upgrade legacy WebLogic 8.1.5 application into Workshop 9.2.2 using the migration tool. I am getting the following error message when trying to compile the migrated EJB entity bean codes. No warnings were reported during the upgrade process. I tried searching in Dev2Dev for IWAE0037E but no results were returned. Please let me know if you have encountered similar issues and any pointers on how to resolve them. Thanks in advance. :^O
Error Message:
IWAE0037E The interfaces of the linked enterprise bean WorkGroupBean do not match those in EJB ref ejb/WorkGroupBean in module EJB.jar.
The error points to the application.xml generated by WebLogic 8.1.5.
This is the original EJBgen annotations and the import wizard inserted annotations.
* @ejbgen:entity default-transaction="Mandatory"
*   ejb-name = "WorkGroupBean"
*   data-source-name="ds.CommonDS"
*   table-name = "WORKGROUP"
*   prim-key-class = "java.lang.Integer"
* @ejbgen:jndi-name
*   local="ejb.WorkGroupLocal"
* @ejbgen:file-generation local-class = "true" local-class-name="WorkGroupLocal" local-home = "true" local-home-name="WorkGroupLocalHome" remote-class="false" remote-class-name="WorkGroup" remote-home="false" remote-home-name="WorkGroupHome" value-class = "false" value-class-name = "WorkGroupValue" pk-class = "true"
* @ejbgen:finder ejb-ql="SELECT OBJECT(o) from WorkGroupBean as o" generate-on="Local" signature="Collection findAllWorkgroupBeans()"
* @ejbgen:finder ejb-ql="SELECT OBJECT(o) from WorkGroupBean as o where o.wkgName = ?1" generate-on="Local" signature="Collection findWkgId (java.lang.String gParamValue)"
@Entity(defaultTransaction = Constants.TransactionAttribute.MANDATORY,
        ejbName = "WorkGroupBean",
        dataSourceName = "ds.CommonDS",
        tableName = "WORKGROUP",
        primKeyClass = "Integer")
@FileGeneration(localClass = Constants.Bool.TRUE,
                localClassName = "WorkGroupLocal",
                localHome = Constants.Bool.TRUE,
                localHomeName = "WorkGroupLocalHome",
                remoteClass = Constants.Bool.FALSE,
                remoteClassName = "WorkGroup",
                remoteHome = Constants.Bool.FALSE,
                remoteHomeName = "WorkGroupHome",
                valueClass = Constants.Bool.FALSE,
                valueClassName = "WorkGroupValue",
                pkClass = Constants.Bool.TRUE)
@Finders({
    @Finder(ejbQl = "SELECT OBJECT(o) from WorkGroupBean as o",
            generateOn = Finder.GenerateOn.LOCAL,
            signature = "Collection findAllWorkgroupBeans()"),
    @Finder(ejbQl = "SELECT OBJECT(o) from WorkGroupBean as o where o.wkgName = ?1",
            generateOn = Finder.GenerateOn.LOCAL,
            signature = "Collection findWkgId (java.lang.String gParamValue)")
@JndiName(local = "ejb.WorkGroupLocal")
@WeblogicCompatibility(entityAlwaysUsesTransaction = Constants.Bool.TRUE)

Hi Vincent
I found couple of support cases where the same error happened because of CMR in EJB or due to the way you import your ejb project for upgrade.
Could you please open a support case at http://support.bea.com and an engineer would be able to look at your application and help you with it?
Vimala-

Similar Messages

  • Permissions error messages when migrating presets/preferences (Mac)

    When the program starts it asks if I want to take the preferences from CS5.1 and migrate to 6 but when I say yes it gives me all kinds of error messages that the files are locked and when I quit it says it can't say my preferences
    Would you like to migrate presets from the following versions?
    Line: 212 - An error occurred when migrating the preset from...
    ~/Library/Preferences/Adobe Photoshop CS5.1 Settings/WorkSpaces/KD
    to...
    ~/Library/Preferences/Adobe Photoshop CS6 Settings/WorkSpaces/KD
    Line: 215 - An error occurred when migrating the preset from...KD
    Administrative privileges are required to migrate these presets.
    error messages - Line: 215 - An error occurred when migrating the preset from...Keith
    When quiting PS - error message - Could not save Preferences because the file is locked, you do not have necessary access permissions, or another program is using the file. Use the ‘Get Info’ command in the Finder to ensure the file is unlocked and you have permission to access the file. If the problem persists, save the document to a different file or duplicate it in the Finder.

    I'm sure a lot of work went into this feature, but...
    Automated upgrades are always highly called-for but in practical terms almost never good to do.
    Trying to save a little time in setting a brand new application up seems a little silly, given that it's not a given that all your preferences and settings from the old version will be directly applicable to the new version, and an automated transfer could copy some problems latent in your old settings to the new version.
    Why not just install the new version afresh, then go through and review all the settings and make appropriate choices?  You need to get familiar with the new version anyway.
    Then, if later you find out something's missing or seems different, you can always fire up the old version and note or save the settings and make the same settings in the new version.
    This is more years of experience than I care to admit talking.
    -Noel

  • Why do I get an error message when attempting to download music into a project in Ellements 13?

    Why do I get an error message when attempting to download music into a project in Ellements 13?

    cornman30
    What computer operating system?
    And, where is the music coming from, iTunes? If so, that is a known problem with Premiere Elements (just about any version).
    The answer has been to convert the iTunes music to the wav version in iTunes.
    The following is the iTunes' document how to.
    iTunes: How to convert a song to a different file format - Apple Support
    Any questions, please do not hesitate to ask.
    If other than above, please supply more details to help us help you.
    Thank you.
    ATR

  • Error messages when I compile a Visual C++ 2010 project that includes the Atlcomcli.h file

    Hello,
    I am getting error messages when I compile a Visual C++ 2010 project that includes the Atlcomcli.h file.
    The error messages are:
    Error    1    error C2338: CVarTypeInfo< char > cannot be compiled with /J or _CHAR_UNSIGNED flag enabled    c:\program files\microsoft visual studio 10.0\vc\atlmfc\include\atlcomcli.h
    Search and found link to download hotfix KB982517. But no download available.
    https://connect.microsoft.com/VisualStudio/feedback/details/613888/i-would-like-to-receive-hotfix-kb982517-or-make-this-available-in-the-downloads-section
    Please help me to resolve this issue.
    Thanks,
    Gagan

    I would have to ask: why are you using _CHAR_UNSIGNED? Is this really necessary? I have to admit that the fact that by default char in C++ is signed is an annoying fact, but most of us have just gotten used to it.
    Have you tried the workaround
    #pragma push_macro("ATLSTATIC_ASSERT")
    #undef ATLSTATIC_ASSERT
    #define ATLSTATIC_ASSERT(x,y)
    #include <atlcomcli.h>
    #undef ATLSTATIC_ASSERT
    #pragma pop_macro("ATLSTATIC_ASSERT")
    that is described in the link
    https://support.microsoft.com/kb/982517?wa=wsignin1.0
    David Wilkinson | Visual C++ MVP

  • Getting error msg when trying to run 'weblogic.DDConverter', need help

    I'm getting the following error when I try to run the 'weblogic.DDConverter' program to convert a deployment descriptor for an EAR file currently running under WLS 8.1 (that needs to be migrated to WLS 9.2):
    [DDConverter] START Converting EAR CDMS.ear
    Exception in thread "main" javax.xml.stream.FactoryConfigurationError: Provider
    javax.xml.stream.XMLInputFactory could not be instantiated: java.lang.Instantiat
    ionException
    at javax.xml.stream.XMLInputFactory.newInstance(Unknown Source)
    at weblogic.application.descriptor.BasicMunger2.<clinit>(BasicMunger2.ja
    va:76)
    at weblogic.application.ApplicationDescriptor$MyApplicationDescriptor.cr
    eateXMLStreamReader(ApplicationDescriptor.java:433)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescr
    iptorBean(AbstractDescriptorLoader2.java:369)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescrip
    torBeanWithoutPlan(AbstractDescriptorLoader2.java:720)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescrip
    torBean(AbstractDescriptorLoader2.java:729)
    at weblogic.application.ApplicationDescriptor.getApplicationDescriptor(A
    pplicationDescriptor.java:277)
    at weblogic.application.ddconvert.EarConverter.convertDDs(EarConverter.j
    ava:66)
    at weblogic.application.ddconvert.DDConverter.runBody(DDConverter.java:1
    57)
    at weblogic.utils.compiler.Tool.run(Tool.java:158)
    at weblogic.utils.compiler.Tool.run(Tool.java:115)
    at weblogic.application.ddconvert.DDConverter.main(DDConverter.java:177)
    at weblogic.DDConverter.main(DDConverter.java:10)
    Any ideas as to how to resolve this?
    Edited by aroc725 at 09/25/2007 1:19 PM

    Those slashes in the first line of the error message suggest to me that maybe you referred to a class incorrectly in your source code.

  • How to deal with security when migrating application from weblogic 5.1 to weblogic 6.1?

    Dear All,
    I have one statement int weblogic 5.1 weblogic.propertis as follow,
    weblogic.security.realmClass=com.tbcn.security.realm.TestRealm
    but after converting to weblogic 6.1 there are no corresponding statement in
    the file config.xml. And when i start the new application, error occured.
    what should I do?
    The error message is:
    <2001/8/27 am 11:33:42> <Notice> <Management> <Loading configuration file
    .\config\tbcn\config.xml
    <2001/8/27 am 11:33:49> <Emergency> <Server> <Unable to initialize the
    server: 'Fatal initializatio
    Throwable: java.lang.NullPointerException
    java.lang.NullPointerException
    at
    weblogic.security.SecurityService.initializeRealm(SecurityService.java:261)
    at
    weblogic.security.SecurityService.initialize(SecurityService.java:115)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:385)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
    at weblogic.Server.main(Server.java:35)
    '>
    The WebLogic Server did not start up properly.
    Exception raised: java.lang.NullPointerException
    java.lang.NullPointerException
    at
    weblogic.security.SecurityService.initializeRealm(SecurityService.java:261)
    at
    weblogic.security.SecurityService.initialize(SecurityService.java:115)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:385)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception

    Dear Satya,
    My weblogic propertis file as follow,
    # CORE PROPERTIES
    # You should set these before you start the WebLogic Server the first time.
    # If you need more instructions on individual properties in this
    # section, check the same section in the Optional Properties, where
    # we've left the long explanations. Or, better yet, go to our
    # website and read all about properties, at:
    # http://www.weblogic.com/docs51/admindocs/properties.html
    # CORE SYSTEM PROPERTIES
    # TCP/IP port number at which the WebLogic Server listens for connections
    weblogic.system.listenPort=7001
    # CORE SECURITY-RELATED PROPERTIES
    # Read important information about security at:
    # http://www.weblogic.com/docs51/admindocs/properties.html
    # REQUIRED: The system password MUST be set in order to start the
    # WebLogic Server. This password is case-sensitive, at least 8 characters.
    # The username for the privileged user is ALWAYS "system".
    # This username and password also includes httpd access (see
    # HTTPD properties below).
    weblogic.password.system=12345678
    # RECOMMEND Set to 'everyone' if HTTPD is enabled
    weblogic.allow.execute.weblogic.servlet=everyone
    # Set individual ACLs to restrict access to HTTP-related resources,
    # such as the Administration servlets.
    # To make your own servlets generally available, follow this
    # pattern (provide a weblogic.allow.execute) for your packages and
    # set ACLs as appropriate.
    # CORE SECURITY-RELATED PROPERTIES FOR SSL
    # Read important information about SSL at:
    # http://www.weblogic.com/docs51/classdocs/API_secure.html
    # Enable SSL
    # (default if property not defined is false)
    weblogic.security.ssl.enable=true
    # SSL listen port
    weblogic.system.SSLListenPort=7002
    # Servlets for SSL
    # Authentication servlet for creating tokens for applets
    weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationS
    ervlet
    # Limits number of unclaimed stored tokens
    weblogic.security.certificateCacheSize=3
    # Capture CA root of client servlet
    weblogic.httpd.register.AdminCaptureRootCA=admin.AdminCaptureRootCA
    # Certificates for SSL
    # Name of acceptable CA roots
    # For client authentication change value to a valid .pem file
    #weblogic.security.clientRootCA=SecureServerCA.pem
    # Server certificates for SSL
    weblogic.security.certificate.server=democert.pem
    weblogic.security.key.server=demokey.pem
    weblogic.security.certificate.authority=ca.pem
    # registration for certificate generator servlet
    weblogic.httpd.register.Certificate=utils.certificate
    weblogic.allow.execute.weblogic.servlet.Certificate=system
    # CORE HTTPD ADMINISTRATIVE PROPERTIES
    # True permits the HTTPD to run (default)
    # Uncomment this property to disable HTTPD
    #weblogic.httpd.enable=false
    # If authentication is required, add username/password for each user
    # who will be included in an ACL, as in this commented-out example:
    #weblogic.password.peter=#8gjsL4*
    # SYSTEM PROPERTIES
    # System properties in this section are set to system defaults
    # Performance pack. The shared library must be accessible from your
    # PATH (NT) or from your shared library path (UNIX; the name of the
    # variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
    weblogic.system.nativeIO.enable=true
    # Outputs logging information to the console as well as to the log file
    weblogic.system.enableConsole=true
    # Sets the directory or URL for the WebLogic Admin help pages
    # The help pages are shipped in the "docs/adminhelp" directory, in the
    # default document root in public_html
    weblogic.system.helpPageURL=/weblogic/myserver/public_html/docs51/adminhelp/
    # If you prefer to access the most recent help pages, you can do so online
    # by commenting out the previous property and uncommenting this one:
    #weblogic.system.helpPageURL=http://www.weblogic.com/docs51/adminhelp/
    # Properties for tuning the server's performance
    # Number of WebLogic Server execute threads.
    weblogic.system.executeThreadCount=15
    # Other optional system properties
    # Limits size of weblogic.log (in K) and versions old log
    weblogic.system.maxLogFileSize=1024
    # Adjust minimum length of password
    weblogic.system.minPasswordLen=8
    # UNIX only: If running on port 80 on UNIX, enable the setUID program
    #weblogic.system.enableSetUID=false
    # UNIX only: Unprivileged user to setUID to after starting up
    # WebLogic Server on port 80
    #weblogic.system.nonPrivUser=nobody
    # CLUSTER-SPECIFIC PROPERTIES
    # Cluster-specific properties in this section are set to system defaults.
    # CLUSTER USERS: Note that ALL Cluster-specific properties should be set
    # in the per-cluster properties file ONLY.
    # Time-to-live (number of hops) for the cluster's multicast messages
    # (default 1, range 1-255).
    #weblogic.cluster.multicastTTL=1
    # Sets the load-balancing algorithm to be used between
    # replicated services if none is specified. If not specified,
    # round-robin is used.
    #weblogic.cluster.defaultLoadAlgorithm=round-robin
    # SERVER-SPECIFIC CLUSTER PROPERTIES
    # Cluster-related properties in this section are set to system defaults.
    # CLUSTER USERS: Note that these server-specific cluster-related properties
    # should be set in the per-server properties file ONLY.
    # Sets the weight of the individual server for the weight-based
    load-balancing.
    # Range is 0 - 100.
    # Larger numbers increase the amount of traffic routed to this server.
    #weblogic.system.weight=100
    # SYSTEM STARTUP FILES - Examples
    # CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
    # objects should be registered in the per-server properties file.
    # All other startup classes should be registered in the per-cluster
    # properties file.
    # For more info on writing and using startup file, see the
    # Developers Guide "Writing a WebLogic Client application," at
    # http://www.weblogic.com/docs51/classdocs/API_t3.html
    # Register a startup class by giving it a virtual name and
    # supplying its full pathname.
    #weblogic.system.startupClass.[virtual_name]=[full_pathname]
    # Add arguments for the startup class
    #weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
    # This example shows the entry for examples/t3client/StartupQuery.java
    #weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
    #weblogic.system.startupArgs.doquery=\
    # query=select * from emp,\
    # db=jdbc:weblogic:pool:demoPool
    # SYSTEM SHUTDOWN FILES - Examples
    # For more info on writing and using shutdown file, see the
    # Developers Guide "Writing a WebLogic Client application," at
    # http://www.weblogic.com/docs51/classdocs/API_t3.html
    # Register a shutdown class by giving it a virtual name and
    # supplying its full pathname.
    #weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
    # Add arguments for the shutdown class
    #weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
    # This example shows the entry for examples/t3client/ShutdownTest.java
    #weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
    #weblogic.system.shutdownArgs.ShutdownTest=\
    # outfile=c:/temp/shutdown.log
    # SECURITY-RELATED PROPERTIES FOR WORKSPACES
    # For backward compatibility, the following entries disable Access
    # Control on Workspaces
    weblogic.allow.read.weblogic.workspace=everyone
    weblogic.allow.write.weblogic.workspace=everyone
    # JOLT FOR WEBLOGIC PROPERTIES
    # These properties configure a BEA Jolt connection pool for use with
    # the simpapp and bankapp examples, and register a servlet for use with
    # with the simpapp example. The default server address provided here
    # points to a public TUXEDO server that is hosted by BEA for use with
    # this example.
    # Servlet registration for simpapp example:
    #weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServle
    t
    # Pool creation and cleanup
    # note this example is set up to work with the public
    # demo TUXEDO server available from BEA's website:
    #weblogic.system.startupClass.demojoltpoolStart=\
    # bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
    #weblogic.system.startupArgs.demojoltpoolStart=\
    # poolname=demojoltpool,\
    # appaddrlist=//beademo1.beasys.com:8000,\
    # failoverlist=//beademo1.beasys.com:8000,\
    # minpoolsize=1,\
    # maxpoolsize=3
    #weblogic.system.shutdownClass.demojoltpoolStop=\
    # bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
    #weblogic.system.shutdownArgs.demojoltpoolStop=\
    # poolname=demojoltpool
    # WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
    # The registrations enable a BEA IIOP connection pool and
    # register servlets for use with the simpapp and university examples.
    # Configure for your environment and uncomment to use.
    # Uncommenting these properties requires WebLogic Enterprise Connectivity
    # and an operating WebLogic Enterprise Server.
    # Servlet registration for simpapp servlet example
    #weblogic.httpd.register.SimpappServlet=\
    # examples.wlec.servlets.simpapp.SimpappServlet
    #weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
    # Servlet registration for simpapp EJB example
    # (You'll need to add the wlec_ejb_simpapp.jar to the
    # weblogic.ejb.deploy property in this file.)
    #weblogic.httpd.register.ejbSimpappServlet=\
    # examples.wlec.ejb.simpapp.ejbSimpappServlet
    #weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
    # Pool creation and cleanup for the simpapp example
    #weblogic.CORBA.connectionPool.simplepool=\
    # appaddrlist=//wlehost:2468,\
    # failoverlist=//wlehost:2468,\
    # minpoolsize=2,\
    # maxpoolsize=3,\
    # username=wleuser,\
    # userrole=developer,\
    # domainname=simpapp
    # Servlet registration for university Servlet example:
    #weblogic.httpd.register.UniversityServlet=\
    # examples.wlec.servlets.university.UniversityServlet
    #weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
    # Pool creation and cleanup for the University example:
    #weblogic.CORBA.connectionPool.Univpool=\
    # appaddrlist=//wlehost:2498,\
    # failoverlist=//wlehost:2498,\
    # minpoolsize=2,\
    # maxpoolsize=3,\
    # username=wleuser,\
    # userrole=developer,\
    # apppassword=wlepassword,\
    # domainname=university
    # WEBLOGIC FILE PROPERTIES
    # Maps a volume name to a path, for client file read/write
    #weblogic.io.fileSystem.[volumeName]=[fullPathName]
    # WEBLOGIC JMS DEMO PROPERTIES
    # CLUSTER USERS: Note that ALL JMS deployment should be done in the
    # per-cluster properties file ONLY.
    # You set up a JDBC connection pool if you want persistent messages
    # (including durable subscriptions). To use JMS and EJBs in the same
    # transaction, both must use the same JDBC connection pool. Uncomment
    # the following property to use the default JDBC connection pool
    # 'demo', which is defined in the Demo connection pool section of this file.
    #weblogic.jms.connectionPool=demoPool
    # The JMS Webshare example demonstrates how the ClientID for a
    # durable subscriber is configured in the connection factory:
    #weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
    #weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
    #weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
    #weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
    # The JMS trader example shows how to use JMS with an EJB. In addition
    # to uncommenting the following properties, you must also set up and
    # deploy the EJB example examples.ejb.basic.statelessSession.Trader in
    # ejb_basic_statelessSession.jar to try out this JMS example:
    #weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
    #weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
    #weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
    #weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
    # Registers the underlying servlet
    #weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
    # These properties are used with the ServerReceive JMS example,
    # which demonstrates how to establish a JMS message consumer
    # in a startup class:
    #weblogic.system.startupClass.serverReceive=\
    # examples.jms.startup.ServerReceive
    #weblogic.system.startupArgs.serverReceive=\
    # connectionFactory=javax.jms.TopicConnectionFactory,\
    # topic=javax.jms.exampleTopic
    # These properties are used with the PoolReceive JMS example,
    # which demonstrates how to establish a pool of JMS message consumers
    # in a startup class:
    #weblogic.system.startupClass.poolReceive=\
    # examples.jms.startup.PoolReceive
    #weblogic.system.startupArgs.poolReceive=\
    # connectionFactory=javax.jms.TopicConnectionFactory,\
    # topic=javax.jms.exampleTopic
    #weblogic.allow.create.weblogic.jms.ServerSessionPool=everyone
    # WEBLOGIC RMI DEMO PROPERTIES
    # CLUSTER USERS: Note that pinned RMI objects should be registered
    # in the per-server properties file ONLY. All other RMI startup
    # classes should be registered in the per-cluster properties file.
    # Remote classes registered at startup after the pattern:
    #weblogic.system.startupClass.[virtualName]=[fullPackageName]
    # These examples can be compiled to see RMI in action. Uncomment to use:
    #weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
    #weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
    #weblogic.system.startupClass.stock=examples.rmi.stock.StockServer
    # WEBLOGIC EJB DEMO PROPERTIES
    # CLUSTER USERS: Note that ALL EJB deployment should be done in the
    # per-cluster properties file ONLY.
    # See WebLogic Demo Connection Pool below for a connection pool
    # to use with these examples.
    # Deploys EJBeans. Uncomment the appropriate lines below and
    # modify DBMS-related info and paths to match your particular installation:
    # TBCN EJB PROPERTIES
    weblogic.ejb.deploy=\
    C:/weblogic/myserver/AccountSB.jar, \
    C:/weblogic/myserver/AddressEntryDet.jar, \
    C:/weblogic/myserver/AddressEntry.jar, \
    C:/weblogic/myserver/Affiliate.jar, \
    C:/weblogic/myserver/ContactPerson.jar, \
    C:/weblogic/myserver/ContactSB.jar, \
    C:/weblogic/myserver/Factory.jar, \
    C:/weblogic/myserver/FactorySups.jar, \
    c:/weblogic/myserver/LoginUsers.jar, \
    c:/weblogic/myserver/Member.jar, \
    c:/weblogic/myserver/MemberQuotaUsage.jar,\
    c:/weblogic/myserver/MemberToCategory.jar,\
    c:/weblogic/myserver/Organization.jar, \
    c:/weblogic/myserver/Person.jar, \
    c:/weblogic/myserver/QuotaType.jar,\
    c:/weblogic/myserver/Registration.jar, \
    c:/weblogic/myserver/TempAccounts.jar, \
    c:/weblogic/myserver/TempDomain.jar, \
    c:/weblogic/myserver/UserAccount.jar, \
    c:/weblogic/myserver/UserRole.jar, \
    c:/weblogic/myserver/BuyerProducts.jar, \
    c:/weblogic/myserver/Catalog.jar, \
    c:/weblogic/myserver/Categories.jar, \
    c:/weblogic/myserver/CategoryToCategory.jar, \
    c:/weblogic/myserver/CountryToCategory.jar, \
    c:/weblogic/myserver/InvitedMember.jar, \
    c:/weblogic/myserver/ProductOrigin.jar, \
    c:/weblogic/myserver/ProductOtherFee.jar,\
    c:/weblogic/myserver/ProductSups.jar, \
    c:/weblogic/myserver/Products.jar,\
    c:/weblogic/myserver/ProductToCategory.jar, \
    c:/weblogic/myserver/SecondaryQcEntry.jar, \
    c:/weblogic/myserver/CodeClass.jar,\
    c:/weblogic/myserver/ConfirmationSB.jar, \
    c:/weblogic/myserver/PurchasedPackage.jar,\
    c:/weblogic/myserver/RejectReasonCode.jar, \
    c:/weblogic/myserver/ServiceOrder.jar,\
    c:/weblogic/myserver/ServiceOrderLog.jar,\
    c:/weblogic/myserver/ServiceOrderState.jar,\
    c:/weblogic/myserver/ServiceOrderType.jar,\
    c:/weblogic/myserver/ServicePackageDetails.jar, \
    c:/weblogic/myserver/ServicePackage.jar, \
    c:/weblogic/myserver/ServicePayment.jar, \
    c:/weblogic/myserver/ServiceReqSB.jar, \
    c:/weblogic/myserver/TAM.jar, \
    c:/weblogic/myserver/SubscriptionEB.jar, \
    c:/weblogic/myserver/PostingCategoryEB.jar, \
    c:/weblogic/myserver/PostingBrowsedEB.jar, \
    c:/weblogic/myserver/PostingInfoEB.jar, \
    c:/weblogic/myserver/TransactionLogEB.jar, \
    c:/weblogic/myserver/PostingSB.jar
    #weblogic.ejb.deploy=\
    # d:/weblogic/myserver/ejb_basic_beanManaged.jar, \
    # d:/weblogic/myserver/ejb_basic_containerManaged.jar, \
    # d:/weblogic/myserver/ejb_basic_statefulSession.jar, \
    # d:/weblogic/myserver/ejb_basic_statelessSession.jar, \
    # d:/weblogic/myserver/ejb_extensions_finderEnumeration.jar, \
    # d:/weblogic/myserver/ejb_extensions_readMostly.jar, \
    # d:/weblogic/myserver/ejb_subclass.jar, \
    # d:/weblogic/myserver/jolt_ejb_bankapp.jar
    # Servlet used by the EJB basic beanManaged example
    # Uncomment to use:
    weblogic.httpd.register.beanManaged=\
    examples.ejb.basic.beanManaged.Servlet
    # Add a list of users (set the password with
    weblogic.password.[username]=XXX)
    # to set an ACL for this servlet:
    #weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
    #weblogic.password.user1=user1Password
    #weblogic.password.user2=user2Password
    # WEBLOGIC XML DEMO PROPERTIES
    # These properties are required to run the XML examples.
    # Uncomment to use.
    # CLUSTER USERS: Note that ALL servlets should be set up
    # in the per-cluster properties file ONLY.
    #weblogic.httpd.register.StockServlet=examples.xml.http.StockServlet
    # BizTalk example properties
    #weblogic.jms.queue.tradeIncoming=biztalk.jms.tradeIncoming
    #weblogic.jms.queue.tradeError=biztalk.jms.tradeError
    #weblogic.httpd.register.BizTalkServer=examples.xml.biztalk.BizHttpProtocolA
    dapter
    #weblogic.httpd.initArgs.BizTalkServer=bizQueue=biztalk.jms.tradeIncoming
    # WEBLOGIC ZAC DEMO PROPERTIES
    # These registrations enable the ZAC Publish Wizard.
    weblogic.zac.enable=true
    # Set the publish root for a WebLogic Server. Edit and
    # uncomment to use.
    #weblogic.zac.publishRoot=d:/weblogic/zac
    # Set an ACL for each package you publish. The [name] is
    # the "Package name" you assign in the ZAC Publish Wizard.
    # Publish a package, edit this property, and uncomment to use.
    #weblogic.allow.read.weblogic.zac.[name]=[user list]
    #weblogic.allow.write.weblogic.zac.[name]=system
    # HTTPD ADMINISTRATIVE PROPERTIES
    # Enables logging of HTTPD info in common log format and
    # sets the log file name (default is "access.log" in "myserver")
    weblogic.httpd.enableLogFile=true
    weblogic.httpd.logFileName=access.log
    # Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
    weblogic.httpd.enableEvents=false
    # Enables HTTP sessions
    weblogic.httpd.session.enable=true
    # Sets an optional cookie name. The default name is "WebLogicSession".
    # Prior to version 4.0, the default was "TengahSession". To make
    # this backward compatible with cookies generated from previous
    # installations, you should set this property to "TengahSession".
    # Uncomment this line and set this to any string of your choice,
    # or comment out this property to use the default.
    #weblogic.httpd.session.cookie.name=WebLogicSession
    # MIME types
    weblogic.httpd.mimeType.text/html=html,htm
    weblogic.httpd.mimeType.image/gif=gif
    weblogic.httpd.mimeType.image/jpeg=jpeg,jpg
    weblogic.httpd.mimeType.application/pdf=pdf
    weblogic.httpd.mimeType.application/zip=zip
    weblogic.httpd.mimeType.application/x-java-vm=class
    weblogic.httpd.mimeType.application/x-java-archive=jar
    weblogic.httpd.mimeType.application/x-java-serialized-object=ser
    weblogic.httpd.mimeType.application/octet-stream=exe
    weblogic.httpd.mimeType.text/vnd.wap.wml=wml
    weblogic.httpd.mimeType.text/vnd.wap.wmlscript=wmls
    weblogic.httpd.mimeType.application/vnd.wap.wmlc=wmlc
    weblogic.httpd.mimeType.application/vnd.wap.wmlscriptc=wmlsc
    weblogic.httpd.mimeType.image/vnd.wap.wbmp=wbmp
    # In seconds, the keep-alive for HTTP and HTTPS requests
    weblogic.httpd.http.keepAliveSecs=60
    weblogic.httpd.https.keepAliveSecs=120
    # WEBLOGIC JDBC DRIVER PROPERTIES
    # Enables JDBC driver logging and sets the file name for the log
    # The weblogic.jdbc.logFile is placed in the per-server
    # directory (default is "myserver")
    weblogic.jdbc.enableLogFile=false
    weblogic.jdbc.logFileName=jdbc.log
    # WEBLOGIC JDBC CONNECTION POOL MANAGEMENT
    # CLUSTER USERS: Note that ALL JDBC connection pools should be set up
    # in the per-cluster properties file ONLY.
    # For creating JDBC connection pools. This example shows a connection
    # pool called "oraclePool" that allows 3 T3Users "guest," "joe," and "jill"
    # to use 4 JDBC connections (with a potential for up to 10 connections,
    # incremented by two at a time, with a delay of 1 second between each
    # attempt to connect to the database), to an Oracle database server called
    # "DEMO." If more than 4 connections are opened, after 15 minutes, unused
    # connections are dropped from the pool until only 4 connections remain
    open.
    # Every 10 minutes, any unused connections in the pool are tested and
    # refreshed if they are not viable.
    #weblogic.jdbc.connectionPool.oraclePool=\
    # url=jdbc:weblogic:oracle,\
    # driver=weblogic.jdbc.oci.Driver,\
    # loginDelaySecs=1,\
    # initialCapacity=4,\
    # maxCapacity=10,\
    # capacityIncrement=2,\
    # allowShrinking=true,\
    # shrinkPeriodMins=15,\
    # refreshMinutes=10,\
    # testTable=dual,\
    # props=user=SCOTT;password=tiger;server=DEMO
    # Get more details on each argument for this property in the
    # Administrators Guide on setting properties at:
    # http://www.weblogic.com/docs51/admindocs/properties.html
    # Set up ACLs for this connection pool with the following:
    weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=everyone
    # guest,joe,jill
    #weblogic.allow.reset.weblogic.jdbc.connectionPool.oraclePool=\
    # joe,jill
    #weblogic.allow.shrink.weblogic.jdbc.connectionPool.oraclePool=\
    # joe,jill
    # This property is an ACL that specifies the users who can
    # create dynamic connection pools:
    #weblogic.jdbc.connectionPoolcreate.admin=joe,jill
    # Read more about setting up and using connection pools in the
    # developers guide for WebLogic JDBC at:
    # http://www.weblogic.com/docs51/classdocs/API_jdbct3.html#T5a
    # TBCN JDBC CONNECTION POOL MANAGEMENT
    weblogic.jdbc.connectionPool.oraclePool=\
    url=jdbc:oracle:thin:@202.109.102.151:1521:tbcn,\
    driver=oracle.jdbc.driver.OracleDriver,\
    loginDelaySecs=1,\
    initialCapacity=2,\
    maxCapacity=10,\
    capacityIncrement=2,\
    allowShrinking=true,\
    shrinkPeriodMins=15,\
    refreshMinutes=10,\
    testTable=dual,\
    props=user=tbcn;password=ca91768
    weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=everyone
    weblogic.jdbc.TXDataSource.oracleDataSource=oraclePool
    weblogic.jdbc.DataSource.oracleReadOnlyDataSource=oraclePool
    # WEBLOGIC DEMO CONNECTION POOL PROPERTIES
    # CLUSTER USERS: Note that ALL JDBC connection pools should be set up
    # in the per-cluster properties file ONLY.
    # This connection pool uses the sample Cloudscape database shipped
    # with WebLogic. Used by the EJBean, JHTML, JSP and JMS examples.
    # Uncomment to use:
    #weblogic.jdbc.connectionPool.demoPool=\
    # url=jdbc:cloudscape:demo,\
    # driver=COM.cloudscape.core.JDBCDriver,\
    # initialCapacity=1,\
    # maxCapacity=2,\
    # capacityIncrement=1,\
    # props=user=none;password=none;server=none
    # Add a TXDataSource for the connection pool:
    #weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.demoPool=demoPool
    # Add an ACL for the connection pool:
    #weblogic.allow.reserve.weblogic.jdbc.connectionPool.demoPool=everyone
    # WEBLOGIC HTTP SERVLET PROPERTIES
    # CLUSTER USERS: Note that ALL servlets should be set up
    # in the per-cluster properties file ONLY.
    # WebLogic offers different types of servlets for various uses.
    # Classpath servlet registration
    # The ClasspathServlet is used to serve classes from
    # the system CLASSPATH. It is used by applets to load
    # classes they depend upon, and is registered against
    # the virtual name 'classes' here by default. This means
    # you should set your applet codebase to "/classes".
    # You can register multiple virtual names for this servlet.
    # Note that it can also be used to serve other
    # resources/files from the system CLASSPATH.
    # Don't confuse the ClasspathServlet with the ServletServlet. The
    # ClasspathServlet is used for serving classes for client-side Java only.
    # The ServletServlet is used to invoke unregistered servlets.
    # See the Administrators Guide "Setting up WebLogic as an HTTP server"
    # http://www.weblogic.com/docs51/admindocs/http.html#classfile for more
    info.
    weblogic.httpd.register.classes=weblogic.servlet.ClasspathServlet
    # We also set an open ACL for everyone to call the ClasspathServlet
    # so that applets work without requiring further changes.
    weblogic.allow.execute.weblogic.servlet.classes=everyone
    # File servlet registration
    # FileServlet searches below the documentRoot for the requested file
    # and serves it if found. If the requested file is a directory,
    # FileServlet will append the defaultFilename to the requested path
    # and serve that file if found.
    weblogic.httpd.register.file=weblogic.servlet.FileServlet
    weblogic.httpd.initArgs.file=defaultFilename=index.html
    weblogic.httpd.indexFiles=zh_TW/index.htm
    # ServerSideInclude servlet registration
    # SSIServlet searches below the documentRoot for the
    # requested .shtml file and serves it if found.
    weblogic.httpd.register.*.shtml=weblogic.servlet.ServerSideIncludeServlet
    # Example URL: http://localhost:7001/portside/welcome.shtml
    # for the file /weblogic/myserver/public_html/portside/welcome.shtml
    # PageCompileServlet (used by JHTML)
    # See the information below under WebLogic JHTML
    # JSPServlet (used by JSP)
    # See the information below under WebLogic JSP
    # ServletServlet registration
    # Allows unregistered servlets in the servlet classpath (see Servlet
    # reload properties below) to be r

  • Mac OS error -208 when opening MIDI files in Quicktime Pro

    Quicktime no longer plays MIDI files. it used to. now i get the Mac OS error -208 claiming the file is corrupted. but i can play the file on a PC, and other people receiving the files by email can open them (though a few other Mac owners are now also having trouble for the first time).
    this problem started about two weeks ago. i did nothing different to my machine (MacBook pro), and wonder if a background system update is to blame.
    i uninstalled Quicktime and reinstalled it. no luck. any ideas?

    here's some further clarification, provided by John Hetland, who worked out the fix:
    1. The MIDI analyzer I used is a cool freeware program midi2txt.exe from
    http://www.gnmidi.com/
    2. When I ran midi2txt with the -error switch and the name of the MIDI file,
    it said something like "Warning: 21 bytes of garbage at end of file." It
    turned out that the MIDI file was made in fixed-length records, and there
    was space left over in the last record. This situation is simply ignored by
    most players, but the current version of QuickTime apparently doesn't know
    what to do if the file is not EXACTLY the length needed for the MIDI codes.
    3. I can't give instructions for fixing the error because what I fixed was
    not any MIDI file; I fixed the program I wrote that generated the flawed
    MIDIs. But if someone should encounter this very problem in a MIDI from some
    other source, and that someone has expertise in file manipulation, one
    should look for hex 'FF2F00' in the last record and delete everything that
    follows it.

  • Error message when migrating Mail.

    I've installed Yosemite on a 5 or 6 year old iMac. When I try and open mail it starts to migrate my old data and I get this error message:
    Your Mail index has been damaged. To repair it quit Mail. Mail will repair the index the next time you open Mail.
    First off, Mail is not open. When I try and open it, it starts to migrate again and I get the same error message.
    Thanks for any help.

    I recently upgraded from OS X 10.6 to 10.10. I encountered failure identical to the above post. Here was one possible workaround
    Restore a recent backup of my computer (running 10.6) to an external drive.
    Startup my computer from the external drive.
    Upgrade to 10.7. (I suppose 10.8 or 10.9 might have worked.)
    Launch "Mail" and allow it to upgrade mail from 10.6 to 10.7. Repeat this step for each user account of the computer.
    Upgrade to 10.10.
    Launch "Mail" and allow it to upgrade mail from 10.7 to 10.10. Repeat this step for each user account of the computer.
    Thoroughly test to ensure all data is present.
    Use a cloning app such as SuperDuper, clone from the external drive to the internal drive. This will erase the internal drive, so step #7 above is critical.
    Variants of this procedure are possible. For example, this variant involving Migration Assistant also seems to work.
    Restore a recent backup of my computer (running 10.6) to an external drive.
    Startup a computer from the external drive.
    Locate a computer running 10.7. (I suppose 10.8 or 10.9 might have worked.)
    Use Migration Assistant to relocate your account(s) from the 10.6 external drive to the 10.7 computer.
    Launch "Mail" and allow it to upgrade mail from 10.6 to 10.7. Repeat this step for each user account of the computer.
    Thoroughly test to ensure all data is present.
    Startup your computer in the already upgraded 10.10.
    Delete your account(s) from 10.10. This will erase data, so step #6 above is critical.
    Use Migration Assistant to relocate your account(s) from the 10.7 computer to your 10.10 computer.
    Launch "Mail" and allow it to upgrade mail form 10.7 to 10.0. Repeat this step for each user account of the computer.
    Summation: If you want to keep "Mail", don't upgrade directly from 10.6 to 10.10. Step up with something in between. Hopefully a future patch to 10.10 will make the upgrade from 10.6 easier.
    More advanced: If you are tech savvy and know where files are stored in the Library, you can just replace many steps above with a process involving just moving the needed files. These seem to be located here in 10.6 and 10.7...
    ~/Library/Mail/
    ~/Library/Mail Downloads/
    ~/Library/Preferences/com.apple.mail.*
    Where ~ references your home folder such as Macintosh HD/Users/yourname, and where * is a wildcard for any characters.
    Tip: If you launch the Mail app, stop and restart to avoid caching issues.

  • Validation errors flash when migrating site to html 5

    Hello,
    I am in the middle of migrating my website to HTML5. My website contains a few .swf files that I've
    embedded in myt html code. When I am validation my site (at W3C) I get a few errors. I hope someone
    can help me with this problem.
    This is the code i am using:
    <object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=8,0,0,24" width="270" height="175">
    <param name="movie" value="flash/header_v8_1_orangeflower.swf?button=1" />
    <param name="quality" value="high" />
    <param name="menu" value="false" />
    </object>
    When validating i get this error:
      Line 63, Column 131: Element object is missing one or more of the following attributes: data, type.
    …ub/shockwave/cabs/flash/swflash.cab#version=8,0,0,24" width="270" height="175">

    I also recommend swfobject... but sometimes all the extra IE conditional statements that comes with version 2+ can cause problems. I like the earlier 1.5 version myself.
    Either version.... they are still both Flash detection methods. The real stregth of using Flash detection is the ability to add "Alternate content".... NOT as a mean of just placing Flash on a Web page. That can be done with just HTML <object> code.... no swfobject needed.
    The single <object> method..... Very simple and clean:
    <object data="path_to_file/file.swf" type="application/x-shockwave-flash" width="insert_width_of_movie" height="insert_height_of_movie">
      <param name="movie" value="path_to_file/file.swf">
      <param name="SomeOtherParam" value="ParamValue">
    </object>
    Edit as needed for your content
    Best wishes,
    Adninjastrator

  • Unknown error (0x1008) when migrating to cluster shared volume.

    Hi All,
    Currently have 4 HV hosts with FC IBM SAN. Each host is Hyper-V Server 2008 R2 6.1.76.01, System Center 2012 Virtual Machine Manager 3.0.6062. The SAN has been broken up into 20 LUN's, each LUN has been formatted NTFS and hosts the single VHD file for each
    of the 20 VM's.
    We have provisioned a 3TB CSV to use as a sort of staging area and are attempting to migrate each VM to this in order to consolidate and recreate the individual LUN's into another CSV.
    When attempting to perform a live storage migration we receive the following error almost instantly.
    Error (12711)
    VMM cannot complete the WMI operation on the server (DGHVS02.example.com.au.local) because of an error: [MSCluster_Resource.Name="DTHV_EXAMPLEVM03_8abc6468-ae4a-41db-bd67-d787b81a6772"] 
    Unknown error (0x1008)
    Recommended Action
    Resolve the issue and then try the operation again.
    There is nothing in the event logs on either server (VMM or HV host).
    We have also attempted to start a debug trace but the VMM event providers are missing.
    Any help would be much appreciated.

    This has been solved.
    [MSCluster_Resource.Name="DTHV_EXAMPLEVM03_8abc6468-ae4a-41db-bd67-d787b81a6772"]
    This is resource is added by DoubleTake to each VM which manages live replication to a DR site. Once replication was stopped for this VM storage migration worked.
    Hope this helps someone else.......

  • Error code when migrating pics from iPhotos to Photos

    Migrating iphotos to photos stops at 30% with error code  "An unexpected error had occurred".  HELP

    Maybe these two Apple documents will help:
    Migrating from iPhoto for iOS to Photos on iOS 8 - Apple Support
    Get help finding your Photos in iOS 8 or later - Apple Support

  • I am getting quicktime error 50 when I attempt to export a retimed project in fcpx to youtube. I mix and match retime rates. I usaully have no issues. The entire project is retimed.

    I am getting quicktime error 50 message when I try to share a project to youtube. I use retime frequently, mixing and matching rates with no issues. I am having trouble with this project. The entire project is retimed ( which  I have done before), it is four minutes and change in length. I used different rates, holds as well, and
    secondary storylines ( retimed to match the primary clip rate ). Any suggestions would be helpfull, thank you.

    I figured it out:
    FCPX does not support NTFS drives, even with Paragon NTFS working perfectly for everything else on the system.
    I guess Apple (just) assumes that nobody will, or should, be using any other filesystem than Mac with FCPX.
    I wasted hours looking for a solution, when a better error message besides a misleading "cannot allocate memory" could have been something more useful.
    Not impressed.

  • Error Message When Attempting to Open a Portfolio of Projects

    "The description cannot exceed the maximum length of 400 kilobytes"
    When I click OK it returns me to all projects again rather than just the projects in the portfolio I have selected. What is causing this?

    Hello
    The error message that is described is caused by corrupted user preferences (     Error: "The description cannot exceed the maximum length of 400 kilobytes" when opening Projects or Portfolios. (Doc ID 907406.1)) you can solve the issue by deleting them or create a new user in order to avoid the error, please refer to the following note for the solution
    How To Delete A User's Application User Preference Settings (Edit, User Preferences) If The Account Has Become Corrupted In Project Management Or Web Access (Doc ID 894279.1)

  • Error -2002 when importing quicktime movie clips into iMovie Project

    When I import QuickTime movie clips into my project, the scroll bar fills about 1/3 of the way, and then I get this message:
    Can't open file "DSCN0812.MOV"; skipping it and continuing. I CLICK "OK," and then this message appears:
    Error during import
    The file could not be imported: (-2002)
    This happens to every movie clip. Anyone have any idea what's happening here?
    Thanks!

    Paul Kirtley wrote:
    .. file "DSCN0812.MOV"..
    The file could not be imported: (-2002)
    I guess, you try to import 'moving images' from a still cam, right? these are in a codec (=mov is no format, just a container) , iM doesn't support. Use the free tool *Mpeg Streamclip* www.squared5.com to convert these files to 'dv stream' BEFORE importing to iMovie.

  • Why do I get an error message when trying to open PE 8.0 projects with PE9.0?

    I am trying to open a project in PE 9.0 that I made with PE 8.0. Each time, and with different projects, I get this error message:
    "Projects created with Adobe Premiere Pro and Adobe Premiere Elements are not compatible. Please use apropriate application to open this project."
    I have never used Adobe Premiere Pro nor is in installed on my computer! I updated my PE 8.0 with the patch that came out last year.
    My Operating System is Windows XP Pro, Service Pack  3, system specs are SATA 2 RAID 1 with dual 1 TB hard drives. 4 GB RAM. I have an Intel Core2  processor Q6600 (2.4 Ghz, 1066 FSB) with Quad Core technology and 8 MB cache, 4  GB DDR2 SDRAM at 800 MHz.
    My hard drive has been defragmented and have 779 GB or 83 percent free space.

    Can you create a test Project in PrE 9 and does that work. If so, close that Project and then Open it again in PrE 9.
    It could be as simple as your PrE 8 Projects just not Opening in PrE 9. There is often forward compatibility, but not always. It is usually best to finish Projects in the version, in which they were started.
    Good luck,
    Hunt

Maybe you are looking for