IPS Auto Update Error

I am having an issue with the IPS. I have configured it for auto update and I am trying to download a new signature package. It seems to be working. However, once it comes across the package to download, it gives me this error:
evError: eventId=1232049941352795438 severity=error vendor=Cisco
originator:
hostId: xxxxips11
appName: mainApp
appInstanceId: 347
time: 2009/01/29 15:22:03 2009/01/29 10:22:03 GMT-05:00
errorMessage: name=errSystemError autoUpdate successfully selected a package () from the cisco.com locator service, however, package download failed: This package file does not have the required .pkg extension
I know that it is trying to download the correct package because I get this message prior:
evStatus: eventId=1232049941352795436 vendor=Cisco
originator:
hostId: xxxxips11
appName: mainApp
appInstanceId: 342
time: 2009/01/29 15:22:03 2009/01/29 10:22:03 GMT-05:00
autoUpgradeServerCheck:
uri: xxxxxx@//
packageFileName: IPS-sig-S378-req-E3.pkg
result: status=true
Does anyone know what this could possibly be?

Upgrade IPS MC and Security Monitor to 2.2.

Similar Messages

  • WRVS4400NV2 IPS now blocking Cisco IPS Auto Update Server

    Yesterday I noted that my ASA5505 AIP-SSC5 card was failing to auto  update as it had been doing without issue for months. I looked in the logs and the IPS was  showing an HTTP Error when attempting to update. I checked and nothing  had changed in the IPS configuration. Then, on a hunch, I checked the IPS log of the WRVS4400N which is the edge router for the small business network.
    The WRVS4400N IPS was blocking connections with the cisco auto update  server because it detected an RPC Anomaly in the traffic. So apparently,  something has changed in the cisco IPS auto update server (https://198.133.219.25//cgi-bin/front.x/ida/locator/locator.pl) response that the cisco small business router misidentifies as a threat. . .
    FYI-I also posted this issue to the small business router community discussion forum.

    Yesterday I noted that my ASA5505 AIP-SSC5 card was failing to auto  update as it had been doing without issue for months. I looked in the logs and the IPS was  showing an HTTP Error when attempting to update. I checked and nothing  had changed in the IPS configuration. Then, on a hunch, I checked the IPS log of the WRVS4400N which is the edge router for the small business network.
    The WRVS4400N IPS was blocking connections with the cisco auto update  server because it detected an RPC Anomaly in the traffic. So apparently,  something has changed in the cisco IPS auto update server (https://198.133.219.25//cgi-bin/front.x/ida/locator/locator.pl) response that the cisco small business router misidentifies as a threat. . .
    FYI-I also posted this issue to the small business router community discussion forum.

  • IOS IPS auto-update

    Hi,
    I have a couple of questions I hope people could answer:
    1) What recommendations/options are available for downloading signature files to a HTTP/TFTP server prior to having the IOS IPS device pull them from the server?  Is their a way to automate the HTTP/TFTP server downloading the signatures? (Cron job or such)
    2) Does the signature file name change each time a new signature file is released? If it does, would I have to go back to the router to update the URL string that is configured in the ip ips auto-update section? I would hate to have to update 200 CPE devices each time a new signature file is released.
    Hoping someone could answer these or help point me in the right direction to find the answer out.
    regards M

    I found this link with answers my one question.
    Cisco IOS Intrusion Prevention System (IPS)
    Tuning, Deploying and Updating Cisco IOS IPS Signature Sets For Multiple-Device Deployments
    http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6586/ps6634/white_paper_c11_549300.html

  • IPS Auto update - http error response

    Hi
    I am having trouble doing auto signature update on my AIP-SSM. This is what i am getting on #show statistics host
    Auto Update Statistics
    lastDirectoryReadAttempt = 11:00:08 GMT+08:00 Mon Jul 06 2009
    = Read directory: https://198.133.219.25//cgi-bin/front.x/ida/locator/locator.pl
    = Error: http error response: 500
    lastDownloadAttempt = N/A
    lastInstallAttempt = N/A
    nextAttempt = 12:00:00 GMT+08:00 Mon Jul 06 2009
    Fyi..my CCO credentials are perfectly fine, as i am able to download signature files manually from Cisco Download site.
    Please advise

    If you are looking at the Auto Update Statistics in your sh tech, you can see a "http error response: 500" This is an internal web server error. Are you sure there is nothing between the AIP-SSM and the internet besides the ASA? Maybe there is an embedded web server like Barracuda? Do you know if your ISP is providing proxy services for you?

  • IPS Auto Update 5525X

    Hello,
    I have two IPS ASA5525-IPS "module" of 5525-X Firewall.
    I set the proxy connection in DNS/Proxy Settings for update the signatures, but, i receive an error above:
    Auto Update Statistics
       lastDirectoryReadAttempt = 11:03:09 GMT-03:00 Wed Jan 09 2013
        =   Read directory: https://198.133.219.25//cgi-bin/front.x/ida/locator/locator.pl
        =   Error: AutoUpdate exception: HTTP connection failed [1,110]
       lastDownloadAttempt = N/A
       lastInstallAttempt = N/A
       nextAttempt = 11:00:00 GMT-03:00 Thu Jan 10 2013
    Auxilliary Processors Installed
    Testing the connection i can see the packet direct in my firewall, and not passing over the proxy, i need the IPS use the proxy to update signatures.
    The configuration looks okay for me.
    Any sugestions?
    Tks a lot.

    Hi,
    This enhancement to use proxy server for updates would be available in future release. (CSCsv89560)
    Regards,
    Sawan Gupta

  • IPS Auto Update failing

    I've configured the signature auto update via the GUI and CLI but receive the same error:
    evError: eventId=1210198298109812431 vendor=Cisco severity=error
    originator:
    hostId: LON-Sensor
    appName: mainApp
    appInstanceId: 341
    time: Jun 06, 2008 03:00:07 UTC offset=60 timeZone=BST
    errorMessage: MainApplication::downloadAndStartUpdate Error status returned with status str Found name=errSystemError
    Any ideas? I've rebooted both the IPS & ASA in the hope that would resolve the problem to no avail. I have another ASA/IPS in a different site and that works ok.

    Hi, I got the information :)
    show stat host
    General Statistics
    Last Change To Host Config (UTC) = 14-Jan-2009 14:38:43
    Command Control Port Device = GigabitEthernet0/0
    Network Statistics
    = ge0_0 Link encap:Ethernet HWaddr 00:13:C4:80:C3:C1
    = inet addr:192.168.1.11 Bcast:192.168.1.255 Mask:255.255.255.0
    = UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    = RX packets:25375769 errors:0 dropped:0 overruns:0 frame:0
    = TX packets:2411636 errors:0 dropped:0 overruns:0 carrier:0
    = collisions:0 txqueuelen:1000
    = RX bytes:2570835196 (2.3 GiB) TX bytes:657595036 (627.1 MiB)
    = Base address:0xbc00 Memory:f8200000-f8220000
    NTP Statistics
    status = Not applicable
    Memory Usage
    usedBytes = 660455424
    freeBytes = 372043776
    totalBytes = 1032499200
    CPU Statistics
    Usage over last 5 seconds = 31
    Usage over last minute = 40
    Usage over last 5 minutes = 36
    Memory Statistics
    Memory usage (bytes) = 660455424
    Memory free (bytes) = 372043776
    Auto Update Statistics
    lastDirectoryReadAttempt = 08:40:00 GMT-06:00 Wed Feb 04 2009
    = Read directory: https://198.133.219.25//cgi-bin/front.x/ida/locator/locator.pl
    = Error: AutoUpdate exception: HTTP connection failed [1,111]
    lastDownloadAttempt = N/A
    lastInstallAttempt = N/A
    nextAttempt = 08:40:00 GMT-06:00 Thu Feb 05 2009
    Auxilliary Processors Installed.
    ! Current configuration last modified Mon Jan 19 17:15:14 2009
    ! Version 6.2(1)
    ! Host:
    ! Realm Keys key1.0
    ! Signature Definition:
    ! Signature Update S379.0 2009-01-30
    ! Virus Update V1.4 2007-03-02
    service interface
    exit
    service authentication
    exit
    service event-action-rules rules0
    overrides deny-attacker-inline
    override-item-status Enabled
    risk-rating-range 90-100
    exit
    exit
    service host
    network-settings
    host-ip 192.168.1.11/24,192.168.1.1
    host-name sensor
    telnet-option disabled
    access-list 10.254.254.0/24
    access-list 192.168.1.0/24
    exit
    time-zone-settings
    offset -360
    standard-time-zone-name GMT-06:00
    exit
    auto-upgrade
    cisco-server enabled
    schedule-option calendar-schedule
    times-of-day 08:40:00
    days-of-week monday
    days-of-week tuesday
    days-of-week wednesday
    days-of-week thursday
    exit
    user-name ********
    password ********
    cisco-url https://198.133.219.25//cgi-bin/front.x/ida/locator/locator.pl
    exit
    exit
    exit
    service logger
    exit
    service network-access
    exit
    service notification
    exit
    service signature-definition sig0
    signatures 9430 1
    status
    enabled true
    exit
    exit
    signatures 11018 1
    status
    enabled true
    exit
    exit
    signatures 12000 0
    status
    enabled true
    exit
    exit
    signatures 12003 0
    status
    enabled false
    exit
    exit
    signatures 12020 0
    status
    enabled true
    exit
    exit
    exit
    service ssh-known-hosts
    exit
    service trusted-certificates
    exit
    service web-server
    exit
    service anomaly-detection ad0
    exit
    service external-product-interface
    exit
    service health-monitor
    memory-usage-policy
    enable true
    exit
    exit
    service analysis-engine
    virtual-sensor vs0
    physical-interface GigabitEthernet0/1
    exit
    exit

  • IPS Auto Update Failure

    Hi,
    I have auto update enabled in my AIP SSM 10 , at the time of auto updates i have observed the following messages in Console
    "Broadcast Message from IPS
    Applying update IPS-sig-S766-req-E4"
    It remains in this condition and then i have to do a hw-module reset to get it back again , moreover updates which were downloaded arent applied.
    Kindly Help

    When signature auto-update failures are diagnosed, look at the HTTP             error codes.
    IPS# show statistics host
    Auto Update Statistics
    lastDirectoryReadAttempt = 19:31:09 CST Thu Nov 18 2010
    = Read directory: https://72.163.4.161//cgi-bin/front.x/ida/locator/locator.pl
    = Error: AutoUpdate exception: HTTP connection failed [1,110]   <--
    lastDownloadAttempt = 19:08:10 CST Thu Nov 18 2010
    lastInstallAttempt = 19:08:44 CST Thu Nov 18 2010
    nextAttempt = 19:35:00 CST Thu Nov 18 2010
    Message Meaning
    Error: AutoUpdate exception: HTTP connection failed                           [1,110]
    Authentication failed. Check the username and                           password.
    status=false AutoUpdate exception: Receive HTTP response                           failed [3,212]
    The request to the Auto Update server timed                           out.
    Error: http error response: 400
    Make sure the cisco-url setting is defaulted. If the CCO ID                           is greater than 32 characters in length, try a different CCO ID. This can be a                           limitation on the Cisco download server.
    Error: AutoUpdate exception: HTTP connection failed                           [1,0]
    Network issue prevented download or there is a potential                           issue with the download servers.
    and also keep in mind that CCO username should not contain any special characters, for             example, @ . Refer to Cisco bug ID CSCsq30139  (registered customers only)          for more             information.

  • ASA IPS, auto update issue

    Hi,
    I am having an issue with auto update on the IPS module installed the ASA.
    Auto Update Statistics
    lastDirectoryReadAttempt = 06:00:34 UTC Wed Feb 23 2009
    = Read directory: https://198.133.219.25//cgi-bin/front.x/ida/locator/loca
    tor.pl
    = Error: AutoUpdate exception: Receive HTTP response failed [3,212]
    lastDownloadAttempt = N/A
    lastInstallAttempt = N/A
    nextAttempt = 06:00:00 UTC Thu Feb 24 2009
    I can see from the above that there is a HTTP response error, I have checked and there does not seem to be any other unit stopping the responses. With regards to the ASA config do I need to allow the IPS module though the ACL's or NAT statements?
    Many thanks MJ

    Hi
    Many thanks for the respose.
    Sorry I have not made any progress with this as yet: the only thing I have done is us the packet tracer, which passed I am just going to check the route of the packet once it has left the interface as it has got to be that or the URL is wrong.
    Regards MJ

  • Air Auto Update Error -- Flash Builder Burrito.

    This is my first attempt at this, so I may be missing something simple.
    I'm not having any luck getting an Air app to automatically update.
    If I manually go to  http://localhost/air1/air1.air and redownload the file I will get a popup that asks if I want to update the app, but when I say ok I get this error.
    "There was an error checking for updates. Error# 16816"
    I haven't found a reason yet,
    Any ideas?
    update.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <update xmlns="http://ns.adobe.com/air/framework/update/description/2.5">
      <version>2.0</version>
      <url>http://localhost/air1/air1.air</url>
      <description>1.0 - First version</description>
    </update>
    file -- air1.mxml
    <?xml version="1.0" encoding="utf-8"?>
    <s:WindowedApplication xmlns:fx="http://ns.adobe.com/mxml/2009"
                           xmlns:s="library://ns.adobe.com/flex/spark"
                           xmlns:mx="library://ns.adobe.com/flex/mx"
                           applicationComplete="init()">
        <fx:Declarations>
            <!-- Place non-visual elements (e.g., services, value objects) here -->
        </fx:Declarations>
        <fx:Script>
            <![CDATA[
                import air.update.events.UpdateEvent;
                import air.update.ApplicationUpdaterUI;
                import mx.controls.Alert;
                protected var appUpdater:ApplicationUpdaterUI = new ApplicationUpdaterUI(); // Used for auto-update
                protected function init():void
                    // Check for update
                    this.checkUpdate();
                    Alert.show("checking update");
                // This function is triggered when the application finished loading.
                // Initialize appUpdater and set some properties
                protected function checkUpdate():void
                    // set the URL for the update.xml file
                    appUpdater.updateURL = "http://localhost/air1/update.xml";
                    appUpdater.addEventListener(UpdateEvent.INITIALIZED, onUpdate);
                    appUpdater.addEventListener(ErrorEvent.ERROR, onUpdaterError);
                    // Hide the dialog asking for permission for checking for a new update.
                    // If you want to see it just leave the default value (or set true).
                    appUpdater.isCheckForUpdateVisible = true;
                    appUpdater.initialize();
                // Handler function triggered by the ApplicationUpdater.initialize.
                // The updater was initialized and it is ready to take commands.
                protected function onUpdate(event:UpdateEvent):void
                    // start the process of checking for a new update and to install
                    appUpdater.checkNow();
                // Handler function for error events triggered by the ApplicationUpdater.initialize
                protected function onUpdaterError(event:ErrorEvent):void
                    Alert.show(event.toString());
            ]]>
        </fx:Script>
        <s:Button x="47" y="55" label="Button"/>
        <mx:ColorPicker x="61" y="119"/>
        <s:ComboBox x="77" y="216"/>
        <s:ComboBox x="77" y="185"/>
        <s:ComboBox x="77" y="154"/>
    </s:WindowedApplication>
    file  -- air1-app.xml
    <?xml version="1.0" encoding="utf-8" standalone="no"?>
    <application xmlns="http://ns.adobe.com/air/application/2.5">
    <!-- Adobe AIR Application Descriptor File Template.
        Specifies parameters for identifying, installing, and launching AIR applications.
        xmlns - The Adobe AIR namespace: http://ns.adobe.com/air/application/2.5
                The last segment of the namespace specifies the version
                of the AIR runtime required for this application to run.
        minimumPatchLevel - The minimum patch level of the AIR runtime required to run
                the application. Optional.
    -->
        <!-- A universally unique application identifier. Must be unique across all AIR applications.
        Using a reverse DNS-style name as the id is recommended. (Eg. com.example.ExampleApplication.) Required. -->
        <id>air1</id>
        <!-- Used as the filename for the application. Required. -->
        <filename>air1</filename>
        <!-- The name that is displayed in the AIR application installer.
        May have multiple values for each language. See samples or xsd schema file. Optional. -->
        <name>air1</name>
        <!-- A string value of the format <0-999>.<0-999>.<0-999> that represents application version which can be used to check for application upgrade.
        Values can also be 1-part or 2-part. It is not necessary to have a 3-part value.
        An updated version of application must have a versionNumber value higher than the previous version. Required for namespace >= 2.5 . -->
        <versionNumber>2.0.0</versionNumber>
        <!-- A string value (such as "v1", "2.5", or "Alpha 1") that represents the version of the application, as it should be shown to users. Optional. -->
        <!-- <versionLabel></versionLabel> -->
        <!-- Description, displayed in the AIR application installer.
        May have multiple values for each language. See samples or xsd schema file. Optional. -->
        <!-- <description></description> -->
        <!-- Copyright information. Optional -->
        <!-- <copyright></copyright> -->
        <!-- Publisher ID. Used if you're updating an application created prior to 1.5.3 -->
        <!-- <publisherID></publisherID> -->
        <!-- Settings for the application's initial window. Required. -->
        <initialWindow>
            <!-- The main SWF or HTML file of the application. Required. -->
            <!-- Note: In Flash Builder, the SWF reference is set automatically. -->
            <content>[This value will be overwritten by Flash Builder in the output app.xml]</content>
            <!-- The title of the main window. Optional. -->
            <!-- <title></title> -->
            <!-- The type of system chrome to use (either "standard" or "none"). Optional. Default standard. -->
            <!-- <systemChrome></systemChrome> -->
            <!-- Whether the window is transparent. Only applicable when systemChrome is none. Optional. Default false. -->
            <!-- <transparent></transparent> -->
            <!-- Whether the window is initially visible. Optional. Default false. -->
            <!-- <visible></visible> -->
            <!-- Whether the user can minimize the window. Optional. Default true. -->
            <!-- <minimizable></minimizable> -->
            <!-- Whether the user can maximize the window. Optional. Default true. -->
            <!-- <maximizable></maximizable> -->
            <!-- Whether the user can resize the window. Optional. Default true. -->
            <!-- <resizable></resizable> -->
            <!-- The window's initial width in pixels. Optional. -->
            <!-- <width></width> -->
            <!-- The window's initial height in pixels. Optional. -->
            <!-- <height></height> -->
            <!-- The window's initial x position. Optional. -->
            <!-- <x></x> -->
            <!-- The window's initial y position. Optional. -->
            <!-- <y></y> -->
            <!-- The window's minimum size, specified as a width/height pair in pixels, such as "400 200". Optional. -->
            <!-- <minSize></minSize> -->
            <!-- The window's initial maximum size, specified as a width/height pair in pixels, such as "1600 1200". Optional. -->
            <!-- <maxSize></maxSize> -->
        <autoOrients>false</autoOrients>
        <fullScreen>false</fullScreen>
        <visible>false</visible>
      </initialWindow>
        <!-- We recommend omitting the supportedProfiles element, -->
        <!-- which in turn permits your application to be deployed to all -->
        <!-- devices supported by AIR. If you wish to restrict deployment -->
        <!-- (i.e., to only mobile devices) then add this element and list -->
        <!-- only the profiles which your application does support. -->
        <!-- <supportedProfiles>desktop extendedDesktop mobileDevice extendedMobileDevice</supportedProfiles> -->
        <!-- The subpath of the standard default installation location to use. Optional. -->
        <!-- <installFolder></installFolder> -->
        <!-- The subpath of the Programs menu to use. (Ignored on operating systems without a Programs menu.) Optional. -->
        <!-- <programMenuFolder></programMenuFolder> -->
        <!-- The icon the system uses for the application. For at least one resolution,
        specify the path to a PNG file included in the AIR package. Optional. -->
        <!-- <icon>
            <image16x16></image16x16>
            <image32x32></image32x32>
            <image36x36></image36x36>
            <image48x48></image48x48>
            <image72x72></image72x72>
            <image128x128></image128x128>
        </icon> -->
        <!-- Whether the application handles the update when a user double-clicks an update version
        of the AIR file (true), or the default AIR application installer handles the update (false).
        Optional. Default false. -->
        <!-- <customUpdateUI></customUpdateUI> -->
        <!-- Whether the application can be launched when the user clicks a link in a web browser.
        Optional. Default false. -->
        <!-- <allowBrowserInvocation></allowBrowserInvocation> -->
        <!-- Listing of file types for which the application can register. Optional. -->
        <!-- <fileTypes> -->
            <!-- Defines one file type. Optional. -->
            <!-- <fileType> -->
                <!-- The name that the system displays for the registered file type. Required. -->
                <!-- <name></name> -->
                <!-- The extension to register. Required. -->
                <!-- <extension></extension> -->
                <!-- The description of the file type. Optional. -->
                <!-- <description></description> -->
                <!-- The MIME content type. -->
                <!-- <contentType></contentType> -->
                <!-- The icon to display for the file type. Optional. -->
                <!-- <icon>
                    <image16x16></image16x16>
                    <image32x32></image32x32>
                    <image48x48></image48x48>
                    <image128x128></image128x128>
                </icon> -->
            <!-- </fileType> -->
        <!-- </fileTypes> -->
        <!-- Specify Android specific tags that get passed to AndroidManifest.xml file. -->
        <!--<android>
            <manifestAdditions>
            <![CDATA[
                <manifest android:installLocation="auto">
                    <uses-permission android:name="android.permission.INTERNET"/>
                    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
                    <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/>
                    <uses-configuration android:reqFiveWayNav="true"/>
                    <supports-screens android:normalScreens="true"/>
                    <uses-feature android:required="true" android:name="android.hardware.touchscreen.multitouch"/>
                    <application android:enabled="true">
                        <activity android:excludeFromRecents="false">
                            <intent-filter>
                                <action android:name="android.intent.action.MAIN"/>
                                <category android:name="android.intent.category.LAUNCHER"/>
                            </intent-filter>
                        </activity>
                    </application>
                </manifest>
            ]]>
            </manifestAdditions>
        </android> -->
        <!-- End of the schema for adding the android specific tags in AndroidManifest.xml file -->
    </application>

    This appears to be a Flex question. Please try posting to the Flex forums here http://forums.adobe.com/community/flex/flex_general_discussion for better response.

  • IPS auto update

    Hello, Customers having IPS 4215 version 6.0(5)E3 are having their sensor crashing following auto update from an FTP server.
    The web interface is no more accessible and the analysis engine stopped( I've attached the show tech-support)
    The problem happened with different signatures S383 and S384, please advise

    Having a 4215 sensor crash on a signature update is a very common event.
    The 4215 sensors only have 512 MB or RAM (most sensors have 1 or 2 GB), this has caused many problems during the update process.
    You can try rebooting the sensor several times, if that doesnt bring it back to life, you can try resetting the signature policy back to default, if that doesn't help you'll need to open a TAC case to modify some of the signature build time memory parmeters.

  • IOS IPS auto-update without CSM

    Hi,
    We have 400 x 1811 router on which we need to update the IPS signature definition and custom signature.
    What is the best way to do it withou running CSM ?
    According to Cisco documentation, we need to add the auto-update command with an .XML extention. But when we load a .pkg in a router, the output is 4 different files. Unfortunalty we can auto-update only one file. Which one to I need to load on our TFTP server ?
    All the exemples of Cisco are using one single XML file.
    Does a single file with the signature defenition, category, default and type exist ?
    Since all our router have the same IPS config, I tought I could use one router at the central office with the configuration we want. And by someway asking the remote routers to auto-update their XML file on that router on which I would have activated a TFTP server.
    Anyone ever had to upgrade a lot of router IOS IPS signature?

    This can now be done in the 15.1T branch using cisco.com to download the update directly, see :
    http://www.cisco.com/en/US/docs/ios/15_1/release/notes/151TNEWF.html#wp1040750
    http://www.cisco.com/en/US/docs/ios/sec_data_plane/configuration/guide/sec_ips5_sig_fs_ue.html#wp1137583

  • IPS auto-update vs manual download

    Is there a delay in what's available via auto-update and updates that are available for manual download through cisco.com?  I noticed today that S498 became available yesterday, but my IPS module in my ASA hasn't downloaded it automatically yet.  When I do a #sh statistics host, I have a recent download attempt that says "Success: No installable auto update package found on server.
    Just wondering if there is a delay between manual and auto updates or if I need to be concerned that my auto-udpates aren't working properly.
    Thanks!

    The "lastDirectoryReadAttempt" is when the last check occurred (should match your scheduled timing).  If the status is that there is no available update, that is as far as the process goes.  If an update is available, the sensor should attempt to download.
    The "lastDownloadAttempt" will indicate the last time an update download was found and the download was attempted.
    The "lastInstallAttempt" will indicate the last time an update was downloaded and install initiated.
    It does look like it checked at a point today and did not find an available update.  That your outputs are UTC, I cannot correlate when the check today was run in relation to the publishing of the latest update.  It may be that there is a cache engine between your sensor and Cisco, and it is indicating that there is nothing available.  I would give the process another 24 hours to update.
    Scott

  • IPS Auto Update not working

    The auto update is not working on the IPS. The current signature version is S502 but my IPS is S479
    show statistics host output
    Auto Update Statistics
       lastDirectoryReadAttempt = 05:35:12 GMT-05:00 Mon Jul 26 2010
        =   Read directory: https://198.133.219.25//cgi-bin/front.x/ida/locator/locator.pl
        =   Success: No installable auto update package found on server
       lastDownloadAttempt = N/A
       lastInstallAttempt = N/A
       nextAttempt = 05:35:00 GMT-05:00 Tue Jul 27 2010
    Auxilliary Processors Installed
    show version output
    Application Partition:
    Cisco Intrusion Prevention System, Version 6.1(1)E3
    Host:
        Realm Keys          key1.0
    Signature Definition:
        Signature Update    S479.0                   2010-03-19
        Virus Update        V1.4                     2007-03-02
    OS Version:             2.4.30-IDS-smp-bigphys
    Platform:               ASA-SSM-10
    Serial Number:          JAF10241017
    Licensed, expires:      03-Sep-2010 UTC
    S479.

    It looks like the issue is that the IPS is running the E3 engine (6.1(1)E3).  All new updates require the E4 engine, so you'll have to update the sensor to 6.2(2)E4 or 7.0(4)E4.  Upgrade links and instructions can be found here:
    https://supportforums.cisco.com/docs/DOC-12212

  • AIR Auto update error

    Hello all,
    I am trying to build an autoupdate app in AIR using FB4. I use the code :
    import flash.system.System;
            import flash.events.ErrorEvent;
            import air.update.ApplicationUpdaterUI;
            import air.update.events.UpdateEvent;
            [Bindable]
            private var appUpdater:ApplicationUpdaterUI = new ApplicationUpdaterUI();
    protected function checkForUpdate():void {
                NativeApplication.nativeApplication.addEventListener( Event.EXITING,
                    function(e:Event):void {
                        var opened:Array = NativeApplication.nativeApplication.openedWindows;
                        for (var i:int = 0; i < opened.length; i ++) {
                            opened[i].close();
                setApplicationVersion();
                appUpdater.updateURL = "http://localhost/updateTest/update.xml";
                appUpdater.isCheckForUpdateVisible = false;
                appUpdater.addEventListener(UpdateEvent.INITIALIZED, onUpdate);
                appUpdater.addEventListener(ErrorEvent.ERROR, onError);
                appUpdater.initialize();
            protected function onError(event:ErrorEvent):void {
                Alert.show(event.toString());
            protected function onUpdate(event:UpdateEvent):void {
                appUpdater.checkNow();
            protected function setApplicationVersion():void {
                var appXML:XML = NativeApplication.nativeApplication.applicationDescriptor;
                var ns:Namespace = appXML.namespace();
                ver.text = "Current version is " + appXML.ns::version;
    whats wrong in the above code.... when the checkForUpdate function initiated an error occured :
    TypeError: Error #1007: Instantiation attempted on a non-constructor.
        at mx.controls::ProgressBar/createChildren()
        at mx.core::UIComponent/initialize()[E:\dev\beta1\frameworks\projects\framework\src\mx\core\ UIComponent.as:6510]
        at mx.core::UIComponent/http://www.adobe.com/2006/flex/mx/internal::childAdded()[E:\dev\beta1\frameworks\projects\ framework\src\mx\core\UIComponent.as:6402]
        at mx.core::Container/http://www.adobe.com/2006/flex/mx/internal::childAdded()[E:\dev\beta1\frameworks\projects\ framework\src\mx\core\Container.as:3879]
        at mx.core::Container/addChildAt()[E:\dev\beta1\frameworks\projects\framework\src\mx\core\Co ntainer.as:2541]
        at mx.core::Container/addChild()[E:\dev\beta1\frameworks\projects\framework\src\mx\core\Cont ainer.as:2459]
        at ApplicationUpdaterDialogs/_ApplicationUpdaterDialogs_ApplicationUpdaterVBox10_c()
        at mx.core::DeferredInstanceFromFunction/getInstance()[E:\dev\beta1\frameworks\projects\fram ework\src\mx\core\DeferredInstanceFromFunction.as:105]
        at mx.states::AddChild/createInstance()
        at mx.states::AddChild/set targetFactory()
        at ApplicationUpdaterDialogs/_ApplicationUpdaterDialogs_AddChild8_i()
        at ApplicationUpdaterDialogs/_ApplicationUpdaterDialogs_State7_c()
        at ApplicationUpdaterDialogs()
        at _ApplicationUpdaterDialogs_mx_managers_SystemManager/create()
        at mx.managers::SystemManager/initializeTopLevelWindow()[E:\dev\beta1\frameworks\projects\fr amework\src\mx\managers\SystemManager.as:3581]
        at mx.managers::SystemManager/http://www.adobe.com/2006/flex/mx/internal::docFrameHandler()[E:\dev\beta1\frameworks\proj ects\framework\src\mx\managers\SystemManager.as:3400]
        at mx.managers::SystemManager/docFrameListener()[E:\dev\beta1\frameworks\projects\framework\ src\mx\managers\SystemManager.as:3258]

    Just Got The Solution for Error 16811 &  16816
    Note Following things to avoide update error
    No 1.>
    You xml schema for update descriptor.xml in  server should look similar to this
    <?xml version="1.0" encoding="utf-8"?>
    <update xmlns="http://ns.adobe.com/air/framework/update/description/2.5">
      <versionNumber>2.0</versionNumber>
      <url>http://localhost/SerialHunter/SerialHunter.air</url>
      <description><![CDATA[
    SerialHunter Version 2.0 by Rajendra Khope
    This new version includes:
        * AutoUpdate
        * Enhaced UI functions
        * Ability to add providers       
      ]]></description>
    </update>
    Note xmlns="http://ns.adobe.com/air/framework/update/description/2.5"
    and versionNumber instead of version
    Also make similar changes in appxml version field (in Burrito its by default versionNumber )
    No 2>
    if u are using code to display veesion number make sure it should look like:
    var appXML:XML = NativeApplication.nativeApplication.applicationDescriptor;
    var ns:Namespace = appXML.namespace();
    pnlMain.title=appXML.ns::name+" v "+appXML.ns::versionNumber
    Thats it...!
    Rajendra Khope
    bkrajendra at gmail dot com

  • AIR auto update error, and question about POST parameters

    Hello,
    I'm getting a Download Failed error in the AIR autoupdating process;
    There was an error downloading the update. Error# 16822
    I recall this working once, the very first time that I tried it.
    My app.xml file contains this line:
        <version>12</version>
    and my update.xml file contains:
    <update xmlns="http://ns.adobe.com/air/framework/update/description/1.0">
      <version>12</version>
      <url>http:/players.biemedia.com/ooyala/Composer/Composer.air</url>
      <description>12 - Bug fixes and prepopulating defaults for player creation screen</description>
    </update>
    Pasting the URL into a browser works.
    However, this stuffresides on cloudfront.  in the past i have noticed that if something tries to send post parameters along with the request, cloudfront will deny the request.  Is it possible that the AIR app is sending POST parameters when hitting the download URL, and could this behavior be new in the last 6 months or so?
    Any other ideas?
    Thanks,
    Gerry

    Just Got The Solution for Error 16811 &  16816
    Note Following things to avoide update error
    No 1.>
    You xml schema for update descriptor.xml in  server should look similar to this
    <?xml version="1.0" encoding="utf-8"?>
    <update xmlns="http://ns.adobe.com/air/framework/update/description/2.5">
      <versionNumber>2.0</versionNumber>
      <url>http://localhost/SerialHunter/SerialHunter.air</url>
      <description><![CDATA[
    SerialHunter Version 2.0 by Rajendra Khope
    This new version includes:
        * AutoUpdate
        * Enhaced UI functions
        * Ability to add providers       
      ]]></description>
    </update>
    Note xmlns="http://ns.adobe.com/air/framework/update/description/2.5"
    and versionNumber instead of version
    Also make similar changes in appxml version field (in Burrito its by default versionNumber )
    No 2>
    if u are using code to display veesion number make sure it should look like:
    var appXML:XML = NativeApplication.nativeApplication.applicationDescriptor;
    var ns:Namespace = appXML.namespace();
    pnlMain.title=appXML.ns::name+" v "+appXML.ns::versionNumber
    Thats it...!
    Rajendra Khope
    bkrajendra at gmail dot com

Maybe you are looking for