IPS Manager Exp 7.0.3 fails to connect to AIP-SSM module

Hi, am trying to connect to my IPS module nested in a Cisco ASA 5540 appliance. Yesterday i was able to connect and do my configurations but when running the IME today i dint find my sensor module in the devices list so i tried adding it again and it gives an error. The IME systems logs are:
2010-07-22 09:29:30,092 [j_] WARN - addSource() source exists
2010-07-22 09:29:30,092 [ty] ERROR - 1
2010-07-22 09:32:06,775 [j_] WARN - addSource() source exists
2010-07-22 09:32:06,775 [ty] ERROR - 1
2010-07-22 09:33:47,753 [j_] WARN - addSource() source exists
2010-07-22 09:33:47,753 [ty] ERROR - 1
2010-07-22 09:45:16,887 [j_] WARN - addSource() source exists
2010-07-22 09:45:16,887 [ty] ERROR - 1
Kindly assist on how to overcome this.
Jerry.

Its ok guys, silly Windows issues, i had to run the application as an administrator!!!!!!     

Similar Messages

  • IPS Signature DataBase - ASA IPS/IOS IPS/IPS 42xx/AIP-SSM

    Hi,
    Can anyone briefly tell me the signature database details (No of Signature) among the following devices,
    -->ASA IPS/IOS IPS/IPS 42xx/AIP-SSM.
    Thanks,

    IPS on ASA/PIX = just 50 or so common signatures
    AIP-SSM module = same signatures as Cisco 4200 series sensors. Little minor differences exist (like IPv6 signature support etc.)
    Please rate if helpful.
    Regards
    Farrukh

  • Activating IPS AIP-SSM

    Hello Everyone,
    Some time ago we purchase a couple of ASA5510s with the IPS aip-ssm modules in them. I got them installed and got the vpns running, but never activated the IPS module on them.
    I am getting ready to get the IPS modules going. But, don't I need some time of subscription so that the IPS module can download signature updates?
    Does anyone know what the part number on that subscription is? I am seeing listings for "content security plus" licenses, but I think that is something different. I am also seeing licenses for Botnet traffic filter licenses. But, again, I am not sure if that's the right one.
    Thanks,
    Ben

    You will need a subscription license in order to take advantage of signature and Global Correlation updates. The official name for this license is "Cisco Services for IPS".  Take a look at the following Q&A doc which covers some of the part numbers.
    http://www.cisco.com/en/US/services/ps2827/ps6076/services_qa0900aecd8022e962.pdf

  • Device Manager HP Printer ! Symbol, Windows "failed to connect" Sound- Yet Printer Works

    Every startup, I hear the Windows "device failed to connect" sound.  How can I get rid of this?
    I have an HP J6480 Printer with WIn 7.  Device Manager is not recognizing the printer driver. 
    Under Device Manager, the printer is listed with the ! error symbol.  No other devices have an error symbol.  Yet the HP Solution Center and printer work.
    1)  I have tried fresh installs of the current HP Full Feature Software. 
    2) I have tried the HP Uninstall program, going through all five Uninstall programs two times.
    3) I have run CCleaner to clear registry issues.
    4) I have tried deleting the Device Manager "Officejet ! J6400 series" entry.  The Solution Center and the printer then do not work.  Apparently, Device Manager recognizes the printer but not the driver.  I have to go to "Programs", "HP", then "Officejet J6400 Series" to reinstall the software. 
    5) I have tried to get Device Manager to recognize the software.  When I click on "! Officejet 6400 series",  I get the message "the drivers for this device are not installed (code 28)".  If I then click on "Update Driver" and select" Browse my computer for driver software" then click on "Browse "C:\Users\Myname\Downloads", where I have both the HP 13.0 Full Feature Sofware Software and the Basic Print and Scan Driver files, it says "Windows cannot find driver software".   If i click on "Search automatically for driver software" I get the same message.
    I would very much appreciate any ideas!  Thank you!
    This question was solved.
    View Solution.

    Friendlycomputr,
    Your persistence is admirable! I totally understand you just want it working properly. I really appreciate the updates, I am going to look into this and get back to you as soon as I can!
    Thanks again
    HevnLgh
    I work on behalf of HP
    Please click “Accept as Solution” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos Thumbs Up" to the left of the reply button to say “Thanks” for helping!

  • "Failed to connect to the service manager" when I try to add nodes to a cluster on Windows Server 2008 R2

    Hello,
    I get the following error message everytime I try to add a node to an existing cluster "Failed to connect to the service manager".
    I'm running Windows Server 2008 R2,
    Any ideas?

    Hi saeedawadx,
    Please run the cluster validation and post the error or warning information, in normal scenario the “Failed to connect to the service manager” issue often caused by the firewall
    or AV soft block the others node connect, please try to disable the firewall and AV soft then try again.
    The following related article will give more helpful tips,
    The case of the server who couldn’t join a cluster – operation returned because the timeout period expired
    http://blogs.technet.com/b/roplatforms/archive/2010/04/28/the-case-of-the-server-who-couldn-t-join-a-cluster-operation-returned-because-the-timeout-period-expired.aspx
    Trouble Connecting to Cluster Nodes? Check WMI!
    http://blogs.msdn.com/b/clustering/archive/2010/11/23/10095621.aspx
    I’m glad to be of help to you!
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Distribution manager failed to connect to the distribution point

    After upgrading my distribution point to windows server 2012 standard I can't distribute content to my distribution point.
    I see the following error.
    source: SMS Server
    Component: SMS_DISTRIBUTION_MANAGER
    message id 2391
    Distribution Manager failed to connect to the distribution point Check your network and firewall settings.
    The firewall is not enabled. 
    wbemtest is able to connect to the remote server that has the distribution point role installed.
    The network access account is working.
    How do I fix this?

    but why does it most of the time work? I did inplace upgrade at least 6 times from 2008 R2 to 2012 R2 and every DP except one works fine.
    I'm not completely sure, but I think, my faulty one, that I'm trying to get working, was working correctly after the inplace upgrade. But as I said, that is only a theory, I'm just curious if that's possible.
    I have the same issue as described above.
    The IT guys from LukOIL

  • Distribution manager failed to create the defined share or folder on distribution point and failed to connect to remote distribution point

    We have recently upgraded remote distribution point to SCCM 2012 R2 CU4. when i try to distribute the package getting the error on the distribution point configuration status "Distribution manager failed to create the defined share or folder on distribution
    point and failed to connect to remote distribution point"
    Errors on the package transfer log file.
    CWmi::Connect() could not connect to \\XXXXXXXX.COM\root\SCCMDP. error = The operation completed successfully.. Will try FQDN
    CWmi::Connect() failed to connect to \\XXXXXXX.COM\root\SCCMDP. error = The RPC server is unavailable.
    Failed to connect to the DP WMI namespace on the remote DP

    Thanks Sandys for your suggestions.
    i have tried wbemtest from site server(Secondary site) and remote DP server. Receiving the "The RPC
    server is unavailable" from both ends.
    error:0x800706ba - The RPC server is unavailable

  • Management Data Warehouse Data Collection fails due to login failure

    Hello,
    I am trying to set up a Management Data Warehouse on a server other than the one I want statistics of.  Unfortunately, each upload fails because the data collector upload job cannot log onto the warehouse server.  For some inexplicable reason the process is trying to log on using domain\serverName.  Obviously no such user exists, and the process fails.  Below is the error message I see in the logs:
    Description: An error occurred with the following error message: "An error occurred while verifying the result set schema against the output table schema. The data collector cannot connect to the management data warehouse. : Login failed for user 'domain\server name$'.".
    Any help would be greatly appreciated.
    Thanks,
    Zachary

    http://technet.microsoft.com/en-us/library/bb677211.aspx says
    The data warehouse is installed on a different computer from the data collector. Probable causes are network connectivity problems or an unavailable host server. This error only affects upload packages.
    Handling: Because there is no advance notification about a server shutdown, this error cannot be anticipated and handled automatically. The error is logged and after a brief interval, the upload is restarted. After four unsuccessful upload attempts, the collection set is disabled and its state is written to the execution log.
    Note:
    Any data that is collected while the collection set is running is kept and accumulated. If the upload package can connect to the data warehouse, the accumulated data is uploaded.
    Blog: http://dineshasanka.spaces.live.com

  • How to create an rule with action to subtract from the event log of Ips manager express console?

    how to create an rule with action to subtract from the event log of Ips manager express console?, some knows of has an guide?.
    Thank you.
    Sent from Cisco Technical Support iPad App

    Hi,
    http://www.cisco.com/en/US/products/sw/secursw/ps2113/products_tech_note09186a0080bc7910.shtml
    HTH
    Luis Silva
    "If you need PDI (Planning, Design, Implement) assistance feel free to reach us"
    http://www.cisco.com/web/partners/tools/pdihd.html

  • Network Manager fails to connect with Huawei E3276 modem after upgrade

    Hi,
    I have Huawei E3276 (lsusb: Huawei Technologies Co., Ltd. E398 LTE/UMTS/GSM Modem/Networkcard).
    I wasn't updating the system for a long time (since KDE 4.14.3), but after upgrade Network Manager can't connect anymore.
    I also tried on the fresh install on different machine (KDE + Plasma 5.3), but I get the same error...
    Error: failed to connect modem: Only IPv4 is supported by this modem.
    I realize that this problem has nothing to do with KDE, but with new version of NM + MM, systemd, dhcpcd or dhclient?
    Why now Network Manager don't use ppp like before upgrade (different connection type "cdc-wdm0")?
    I would be grateful for any advice.
    After upgrade (KDE 4.14.3 -> 15.04 apps/5.2 plasma):
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: starting connection 'Orange'
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) started...
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> NetworkManager state is now CONNECTING
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: prepare -> need-auth (reason 'none') [40 60 0]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) complete.
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) started...
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) complete.
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect started...
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (4/8): Wait to get fully enabled
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (5/8): Register
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (6/8): Bearer
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (7/8): Connect
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> registered)
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): modem state changed, 'connecting' --> 'registered' (reason: user-requested)
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <warn> (cdc-wdm0) failed to connect modem: Only IPv4 is supported by this modem
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: prepare -> failed (reason '(null)') [40 120 1]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> NetworkManager state is now DISCONNECTED
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> Disabling autoconnect for connection 'Orange'.
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <warn> (cdc-wdm0): Activation: failed for connection 'Orange'
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: failed -> disconnected (reason 'none') [120 30 0]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): deactivating device (reason 'none') [0]
    Before upgrade (KDE 4.14)
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) starting connection 'Orange'
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> NetworkManager state is now CONNECTING
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) scheduled...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) started...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) complete.
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect started...
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (4/8): Wait to get fully enabled
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (5/8): Register
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (6/8): Bearer
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (7/8): Connect
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1) modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <warn> (ttyUSB0): port attributes not fully set
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (8/8): All done
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1) modem state changed, 'connecting' --> 'connected' (reason: user-requested)
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <warn> (ttyUSB0): failed to look up interface index
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) scheduled...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) starting...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1): device state change: prepare -> config (reason 'none') [40 50 0]
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) successful.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) scheduled.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) complete.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) started...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1): device state change: config -> ip-config (reason 'none') [50 70 0]
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> using modem-specified IP timeout: 20 seconds
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> starting PPP connection
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> pppd started with pid 780
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) complete.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) started...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    mar 23 19:31:33 AsusN56VZ pppd[780]: Plugin /usr/lib/pppd/2.4.6/nm-pppd-plugin.so loaded.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: Plugin /usr/lib/pppd/2.4.6/nm-pppd-plugin.so loaded.
    mar 23 19:31:33 AsusN56VZ kernel: PPP generic driver version 2.4.2
    mar 23 19:31:33 AsusN56VZ pppd[780]: pppd 2.4.6 started by root, uid 0
    mar 23 19:31:33 AsusN56VZ pppd[780]: Using interface ppp0
    mar 23 19:31:33 AsusN56VZ pppd[780]: Connect: ppp0 <--> /dev/ttyUSB0
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: Using interface ppp0
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: Connect: ppp0 <--> /dev/ttyUSB0
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <warn> /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring...
    mar 23 19:31:33 AsusN56VZ pppd[780]: CHAP authentication succeeded: Welcome!!
    mar 23 19:31:33 AsusN56VZ pppd[780]: CHAP authentication succeeded
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: CHAP authentication succeeded: Welcome!!
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: CHAP authentication succeeded
    mar 23 19:31:33 AsusN56VZ kernel: PPP BSD Compression module registered
    mar 23 19:31:33 AsusN56VZ kernel: PPP Deflate Compression module registered
    mar 23 19:31:35 AsusN56VZ ModemManager[267]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: access technology changed (umts -> hspa-plus)
    mar 23 19:31:35 AsusN56VZ NetworkManager[268]: <info> PPP manager(IP Config Get) reply received.
    mar 23 19:31:35 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    mar 23 19:31:35 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Commit) started...
    Linux Mint 17.1 KDE (works the same like Arch before update)
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) starting connection 'Orange Standard access - with image compression'
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> NetworkManager state is now CONNECTING
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) scheduled...
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) started...
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) complete.
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Simple connect started...
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Simple connect state (3/8): Enable
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'disabled' --> 'enabling' (reason: user-requested)
    May 7 20:06:33 mint17-vm ModemManager[781]: <warn> (ttyUSB1): port attributes not fully set
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering)
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
    May 7 20:06:34 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: signal quality updated (80)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (4/8): Wait to get fully enabled
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (5/8): Register
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (6/8): Bearer
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'enabling' --> 'registered' (reason: user-requested)
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> WWAN now enabled by management service
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (7/8): Connect
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: signal quality updated (77)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: access technology changed (unknown -> lte)
    May 7 20:06:35 mint17-vm ModemManager[781]: <warn> (ttyUSB0): port attributes not fully set
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (8/8): All done
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'connecting' --> 'connected' (reason: user-requested)
    May 7 20:06:35 mint17-vm NetworkManager[835]: <warn> (ttyUSB0): failed to look up interface index
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) scheduled...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) starting...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: prepare -> config (reason 'none') [40 50 0]
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) successful.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) scheduled.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) complete.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) started...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: config -> ip-config (reason 'none') [50 70 0]
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> using modem-specified IP timeout: 20 seconds
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> starting PPP connection
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> pppd started with pid 2468
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) complete.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) started...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    May 7 20:06:35 mint17-vm pppd[2468]: Plugin /usr/lib/i386-linux-gnu/pppd/2.4.5/nm-pppd-plugin.so loaded.
    May 7 20:06:35 mint17-vm pppd[2468]: pppd 2.4.5 started by root, uid 0
    May 7 20:06:35 mint17-vm pppd[2468]: Using interface ppp0
    May 7 20:06:35 mint17-vm pppd[2468]: Connect: ppp0 <--> /dev/ttyUSB0
    May 7 20:06:35 mint17-vm NetworkManager[835]: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
    May 7 20:06:35 mint17-vm NetworkManager[835]: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <warn> /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring...
    May 7 20:06:35 mint17-vm pppd[2468]: CHAP authentication succeeded: Welcome!!
    May 7 20:06:35 mint17-vm pppd[2468]: CHAP authentication succeeded
    May 7 20:06:35 mint17-vm kernel: [ 82.363825] PPP BSD Compression module registered
    May 7 20:06:35 mint17-vm kernel: [ 82.368188] PPP Deflate Compression module registered
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> PPP manager(IP Config Get) reply received.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Commit) started...
    May 7 20:06:36 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
    May 7 20:06:36 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Commit) complete.
    May 7 20:06:36 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: secondaries -> activated (reason 'none') [90 100 0]
    May 7 20:06:36 mint17-vm NetworkManager[835]: <info> NetworkManager state is now CONNECTED_GLOBAL
    Last edited by Shocker (2015-05-07 19:18:43)

    This week, after update, modem works again.
    However, there's a new bug in the kernel, which was not there before:
    kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
    but the modem works and connects to the network.
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> Auto-activating connection 'Orange'.
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: starting connection 'Orange'
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) started...
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> NetworkManager state is now CONNECTING
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) complete.
    may 24 09:32:44 AsusN56VZ ModemManager[338]: <info> Simple connect started...
    may 24 09:32:44 AsusN56VZ ModemManager[338]: <info> Simple connect state (1/8): Unlock check
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Simple connect state (2/8): Wait to get fully initialized
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (locked -> initializing)
    may 24 09:32:47 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2: unknown notification 3 received: index 2 len 4
    may 24 09:32:47 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2: unknown notification 3 received: index 2 len 4
    may 24 09:32:47 AsusN56VZ ModemManager[338]: Invalid mobile equipment error code: 50
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (initializing -> disabled)
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Simple connect state (3/8): Enable
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <warn> (ttyUSB1): port attributes not fully set
    may 24 09:32:47 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'locked' --> 'disabled' (reason: unknown)
    may 24 09:32:47 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'disabled' --> 'enabling' (reason: user preference)
    may 24 09:32:47 AsusN56VZ NetworkManager[342]: <warn> (cdc-wdm0) failed to enable modem: GDBus.Error:org.freedesktop.ModemManager1.Error.Core.InProgress: Cannot enable modem: already being enabled
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering)
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
    may 24 09:32:48 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2: unknown notification 3 received: index 2 len 4
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (4/8): Wait to get fully enabled
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (5/8): Register
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (6/8): Bearer
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'enabling' --> 'registered' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (7/8): Connect
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> registered)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'connecting' --> 'registered' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect started...
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (4/8): Wait to get fully enabled
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (5/8): Register
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (6/8): Bearer
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (7/8): Connect
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (8/8): All done
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'connecting' --> 'connected' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) scheduled...
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) starting...
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: prepare -> config (reason 'none') [40 50 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) successful.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) complete.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 3 of 5 (IP Configure Start) scheduled.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 3 of 5 (IP Configure Start) started...
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: config -> ip-config (reason 'none') [50 70 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> Activation (wwp0s20u2i2) Beginning DHCPv4 transaction (timeout in 15 seconds)
    may 24 09:33:08 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
    may 24 09:33:08 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
    may 24 09:33:08 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> dhclient started with pid 3624
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): IPv6 configuration disabled
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 3 of 5 (IP Configure Start) complete.
    may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPDISCOVER on wwp0s20u2i2 to 255.255.255.255 port 67 interval 7
    may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPREQUEST on wwp0s20u2i2 to 255.255.255.255 port 67
    may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPOFFER from 10.X.X.X
    may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPACK from 10.X.X.X
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> address 10.X.X.X
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> plen 30 (255.255.255.252)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> gateway 10.X.X.X
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> server identifier 10.X.X.X
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> lease time 518400
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> nameserver '194.X.X.X'
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> nameserver '194.X.X.X'
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (wwp0s20u2i2): DHCPv4 state changed unknown -> bound
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 5 of 5 (IPv4 Commit) started...
    may 24 09:33:08 AsusN56VZ avahi-daemon[1326]: Joining mDNS multicast group on interface wwp0s20u2i2.IPv4 with address 10.X.X.X.
    may 24 09:33:08 AsusN56VZ avahi-daemon[1326]: New relevant interface wwp0s20u2i2.IPv4 for mDNS.
    may 24 09:33:08 AsusN56VZ avahi-daemon[1326]: Registering new address record for 10.X.X.X on wwp0s20u2i2.IPv4.
    may 24 09:33:08 AsusN56VZ dhclient[3624]: bound to 10.X.X.X -- renewal in 252436 seconds.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 5 of 5 (IPv4 Commit) complete.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: secondaries -> activated (reason 'none') [90 100 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> NetworkManager state is now CONNECTED_LOCAL
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> NetworkManager state is now CONNECTED_GLOBAL
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> Policy set 'Orange' (wwp0s20u2i2) as default for IPv4 routing and DNS.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> Writing DNS information to /usr/bin/resolvconf
    may 24 09:33:09 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: successful, device activated.

  • Access Manager Failed to Connect to Directory Server

    Dear All,
    I have problem with Directory Server connection in Access Manager. This happened in Production site, all application that integrated with Oracle Access Manager (OAM) for Single Sign On are not accessible after the Directory Server connection problem occur in OAM. The problem has only started occurring suddenly, before it the all service including the OAM and Directory Server is running well. Below are the error messages that appear in WebGate log file (ohs1.log) and OAM log file (oblog.log) :
    >> OHS/WebGate (ohs1.log) :
    [2014-01-21T09:25:12.0053+07:00] https://community.oracle.com/OHS https://community.oracle.com/OHS-9999 https://community.oracle.com/apache2entry_web_gate.cpp host_id: &lt;WEBGATE_HOSTNAME&gt; [host_addr:10.10.254.178] [ecid: 004w76rlRYt0NuapxKL6iW0000sE001oGY] The host and port from the requested URL could not be found in the Policy database. Check if the corresponding directory service is up.
    >> OAM (Oblog.log):
    2014/01/15@03:12:23.833746      [30573 30606 | tel:30573%20%20%2030606]   DB_RUNTIME      ERROR  0x000008C1      ../ldap_connection_mngr.cpp:443 "Failed to connect to directory server" lpszHost&lt;LDAP_HOSTNAME_VIA_LOADBALANCER&gt; port&lt;LDAP_PORT_VIA_LOAD_BALANCER&gt;
    The OAM using the Load Balancer between the LDAP Directory Server to OAM's component. When the error appears, there are no problem with the Load Balancer and all of Directory Sever services is up. There are two Directory Server servers in Multi Master Replication and 14 WebGate servers that integrated with OAM. Is there a limitation number of WebGate for integrated to the OAM?
    I have tried to set some parameters in OAM configuration to solve this problem. I set the Maximum Connection of Directory Server parameter to 10 value (in OAM Console), the LDAPOperationTimeout paramater to 1 hour value and the LDAPMaxNoOfRetries parameter to 2 value (in the globalparams.xml). After set these parameters, the error is not appear in some days, but suddenly appear again in the same error message. May be set these parameters is not appropriate solution for the problem or the value that I set is not correct. Any experience with this?
    I still don't know what the root cause of this problem. Restart all of OAM services (including the WebGate) is temporary solution when the error appear.
    Any idea for this problem?
    Thanks in advice.

    Hi Jun-Y,
    Thank you for your answer.
    What do you means with the Directory Server's idle timeout is the "Idle Timeout" parameter in LDAP Client Control Settings?
    I use Oracle Directory Server Enterprise 11.1.1.5.0. Now, the Directory Server's idle timeout parameter is "unlimited" value.
    If the idle timeout of the load balancer set 1 hour, it means that I must change the directory server's idle timeout to be less than 1 hour. Isn't right?

  • Oracle Access Manager 11gR2 Web application: "oam" failed to preload

    Any pointers for troubleshooting this error?
    Managed Server starts up but fails to start-up "oam" deployment.
    weblogic.application.ModuleException: [HTTP:101216]Servlet: "AMInitServlet" failed to preload on startup in Web application: "oam".
    java.lang.ExceptionInInitializerError
            at oracle.security.am.pbl.transport.http.AMInitServlet.initializeAmServer(AMInitServlet.java:113)
            at oracle.security.am.pbl.transport.http.AMInitServlet.init(AMInitServlet.java:79)
            at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
            at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
            at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
            at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
            at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
            at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1981)
            at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1955)
            at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1874)
            at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3154)
            at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1518)
            at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:484)
            at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
            at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
            at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
            at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
            at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
            at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:671)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
            at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:59)
            at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
            at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
            at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
            at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
            at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
            at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:149)
            at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
            at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
            at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
            at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
            at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
            at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
            at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
            at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
            at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused by: java.lang.NullPointerException
            at oracle.security.am.pbl.diagnostic.DiagnosticUtil.<init>(DiagnosticUtil.java:80)
            at oracle.security.am.pbl.diagnostic.DiagnosticUtil.<clinit>(DiagnosticUtil.java:65)
            ... 45 more
            at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1520)
            at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:484)
            at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
            Truncated. see log file for complete stacktrace
    Caused By: java.lang.NullPointerException
            at oracle.security.am.pbl.diagnostic.DiagnosticUtil.<init>(DiagnosticUtil.java:80)
            at oracle.security.am.pbl.diagnostic.DiagnosticUtil.<clinit>(DiagnosticUtil.java:65)
            at oracle.security.am.pbl.transport.http.AMInitServlet.initializeAmServer(AMInitServlet.java:113)
            at oracle.security.am.pbl.transport.http.AMInitServlet.init(AMInitServlet.java:79)
            at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)

    SOA is not required. WebGate is a separate installation, separate from where you install the Oracle Access Manager.
    Oracle Access Manager is like the management station, WebGate would typically be installed on a host where a Web Server is running. So WebGate running on the WebServer host would be used to provide access control functions for web pages hosted on Web Server. You will have to do the configuration of WebGate separately after Access Manager has been installed. Please mark answer helpful/correct if helpful.

  • CSM IPS Manager doesn't display IPS sensors.

    I am doing inital configuration of the CSM v3.0 The IPS sensor 4250xl that I have added to CSM doesn't show up in the IPS Manager. Moreover, the Devices->Sensor window doesn't appear to be displayed correctly - there is a browser icon indicating missing content.
    Any ideas what may be the issue. Thanks.

    You might be running into a bug here. The bug-Id is:CSCsa83631

  • Configuring signature through IPS Manager in CSM3.0

    I was trying to customize the siganture with IPS manager in CSM3.0.Any changes in CSM3.0 only displays in the window but looks like it is not been applied to IDSM2 which has IPS v5.1.The same change If I make through IDM to idsm2
    it works fine.
    This how I am testing: Just changed the sev level (low to high) in one of the bulit in siganture (say 2100 sweep)
    from the IPS manager in CSM3.0.Then, when a traffic triggers that signature,the IPS Eventviewer still shows the sev level as "low" only.
    But if I do the same changes though IDM I can see the sev level as "high" in the IPS event viewer5.0.
    I also have 2 x 6500 with single IDSM2 on both switches.I could add only one IDSM2 to IPS manager (via DCR in comman services )and the other one I couldnot.Any suggestions please

    Hi,Thanks for your response.IPS Sensor is configured.I use the same username/password with priv15 through IDM as well.
    Here is the Problem Summary:
    ============================
    We are using CSM3.0 for managing IDSM2 modules and we are having the following difficulties
    I. Adding new IDSM2 sensor module into CSM3.0 through IPS
    II.Customization of any signature
    I.Adding new IDSM2 sensor module into CSM3.0 through IPS
    We followed up the below procedures to add the IDSM2 modules
    1.Go to CCS, device crenditials, select the type as cisco service modules and give the device crenditials like IP Address, username/password etc
    2.Go to IPS Manager, under device tab we could see the IDSM2 module has been added.Then go to sensor group and re-import it.It works fine ie we could add and see the same in IPS manager.
    Note: 1st sensor was successfully added where as the 2nd sensor couldnot be added in IPS
    3.We could see that the same has been added into common services.But when we see in IPS Manager Device sensor or sensor group, we could not see the IDSM2 module.
    Only the 1st sensor is showed in the IPS window.So we couldnot re-import the second sensor in to the specified group ( the group is same as the 1st sensor)
    II.Customization of any signature:
    We followed up the above said procedures ( as per I 1 to 2) to add the IDSM2 modules
    Note: 1st sensor was successfully added where as the 2nd sensor couldnot be added in IPS
    1.Go to configuration, select the IPS siganture5.1, apply some changes like
    Changing the sev level from ?low? to ? high? for one of the built in signature ( ID 2100) by tuning. The changes appear in the CSM IPS console. But it doesn?t apply to the IDSM module. After this change, if the signature triggers IEV should show the changed level ? high?. But the IEV still shows the old level for the signature ID 2100 as ?low? only. The main screen under device tab still shows that configuration as pending.ie it looks like the changes made in CSM/IPS manager doesn?t applied to IDSM2 module
    Note: If we make the same changes by using the IDM which behaves as expected.ie IEV shows the sev level for the tuned signatureID (2100) as ?high?
    Please suggest us where are we missing?
    Here are the details about the modules
    Module: IDSM2 module
    Ver: 5.1(1)S229.0V1.0
    CSM : 3.0
    IEV: 5.1.1

  • Endpoint Protection Managed Workstations: Antimalware policy application failed

    Hello,
    When looking at the Endpoint statistics I have the line for systems failing to apply policy. An easy fix to this is to delete the registry.pol file. I would like to make a collection that automates this task for me. Basically if it reports back failure,
    it gets added to a collection, an advertisement runs on it to fix it and redeploy the policy.
    The only thing I need to know is the query behind the "Endpoint Protection Managed Workstations: Antimalware policy application failed" so I can make a collection for it. Does anyone happen to know it?
    Thanks

    Client logs:
    Client 1:
    Create Process Command line: "c:\Program Files\Microsoft Security Client\\ConfigSecurityPolicy.exe" "C:\WINDOWS\CCM\EPAMPolicy.xml". EndpointProtectionAgent 11/3/2014 12:27:00 PM 2056 (0x0808)
    Failed to apply the policy C:\WINDOWS\CCM\EPAMPolicy.xml with error (0x80004005). EndpointProtectionAgent 11/3/2014 12:27:00 PM 2056 (0x0808)
    Failed to apply policy with error 0x80004005, retry number : 1 after 60 second. EndpointProtectionAgent 11/3/2014 12:27:00 PM 2056 (0x0808)
    Create Process Command line: "c:\Program Files\Microsoft Security Client\\ConfigSecurityPolicy.exe" "C:\WINDOWS\CCM\EPAMPolicy.xml". EndpointProtectionAgent 11/3/2014 12:28:00 PM 2056 (0x0808)
    Failed to apply the policy C:\WINDOWS\CCM\EPAMPolicy.xml with error (0x80004005). EndpointProtectionAgent 11/3/2014 12:28:00 PM 2056 (0x0808)
    Failed to apply policy with error 0x80004005, retry number : 2 after 60 second. EndpointProtectionAgent 11/3/2014 12:28:00 PM 2056 (0x0808)
    Create Process Command line: "c:\Program Files\Microsoft Security Client\\ConfigSecurityPolicy.exe" "C:\WINDOWS\CCM\EPAMPolicy.xml". EndpointProtectionAgent 11/3/2014 12:29:00 PM 2056 (0x0808)
    Failed to apply the policy C:\WINDOWS\CCM\EPAMPolicy.xml with error (0x80004005). EndpointProtectionAgent 11/3/2014 12:29:00 PM 2056 (0x0808)
    Failed to apply policy with error 0x80004005, retry number : 3 after 60 second. EndpointProtectionAgent 11/3/2014 12:29:00 PM 2056 (0x0808)
    Create Process Command line: "c:\Program Files\Microsoft Security Client\\ConfigSecurityPolicy.exe" "C:\WINDOWS\CCM\EPAMPolicy.xml". EndpointProtectionAgent 11/3/2014 12:30:00 PM 2056 (0x0808)
    Failed to apply the policy C:\WINDOWS\CCM\EPAMPolicy.xml with error (0x80004005). EndpointProtectionAgent 11/3/2014 12:30:00 PM 2056 (0x0808)
    Failed to apply policy with error 0x80004005, retry number : 4 after 60 second. EndpointProtectionAgent 11/3/2014 12:30:00 PM 2056 (0x0808)
    Create Process Command line: "c:\Program Files\Microsoft Security Client\\ConfigSecurityPolicy.exe" "C:\WINDOWS\CCM\EPAMPolicy.xml". EndpointProtectionAgent 11/3/2014 12:31:00 PM 2056 (0x0808)
    Failed to apply the policy C:\WINDOWS\CCM\EPAMPolicy.xml with error (0x80004005). EndpointProtectionAgent 11/3/2014 12:31:00 PM 2056 (0x0808)
    Failed to apply policy with error 0x80004005, retry number : 5 after 60 second. EndpointProtectionAgent 11/3/2014 12:31:00 PM 2056 (0x0808)
    Create Process Command line: "c:\Program Files\Microsoft Security Client\\ConfigSecurityPolicy.exe" "C:\WINDOWS\CCM\EPAMPolicy.xml". EndpointProtectionAgent 11/3/2014 12:32:00 PM 2056 (0x0808)
    Failed to apply the policy C:\WINDOWS\CCM\EPAMPolicy.xml with error (0x80004005). EndpointProtectionAgent 11/3/2014 12:32:01 PM 2056 (0x0808)
    Save new policy state 2 to registry SOFTWARE\Microsoft\CCM\EPAgent\PolicyApplicationState EndpointProtectionAgent 11/3/2014 12:32:01 PM 2056 (0x0808)
    State 2 and ErrorCode -2147467259 and ErrorMsg Failed to open the local machine Group Policy and PolicyName Antimalware Policy and GroupResolveResultHash 23496E87C22E7CA5048254CC04CCF582A084C108 is NOT changed. EndpointProtectionAgent 11/3/2014 12:32:01 PM 2056 (0x0808)
    Skip sending state message due to same state message already exists. EndpointProtectionAgent 11/3/2014 12:32:01 PM 2056 (0x0808)
    Client 2:
    Apply AM Policy. EndpointProtectionAgent 11/4/2014 7:27:50 AM 2536 (0x09E8)
    Failed to generate AM policy XML with error code 0x8000ffff EndpointProtectionAgent 11/4/2014 7:27:50 AM 2536 (0x09E8)
    Save new policy state 2 to registry SOFTWARE\Microsoft\CCM\EPAgent\PolicyApplicationState EndpointProtectionAgent 11/4/2014 7:27:50 AM 2536 (0x09E8)
    start to send State Message with topic type = 2002, state id = 2, error code = 0x8000ffff, and message = <Instance><AppliedAmPolicies/></Instance>
    EndpointProtectionAgent 11/4/2014 7:27:50 AM 2536 (0x09E8)
    Start to send state message. EndpointProtectionAgent 11/4/2014 7:27:50 AM 2536 (0x09E8)
    Send state message successfully EndpointProtectionAgent 11/4/2014 7:27:51 AM 2536 (0x09E8)
    Firewall provider is installed. EndpointProtectionAgent 11/4/2014 7:27:51 AM 2536 (0x09E8)
    Installed firewall provider meet the requirements. EndpointProtectionAgent 11/4/2014 7:27:51 AM 2536 (0x09E8)
    Endpoint is triggered by WMI notification. EndpointProtectionAgent 11/4/2014 7:27:51 AM 2536 (0x09E8)
    File C:\Windows\ccmsetup\SCEPInstall.exe version is 4.3.215.0. EndpointProtectionAgent 11/4/2014 7:27:51 AM 2536 (0x09E8)
    EP version 4.3.215.0 is already installed. EndpointProtectionAgent 11/4/2014 7:27:51 AM 2536 (0x09E8)
    Expected Version 4.3.215.0 is exactly same with installed version 4.3.215.0. EndpointProtectionAgent 11/4/2014 7:27:51 AM 2536 (0x09E8)
    Handle EP AM policy. EndpointProtectionAgent 11/4/2014 7:27:51 AM 2536 (0x09E8)
    Apply AM Policy. EndpointProtectionAgent 11/4/2014 7:27:51 AM 2536 (0x09E8)
    Failed to generate AM policy XML with error code 0x8000ffff EndpointProtectionAgent 11/4/2014 7:27:51 AM 2536 (0x09E8)
    Save new policy state 2 to registry SOFTWARE\Microsoft\CCM\EPAgent\PolicyApplicationState EndpointProtectionAgent 11/4/2014 7:27:51 AM 2536 (0x09E8)
    State 2 and ErrorCode -2147418113 and ErrorMsg Failed to load WMI instances. and PolicyName Antimalware Policy and GroupResolveResultHash 2B22C160D3BC8DC4BECF08D4F632D4756D4C9622 is NOT changed. EndpointProtectionAgent 11/4/2014 7:27:51 AM 2536 (0x09E8)
    Skip sending state message due to same state message already exists. EndpointProtectionAgent 11/4/2014 7:27:51 AM 2536 (0x09E8)
    Client 3:
    Apply AM Policy. EndpointProtectionAgent 11/3/2014 12:26:00 PM 1768 (0x06E8)
    Create Process Command line: "c:\Program Files\Microsoft Security Client\\ConfigSecurityPolicy.exe" "C:\Windows\CCM\EPAMPolicy.xml". EndpointProtectionAgent 11/3/2014 12:26:00 PM 1768 (0x06E8)
    Failed to apply the policy C:\Windows\CCM\EPAMPolicy.xml with error (0x80004005). EndpointProtectionAgent 11/3/2014 12:26:00 PM 1768 (0x06E8)
    Failed to apply policy with error 0x80004005, retry number : 1 after 60 second. EndpointProtectionAgent 11/3/2014 12:26:00 PM 1768 (0x06E8)
    Create Process Command line: "c:\Program Files\Microsoft Security Client\\ConfigSecurityPolicy.exe" "C:\Windows\CCM\EPAMPolicy.xml". EndpointProtectionAgent 11/3/2014 12:27:00 PM 1768 (0x06E8)
    Failed to apply the policy C:\Windows\CCM\EPAMPolicy.xml with error (0x80004005). EndpointProtectionAgent 11/3/2014 12:27:00 PM 1768 (0x06E8)
    Failed to apply policy with error 0x80004005, retry number : 2 after 60 second. EndpointProtectionAgent 11/3/2014 12:27:00 PM 1768 (0x06E8)
    Create Process Command line: "c:\Program Files\Microsoft Security Client\\ConfigSecurityPolicy.exe" "C:\Windows\CCM\EPAMPolicy.xml". EndpointProtectionAgent 11/3/2014 12:28:00 PM 1768 (0x06E8)
    Failed to apply the policy C:\Windows\CCM\EPAMPolicy.xml with error (0x80004005). EndpointProtectionAgent 11/3/2014 12:28:00 PM 1768 (0x06E8)
    Failed to apply policy with error 0x80004005, retry number : 3 after 60 second. EndpointProtectionAgent 11/3/2014 12:28:00 PM 1768 (0x06E8)
    Create Process Command line: "c:\Program Files\Microsoft Security Client\\ConfigSecurityPolicy.exe" "C:\Windows\CCM\EPAMPolicy.xml". EndpointProtectionAgent 11/3/2014 12:29:00 PM 1768 (0x06E8)
    Failed to apply the policy C:\Windows\CCM\EPAMPolicy.xml with error (0x80004005). EndpointProtectionAgent 11/3/2014 12:29:01 PM 1768 (0x06E8)
    Failed to apply policy with error 0x80004005, retry number : 4 after 60 second. EndpointProtectionAgent 11/3/2014 12:29:01 PM 1768 (0x06E8)
    Create Process Command line: "c:\Program Files\Microsoft Security Client\\ConfigSecurityPolicy.exe" "C:\Windows\CCM\EPAMPolicy.xml". EndpointProtectionAgent 11/3/2014 12:30:01 PM 1768 (0x06E8)
    Failed to apply the policy C:\Windows\CCM\EPAMPolicy.xml with error (0x80004005). EndpointProtectionAgent 11/3/2014 12:30:01 PM 1768 (0x06E8)
    Failed to apply policy with error 0x80004005, retry number : 5 after 60 second. EndpointProtectionAgent 11/3/2014 12:30:01 PM 1768 (0x06E8)
    Create Process Command line: "c:\Program Files\Microsoft Security Client\\ConfigSecurityPolicy.exe" "C:\Windows\CCM\EPAMPolicy.xml". EndpointProtectionAgent 11/3/2014 12:31:01 PM 1768 (0x06E8)
    Failed to apply the policy C:\Windows\CCM\EPAMPolicy.xml with error (0x80004005). EndpointProtectionAgent 11/3/2014 12:31:01 PM 1768 (0x06E8)
    Save new policy state 2 to registry SOFTWARE\Microsoft\CCM\EPAgent\PolicyApplicationState EndpointProtectionAgent 11/3/2014 12:31:01 PM 1768 (0x06E8)
    State 2 and ErrorCode -2147467259 and ErrorMsg Failed to open the local machine Group Policy and PolicyName Antimalware Policy and GroupResolveResultHash 23496E87C22E7CA5048254CC04CCF582A084C108 is NOT changed. EndpointProtectionAgent 11/3/2014 12:31:01 PM 1768 (0x06E8)
    Skip sending state message due to same state message already exists. EndpointProtectionAgent 11/3/2014 12:31:01 PM 1768 (0x06E8)
    I have 12 systems total having issues with Policy right now.

