Extension of JComboBox was not serializable

I reduced my example code to a simple extension of JComboBox without any new member. After that the frame was not longer serializeable. There was a workaround for my problem but I still want to know why this exception occurs.

What's the exception that's occuring? And are you trying to serialize the JComboBox or the JFrame? I don't know much about serialization, but when you serialize an object that contains references to instances of other objects, are the references stored? Maybe when you serialize your frame, the references that it contains to the components it's holding are lost.

Similar Messages

  • Every time I install an update of itunes, I get an error message saying: "/System/Library/Extensions/WkClassicNotSeizeDriver.Kext" was not installed Correctly. Has any one had it? Can you help me?

    Every time I install an update of itunes, I get an error message saying: "/System/Library/Extensions/WkClassicNotSeizeDriver.Kext" was not installed Correctly. Has any one had it? Can you help me?

    Find out what that third party software the kext file belongs to and update or use the developers method to uninstall the third party software responsible for it.
    I suspect it's a iTunes extension perhaps?
    You also can use the manual method of Finder > Go > Computer and opening your drive, then your  System/Library/Extensions folder and looking for the file and moving it out onto the desktop, you will need to be in Admin user and use your password, then reboot to clear the random access memory. However this method doesn't remove the parent program you still need to do that.
    How to uninstall/install software on your Mac
    The kext file wasn't loaded, so it's not running, but removing it from the Extensions folder or uninstalling what put it there will solve your notification problem as that's all it appears to be.

  • I get an error message when using google search: Debug Error:[Exception... "Node was not found" code: "8" nsresult: "0x80530008 (NS_ERROR_DOM_NOT_FOUND_ERR)" location: "chrome://ffamazonhot/content/lib/Extension.debug.js Line: 366"]

    Debug Error:[Exception... "Node was not found" code: "8" nsresult: "0x80530008 (NS_ERROR_DOM_NOT_FOUND_ERR)" location: "chrome://ffamazonhot/content/lib/Extension.debug.js Line: 366"]

    Tools->Add-ons->Extensions
    At the top of the Firefox window, click on the Tools menu and select Add-ons. The Add-ons window will appear.
    In the Add-ons window, select the Extensions panel.
    Select the add-on you wish to uninstall.
    Click the Uninstall button. When prompted, click Uninstall to confirm.
    Then restart Firefox.
    Read here:
    [[Uninstalling add-ons|#How to uninstall extensions and themes|Uninstalling extensions]]

  • I get a message Debug Error:[Exception... "Node was not found" code: "8" nsresult: "0x80530008 (NS_ERROR_DOM_NOT_FOUND_ERR)" location: "chrome://ffebayhot/content/lib/Extension.debug.js Line: 366"] using Vista. I don't understand how to delete the "ebay

    Every time I try to use google for a search, I get the following error msg. Debug Error:[Exception... "Node was not found" code: "8" nsresult: "0x80530008 (NS_ERROR_DOM_NOT_FOUND_ERR)" location: "chrome://ffebayhot/content/lib/Extension.debug.js Line: 366"]. I saw the solution provided for MS XP, but not for Vista. Also, while I saw the solution, I need more explicit instructions on how to "delete the ebay extension".
    == This happened ==
    Every time Firefox opened
    == When I try to load google from Firefox, I get the error message, Debug Error:[Exception... "Node was not found" code: "8" nsresult: "0x80530008 (NS_ERROR_DOM_NOT_FOUND_ERR)" location: "chrome://ffebayhot/content/lib/Extension.debug.js Line: 366"]

    Tools->Add-ons->Extensions
    At the top of the Firefox window, click on the Tools menu and select Add-ons. The Add-ons window will appear.
    In the Add-ons window, select the Extensions panel.
    Select the add-on you wish to uninstall.
    Click the Uninstall button. When prompted, click Uninstall to confirm.
    Then restart Firefox.
    Read here:
    [[Uninstalling add-ons|#How to uninstall extensions and themes|Uninstalling extensions]]

  • I receive the message: "The extension could not be loaded because it was not properly signed."

    When I try to open the Library in Photoshop, I receive the message: "The extension could not be loaded because it was not properly signed." It worked last week, but now I get this message and the Library is completely empty in Illustrator. My Library has stuff in it and I can see it on my iPad Apps.

    I am working on a PC, using Photoshop CC 2014
    Operating System:
    Error Message:
    Settings in Photoshop > Preference > Performance:
    Type of file you were working on: No file; just opened up Photoshop to begin working
    This is the first time this has happened - I have not doe any other troubleshooting.
    Camera Raw does not apply here.
    Thanks.

  • PS show The extension could not be loaded because it was not properly signed

    When I'm open Libraries in photoshop cs2014 it's show
    The extension could not be loaded because it was not properly signed
    I'm try to reinstalled but it still error.
    How can i'm fixed this

    This is an open forum, not Adobe support... you need Adobe staff support to help
    Adobe contact information - http://helpx.adobe.com/contact.html
    -Select your product and what you need help with
    -Click on the blue box "Still need help? Contact us"

  • Extension could not be loaded because it was not properly signed

    Followed the steps on the tutorial to get an extension created in eclipse. I can export it and run it just fine, but it won't load when running from eclipse. I get the error: "extension could not be loaded because it was not properly signed." I can't seem to find where to configure this. Any help is appreciated.

    Thanks for the help. Yes that addressed the issue.
    On a side note, the tutorial I followed was the one that came with the plugin. Specifically I'm referring to the following file:
    //<eclipse_path>/plugins/com.adobe.cside.html.docs_1.0.0.201307260955/doc/getting_started/ Create_Your_Own_HTML5_Extension_In_5_Minutes.htm
    This is the HTML page for the "Create Your Own HTML5 Extension In 5 Minutes" walkthrough. It makes no mention of changing "PlayerDebugMode". I downloaded the eclipse plugin from the following link:
    http://labs.adobe.com/downloads/extensionbuilder3.html
    Is there a more up to date plugin? Where is the documentation that references changing the settings you mentionned?

  • Import-SPWeb Error - The string was not recognized as a valid DateTime. There is an unknown word starting at index 0

    Using the Export-SPWeb PowerShell command on a server to move a document library from one site colelction in a content database to another site collection in a seperate content database.
    Am using the following command:
    Export-SPWeb
    -Identity
    https://sp.bacl.net/legal/rr
    -Path
    \\bacvsspa01\backups\rr\rr.cmp
    -ItemUrl
    rr
    -IncludeVersions
    All
    -IncludeUserSecurity
    Not all documents are transferred hwoever. I get some errors like the following:
    [11/02/2014 2:21:44 PM] [ListItem] [16Jun11 17.32.09_BAC employees provid_Tom Heading.msg] Progress: Importing
    [11/02/2014 2:21:44 PM] [ListItem] [16Jun11 17.32.09_BAC employees provid_Tom Heading.msg]   Verbose: List URL: /legal/legal/rr
    [11/02/2014 2:21:44 PM] [ListItem] [16Jun11 17.32.09_BAC employees provid_Tom Heading.msg]   Error: The string was not recognized as a valid DateTime. There is an unknown word starting at index 0.
    [11/02/2014 2:21:44 PM] [ListItem] [16Jun11 17.32.09_BAC employees provid_Tom Heading.msg]   Debug:    at System.DateTime.Parse(String s, IFormatProvider provider)
       at System.Convert.ToDateTime(String value, IFormatProvider provider)
       at System.Runtime.Serialization.SerializationInfo.GetDateTime(String name)
       at Microsoft.SharePoint.Deployment.MetaInfoProperty..ctor(SerializationInfoHelper infoHelper)
       at Microsoft.SharePoint.Deployment.FileSerializer.GetMetaInfo(SerializationInfoHelper infoHelper)
       at Microsoft.SharePoint.Deployment.FileSerializer.CreateOrUpdateFile(Object fileOrListItem, SPLoggerObject loggerObject, SPWeb web, Guid id, String& fileUrl, Boolean fileExistsInDb, Boolean isFirstVersion, Boolean hasWebParts, SerializationInfoHelper
    infoHelper, SerializationInfoHelper infoHelperListitem, StreamingContext context)
       at Microsoft.SharePoint.Deployment.FileSerializer.CreateOrUpdateFileAndAssocData(Object fileOrListItem, SPLoggerObject loggerObject, SPWeb web, Guid id, String& fileUrl, Boolean fileExistsInDb, SerializationInfoHelper infoHelper, SerializationInfoHelper
    infoHelperListitem, StreamingContext context, ISurrogateSelector selector)
       at Microsoft.SharePoint.Deployment.ListItemSerializer.AddOrUpdateDoclibItem(SerializationInfoHelper infoHelper, SPListItem& listItem, SPLoggerObject loggerObject, SPWeb web, Guid newId, String& listItemServerRelativeUrl, Boolean bIsPublish,
    Boolean exists, StreamingContext context, ISurrogateSelector selector)
       at Microsoft.SharePoint.Deployment.ListItemSerializer.SetObjectData(Object obj, SerializationInfo info, StreamingContext context, ISurrogateSelector selector)
    I had a look in the .cmp file that was created (Changed extensions to .cab) and had a look at the Manifest.xml file. Relevant XML below:
    <SPObject Id="b18cc711-e5df-4ee7-9639-866e5b6613b0" ObjectType="SPFile" ParentId="1ad76e87-43e6-4cbf-a0a1-53af4975668f" ParentWebId="4be7e61f-b1c7-473f-acc3-0bae06e32024" ParentWebUrl="/legal/rr" Url="/legal/rr/rr/Employees
    giving First Aid/16Jun11 17.32.09_BAC employees provid_Tom Heading.msg">
            <File Url="rr/Employees giving First Aid/16Jun11 17.32.09_BAC employees provid_Tom Heading.msg" Id="b18cc711-e5df-4ee7-9639-866e5b6613b0" ParentWebId="4be7e61f-b1c7-473f-acc3-0bae06e32024"
    ParentWebUrl="/legal/rr" Name="16Jun11 17.32.09_BAC employees provid_Tom Heading.msg" ListItemIntId="37" ListId="020f8304-a50f-413b-be27-40d0ccc9e497" ParentId="1ad76e87-43e6-4cbf-a0a1-53af4975668f" TimeCreated="2011-11-16T07:02:00"
    TimeLastModified="2011-11-16T07:02:00" Version="1.0" CheckinComment="Loaded Using Dell Solutions for SharePoint" FileValue="00000013.dat" Author="29" ModifiedBy="24">
                <Properties>
                    <Property Name="vti_title" Type="String" Access="ReadOnly" Value="BAC employees providing first aid" />
                    <Property Name="source_item_id" Type="String" Access="ReadWrite" Value="source_item_id:1" />
                    <Property Name="vti_foldersubfolderitemcount" Type="Integer" Access="ReadOnly" Value="0" />
                    <Property Name="Attach Count" Type="String" Access="ReadWrite" Value="Attach Count:0" />
                    <Property Name="Created By" Type="Boolean" Access="ReadWrite" Value="Created By:BNE_AIR1\\jbrown" />
                    <Property Name="Importance" Type="String" Access="ReadWrite" Value="Importance:1" />
                    <Property Name="From1" Type="Time" Access="ReadWrite" Value="From1:Tom Heading" />
                    <Property Name="AttachCount" Type="String" Access="ReadWrite" Value="AttachCount:0" />
                    <Property Name="ContentTypeId" Type="String" Access="ReadWrite" Value="0x0101003699C96894FF79479322E4A235852946000530E240279BA54D8F621B39A4E09CF3"
    />
                    <Property Name="Modified By" Type="Boolean" Access="ReadWrite" Value="Modified By:BNE_AIR1\\jbrown" />
                    <Property Name="vti_folderitemcount" Type="Integer" Access="ReadOnly" Value="0" />
                    <Property Name="display_urn\:schemas-microsoft-com\:office\:office#Author" Type="String" Access="ReadWrite" Value="Jenny Brown"
    />
                    <Property Name="Document Created By" Type="Boolean" Access="ReadWrite" Value="Document Created By:BNE_AIR1\\jbrown" />
                    <Property Name="Created_x0020_By" Type="Boolean" Access="ReadWrite" Value="Created_x0020_By:BNE_AIR1\\jbrown" />
                    <Property Name="vti_cachedtitle" Type="String" Access="ReadOnly" Value="BAC employees providing first aid" />
                    <Property Name="Modified_x0020_By" Type="Boolean" Access="ReadWrite" Value="Modified_x0020_By:BNE_AIR1\\jbrown" />
                    <Property Name="ContentType" Type="String" Access="ReadWrite" Value="Legal Document" />
                    <Property Name="Attach_x0020_Count" Type="String" Access="ReadWrite" Value="Attach_x0020_Count:0" />
                    <Property Name="display_urn\:schemas-microsoft-com\:office\:office#Editor" Type="String" Access="ReadWrite" Value="Jenny Brown"
    />
                    <Property Name="vti_parserversion" Type="String" Access="ReadOnly" Value="15.0.0.4535" />
                    <Property Name="To" Type="Boolean" Access="ReadWrite" Value="To:Barry Peach" />
    <Property Name="From" Type="Time" Access="ReadWrite" Value="From:Tom Heading" />
                    <Property Name="Document Modified By" Type="Boolean" Access="ReadWrite" Value="Document Modified By:BNE_AIR1\\jbrown"
    />
                </Properties>
            </File>
        </SPObject>
    Now, looking at the source document library, this document has the field in question set to String, so why has it been marked as a Time filed type in the expiort file?
    Is anyone aware of any issues with the Export-SPWeb commandlet?
    SharePoint 2013 + March PU + AUG 2013 CU.
    Any help appreciated.

    Hi Richard,
    According to your description, the error occurred when you ran the Export-SPWeb command.
    I recommend to verify the things below for troubleshooting:
    Save the document library as an template(include content) and create a new document library based on the template, then run the Export-SPWeb command to export the new document library to see if the issue still occurs.
    Did this issue occur with other document library? If not, you can delete the string field with error, then run the Export-SPWeb command to narrow the issue scope.
    As a workaround, you can save the library as a template and deploy it to the site collection where you want to move the library, then create the new library in the site collection.
    Best regards.
    Thanks
    Victoria Xia
    TechNet Community Support

  • SAP Java Crypto Toolkit was not found

    Hi,
    I m trying to install Netweaver 7.0 BI and portal with SR3 package. Installation is Cluster installation on windows 2008 and sql 2008 platform. When I came to Centarl instance installtion. On Start Java Phase I had the error. I put the error below. I check the notes Note 1071472 - FileSystem SecureStore connection issues, Note 914818 - JSPM: Could not detect database, Note 1154133 - JSPM: SAP Java Crypto Toolkit was not found.
    Thank you For your Help.
    Bootstrap MODE:
    <INSTANCE GLOBALS>
    determined by parameter [ID0276347].
    Exception occurred:
    com.sap.engine.bootstrap.SynchronizationException: Database initialization failed! Check database properties!
         at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:476)
         at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:146)
         at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:971)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    ==[ Caused by: ]==----
    com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
         at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:115)
         at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)
         at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149)
         at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236)
         at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49)
         at com.sap.engine.bootstrap.Synchronizer.<init>(Synchronizer.java:74)
         at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:473)
         at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:146)
         at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:971)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    Caused by: com.sap.sql.log.OpenSQLException: Error while accessing secure store: Encryption or decryption is not possible because the full version of the SAP Java Crypto Toolkit was not found (iaik_jce.jar is required, iaik_jce_export.jar is not sufficient) or the JCE Jurisdiction Policy Files don't allow the use of the "PbeWithSHAAnd3_KeyTripleDES_CBC" algorithm..
         at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:106)
         at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:145)
         at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:226)
         at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:197)
         at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:112)
         ... 13 more
    Caused by: com.sap.security.core.server.secstorefs.NoEncryptionException: Encryption or decryption is not possible because the full version of the SAP Java Crypto Toolkit was not found (iaik_jce.jar is required, iaik_jce_export.jar is not sufficient) or the JCE Jurisdiction Policy Files don't allow the use of the "PbeWithSHAAnd3_KeyTripleDES_CBC" algorithm.
         at com.sap.security.core.server.secstorefs.SecStoreFS.openExistingStore(SecStoreFS.java:1975)
         at com.sap.sql.connect.OpenSQLConnectInfo.getStore(OpenSQLConnectInfo.java:802)
         at com.sap.sql.connect.OpenSQLConnectInfo.lookup(OpenSQLConnectInfo.java:783)
         at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:209)
         ... 15 more
    Caused by: javax.crypto.NoSuchPaddingException: Padding 'PKCS5Padding' not implemented.
         at iaik.security.cipher.w.engineSetPadding(Unknown Source)
         at iaik.security.cipher.PbeWithSHAAnd3_KeyTripleDES_CBC.<init>(Unknown Source)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
         at java.lang.Class.newInstance0(Class.java:308)
         at java.lang.Class.newInstance(Class.java:261)
         at javax.crypto.SunJCE_b.a(DashoA12275)
         at javax.crypto.SunJCE_b.a(DashoA12275)
         at javax.crypto.Cipher.a(DashoA12275)
         at javax.crypto.Cipher.getInstance(DashoA12275)
         at com.sap.security.core.server.secstorefs.Crypt.<init>(Crypt.java:220)
         at com.sap.security.core.server.secstorefs.SecStoreFS.<init>(SecStoreFS.java:1346)
         at com.sap.sql.connect.OpenSQLConnectInfo.getStore(OpenSQLConnectInfo.java:798)
         ... 17 more
    [Bootstrap module]> Problem occurred while performing synchronization.

    Hi
    > > Caused by: com.sap.sql.log.OpenSQLException: Error while accessing secure store: Encryption or decryption is not possible because the full version of the SAP Java Crypto Toolkit was not found (iaik_jce.jar is required, iaik_jce_export.jar is not sufficient) or the JCE Jurisdiction Policy Files don't allow the use of the "PbeWithSHAAnd3_KeyTripleDES_CBC" algorithm..
    >      at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:106)
    >      at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:145)
    >      at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:226)
    >      at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:197)
    >      at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:112)
    It looks like the JCE file which you have downloaded is not the correct one. As you can see some jar files are missing. Check JCE files.
    Check SAP Note 1240081 - "Java Cryptography Extension Jurisdiction Policy" files
    Thanks
    Sunny

  • Processing this item failed because of a PDF parser error. Input string was not in a correct format.

    Good Morning,
    We're having issues parsing several hundred PDF files located in two separate Record Center sites. All other PDF documents in the environment are being crawled and parsed without issue. I've verified the permissions for the Search service account, but that
    doesn't seem to be the issue. Searching for this particular error hasn't returned much, but I have ensured that the Search service account has been added to the necessary Local Security Policy objects and cleared the configuration cache. Any help would be
    greatly appreciated.
    Processing this item failed because of a PDF parser error. ( Error parsing document 'https://asdf.com/sites/HRRecords/asdf.pdf'. Input string was not in a correct format.; ; SearchID = 6642FEEF-6921-434E-B084-02809173D8A7 )

    This issue came back up for me as my results aren't displaying since this data is not part of the search index.
    Curious if anyone knows of a way to increase the parser server memory in SharePoint 2013 search?
    http://sharepoint/materials-ca/HPSActiveCDs/Votrevieprofessionnelleetvotrecarrireenregistrement.zip
    Processing this item failed because the parser server ran out of memory. ( Error parsing document 'http://sharepoint/materials-ca/HPSActiveCDs/Votrevieprofessionnelleetvotrecarrireenregistrement.zip'. Document failed to be processed. It probably crashed the
    server.; ; SearchID = 097AE4B0-9EB0-4AEC-AECE-AEFA631D4AA6 )
    http://sharepoint/materials-ca/HPSActiveCDs/Travaillerauseindunequipemultignrationnelle.zip
    Processing this item failed because of a IFilter parser error. ( Error parsing document 'http://sharepoint/materials-ca/HPSActiveCDs/Travaillerauseindunequipemultignrationnelle.zip'. Error loading IFilter for extension '.zip' (Error code is 0x80CB4204). The
    function encountered an unknown error.; ; SearchID = 4A0C99B1-CF44-4C8B-A6FF-E42309F97B72 )

  • 'Payload not Serializable' with custom WSDL data types in message-style web service

    I'm implementing a message-style web service which publishes to a JMS Queue.
    I had the web service built and deployed, but noticed that the "sendRequest" message's
    part was of type "xsd:anyType." This is not specific enough for our interface,
    since it is externally facing and needs to describe the object we're expecting
    on the back end.
    So I replaced xsd:anyType with mynamespace:MyType, which is defined as a complex
    type in the same WSDL document.
    My problem is that when I test the web service with the new WSDL (using the client.jar),
    I get a server-side exception from the DestinationSendAdapter.doPost() method.
    The exception reads:
    javax.servlet.ServletException: Payload not Serializable
    at weblogic.soap.server.servlet.DestinationSendAdapter.doPost(DestinationSendAdapter.java:129)
    The domain object ('classic' JavaBean) that it should map to on the server side
    extends a class that implements Serializable, so it should inherit the trait.
    So my questions are:
    1) Did I properly go about trying to restrict the object type that gets sent to
    my Destination?
    2) If no, what is the correct way? If yes, why am I receiving the Payload not
    Serializable error if the domain object implements Serializable?
    Thanks in advance.

    Resolved:
    Apparently this is the right approach, as it boiled down to a classpath issue
    on the client-side. Thanks anyway.

  • Error while running February 2014 CU for SharePoint 2010 Foundation: The expected version of the product was not found on the system

    I ran SP2 and SP2 for Language Pack successfully before.
    Here is how it looks:
    Product
    Version
    Status
    Language Pack for SharePoint   Foundation 2010 - Portuguese/Português (Brasil)
    Installed
    Microsoft SharePoint Foundation 2010 1046   Lang Pack
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   SharePoint 2010 (KB2687453) 64-Bit Edition
    14.0.7015.1000
    Installed
    Microsoft SharePoint Foundation 2010 1046   Lang Pack Core
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   2010 Server Language Pack (KB2687462) 64-Bit Edition
    14.0.7015.1000
    Installed
    Language Pack for SharePoint,   Project Server and Office Web Apps 2010 - Portuguese/Português (Brasil)
    Installed
    Microsoft Access Services Portuguese   (Brazil) Language Pack
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   SharePoint 2010 (KB2687453) 64-Bit Edition
    14.0.7015.1000
    Installed
    Microsoft Document Lifecycle Components   Portuguese (Brazil) Language Pack
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   SharePoint 2010 (KB2687453) 64-Bit Edition
    14.0.7015.1000
    Installed
    Hotfix for Microsoft Office Server   (KB2512800)
    14.0.5138.5000
    Installed
    Microsoft Excel Services Portuguese   (Brazil) Language Pack
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   SharePoint 2010 (KB2687453) 64-Bit Edition
    14.0.7015.1000
    Installed
    Microsoft Excel Web App Portuguese   (Brazil) Language Pack
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   2010 Server Language Pack (KB2687462) 64-Bit Edition
    14.0.7015.1000
    Installed
    Microsoft InfoPath Form Services   Portuguese (Brazil) Language Pack
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   SharePoint 2010 (KB2687453) 64-Bit Edition
    14.0.7015.1000
    Installed
    Microsoft Office Server Proof (Portuguese   (Brazil)) 2010
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   SharePoint 2010 (KB2687453) 64-Bit Edition
    14.0.7015.1000
    Installed
    Microsoft Office Web Apps Portuguese   (Brazil) Language Pack
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   2010 Server Language Pack (KB2687462) 64-Bit Edition
    14.0.7015.1000
    Installed
    Microsoft Office Web Apps Proof   (Portuguese (Brazil)) 2010
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   2010 Server Language Pack (KB2687462) 64-Bit Edition
    14.0.7015.1000
    Installed
    Microsoft Office Web Apps Shared Coms   Portuguese (Brazil) Language Pack
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   2010 Server Language Pack (KB2687462) 64-Bit Edition
    14.0.7015.1000
    Installed
    Microsoft OMUI Portuguese (Brazil)   Language Pack
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   2010 Server Language Pack (KB2687462) 64-Bit Edition
    14.0.7015.1000
    Installed
    Microsoft Project Server Portuguese   (Brazil) Language Pack
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   2010 Server Language Pack (KB2687462) 64-Bit Edition
    14.0.7015.1000
    Installed
    Microsoft Search Server 2010 Portuguese   (Brazil) Language Pack
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   SharePoint 2010 (KB2687453) 64-Bit Edition
    14.0.7015.1000
    Installed
    Hotfix for Microsoft Office Server   (KB2475878)
    14.0.5135.5000
    Installed
    Microsoft Shared Coms Portuguese (Brazil)   Language Pack
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   SharePoint 2010 (KB2687453) 64-Bit Edition
    14.0.7015.1000
    Installed
    Microsoft SharePoint Foundation 2010 1046   Lang Pack
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   SharePoint 2010 (KB2687453) 64-Bit Edition
    14.0.7015.1000
    Installed
    Microsoft SharePoint Portal Portuguese   (Brazil) Language Pack
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   SharePoint 2010 (KB2687453) 64-Bit Edition
    14.0.7015.1000
    Installed
    Microsoft Slide Library Portuguese   (Brazil) Language Pack
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   SharePoint 2010 (KB2687453) 64-Bit Edition
    14.0.7015.1000
    Installed
    Microsoft Visio Services Portuguese   (Brazil) Language Pack
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   SharePoint 2010 (KB2687453) 64-Bit Edition
    14.0.7015.1000
    Installed
    Microsoft Web Analytics Portuguese   (Brazil) Language Pack
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   SharePoint 2010 (KB2687453) 64-Bit Edition
    14.0.7015.1000
    Installed
    Microsoft Word Server Portuguese (Brazil)   Language Pack
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   SharePoint 2010 (KB2687453) 64-Bit Edition
    14.0.7015.1000
    Installed
    Microsoft XMUI Portuguese (Brazil)   Language Pack
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   2010 Server Language Pack (KB2687462) 64-Bit Edition
    14.0.7015.1000
    Installed
    PerformancePoint Services in SharePoint   1046 Language Pack
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   SharePoint 2010 (KB2687453) 64-Bit Edition
    14.0.7015.1000
    Installed
    Microsoft SharePoint   Foundation 2010
    Installed
    Microsoft SharePoint Foundation 2010
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   SharePoint 2010 (KB2687453) 64-Bit Edition
    14.0.7015.1000
    Installed
    Microsoft SharePoint Foundation 2010 1033   Lang Pack
    14.0.4763.1000
    Installed
    Hotfix for Microsoft SharePoint   Foundation 2010 (KB2512804)
    14.0.5138.5000
    Installed
    Microsoft SharePoint Foundation 2010 Core
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   SharePoint 2010 (KB2687453) 64-Bit Edition
    14.0.7015.1000
    Installed
    Microsoft® Search Server 2010   Express
    Installed
    Microsoft Office Server Proof (Arabic)   2010
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   SharePoint 2010 (KB2687453) 64-Bit Edition
    14.0.7015.1000
    Installed
    Microsoft Office Server Proof (English)   2010
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   SharePoint 2010 (KB2687453) 64-Bit Edition
    14.0.7015.1000
    Installed
    Microsoft Office Server Proof (French)   2010
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   SharePoint 2010 (KB2687453) 64-Bit Edition
    14.0.7015.1000
    Installed
    Microsoft Office Server Proof (German)   2010
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   SharePoint 2010 (KB2687453) 64-Bit Edition
    14.0.7015.1000
    Installed
    Microsoft Office Server Proof (Russian)   2010
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   SharePoint 2010 (KB2687453) 64-Bit Edition
    14.0.7015.1000
    Installed
    Microsoft Office Server Proof (Spanish)   2010
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   SharePoint 2010 (KB2687453) 64-Bit Edition
    14.0.7015.1000
    Installed
    Microsoft Search Server 2010 Core
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   SharePoint 2010 (KB2687453) 64-Bit Edition
    14.0.7015.1000
    Installed
    Microsoft Search Server 2010 English   Language Pack
    14.0.4763.1000
    Installed
    Hotfix for Microsoft Office Server   (KB2475878)
    14.0.5135.5000
    Installed
    Microsoft Search Server 2010 Express
    14.0.4763.1000
    Installed
    Microsoft Shared Components
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   SharePoint 2010 (KB2687453) 64-Bit Edition
    14.0.7015.1000
    Installed
    Microsoft Shared Coms English Language   Pack
    14.0.4763.1000
    Installed
    Microsoft SharePoint Foundation 2010 1033   Lang Pack
    14.0.4763.1000
    Installed
    Hotfix for Microsoft SharePoint   Foundation 2010 (KB2512804)
    14.0.5138.5000
    Installed
    Microsoft SharePoint Foundation 2010 Core
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   SharePoint 2010 (KB2687453) 64-Bit Edition
    14.0.7015.1000
    Installed
    Microsoft Web Analytics English Language   Pack
    14.0.4763.1000
    Installed
    Microsoft Web Analytics Web Front End   Components
    14.0.7015.1000
    Installed
    Service Pack 2 for Microsoft   SharePoint 2010 (KB2687453) 64-Bit Edition
    14.0.7015.1000
    Installed
    However when I try to run February CU or December CU I get the error:
    The expected version of the product was not found on the system
    it's possible that I messed up because
    I think I installed a SharePoint Server Service Pack 2 in a SharePoint Foundation Farm.
    these are the files I ran:
    1 - SP2 pt-br
    oserversp2010-kb2687453-fullfile-x64-pt-br
    2 - SP2 for Language Pack pt-br:
    oslpksp2010-kb2687462-fullfile-x64-pt-br
    3 - ran configuration wizard (had na error message the first time and success in the second try)
    4 - December CU or February CU:
    Download SharePoint Foundation 2010 February 2014 CU
    The expected version of the product was not found on the system
    In the first step I think I should have installed
    wsssp2010-kb2687464-fullfile-x64-pt-br
    Now I try to runthis and I get:
    The update is already installed on the system.
    Hopefully this is a QA Environment but it would be a pain to start over.
    Any suggestion?
    Thanks
    J.Clua

    Hi,
    Here are all errors logged:
    [OWSTIMER]   [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:10:18 PM]: Found a missing   feature Id = [81606c80-44b3-47c9-8c24-136bdeb07d64]
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:10:18 PM]: The feature with Id   81606c80-44b3-47c9-8c24-136bdeb07d64 is referenced in the database   [WSS_Content_Sites_01], but is not installed
    on the current farm. The missing   feature may cause upgrade to fail. Please install any solution which contains   the feature and restart upgrade if necessary.
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:10:18 PM]: Found a missing feature Id =   [4b6e8a49-765d-47a1-92f8-91f61d07bbed]
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:10:18 PM]: The feature with Id   4b6e8a49-765d-47a1-92f8-91f61d07bbed is referenced in the database   [WSS_Content_Sites_01], but is not installed
    on the current farm. The missing   feature may cause upgrade to fail. Please install any solution which contains   the feature and restart upgrade if necessary.
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:10:18 PM]: Found a missing feature Id =   [af6d9aec-7c38-4dda-997f-cc1ddbb87c92]
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:10:18 PM]: The feature with Id   af6d9aec-7c38-4dda-997f-cc1ddbb87c92 is referenced in the database   [WSS_Content_Sites_01], but is not installed
    on the current farm. The missing   feature may cause upgrade to fail. Please install any solution which contains   the feature and restart upgrade if necessary.
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:10:18 PM]: Found a missing feature Id =   [00bfea71-dbd7-4f72-b8cb-da7ac0440130]
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:10:18 PM]: The feature with Id   00bfea71-dbd7-4f72-b8cb-da7ac0440130 is referenced in the database   [WSS_Content_Sites_01], but is not installed
    on the current farm. The missing   feature may cause upgrade to fail. Please install any solution which contains   the feature and restart upgrade if necessary.
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:16:17 PM]: Found a missing feature Id =   [5daabc0d-5714-4b95-9238-95d58704bc11], Name = [Blog Rating], Description =   [This feature allows visitors
    to rate blog posts], Install Location = [Blog   Rating]
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:16:17 PM]: The feature with Id   5daabc0d-5714-4b95-9238-95d58704bc11 is referenced in the database   [WSS_Content_AcademiaTI], but is not installed
    on the current farm. The   missing feature may cause upgrade to fail. Please install any solution which   contains the feature and restart upgrade if necessary.
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:23:56 PM]: Found a missing feature Id =   [af6d9aec-7c38-4dda-997f-cc1ddbb87c92]
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:23:56 PM]: The feature with Id   af6d9aec-7c38-4dda-997f-cc1ddbb87c92 is referenced in the database   [WSS_Content_GlobalIT], but is not installed
    on the current farm. The missing   feature may cause upgrade to fail. Please install any solution which contains   the feature and restart upgrade if necessary.
    [OWSTIMER] [SPContentDatabaseSequence]   [DEBUG] [3/11/2014 5:25:49 PM]: Retrieving site definition for language   1046...
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:50 PM]: Found 21 web(s) using missing web template   75801 (lcid: 1046) in ContentDatabase WSS_Content_EXP.
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:50 PM]: The site definitions with Id 75801 is   referenced in the database [WSS_Content_EXP], but is not installed on the   current farm. The
    missing site definition may cause upgrade to fail. Please   install any solution which contains the site definition and restart upgrade   if necessary.
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:50 PM]: Found 1 web(s) using missing web template   75802 (lcid: 1033) in ContentDatabase WSS_Content_EXP.
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:50 PM]: The site definitions with Id 75802 is   referenced in the database [WSS_Content_EXP], but is not installed on the   current farm. The
    missing site definition may cause upgrade to fail. Please   install any solution which contains the site definition and restart upgrade   if necessary.
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:53 PM]: Found a missing feature Id =   [75a0fea7-2d1e-451a-b445-16bc346d7d8e]
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:53 PM]: The feature with Id   75a0fea7-2d1e-451a-b445-16bc346d7d8e is referenced in the database   [WSS_Content_EXP], but is not installed on
    the current farm. The missing   feature may cause upgrade to fail. Please install any solution which contains   the feature and restart upgrade if necessary.
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:53 PM]: Found a missing feature Id =   [75a0fea7-5f69-4282-83ae-22808c0fbfd9]
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:53 PM]: The feature with Id   75a0fea7-5f69-4282-83ae-22808c0fbfd9 is referenced in the database   [WSS_Content_EXP], but is not installed on
    the current farm. The missing   feature may cause upgrade to fail. Please install any solution which contains   the feature and restart upgrade if necessary.
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:53 PM]: Found a missing feature Id =   [75a0fea7-6e3f-4d4a-8f78-245bda567b60]
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:54 PM]: The feature with Id   75a0fea7-6e3f-4d4a-8f78-245bda567b60 is referenced in the database   [WSS_Content_EXP], but is not installed on
    the current farm. The missing   feature may cause upgrade to fail. Please install any solution which contains   the feature and restart upgrade if necessary.
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:54 PM]: Found a missing feature Id =   [75a0fea7-040e-4abb-b94b-32f1e7572840]
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:54 PM]: The feature with Id   75a0fea7-040e-4abb-b94b-32f1e7572840 is referenced in the database   [WSS_Content_EXP], but is not installed on
    the current farm. The missing   feature may cause upgrade to fail. Please install any solution which contains   the feature and restart upgrade if necessary.
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:54 PM]: Found a missing feature Id =   [75a0fea7-b5a0-47d5-90e6-4b3205b02278]
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:54 PM]: The feature with Id   75a0fea7-b5a0-47d5-90e6-4b3205b02278 is referenced in the database   [[OWSTIMER] [SPContentDatabaseSequence] [ERROR]
    [3/11/2014 5:25:54 PM]: Found   a missing feature Id = [75a0fea7-b5a0-47d5-90e6-4b3205b02278]], but is not   installed on the current farm. The missing feature may cause upgrade to fail.   Please install any solution which contains the feature
    and restart upgrade if   necessary.
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:54 PM]: Found a missing feature Id =   [f7b9c169-1418-41f3-888f-8ac436e17a0a]
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:54 PM]: The feature with Id   f7b9c169-1418-41f3-888f-8ac436e17a0a is referenced in the database   [WSS_Content_EXP], but is not installed on
    the current farm. The missing   feature may cause upgrade to fail. Please install any solution which contains   the feature and restart upgrade if necessary.
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:54 PM]: Found a missing feature Id =   [75a0fea7-f13a-4670-8b69-97e90d05f7c8]
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:54 PM]: The feature with Id   75a0fea7-f13a-4670-8b69-97e90d05f7c8 is referenced in the database   [WSS_Content_EXP], but is not installed on
    the current farm. The missing   feature may cause upgrade to fail. Please install any solution which contains   the feature and restart upgrade if necessary.
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:54 PM]: Found a missing feature Id =   [75a0fea7-377d-4b4f-b864-984379ed0f42]
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:54 PM]: The feature with Id   75a0fea7-377d-4b4f-b864-984379ed0f42 is referenced in the database   [WSS_Content_EXP], but is not installed on
    the current farm. The missing   feature may cause upgrade to fail. Please install any solution which contains   the feature and restart upgrade if necessary.
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:54 PM]: Found a missing feature Id =   [75a0fea7-9d96-4f02-a800-a3512154efcd]
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:54 PM]: The feature with Id   75a0fea7-9d96-4f02-a800-a3512154efcd is referenced in the database   [WSS_Content_EXP], but is not installed on
    the current farm. The missing   feature may cause upgrade to fail. Please install any solution which contains   the feature and restart upgrade if necessary.
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:54 PM]: Found a missing feature Id =   [90cd055f-f21f-42c5-b3fe-bb67173583d4]
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:55 PM]: The feature with Id   90cd055f-f21f-42c5-b3fe-bb67173583d4 is referenced in the database   [WSS_Content_EXP], but is not installed on
    the current farm. The missing   feature may cause upgrade to fail. Please install any solution which contains   the feature and restart upgrade if necessary.
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:55 PM]: Found a missing feature Id =   [75a0fea7-0017-4993-85fe-c37971507bbc]
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:55 PM]: The feature with Id   75a0fea7-0017-4993-85fe-c37971507bbc is referenced in the database   [WSS_Content_EXP], but is not installed on
    the current farm. The missing   feature may cause upgrade to fail. Please install any solution which contains   the feature and restart upgrade if necessary.
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:55 PM]: Found a missing feature Id =   [75a0fea7-fe65-41c3-a965-c5df83fb098b]
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:55 PM]: The feature with Id   75a0fea7-fe65-41c3-a965-c5df83fb098b is referenced in the database   [WSS_Content_EXP], but is not installed on
    the current farm. The missing   feature may cause upgrade to fail. Please install any solution which contains   the feature and restart upgrade if necessary.
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:55 PM]: Found a missing feature Id =   [75a0fea7-7c51-4a75-92c1-cbaccb371622]
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:55 PM]: The feature with Id   75a0fea7-7c51-4a75-92c1-cbaccb371622 is referenced in the database   [WSS_Content_EXP], but is not installed on
    the current farm. The missing   feature may cause upgrade to fail. Please install any solution which contains   the feature and restart upgrade if necessary.
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:55 PM]: Found a missing feature Id =   [75a0fea7-b0ef-434e-90d6-ce997d970564]
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:55 PM]: The feature with Id   75a0fea7-b0ef-434e-90d6-ce997d970564 is referenced in the database   [WSS_Content_EXP], but is not installed on
    the current farm. The missing   feature may cause upgrade to fail. Please install any solution which contains   the feature and restart upgrade if necessary.
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:55 PM]: Found a missing feature Id =   [75a0fea7-37d2-484b-b362-dcff1538e2a4]
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:55 PM]: The feature with Id   75a0fea7-37d2-484b-b362-dcff1538e2a4 is referenced in the database   [WSS_Content_EXP], but is not installed on
    the current farm. The missing   feature may cause upgrade to fail. Please install any solution which contains   the feature and restart upgrade if necessary.
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:55 PM]: Found a missing feature Id =   [49c44827-4747-4e89-999c-f199ad95cfa8]
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:56 PM]: The feature with Id   49c44827-4747-4e89-999c-f199ad95cfa8 is referenced in the database   [WSS_Content_EXP], but is not installed on
    the current farm. The missing   feature may cause upgrade to fail. Please install any solution which contains   the feature and restart upgrade if necessary.
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:56 PM]: Found a missing feature Id =   [75a0fea7-42e8-4527-8313-f63c4c49a7e6]
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:56 PM]: The feature with Id   75a0fea7-42e8-4527-8313-f63c4c49a7e6 is referenced in the database   [WSS_Content_EXP], but is not installed on
    the current farm. The missing   feature may cause upgrade to fail. Please install any solution which contains   the feature and restart upgrade if necessary.
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:56 PM]: Found a missing feature Id =   [75a0fea7-a4ce-4a83-867d-f6be0ffdd867]
    [OWSTIMER] [SPContentDatabaseSequence]   [ERROR] [3/11/2014 5:25:56 PM]: The feature with Id   75a0fea7-a4ce-4a83-867d-f6be0ffdd867 is referenced in the database   [WSS_Content_EXP], but is not installed on
    the current farm. The missing   feature may cause upgrade to fail. Please install any solution which contains   the feature and restart upgrade if necessary.
    [OWSTIMER] [SPSiteWssSequence] [ERROR]   [3/11/2014 5:32:40 PM]: Action 4.0.23.0 of   Microsoft.SharePoint.Upgrade.SPSiteWssSequence failed.
    [OWSTIMER] [SPSiteWssSequence] [ERROR]   [3/11/2014 5:32:40 PM]: Inner Exception: Já existe um campo com este nome.
    O nome especificado para este campo é   igual ao de outro campo da lista. Escolha outro nome e tente   novamente.<nativehr>0x81020013</nativehr><nativestack></nativestack>
    [OWSTIMER] [SPSiteWssSequence] [ERROR]   [3/11/2014 5:32:40 PM]:   
    at   Microsoft.SharePoint.Library.SPRequestInternalClass.UpdateField(String   bstrUrl, String bstrListName, String bstrXML)
         at Microsoft.SharePoint.Library.SPRequest.UpdateField(String bstrUrl,   String bstrListName, String bstrXML)
    [OWSTIMER] [SPSiteWssSequence] [ERROR]   [3/11/2014 5:32:40 PM]: Exception: Já existe um campo com este nome.
    O nome especificado para este campo é   igual ao de outro campo da lista. Escolha outro nome e tente novamente.
    [OWSTIMER] [SPSiteWssSequence] [ERROR]   [3/11/2014 5:32:40 PM]:   
    at   Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx)
    [OWSTIMER] [SPUpgradeSession] [ERROR]   [3/11/2014 5:32:40 PM]: Upgrade [SPSite Url=http://sjkqa41:7779] failed.   Microsoft.SharePoint.Upgrade.SPSiteWssSequence has the ContinueOnFailiure bit   set. Moving
    on to the next object in sequence.
    [OWSTIMER] [SPUpgradeSession] [ERROR]   [3/11/2014 5:32:40 PM]: Inner Exception: Já existe um campo com este nome.
    O nome especificado para este campo é   igual ao de outro campo da lista. Escolha outro nome e tente novamente.
    [OWSTIMER] [SPUpgradeSession] [ERROR]   [3/11/2014 5:32:40 PM]:   
    at   Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx)
         at Microsoft.SharePoint.Library.SPRequest.UpdateField(String bstrUrl,   String bstrListName, String bstrXML)
         at Microsoft.SharePoint.SPField.UpdateCore(Boolean bToggleSealed)
         at Microsoft.SharePoint.SPFieldIndexCollection.IndexOneField(Object   field, Boolean bIndexed)
         at Microsoft.SharePoint.SPFieldIndexCollection.Add(SPField field)
         at   Microsoft.SharePoint.Upgrade.RestoreWorkflowAndDatasourceLibraryPermissions.Upgrade()
         at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()
    [OWSTIMER] [SPUpgradeSession] [ERROR]   [3/11/2014 5:32:40 PM]: Exception: Action 4.0.23.0 of   Microsoft.SharePoint.Upgrade.SPSiteWssSequence failed.
    [OWSTIMER] [SPUpgradeSession] [ERROR]   [3/11/2014 5:32:40 PM]:   
    at   Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()
         at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o,   Boolean bRecurse)
    [OWSTIMER] [SPUpgradeSession] [ERROR]   [3/11/2014 5:37:44 PM]: Upgrade Timer job is exiting due to exception:   Microsoft.SharePoint.Upgrade.SPUpgradeException: Upgrade completed with   errors. 
    Review the upgrade log file   located in C:\Program Files\Common Files\Microsoft Shared\Web Server   Extensions\14\LOGS\Upgrade-20140311-164603-307.log. 
    The number of errors and warnings is listed   at the end of the upgrade log file.
         at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CheckPoint()
         at Microsoft.SharePoint.Upgrade.SPUpgradeSession.LogEnd()
         at   Microsoft.SharePoint.Administration.SPUpgradeJobDefinition.Execute(Guid   targetInstanceId)
    Despite all the erros, can I consider these farm updated in terms of SharePoint build?
    Thanks
    J.Clua

  • 'int' not serializable!?

    Hello all,
    When deploying my application to WLS 8.1, I keep getting warnings along the lines of
    <Warning> <EJB> <BEA-012034> <The Remote interface method: '//snip// Foo.bar(java.lang.String,int) throws java.rmi.RemoteException //snip// contains a parameter of type: 'int' which is not Serializable. Though the EJB 'Foo' has call-by-reference set to false, this parameter is not Serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is Serializable.>
    This message completely confuses me. Since 'int' is a primitive, it cannot implement the Serializable interface. On the other hand this is not necessary since the JVM knows how to serialize primitives anyway. Furthermore, primitives are by Java specification always passed by value.
    My assumption is that this message is essentially bogus, a weblogic bug if you want, and the int parameter will indeed be passed by value no matter what the warning says. I just cant se how WLS could pass it by reference given that it is running on a VM that implements the java standard.
    Am I missing something here? Please give me your thoughts on this one. We have a customer who is very concerned about these warnings showing up in the log...
    Thank you
    Message was edited by:
    [email protected]

    Hello, and thanks for taking a stab at this.
    While it is great that the fix you ar putting into SP5 allows the administrator to supress BEA-012034 warnings all together, would it not be better to simply correct the code not to issue BEA-012034 warnings for ints, floats and other primitives? Enabeling your fix would indeed make these incorrect messages go away, but it will also supress correct BEA-012034 warnings should our ejb interface [heaven forbid :] contain non-serializable objects.
    thanks

  • Document in xml - Not serializable? Well, I need to cache it.

    Can anyone tell me how can I serialize DOM Document.
    When we try to put it in cache, cache complains that it
    is not serializable (I believe ElementImpl is not Serializable).
    In javadoc it shows serializable form for this Element, but when I look in the source it does not implements Serializable (and none of its parent interfaces).
    My question is this?
    Does anyone know how to serialize Document.
    (I do need to Serialize Document, not XML.In my case it
    is too expensive to parse XML every time I come back
    from cache)
    How do I use Serializable form of one class or interface?
    Thank You.
    Edmon

    Sorry about not being very helpful earlier. The number of people who submit JDC forum questions without reading even the elementary intro docs is rather staggering, IMHO. Here is something more detailed:
    (a) "Serialized form" of a class as found in javadoc has little to do with whether or not the class has been declared as Serializable by the implementor.
    (b) what matters to Java serialization is whether the object in question is runtime-Serializable. In your particular case, org.w3c.dom.Document is an interface and it was not declared as Serializable by W3C. Perhaps justifiably so, because that imposes unfair requirements on parser implementors [seeing that not everybody is expected to want to serialize a DOM tree the way you do].
    However, a particular parser implementation is free to make its Document implementation class as Serializable. If that is the case, writeObject(obj) will succeed even if "obj" variable is of Document [not Serializable] type but happens to point to a Serializable implementation class.
    But, if you rely on this behavior you are locking yourself into that particular parser implementation. Should you choose a different XML parser in the future you will see serialization errors at runtime. With things like JAXP and a variety of XML parsers available this perhaps is not the way to go.
    Things would have been different if Document was declared to implement Serializable. Then all XML parsers would have had a standard behavior for the DOM trees they produced, regardless of implementation details. This is not the case, though.
    Vlad.

  • Document in xml - Not serializable?

    Hi, I was working with the Document in xml.
    I tried to serialize it, but it seems that the implemantation of it is not serializable.
    The problem is that the object is created with a factory method, so also inheriting it is no use, since the creation is not in our hands.
    The only solution i can see is to inherit also the Factory and to ovverde the creation method.
    Any suggestion?
    Thanks,
    Doron

    why do you want to serialize the document object?
    you might as well serialize the xml file it represents and when or where needed, just parse it and get its document object, which would essentially be the same as the object you are trying to serialize.

