Error stating mail version too old after 10.6.8 update

I upgraded 3 Intel Macs to Snow Leopard.  A Macbook, Mac Pro and an iMac.  After the upgrade I ran software update and updated to 10.6.8.  This worked without issue on the Macbook and Mac Pro. 
However, on the iMac, when I open mail, I get the following message:
You have Mail version 4.2 (1078/1084). It can’t be used on Mac OS X Version 10.6.8 (Build 10K549). For more information, click the Help button.
I've tried reinstalling Mail from the Optional Installs on the Snow Leopard install disk.  I've also moved the com.apple.mail.plist to the desktop.  None of this is making any difference.

Good call here.  I had already done all updates, no new updates were available, that's what was so confusing, mail should have been updated.  Then I looked all over for a way to get to find a version of Mail 4.5, no dice.
I spend all day on Windows at work and then come home and forget things like the ability to grab an Application from another machine and drag it to my desktop.  That suggestion did the trick and I'm back in business.
Thanks

Similar Messages

  • Synch with desk top using OS X 10.6.8.  Won't recognise iPad, which it says has iTunes version too old.  How do I update iPad?

    I have a desk top upgraded to OS X 10.6.8.  Now won't recognise/synch iPad, which it says needs to have iTunes version 11.1 or later.  Why hasn't iPad updated or how can I do it manually?

    What do you need to update on your iPad?  Which model do you have and and which iOS version?  If you have an iPad 2 or newer with at least iOS 5 you can update the operating system over your WiFi by going to Settings > General > Software Update.

  • Version too old error

    Post Author: niketya
    CA Forum: Older Products
    I have never used Crystal Report so my knowledge about this product is rather poor.  We are using crystal viewer in a custom made application which generates crystal reports and saves them in 1rd format.  Granted we can export the documents to pdf, however people choose not to.  Anyway, we are getting a new web application and it does not use Crystal Report.  I have installed the CR XI viewer and when open a report file I get the following  along the lines of "Version too old use version 9 to open it".  Clearly the generated reports are from version 9.  I was wandering If I could open these reports in Access or in a stand alone application? Many thanksNiketya 

    Actually the JRE/Jinit version has nothing to do with the error. The error is caused when the Forms applet (i.e. frmall.jar, frmall_jinit.jar) version is not in sync with the Forms Servlet or Runtime version.
    Clear the JRE/Jinit JAR cache and retest. If this continues to fail, consider whether or not you have recently installed any patches to the Application Server. If so, you may have not successfully completed that task. If the client jar files (i.e. frmall.jar, frmall_jinit.jar) where not updated during a patch installation, the error you are seeing is likely to occur. This can also occur if the client accesses more than one minor version of an Application Server installation (i.e. 10.1.2.0.2 and 10.1.2.2).
    Installing a new JRE only indirectly solves this problem. The reason is that when a new JRE is installed, the JRE cache is empty the first time it is used and therefore resembles the cache clearing recommendation noted above.
    FYI: FRM-92150 Client version too new occurs, after a patch installation, when the client JAR files are updated but the Forms Servlet or Runtime is not. Again, clearing cache can sometimes solve this problem if recent patching was not attempted.

  • FRM-92160:Fatal error:Webclient version too old

    Somebody pls assist.
    I am running 11gR2 on Redhat, the forms can run on ie9 but can't on ie8. I am getting "FRM-92160:Fatal error:Webclient version too old". Anything I didn't do? I need this wotking as well on ie8.
    Any help would be appreciated.
    regards
    Mo

    Fortunately, the "Web client too old" or "Web client too new" errors are very accurate and clear. When a Forms application attempts to start, one of the first things which occurs is a verification that the client applet (frmall.jar) is of the same version as the server side runtime which is about to host it. "Web client too old", means that the client jar is of an older version than the server side runtime (i.e. frmweb.exe). This can occur if more than one Forms version has been accessed from the same server. Remember that the jar files are cached on the client (in the JRE). So, if you were to run something like v10 from serverA then attempt to run v11 from the same server, you likely would end up with a client too old error. The same would be true if you first try to run 11.1.1 then attempt to access 11.1.2 from the same machine. The issue can also occur if for some reason the jar files in the installation were not patched during a patch installation. This would be rare, but could occur if the patch installation failed during the process. It could also occur if you copies old files into the installation. This is never a good idea.
    So, as mentioned, start by clearing the JRE cache and retesting.
    1. Close ALL open browsers.
    2. Open the JRE Control Panel (found on the Windows Control Panel).
    3. On the General tab, click on "Settings..."
    4. Then click on "Delete files..."
    5. Then click on "Ok".
    6. Exit the JRE Control Panel and retest.
    Important to note is that JRE7 is NOT supported with 11.1.2.0. Be sure that you are using JRE6. If you have JRE7 installed, I would recommend closing ALL open browsers and uninstalling it. You should have only JRE6 installed before testing.

  • FRM-92160: Web Client version too old

    Hi folks,
    i have been developing and running my forms using Oracle 9iDS and the Oracle 9i database. The forms are run in the browser using the version of OC4J that comes with the developer suite.
    i installed Oracle 10g Application server forms and reports services recently, however i have decided not to run my forms through the application server as yet.
    when i tried to run running a form, i had an error message saying
    FRM-92160: Web Client version too old.
    I tried looking up the error but couldn't find it anywhere.
    I can't run my forms now and i do not want to go through the application server as yet.
    Any suggestions as to what to do?
    Thanks in advance.

    I run into the same problem after upgrading my AS10g/W2k to 904011: Forms from the MiddleTier did run, but a Forms started from the DevSuite-environment would raise FRM-92160.
    What worked in my case was copying the MidTier's '...\forms90\java' files over to the DevSuite, ie.
    - backup [DevSuite_Home]\forms90\java to java0
    - copy [MidTier_Home]\forms90\java to [DevSuite_Home]
    After that, my Forms run flawlessly from both DevSuite's OC4J and the AS MidTier. I also 'upgraded' formsweb.cfg in [DevSuite_Home] from JInit 1.3.1.17 to 1.3.1.18 - works.
    Cheers
    Tino

  • FRM-92160: WEB Client Version too old & Vis R12.0.4 invalid objects

    Hello all,
    I'm installing Vision R12.0.4 in a server. That server used to contain Vision R12.0.0 which I upgraded to R12.0.4 but still had some invalid objects (I already submitted that problem in another thread). I installed the new vision instance to the same folder used to contain R12.0.0 vision after remove the old installation.
    After all installation steps completed I tried to connect from my laptop but I got this error message :
    FRM-92160: WEB Client Version too old
    Had tried to uninstall all java from my laptop but still had the same error message. I had oracle form & report developer 6i and 10g in my laptop. Tried to remove that installation and cleaned the registry but failed to delete LEGACY_ORACLE_LOAD_BALANCER_GO_CLIENT and some other objects.
    I checked the installation and found 35 invalid objects, do APPS compile and left with 32 invalid objects. Here are the invalid objects :
    OWNER     OBJECT_NAME
    APPS     IGCBG_CC_NUMBER_METHODS
    APPS     IGCFG_CC_NUMBER_METHODS
    ORDSYS     ORDIMGEXTCODEC_PKG
    ORDSYS     ORDIMG_PKG
    SYS     XMLGENFORMATTYPE
    SYS     LCR$_ROW_LIST
    SYS     LCR$_ROW_UNIT
    SYS     AQ$_SRVNTFN_MESSAGE
    SYS     AQ$_REG_INFO
    SYS     AQ$_REG_INFO_LIST
    SYS     DBMS_SUMADV
    SYS     AQ$_REG_INFO_LIST
    SYS     DBMS_XPLAN_TYPE
    SYS     DBMS_XPLAN_TYPE_TABLE
    SYS     AQ$_DESCRIPTOR
    SYS     AQ$_SRVNTFN_MESSAGE
    SYS     AQ$_EVENT_MESSAGE
    SYS     AQ$_REG_INFO
    SYS     AQ$_SRVNTFN_MESSAGE
    SYS     MSG_PROP_T
    SYS     AQ$_DESCRIPTOR
    XDB     servlet-list46_T
    XDB     servlet52_COLL
    XDB     servlet47_T
    XDB     xdbconfig58_T
    XDB     servlet-config-type42_T
    XDB     webappconfig65_T
    XDB     sysconfig59_T
    XDB     XDB$RESOURCE_T
    XDB     protocolconfig60_T
    XDB     sysconfig59_T
    XDB     xdbconfig58_T
    XDB     httpconfig64_T
    XDB     protocolconfig60_T
    XDB     httpconfig64_T
    How to solve those problems? Thanks.

    The following views will remain invalid in 12.0.4:
    APPS IGCBG_CC_NUMBER_METHODS
    APPS IGCFG_CC_NUMBER_METHODS
    This is documented in 12.0.4 Release Note:549389.1
    under "Installation and Upgrade Customers"Thanks for the info. At least it solved 2 of my problem rows :P
    anyway, I'm sorry that I can't tried to solve the problem anymore cause the storage was needed for another installation so I'd to remove this problem instance. Maybe if I can try it again I'll let you all know. Thanks

  • Report file version too old

    Hi, I hope I am in the right forum. I downloaded crystal report viewer 2008, but need to view a report that was created using an earlier version. The error message I get is as follows, " Report File version too old. This report was saved from a version of crystal report older than version 9 and cannot be viewed. To fix the problem please open and resave the report from a version of the crystal report designer application at least as recent as version 9".
    How do I do this. I cant seem to get the older versions on the net anymore. Please help

    The error message says "at least as recent as version 9".So, you can try with any version after 9.Following is the link to download a free trial version:
    http: //www.businessobjects.com/product/freetrials.asp
    You may try with Crystal Reports XI or Crystal Reports 2008

  • FRM-92160 web version too old

    Hi guys,
    I had installed oracle 9i and developer6i on the server and configue IIS .When i access through client,if win 98 is installed on client it gives FRM-92160 web version too old error but on client where win2000 is installed ,it works.Any help??

    Check if you have the correct version of Jinitiator on your Win 98 machine.

  • My iOS remains the same as whats inside my iPhone I bought it 18months ago, which is version 4.2.1, I am told by an Apple shop that its too old to do a proper update, unless all my data will have to be erased !! is this true ?  if so, how to get round it

    my iOS remains the same as whats inside my iPhone I bought it 18months ago, which is version 4.2.1, I am told by an Apple shop that its too old to do a proper update, unless all my data will have to be erased !! is this true ?  if so, how to get round it ?    Chuck

    Be sure to do a backup before updating as protection. Photos should
    be synced with your computer, music should be in iTunes, documents
    should be backed up on your computer as should contacts in whatever
    program you use on your computer. You should already have backups
    of your important information to prevent loss in case of theft, crash,
    physical damage. The question is not if your hard drive will crash but
    when, and you iPhone is not a backup device nor fit for the only
    source of any document, picture, music, movie, contact or otherwise
    irreplaceable information.

  • Frm-92160 web version too old error

    plz suggest the solution to overcome from it

    Actually the JRE/Jinit version has nothing to do with the error. The error is caused when the Forms applet (i.e. frmall.jar, frmall_jinit.jar) version is not in sync with the Forms Servlet or Runtime version.
    Clear the JRE/Jinit JAR cache and retest. If this continues to fail, consider whether or not you have recently installed any patches to the Application Server. If so, you may have not successfully completed that task. If the client jar files (i.e. frmall.jar, frmall_jinit.jar) where not updated during a patch installation, the error you are seeing is likely to occur. This can also occur if the client accesses more than one minor version of an Application Server installation (i.e. 10.1.2.0.2 and 10.1.2.2).
    Installing a new JRE only indirectly solves this problem. The reason is that when a new JRE is installed, the JRE cache is empty the first time it is used and therefore resembles the cache clearing recommendation noted above.
    FYI: FRM-92150 Client version too new occurs, after a patch installation, when the client JAR files are updated but the Forms Servlet or Runtime is not. Again, clearing cache can sometimes solve this problem if recent patching was not attempted.

  • Why do I get "Version too old to administer message" with CS5?

    I am using CS5 with Windows 7 to administer and edit six websites.
    With five sites, I have no problem accessing Administrator dialogue box.  With one site I get a message saying  "Your version is too old to Administer this website."  The error cropped up very recently, after I contacted my server, who sent me a new connection key. (I believe my server only has CS3 and have noted comments re compatibility.)
    I tried making a new connection via CS5.-- connection works fine but the same error message crops up when I go to the Administer option.
    I don't know if this is related to another problem that initially led me to contact my server:
    I do a lot of updating on this site -- www.commentopia.com - When I attempt to publish, i keep getting an error message:
    "Contribute encountered a network or file system error. Please try again etc."   When I try again,  the page publishes with no problem...
    I encounter the same error message with my other sites and also get pages published only on second attempt.
    Any thoughts will be welcome.
    Thanks,
    Errol

    HHow did you solve this problem?

  • Receiving error ORA-01555: snapshot too old:

    Need some info...
    Currently seeing ORA-01555: snapshot too old: rollback segment number 18 with name "_SYSSMU18$" too small.
    Info:
    SQL> show parameter undo
    NAME TYPE VALUE
    undo_management string AUTO
    undo_retention integer 4200
    undo_suppress_errors boolean FALSE
    undo_tablespace string UNDOTBS_1
    SQL> select max(maxquerylen) from v$undostat;
    MAX(MAXQUERYLEN)
    35792
    SQL>
    run this based on threads in here:
    SQL> select (35792/60)/60 query,(4200/60)/60 retention from dual;
    QUERY RETENTION
    9.94222222 1.16666667
    I need some help figuring out what to set my undo_retention to? Should it be 36000?
    Any help is appreciated.
    Thanks

    Jamie CC wrote:
    The query that was in the alert log was running against a table with 779 rows. The query uses the index (not worried if it wouldn't for that small a table) and came back in one second... This makes no sense. Is it possible that there was a sub-query running and the wrong query was put into the alert log?More likely the query in the alert log was one that died, but the cause was a different query. Remember, the meaning of an ORA-1555 is that the query needed to go back to undo in order to gather a view of the data to a certain SCN, and the data had already been aged out. So the alert log gets the one that died, but the cause is another one. Feel lucky at that, in older versions it was considered an app error IIRC.
    Search for the error on asktom.oracle.com for a number of scenarios, and you might want to review the part of the concepts manual about read consistency to make sense of it all. You might also find Tom's book explanation about it with a google search.
    Also, depending on your version, there may be things to set like retention guarantee.
    I've found on the ERP/MRP systems I work on these errors will appear weekly from people leaving sessions connected after they go home, so I kill 'em off at night. And that's with an undo nearly as big as the db data, that's normally almost empty.

  • Oracle error: Ora-01555 : snapshot too old: rollback segment number 1......

    System Error: Unknown Database error (type qqdb_ResourceException) on WMS_WH1: Execute failed for SQL statement ............... error from database is: ORA-01555: snapshot too old: rollback segment number 1 with name "_SYSSMU1$" too small...
    Any ideas ? Please help.
    Thank you.

    You either have
    - an UNDO tablespace that is way too small (rollback segments that are too small); or
    - an application that does way too many COMMITs (common with apps ported from SQL Server)
    From the added info, I would guess that the Java program has a major loop and does processing on each of the values it gets in that loop. At the end of each turn in the loop, it does a commit. Then it tries to look at the next record in the master list. After a while (say around 388 loops ;-) ) it dies.
    The reason is that when it looks for information in the master query, it needs to rebuild that information to the moment that query was initiated. It uses rollback (AKA undo) to rebuild that. But rollback is not guaranteed to exist after a commit (unless forced) and once a commit happens, that area can be reused. When it is reused, the information is no longer there to rebuild the row, and that raises an ORA-01555
    Edited by: Hans Forbrich on Sep 11, 2009 3:44 PM

  • Pages 5.1 error "This document is too old. To open it, save it with Pages '09 first."

    When trying to open a Pages '08 file from a MacBook Pro in Pages 5.1 on an iMac, I get thr error message, "This document is too old. To open it, save it with Pages '09 first". I cannot locate a Pages '09 to use.  I can export the file from Pages '08 into a Microsoft Word Doc file and can open it then. How I do I solve the problem and open files in Pages 5.1?

    It is A solution that works if you don't have too many Page files to convert, but is very poor solution if trying to move everything off of the MacBook Pro to the iMac.  I don't necessarily need to open the 5 years of files, but if I need to look at something archived, I'm dead in the water.
    It doesn't make sense that a Mac can open a Microsoft product but cannot open a Mac product.  I can understand that a program is not forward compatibale, but almost all programs are backward compatible. This same problem appears with Numbers 3.1.
    Apple needs Microsoft as a solution?

  • UNdo error (ora-01555) - Snapshot too old error

    Hi,
    If undo get filled and if we get a snapshot too old error then what is the solution for this error, plz give step by step solution for this.

    You prevent ORA-01555 errors by
    1) Setting UNDO_RETENTION equal to or greater than the length of the longest running query/ serializable transaction in the system
    2) Ensuring the UNDO tablespace is large enough to accomodate the amount of UNDO generated over that period of time.
    You would need to determine things like the length of your longest running query, the amount of UNDO getting generated, etc. and adjust your UNDO_RETENTION and UNDO tablespace accordingly.
    Justin

Maybe you are looking for