Maybe you are looking for

  • Creative Cloud pops up with trail will expire in 0 days when I run Dreamweaver CS6

    When I click on the icon for Dreamweaver CS6 a panel for Dreamweaver CC pops up with the message "Your trial will expire in 0 days"  "00 days remaining.  It offers "Buy Now" and "Continue Trial". When I click the red x to close out I am returned to D

  • How do I make a button activate when enter is pressed?

    Can anyone help me? I'm trying to activate the JButton "BUTconv" below work when someone presses "enter" on the keyboard. I'm using the code below, but every time I try to compile it, my compiler says that "BUTconv" is an unknown symbol, it 'cannot f

  • Mouse wheel to scroll

    Hi all! Every time I open Adobe Reader XI, I want to use the scroll wheel of the mouse to scroll down the document. Instead, the mouse wheel zooms the current page. Specifically, I set the zoom to "fit one full page at a time", and I want to quickly

  • Missing table begin XSL context for:

    Hi, I'm working on a table listing in an RTF template. This has several <?choose?> commands, a <?for-each?> command, and some variables. All of a sudden I'm getting the above message for all my <?choose?> and <end for-each?> statements Any ideas? I'v

  • What is the equivalent of word on an iPad?

    I'm looking to do schoolwork on my ipad ( I have a removable keyboard for it ) and was wondering if I am able to load microsoft word onto it, or something very similiar to it? Are they any good apps? Thanks