Maybe you are looking for

  • K7T Turbo Limited Edition + Raid

    Im Planning to upgrade to a K7T Turbo Limited Edition + Raid (MS-6330 3.0) with an XP 2000.... are there any issues with the board with this CPU? According to the bios updates theysupport up to XP2600+'s... im not going ddr yet, prices are WAY to hig

  • How to use EBW_DQ_SS for datasource 0UC_SALES_STATS_02

    Hello All, Could someone please guide me how to use the OLTP transaction code EBW_DQ_SS. It is mentioned in help.sap that we need to execute this t-code to update data to the delta queue of datasource 0UC_SALES_STAT_02. I tried running this t-code wi

  • Is the Up-To-Date program for iLife'11 available for Bulgarian customers ?

    Hi, I heard about the Up-To-Date upgrade program for iLife'11. When it will be available for customers from Bulgaria who purchased their computers from bulgarian Apple Premium Reseller stores ?

  • Displaying Report in Web layout

    Hello All, Can anyone please tell me how to display reports in web layout during runtime. I've created a report in month_report.jsp, having both Web Layout & Paper Layouts. At runtime when I call the report the Paper Layout version is getting display

  • JSP Custom Tag and Expressions for parameters

    This should be an easy question. I am trying to use an expression for a           parameter to a jsp or custom jsp tag. When I hard code a value for the           parameter, the tag works fine but when I use the expression, the expression           g