ASA code version upgrade error

I just recently tried to upgrade the code version of a 5510 from 8.3(2) to 9.1 and got this error:
This is an ASA image and cannot be loaded on a PIX platform.
I was consoled into the firewall and watching it boot up, after that error it just said "rebooting..." and nothing ever happened. Can someone please shed some light on this as I have no idea why that error popped up and can't find any documentation about it. I tested the upgrade on a seperate 5510 to make sure it would work beforehand and didn't have any issues. Thanks in advance!

The problem is that the flash storage is corrupt. I have also received this error in the past. Power cycling did absolutely nothing to help, and I was not able to get far enough to boot from ROMMON to boot to another image. It was resolved simply by processing an RMA with Cisco Systems. Out of many hundreds of Cisco devices that I have installed, I have only experienced this happening one time. It seems (based on research) more common with the ASA for some reason. I have absolutely never had this happen with an ISR, or Catalyst switch. Of course, these are all rather different devices. This problem could just be specific to the ASA itself. I had it happen with a 5505. OP had this occur on a 5510. Perhaps this should be looked in to by the ASA dev. team if it has not already been addressed.

Similar Messages

  • 5510 code version upgrade

    I am looking to upgrade a 5510 that is currently on code version 8.0(4) to code version 9.1. I know I will have to upgrade to 1gb ram, but can i just upgrade straight to version 9.1 or do I need to follow an upgrade path? This is a standalone device so I am planning on downtime. Thanks in advance.

    Regarding the "any" keyword (9.0(x) Release Notes)
    "any" now means both ipv4 and ipv6. "any4" for only ipv4 and "any6" for ipv6 only
    Any Keyword
    Now that ACLs support both IPv4 and IPv6, the any keyword now represents "all IPv4 and IPv6 traffic." Any existing ACLs that use the any keyword will be changed to use the any4 keyword, which denotes "all IPv4 traffic."
    In addition, a separate keyword was introduced to designate "all IPv6 traffic": any6.
    Found at (Along with other information):
    Regarding the Xlate settings (9.0(x) Release Notes)
    Used to keep the original old software behaviour identical even when doing a software jump from old to new
    •Per-session  PAT disabled when upgrading— Starting in Version 9.0, by default, all  TCP PAT traffic and all UDP DNS traffic use per-session PAT (see the xlate per-session command  in the command reference). If you upgrade to Version 9.0 from an  earlier release, to maintain the existing functionality of multi-session  PAT, the per-session PAT feature is disabled during configuration  migration. The ASA adds the following deny rules:
    xlate per-session deny tcp any4 any4
    xlate per-session deny tcp any4 any6
    xlate per-session deny tcp any6 any4
    xlate per-session deny tcp any6 any6
    xlate per-session deny udp any4 any4 eq domain
    xlate per-session deny udp any4 any6 eq domain
    xlate per-session deny udp any6 any4 eq domain
    xlate per-session deny udp any6 any6 eq domain
    To enable per-session PAT after you upgrade, enter:
    clear configure xlate
    Found at:
    - Jouni

  • Version upgrade error JOB_RSVBCHCK_R

    Dear experts,
    As part of our test upgrade from SAP 46C to ECC 6.0 we faced an error in
    phase JOB_RSVBCHCK2, where upgrade phase list ToC suggests to check
    t-codes SMQ1,SM13 and we couldt find any outstanding update tasks, so we
    continued by ignoring the phase. Now one more error occured in
    JOB_RSVBCHCK_R phase,again we check the SMQ1,SM13 T-codes,didt find any
    outstanding update tasks. so when we try to ignore the task it is
    asking for password provided by SAP to ignore the phase.
    is it recommended to skip this phase?if yes does anyone have password to skip the phase?

    I know this was answered, but just wanted to post this for the greater good, in case someone else gets stuck as we did...
    During Prepare, we got this error
    A2EEMCEX 151 Entries for application "11" still exist in the extraction queue 
    Long text:
          Changing extraction structure &V#& for application &V#& is forbidden,
          because there are entries that have not yet been processed into an
          extraction queue for application &V#& for at least one client.
          If an extraction structure is changed to the entries that are still
          open in an extraction queue, then these are no longer able to be read
          and can cause terminations with the collective update.
        What to do
          Start the collective update using the function "Job Control" in the
          <DS:TRAN.LBWE>Logistics Extraction Structures Customizing Cockpit</>.
          To get an overview of the logistics extraction queues, see the
          <DS:TRAN.LBWQ>Logistics Queue Overview</>.
    During Prepare we clicked Ignore because we checked all the active clients on this QA box and nothing for those existing clients was in SMQ1 (or SM13 for that matter).  And in LBWE we had turned all the extractors to Inactive (because our BW system has been not operational for years, and we did not really need extractors RFCs running).
    Prepare ended with this error in the checks.log but we thought we could proceed with the SAPUp. 
    Then during the actual upgrade, we get the same error, only it won't let you past it without fixing it or getting a password from SAP.  One problem is - you can only login to client 000 at this point.  The other problem was that the Upgrade was checking these RFCs in a non-existent client!
    As prerequisite, we know that we have to go to SMQ1 (same as LBWQ) and delete any outbound RFC queues.  The problem in our QA box was that there were some from an old client 444 which did not exist.  So we can see these old RFCs pending from SMQ1 because it shows the client.  But SMQ1 doesn't let you delete entries from other clients.
    SAP has a ABAP RSTRFCQD which (per note 763255) deletes queue easily in background.  But this ABAP can't delete in other clients other than the client in which its executed.
    We tried recreating the client just so we could login and run this ABAP, but we did not have the SAP* password for that old client.
    We felt it was easier to just manually delete the entries rather than deleting SAP* and restarting the system. 
    So we just used SQL and deleted the entries from client 444 in the same table SAP's job RSVBCHCK was checking:
    delete from TRFCQOUT where QNAME = 'MCEX11' and MANDT = '444'
    delete from TRFCQOUT where QNAME = 'MCEX12' and MANDT = '444'
    Restarting the upgrade gets back the check in the phase of RSVBCHCK.
    In Production, we don't have extraneous clients, so this should not be a problem.

  • Unsupported java version, the error code is FMR 92095

    help me, i have a problem whit unsupported java version, the error code is FMR 92095. I am working whit os windows 7 and mozilla firefox.
    there are java version ?
    How i can download ?

    Try post a comment in B1DE 2.0.1 new version! blog.

  • Oracle Report Failing After Database Version Upgrade

    I have function code created in RDF file of oracle reports 10g as below-
    create or replace function clobblobtest (TMP_MID varchar2) return varchar is
    missed_text varchar2(1000) := '';
    v_time_stamp date;
    v_end_time date;
    cursor c1(c_time_stamp in date,
              c_mid in varchar2) is
           select mn.TEXT from msgnotes mn
      where mn.mid=c_mid
          and mn.create_date >= c_time_stamp;
    cursor c2(c_time_stamp in date,
              c_mid in varchar2,
              c_end_time in date) is
           select mn.TEXT from msgnotes mn
      where mn.mid=c_mid
          and mn.create_date >= c_time_stamp
          and mn.create_date <= c_end_time;
      IF ('1' = 'INWARD RETURN') then
        select bbi into missed_text from mtf1000 where mid=TMP_mid;
        ELSIF '1'='QPH Missed' then
      Select max(nj.update_date) into v_time_stamp
      from newjournal nj
      where nj.mid=TMP_mid and nj.status = 'CTOVRQ';
      for i in c1(v_time_stamp,TMP_mid) loop
      missed_text:=missed_text||' '||i.text;
      END Loop;
      ELSIF ('Rejected'='Rejected' OR 'REJECTED'='REJECTED') then
      Select min(nj.update_date),max(nj.ENDDATE) into v_time_stamp,v_end_time
      from newjournal nj
      where nj.mid=TMP_mid and nj.actionid2='16' and nj.actionid1 is null;
      for i in c2(v_time_stamp,TMP_mid,v_end_time) loop
      missed_text:=missed_text||' '||i.text;
      END Loop;
      Select max(nj.update_date) into v_time_stamp
      from newjournal nj
      where nj.mid=TMP_mid and nj.status = 'UNSETLED';
      for i in c1(v_time_stamp,TMP_mid) loop
      missed_text:=missed_text||' '||i.text;
      END Loop;
      END IF;
      ELSE missed_text := null;
      END IF;
    Note:- Text column from table msgnotes is of datatype CLOB.
    I have executed report having this function before oracle upgrade and it works fine.
    But when i am trying to execute report after oracle version upgrade from to with same data report fails with runtime error Rep-1401: '' Fatal PL/SQL Error.
    With New version we tried to typecast Text column from clob to varchar and executed report then it works... but report runs on old version without any explicit typecasting.
    Please note when i run and call this funtion from sql developer with upgraded database version it works fine.
    Please advise.

    This error can possibly depend on the fact that the PL/SQL engines are in different versions. When using SQL Developer you use the PL/SQL engine in the database. When using Oracle Reports you use the PL/SQL engine in the Oracle Reports Server (Web Logic Server even maybe). These versions - in the Forms and Reports realm - are different (read: a lower version) than the PL/SQL engine in the database.
    If I check what version I have in Oracle Forms, as an example, I get (Help in the Oracle Forms Builder menu) but in the database I have (select * from product_component_version;)
    That COULD be your to fix it I am not sure...

  • ASA multiple mode upgrade from 8.2.5 to 8.4.5 to 9.0.3

    I'm doing ASA  code upgrade with contexts  from 8.2.5 to 8.4.5 to 9.0.3 and I'm concerned about the NAT syntax with the new code. Should this automatically changed to the new syntax on all contexts or I have to do it manually. Anyone there with that experience, please advise. Thanks.
    Please reply to [email protected]

    I am actually working on a project right now really similar to yours.
    When are you planning to perform the Upgrade???
    As per Cisco documentation the Upgrade should be done from the system context!
    Migration will happen automatically:
    I created a post about it
    Rate all of the helpful posts!!!
    Follow me on

  • ABAP Trial Version SP12:Error while setting up transport environment

    Hi Folks,
    I have successfully installed ABAP trial SP12 on my notebook(XP) and have been able to create some objects.
    Thanks to very effective blogs by Manfred Lutz .
    Now, I'm trying to set up the transport environment as per the blog but face the following error when I execute the step 'Distribute and Activate TMS Configuration'
    Appreciate any help in solving the issue. I'm detailing below the error and the checks I had done.
    Could not start transport control program tp
    Message no. TP608 Diagnosis
    There was an attempt to start the transport control program tp using the local RFC interface. An error occurred here.
      Error code: 4
      RFC error text: timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'
    I did the following based on the long text and after searching the forum:
    Run program RSTPTEST to localize error.
    The program gave the following result for the RFC destination 'CALLTP_WindowsNT':
    ********RESULT OF RSTPTEST***********************************************
    "timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'#Timeout during connection setup (check that partner exists)"
    Run the connection test in SM59 for destination 'CALLTP_WindowsNT':
    The results were inconsistent. The connection test failed often but it was ok a few times.
    The details of the connection failure are as follows:
    *******CONNECTION FAILURE RESULTS******************************************************
    timeout during allocate / CPIC-CALL: 'ThSAPCMRCV' Timeout during connection setu
    ERROR: timeout during allocate
    LOCATION: SAP-Gateway on host JayNB / sapgw00
    DETAIL: no connect of TP D:\SAP\NSP\SYS\exe\run\tp.EXE from host JayNB after 2
    COMPONENT: SAP-Gateway
    COUNTER: 22
    MODULE: gwr3cpic.c
    LINE: 5873
    RETURN CODE: 242
    SUBRC: 0
    RELEASE: 700
    TIME: Sun Mar 23 11:07:53 2008
    VERSION: 2
    *(3) I then went to STMS and regenerated the RFC destinations and then ran the connection test. The result was OK.
    Now, I again execute the 'Distribute and Activate TMS Configuration'  step . It still gives the same error.
    When I run the connection test in SM59, it results in error.
    Further checks:***********************
    (a) The permissions for folder SAP in the local directory were done as instructed in the blog.
    (b) the directory path  /SAP/trans/bin had the following files:
    *TP_DOMAIN_NSP.PFL*  : the last modified date changes every time I execute 'Distribute and Activate TMS Configuration'.
    *DOMAIN*  :The last modified date is in the past. It does not change.
    Please inform how do I set up transport.
    Code Formatted by: Alvaro Tejada Galindo on Apr 1, 2008 4:43 PM

    Hi Krishna ,
    Thank you for the suggestion.
    I did as you suggested by inserting the mapping of ip and host in the hosts file.
    and restarted the server,but I still get the same error "could not start transport control program tp".
    Any other step that I'm missing.
    Thanks again

  • Upgradation Error

    I am getting an error during Upgrade.I am performing upgradation on AIX5.3,oracle10g, SAPr/3 to ECC6.
    running /usr/sap/put/exe/tp pf=/usr/sap/put/bin/SHDUPGIMP1.TPP put QAS
    WARNING: tp terminated with status 12
    analyzing result of tp call ...
          SAPup error message
    SAPup> ERROR: tp terminated with error status -1
                  See logfiles with extension .ECO for details.
    SAPup> ERROR: 8 errors detected during SHADOW_IMPORT_UPG1.
    SAPup> ERROR: 1 activities have been aborted in SHADOW_IMPORT_UPG1.
    SAPup> ERROR: Operation(s) not completely processed.
                  Remaining change requests found in buffer QAS.
                  Ignoring aborted import steps will cause severe inconsistencies
                  and will likely require a full repeat of the whole upgrade.
                  !!! Do not manipulate the import buffer !!!
                  Analyze summary error logfile SHDUPGIMP1.ELG
                  and remove all error conditions in the way
                  it is described in the upgrade manual. Repeat
                  this phase until it is error free.
                  Additional hints may be given in logfiles
                  SLOG700 and /usr/sap/put/log/SAPup.ECO
                - "continue"
                - "cancel"
    log form SHDUPGIMP1.ELG
    2EETW000 sap_dext called with msgnr "32":
    2EETW000 -
    db call info -
    2EETW000 function:   db_ntab (shadow)
    2EETW000 fcode:      NT_RDTDESCR
    2EETW000 tabname:    E070A~
    2EETW000 len:        6
    2EETW000 key:        E070A~
    2EETW000 retcode:    32
    1 ETP111 exit code           : "12"
    Log form SAPup.ECO
    ...started at 20081105094829
    Reading Parameter File "/usr/sap/put/bin/SHDUPGIMP1.TPP" at 20081105094829
    ...begin processing at 20081105094829 61810
    Reading Parameter File "/usr/sap/put/bin/DEFAULT.TP0" at 20081105094830
    Condition level 1, total => TRUE '#if 1 >= 0' => TRUE
    ..finished at 20081105094830 with status UNRESOLVED REQUESTS IN BUFFER.
    ...begin dialogue at 20081105094830
    ...end dialogue at 20081105095219
    ...begin dialogue at 20081105095219
    ...end dialogue at 20081105095220
    ..answered at 20081105095220.
    -> decided to try again.
    ...started at 20081105095220
    Reading Parameter File "/usr/sap/put/bin/SHDUPGIMP1.TPP" at 20081105095220
    ...begin processing at 20081105095220 62286
    Reading Parameter File "/usr/sap/put/bin/DEFAULT.TP0" at 20081105095221
    Condition level 1, total => TRUE '#if 1 >= 0' => TRUE
    ..finished at 20081105095221 with status UNRESOLVED REQUESTS IN BUFFER.
    ...begin dialogue at 20081105095221
    Give me some solution to resolve the above issue

    Thanks for reply.
    I have already applied the latest R3trans & tp in /usr/sap/put/exe.
    R3trans patch no. 183(kernel  release 700)
    Tp patch no.         179(kernel release 700)

  • Incompatible class versions :linkage error- JAVADOM

       We have done Mapping using java DOm,created ZIp file & successfully imported in IR.  
    My NWDS is using java 1.4.2_15
    we are using PI70/Sp09/Java Version 1.5.0_14
    During Execution in IE we  are getting this error.
    error -
    <SAP:Stack>Incompatible class versions (linkage error)</SAP:Stack>
    <Trace level="1" type="T">Interface Mapping http://XI/Mapping/JavaDom/DOMMapping4 IM_ORDER1_ORDER</Trace>
      <Trace level="1" type="T">LinkageError at JavaMapping.load(): Could not load class: CSJAVA/com/yash/xi/DOMMapping4</Trace>
      <Trace level="1" type="T">java.lang.NoClassDefFoundError: JAVA/com/xi/DOMMapping4 (wrong name: com//xi/DOMMapping4) at java.lang.ClassLoader.defineClass0
    shekar chandra

    Check the links they may help u out.
    Event or DOM parsing?
    XML Parsers: DOM and SAX Put to the Test

  • App-v 5.0 Client Package Installation - Error Code: 0C80070003 ( App v Error Code) 74F00F0C80070003 ( Internal error Code )

        I have converted my previous version package which was build upon 4.6, using sequencer to 5.0 app-v client.
    I didn't have any errors & warnings. But, when I tried to install the package , I'm getting the error with error code
    Error Code:
    0C80070003 ( App v Error Code)
    74F00F0C80070003 ( Internal error Code )

    Hi there, 
    It was my mistake and the way we published app connection groups in the past. In the past we published the applications directly through an connection group without publishing the applications themself. In app-v 5.0 sp3 I needed to publish the packages itself

  • DMM Version Mismatch Error

    I am running a TestStand sequence which makes a call to niDMM_init. Most times this works correctly, but intermittently I get error -1074117853 (every week or so, the function is may be called 50 times between failures)
    "Error, Version mismatch error! Please verify the installation of all NI-DMM components. You may need a newer version of NI-DMM"
    There are a large number of developers here who *may* be using different versions of NI-DMM on theor development machines to what is installed on the Test Rigs. This was my first thought - that perhaps there were some incompatibilities in DLL Ordinals between the various versions of NI-DMM. However, rebooting the rig and running the same sequence again allows it to work. Surely if this was the case - the problem would exist every time?
    Sadly I cant attach the sequence here (since the niDMM_init function is buried inside a code module and a sub dll inside that - but I have traced it through and it is the niDMM_init function returing the error).
    What I need to know is:
    Is there a problem with developing on one driver version and then running with another?
    If all the developers use the same versions of the drivers or at least compile the software with the same version - will this go away?
    Why is the problem intermittent?

    My mistake - posted to the wrong board. Have reposted in DMMs

  • HT4972 When I try to update my Ipod 4 touch software from 4.3.5 to the latest version, an error message comes in..."The ipod software update server cannot be contacted"

    When I try to update my Ipod 4 touch software from 4.3.5 to the latest version, an error message comes in..."The ipod software update server cannot be contacted"
    I have also tried downloading a separate 840MB file and manually update, but that doesnt work either

    See the chart below to determine whether you can upgrade your device and what you can upgrade to.
    IPhone, iPod Touch, and iPad iOS Compatibility Chart
         Device                                       iOS Verson
    iPhone 1                                       iOS 3.1.3
    iPhone 3G                                    iOS 4.2.1
    iPhone 3GS                                 iOS 6.1
    iPhone 4                                       iOS 6.1
    iPhone 4S                                    iOS 6.1
    iPhone 5                                       iOS 6.1
    iPod Touch 1                               iOS 3.1.3
    iPod Touch 2                               iOS 4.2.1
    iPod Touch 3                               iOS 5.1.1
    iPod Touch 4                               iOS 6.1
    iPod Touch 5                               iOS 6.1
    iPad 1                                           iOS 5.1.1
    iPad 2                                           iOS 6.1
    iPad 3                                           iOS 6.1
    iPad 4                                           iOS 6.1
    iPad Mini                                      iOS 6.1
    Select the method most appropriate for your situation.
    Upgrading iOS
       1. How to update your iPhone, iPad, or iPod Touch
       2. iPhone Support
       3. iPod Touch Support
       4. iPad Support
         a. Updating Your iOS to Version 6.0.x from iOS 5
              Tap Settings > General > Software Update
         If an update is available there will be an active Update button. If you are current,
         then you will see a gray screen with a message saying your are up to date.
         b. If you are still using iOS 4 — Updating your device to iOS 5 or later.
         c. Resolving update problems
            1. iOS - Unable to update or restore
            2. iOS- Resolving update and restore alert messages

  • "Invalid access code (Bad parameter)" error encountered when trying to import VSS DB into TFS 2012

    I'm trying to import a VSS DB into TFS 2012 using the VSS Upgrade Wizard.
    However, I'm getting an "Invalid access code (Bad parameter)" error when I click the "List Available Projects" link button.
    I have been able to get the wizard going with a different VSS DB, but not this one.
    How can I fix this and get the import going?

    Thank you for your post.
    Do you use OLE Automation objects when you log on VSS? Please refer to this
    FIX: VSS OLE Automation Error Message "Bad Access Parameter"
    Lily Wu
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

  • Is Intraoperative patch need for DB version Upgrade in 11i ?

    Dear All,
    I need to apply ATG RUP7 in 11i instance, but the database should be greater than version otherwise it is not possible,, Am i correct .
    Ok now am Upgrading the DB version to then planning to apply ATG RUP7 , then how the Application will work because the application was running in ebiz release version now upgraded Is there any Intero Patch for application.

    Dear hussien,
    Thank u very much,, i have restarted the installation but again failed with some other reason,, now i am not in hurry,, i restored the old backup and released the instance.
    Can u explain me,, i failed in the last part of this version upgrade. that is while running "catpatch.sql", yes its known issue but still i failed several times to run successfully.
    i am getting error like this below:
    The following statement may cause an
    ORA - 29554: unhanded Java out of memory condition error
    If so, this is because there is insufficient system tablespace,
    shared or java pool size, or some other resource value is too small.
    An additional message describing the problem will be output of the statement.
    PL /SQL procedure successfully completed.first of all i have resized the system tablespace, then i changed the shared_pool_size 150m, previously it was 260M by default, and changed java_pool_size 150M previously it was 64M. then started the database with migrate option and i ran the catpatch.sql.
    Obviously it must complete successfully,, but it failed,
    note: its EBS database

  • LabView 6.0 Evaluation version load error (20)

    I wrote three vi files in LabView 6.0 evaluation version. Afte instaling the 6.1 full version the vi could not be load, giving a code 20 load error. All other vi files loaded normally.
    I could not find any special instructions in these files.
    Any ideas?
    Bessel_Function_j(x) ‏146 KB ‏58 KB
    Read_File+_[V8].vi ‏67 KB

    Refer to the following KnowledgeBase on our website:
    Cyril Bouton
    Applications Engineer
    National Instruments
    Cyril Bouton
    Active LabVIEW Developper

Maybe you are looking for

  • License error when starting evaluation copy of Weblogic Server 7.0

    I have evaluation Copy of bea WL Platform 7.0 on CD. I installed it, obtained the license key and put it in the BEA home directory. Tried to run weblogic server, but it would not run and complains that I didn't have the valid license. Did somebody ha

  • Mail 5: Change font size in Mailboxes column?

    Pretty happy with Mail 5 so far (one day in). Is there any way to change the font size for the left Mailboxes column? It's larger than the other two, and larger than I prefer.

  • Call Recorder ++ has suddenly started crashing & wont open

    ‎I have written to the App developer's tech support 4 times in a week now without the courtesy of a reply so.i thought I would try this board for help.  The app in question is Call Recorder ++ by Ajani InfoTech Private Limited. Version The ap

  • Photos (thumbnails) in iPod Classic got "corrupted"

    I have no idea of how to describe with words, this is a shot of what's going on with my iPod. It happens on some photos in my iPod, they can be viewed as normal pictures by clicking the centre butto

  • How to achieve this?

    Hi Friends, I'm facing one strange problem. Not able to figure it out how to get it. Basically, not able to identify a particular window to let oracle understand how to behave. Let's find the problem -> Oracle Version -> SQL> select * from v$version;