Client Disconnected From Database

I'm running lookout 5.0 on one computer and logging its citadel to another machine. There is more than one lookout process on the PC that is actually running lookout itself. Different processes are logging to different designated database folders on the other computer. When you can actually get lookout to show the history info (i.e hypertrend data and such) on the computer it all works great. However if you ever restart the computer requiring to shutdown lookout, then the next time it boots up it is nearly impossible to get lookout to display the trend info again. You always get the "client disconnected from database" alarm. All the network paths and folder locations are correct. I am lost on this one.

Did you get this error every time you reboot Lookout or sometimes ?
If you get it sometimes:
Simply delete the /database/ Folder in Lookout directory
when you restart Lookout it will creat a new one.
From experience when you get this message the database is realy damage
i dont know why this happens.

Similar Messages

  • ARD client disconnected from ARD under leopard after using curtain

    I have just noticed a problem that occurs when I put a client under curtain mode under leopard....the client disconnects from the ARD console and remains in the locked state until I go over and manually restart the system...anyone else having this issue

    Sorry, I hadn't noticed that someone replied...Geez you would think they would get this stuff corrected...Do you know if there is going to be an improved ARD in the future. I manage a lab and apple tools are better and more reliable but still have a long way to go....
    Glen

  • Clients disconnected from WLC randomly

    Hi,
    I'm doing some tests with clients to see how much time they are kept registered in the controller while they are disconnected. I've set session timeout to 0 (infinite) and user idle timeout to 12 hours. 
    The problem is that sometimes the clients are disconnected from the controller before the user idle timeout expires:
    apfMsDeleteByMscb Scheduling mobile for deletion with deleteReason 6, reasonCode 1
    Other times they are expired normally by the user idle timeout (deleteReason4,reasonCode4).
    If I am not wrong deleteReason 6 corresponds to manual deletion of the client, but there is no manual interventention when this happen, is the controller who deletes it.
    Can anybody explain why this happens randomly?
    WLC version 6.0.196
    Thanks.

    Refer the 2 Bugs :
    Unified APs removing clients on maximum retries.
    CSCti91944
    Description
    Symptom:
    A wireless client might be removed from the mobility database before the user idle timeout. When this happens, if "debug client MAC" is in effect, messages similar to the following are seen on the WLC:
    *spamApTask3: clientmacaddrXYZ Received Idle-Timeout from
    AP macADDR-abc slot 0 for STA XYZ Client MAC ADDR
    *spamApTask3: apfMsDeleteByMscb Scheduling mobile for deletion with
    deleteReason 4, reasonCode 4
    The symptoms, as experienced by the user, depends on the behavior of the client device and on the WLAN configuration as follows:
    - If the WLAN is configured for web-auth, the client is forced to reauthenticate through the web.
    - If the WLAN is configured for L3 mobility and if the client performs an L3 roam at the time of the removal, the client's old IP address in the old subnet is no longer valid, and the client is forced to re-DHCP in the new subnet. Any existing TCP connections fail to work expected. If the client is a 792x wireless phone on a call, the talk path is lost for the remainder of the call.
    - If the WLAN is configured for L2 mobility, then the client is forced to perform a full EAP authentication (if EAP is configured) and to re-DHCP (if DHCP required is configured). In most cases, this does not cause a perceptible service interruption, unless the client's IP address changes.
    Conditions:
    This occurs when an access point fails to transmit 250 consecutive packets to the client (if there are 64 failed retransmits per packet, which means 4 consecutive dropped packets, it triggers the deauth).
    Examples:
    - Client radio is temporarily disabled.
    - Client has gone into hibernation/standby.
    - For a voice client, if the client is in a call and is unable to receive audio packets for a fraction of a second.
    Workaround:
    None; however, reconfiguring the WLAN for layer 2 rather than layer 3 mobility can mitigate the effect.
    Known Affected Releases:
    (3)
    7.0(98.0)
    6.0(199.0)
    6.0(199.4)
    Clients hit Idle timeout after successful authentication
    CSCue34763
    Description
    Symptom:
    A wireless client, while associated/authenticated (in RUN state), will be
    prematurely idle timed out by an AP. With "debug client" in effect on the
    WLC, messages similar to the following are seen:
    *spamApTask2: Jan 30 17:10:17.258: 00:11:22:33:44:55 Received Idle-Timeout from
    AP 84:78:ac:00:11:22, slot 1 for STA 00:11:22:33:44:558
    *spamApTask2: Jan 30 17:10:17.258: 00:11:22:33:44:55 apfMsDeleteByMscb
    Scheduling mobile for deletion with deleteReason 4, reasonCode 4
    The idle timeout event occurs while the client is not idle, and more rapidly,
    after the client's last reassociation, than the configured user idle timeout
    value.
    Conditions:
    Flexconnect (H-REAP) local switching is configured, with DHCP Required.
    Workaround:
    Clients hit Idle timeout after successful authentication
    CSCue34763
    Description
    Symptom:
    A wireless client, while associated/authenticated (in RUN state), will be
    prematurely idle timed out by an AP. With "debug client" in effect on the
    WLC, messages similar to the following are seen:
    *spamApTask2: Jan 30 17:10:17.258: 00:11:22:33:44:55 Received Idle-Timeout from
    AP 84:78:ac:00:11:22, slot 1 for STA 00:11:22:33:44:558
    *spamApTask2: Jan 30 17:10:17.258: 00:11:22:33:44:55 apfMsDeleteByMscb
    Scheduling mobile for deletion with deleteReason 4, reasonCode 4
    The idle timeout event occurs while the client is not idle, and more rapidly,
    after the client's last reassociation, than the configured user idle timeout
    value.
    Conditions:
    Flexconnect (H-REAP) local switching is configured, with DHCP Required.
    Workaround:
    Disable DHCP required.
    Disable DHCP required.

  • VPN Client disconnection from command line

    Hi,
    I want to connect to IPsec VPN on ISA500 by VPN Client (v 5.0.07.0440, the last version, I think), using command line parameters.
    I can connect with the command:
    "%programfiles%\Cisco Systems\VPN Client\ipsecdialer.exe" -c -user myUser -pwd myPassword "MyConnectionEntry"
    but i don't know the command to disconnect from command lines.
    If I do
    "%programfiles%\Cisco Systems\VPN Client\ipsecdialer.exe" -?
    I obtain the list of parameters
    vpngui [-c | -sc [sd] [-user <username>] [-pwd <password> ! -eraseuserpwd]] <connection entry>
    but I don't unterstand what I have to do... I try every combination using -sd parameter (I think means for silent disconnect), but in every case I can only to show VPN interface  without disconnect anything...
    Can anyone help me?
    Thanks

    Prasath,
    This appears to be a data flow issue.  You need to look in the dataflow log file.  Your information indicates the project name is SAMPLES.xml, and the data flow ID is D20091213_014350765.  Look at the data flow log file in
    C:\dqxi\11_7\repository\configuration_rules\runtme_metadata\project_SAMPLES\D20091213_014350765
    Alternatively, you can temporarily replace the transactional reader and writter transforms with their corresonding batch transforms, and run the job from the Project Architect.  Any errors will be displayed in the Running window.
    Paul

  • Can't disconnect from database connection

    Hello,
    One of our application has been running for over a year on a client network, a windows desktop executable connected to an Oracle Standard One Edition, rel. 10.1.0.2., on a Linux server. Now the executable hangs when the users exit the app. It is build using Oracle Objects For OLE and the culprit is the close method of the ODatabase object. Strangely however, we found out that other applications can’t disconnect anymore:
    Both SQL*Plus and Toad will hang when exiting.
    Also, doing a connection test with the Net Manager hangs when a valid login is used. If I put an non-existing user or a locked one (scott/tiger for example), the server does report the problem.
    I've enabled local client tracing on a user desktop but there are no errors reported, which makes sense since it seems like nothing is coming back.
    The network admin over there swears nothing has change on the network config. So I’m hunting possible cause for this. There are several logs file cluttering up disk space in various folders and this file:
    /home/oracle/OraHome_1/sqlnet.log is now up to 3.1 Mb. I believe I can safely delete this one from other messages I found in various newsgroup. I would be surprise however that disk space is the problem since the windows app works fine, doing query in SQL*Plus works fine. (I only tried Toad to check the disconnect “feature”, not familiar with this tool, but it was showing the schema correctly)
    As a developper, I am however curious on whats happening when a disconnect is sent to the server and what are the expected responses, which don’t seem to be coming back anymore. It really looks like some packets are lost on their way back.
    Thanks in advance,
    Eric

    Many thanks! You hit the problem right on!
    Oddly, I can't even drop or disablee the trigger, SQL*Plus freeze. The network admin will perform a shutdown tonite when nobody is using the software. I'll see if I can drop it then.
    Regards,
    Eric

  • Clients disconnecting from WiFi

    symptoms:
    Client shows associated but client does not connect.
    Also, network will show up in "Available Networks" and then disappears.
    Only affecting some computers. All same make and model.
    Controller did show a reboot yesterday at 9:00am for no apparerent reason.
    Config was not lost so, MACs are still entered.
    Connecting clients can disconnect and reconnect - ruling out DHCP.

    Patrick if you are having WLC reboots it is a good idea to open a tac case here so we can check for any crash files.
    with regards to the client not connecting / debug client from the wlc cli will help out to isolate what is going on.
    ssh / telnet to wlc
    debug client xx:xx:xx:xx:xx:xx
    log to a text file
    reproduce the problem
    and paste
    thanks
    Serge

  • Clients disconnected from AP, Sending station has left the BSS

    Issue Experienced
    Clients randomly disconnects average time before disconnect is 15 minutes
    Current AP running config
    Current configuration : 2449 bytes
    ! Last configuration change at 16:49:26 UTC Mon Feb 24 2014
    version 15.2
    no service pad
    service timestamps debug datetime msec
    service timestamps log datetime msec
    service password-encryption
    hostname BE-AP4
    logging rate-limit console 9
    enable secret 5 secret
    no aaa new-model
    no ip cef
    dot11 syslog
    dot11 vlan-name Manufacturing vlan 15
    dot11 ssid BE-WAP1
       vlan 15
       authentication open
       authentication key-management wpa
       guest-mode
       wpa-psk ascii 7 password
    dot11 guest
    power inline negotiation injector override
    username admin privilege 15 password 7
    bridge irb
    interface Dot11Radio0
     no ip address
     no ip route-cache
     encryption mode ciphers tkip
     encryption vlan 15 mode ciphers tkip
     ssid BE-WAP1
     antenna gain 0
     antenna ab-antenna
     stbc
     speed  basic-1.0 basic-2.0 basic-5.5 basic-11.0 basic-6.0 basic-9.0 basic-12.0 basic-18.0 basic-24.0 basic-36.0 basic-48.0 basic-54.0 m0. m1. m2. m3. m4. m5. m6. m7. m8. m9. m10. m11. m12. m13. m14. m15. m16. m17. m18. m19. m20. m21. m22. m23.
     channel 2442
     station-role root
    interface Dot11Radio0.15
     encapsulation dot1Q 15 native
     no ip route-cache
     bridge-group 1
     bridge-group 1 subscriber-loop-control
     bridge-group 1 spanning-disabled
     bridge-group 1 block-unknown-source
     no bridge-group 1 source-learning
     no bridge-group 1 unicast-flooding
    interface Dot11Radio1
     no ip address
     no ip route-cache
     shutdown
     antenna gain 0
     peakdetect
     dfs band 3 block
     channel dfs
     station-role root
     bridge-group 1
     bridge-group 1 subscriber-loop-control
     bridge-group 1 spanning-disabled
     bridge-group 1 block-unknown-source
     no bridge-group 1 source-learning
     no bridge-group 1 unicast-flooding
    interface GigabitEthernet0
     no ip address
     no ip route-cache
     duplex auto
     speed auto
    interface GigabitEthernet0.15
     encapsulation dot1Q 15 native
     no ip route-cache
     bridge-group 1
     bridge-group 1 spanning-disabled
     no bridge-group 1 source-learning
    interface BVI1
     ip address 192.168.15.68 255.255.255.0
     no ip route-cache
    ip default-gateway 192.168.15.254
    ip forward-protocol nd
    ip http server
    no ip http secure-server
    ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag
    Log Output
    *Feb 24 15:39:30.226: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b464 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 15:39:44.446: %DOT11-6-ROAMED: Station 0017.23a9.b464 Roamed to 544a.00e1.e5c0
    *Feb 24 15:39:44.446: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b464 Reason: Sending station has left the BSS
    *Feb 24 15:39:53.154: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b474 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 15:39:57.670: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b464 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 15:40:08.602: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.230b.9bdf Associated KEY_MGMT[WPA PSK]
    *Feb 24 15:40:49.662: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.230a.ee2e Associated KEY_MGMT[WPA PSK]
    *Feb 24 15:41:19.318: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.230a.ee16 Associated KEY_MGMT[WPA PSK]
    *Feb 24 15:43:31.622: %SYS-5-CONFIG_I: Configured from http by  on 192.168.1.97
    *Feb 24 15:43:31.622: %SYS-5-CONFIG_I: Configured from http by  on 192.168.1.97
    *Feb 24 15:43:31.622: %SYS-5-CONFIG_I: Configured from http by  on 192.168.1.97
    *Feb 24 15:43:31.630: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.230a.ee16 
    *Feb 24 15:43:31.630: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.230a.ee2e 
    *Feb 24 15:43:31.630: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.230b.9bdf 
    *Feb 24 15:43:31.630: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b464 
    *Feb 24 15:43:31.630: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b474 
    *Feb 24 15:43:31.630: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b461 
    *Feb 24 15:43:31.630: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b470 
    *Feb 24 15:43:31.630: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.c1e8 
    *Feb 24 15:43:31.630: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 843a.4b55.1136 
    *Feb 24 15:43:31.630: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 843a.4b5e.cd44 
    *Feb 24 15:43:31.630: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 843a.4b55.12ec 
    *Feb 24 15:43:31.642: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
    *Feb 24 15:43:31.654: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Feb 24 15:43:32.642: %DOT11-4-DIVER2_USED: Interface Dot11Radio0, Mcs rates 16-23 disabled due to only two transmit or receive antennas enabled
    *Feb 24 15:43:32.654: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Feb 24 15:43:32.682: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
    *Feb 24 15:43:32.690: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
    *Feb 24 15:43:32.698: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Feb 24 15:43:33.726: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
    *Feb 24 15:43:33.746: %DOT11-4-MAXRETRIES: Packet to client 843a.4b5e.cd44 reached max retries, removing the client
    *Feb 24 15:43:33.766: %DOT11-4-MAXRETRIES: Packet to client 843a.4b55.12ec reached max retries, removing the client
    *Feb 24 15:43:34.726: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    *Feb 24 15:43:36.210: %SYS-5-CONFIG_I: Configured from http by  on 192.168.1.97
    *Feb 24 15:44:09.450: %DOT11-6-ASSOC: Interface Dot11Radio0, Station BE-AP4 6c88.145d.0db8 Associated KEY_MGMT[WPA PSK]
    *Feb 24 15:45:27.522: %DOT11-6-ASSOC: Interface Dot11Radio0, Station BE-AP4 843a.4b5e.cd44 Associated KEY_MGMT[WPA PSK]
    *Feb 24 15:45:27.526: %DOT11-6-ASSOC: Interface Dot11Radio0, Station BE-AP4 843a.4b55.12ec Associated KEY_MGMT[WPA PSK]
    *Feb 24 15:45:27.890: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.230b.9bdf Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 15:45:28.614: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.230a.ee16 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 15:45:28.842: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.230a.ee6b Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 15:45:28.850: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.c1e8 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 15:45:28.862: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b470 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 15:45:28.866: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b461 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 15:45:29.102: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b464 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 15:45:29.110: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b474 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 15:45:29.350: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.230a.ee2e Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 15:47:17.174: %DOT11-7-AUTH_FAILED: Station cc3a.6194.ec3c Authentication failed
    *Feb 24 15:48:32.938: %DOT11-7-AUTH_FAILED: Station 0017.2313.c7bc Authentication failed
    *Feb 24 15:48:38.150: %DOT11-7-AUTH_FAILED: Station 0017.2313.c7bc Authentication failed
    *Feb 24 15:49:11.446: %DOT11-7-AUTH_FAILED: Station 0017.2313.c7bc Authentication failed
    *Feb 24 15:49:23.094: %DOT11-7-AUTH_FAILED: Station 0017.2313.c7bc Authentication failed
    *Feb 24 15:49:56.018: %DOT11-6-ASSOC: Interface Dot11Radio0, Station BE-AP4 843a.4b55.1136 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 15:50:44.850: %DOT11-7-AUTH_FAILED: Station 0017.2313.c7bc Authentication failed
    *Feb 24 15:50:52.198: %DOT11-7-AUTH_FAILED: Station 0017.2313.c7bc Authentication failed
    *Feb 24 15:50:58.106: %DOT11-7-AUTH_FAILED: Station 0017.2313.c7bc Authentication failed
    *Feb 24 15:51:44.738: %DOT11-7-AUTH_FAILED: Station 0017.2313.c7bc Authentication failed
    *Feb 24 15:51:50.150: %DOT11-7-AUTH_FAILED: Station 0017.2313.c7bc Authentication failed
    *Feb 24 15:51:58.738: %DOT11-7-AUTH_FAILED: Station 0017.2313.c7bc Authentication failed
    *Feb 24 15:55:27.622: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 843a.4b55.12ec Reason: Sending station has left the BSS
    *Feb 24 15:55:27.650: %DOT11-6-ASSOC: Interface Dot11Radio0, Station BE-AP4 843a.4b55.12ec Associated KEY_MGMT[WPA PSK]
    *Feb 24 16:01:57.442: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b470 Reason: Sending station has left the BSS
    *Feb 24 16:05:48.854: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b461 Reason: Sending station has left the BSS
    *Feb 24 16:06:28.310: %DOT11-6-ASSOC: Interface Dot11Radio0, Station  f409.d8b0.313d Associated KEY_MGMT[WPA PSK]
    *Feb 24 16:06:50.414: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b464 Reason: Sending station has left the BSS
    *Feb 24 16:06:56.102: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b474 Reason: Sending station has left the BSS
    *Feb 24 16:08:13.282: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b461 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:08:13.914: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b474 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:08:15.870: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b464 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:08:28.066: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.c1e8 Reason: Sending station has left the BSS
    *Feb 24 16:08:34.610: %DOT11-6-ROAMED: Station 0017.230b.9bdf Roamed to 544a.00e1.ef70
    *Feb 24 16:08:34.610: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.230b.9bdf Reason: Sending station has left the BSS
    *Feb 24 16:08:34.622: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b461 Reason: Sending station has left the BSS
    *Feb 24 16:08:34.934: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b474 Reason: Sending station has left the BSS
    *Feb 24 16:08:35.846: %DOT11-6-ROAMED: Station 0017.230a.ee6b Roamed to 00e1.6d4f.6090
    *Feb 24 16:08:35.846: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.230a.ee6b Reason: Sending station has left the BSS
    *Feb 24 16:08:36.394: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b464 Reason: Sending station has left the BSS
    *Feb 24 16:08:36.398: %DOT11-4-MAXRETRIES: Packet to client 0017.23a9.b464 reached max retries, removing the client
    *Feb 24 16:08:37.426: %DOT11-6-ROAMED: Station 0017.230a.ee2e Roamed to 00e1.6d4f.6090
    *Feb 24 16:08:37.426: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.230a.ee2e Reason: Sending station has left the BSS
    *Feb 24 16:08:57.994: %DOT11-6-ROAMED: Station 0017.230a.ee16 Roamed to 544a.00e1.e5c0
    *Feb 24 16:08:57.994: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.230a.ee16 Reason: Sending station has left the BSS
    *Feb 24 16:10:00.562: %DOT11-7-AUTH_FAILED: Station cc3a.6194.ec3c Authentication failed
    *Feb 24 16:10:00.562: %DOT11-4-MAXRETRIES: Packet to client cc3a.6194.ec3c reached max retries, removing the client
    *Feb 24 16:12:41.694: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station f409.d8b0.313d Reason: Sending station has left the BSS
    *Feb 24 16:13:06.994: %DOT11-7-AUTH_FAILED: Station cc3a.6194.ec3c Authentication failed
    *Feb 24 16:13:47.870: %DOT11-6-ASSOC: Interface Dot11Radio0, Station  f409.d8b0.313d Associated KEY_MGMT[WPA PSK]
    *Feb 24 16:16:24.822: %DOT11-7-AUTH_FAILED: Station 0017.2313.c7bc Authentication failed
    *Feb 24 16:16:32.262: %DOT11-7-AUTH_FAILED: Station 0017.2313.c7bc Authentication failed
    *Feb 24 16:16:46.838: %DOT11-7-AUTH_FAILED: Station 0017.2313.c7bc Authentication failed
    *Feb 24 16:16:56.050: %DOT11-7-AUTH_FAILED: Station 0017.2313.c7bc Authentication failed
    *Feb 24 16:17:16.262: %DOT11-7-AUTH_FAILED: Station 0017.2313.c7bc Authentication failed
    *Feb 24 16:20:37.806: %DOT11-4-MAXRETRIES: Packet to client f409.d8b0.313d reached max retries, removing the client
    *Feb 24 16:20:37.806: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station f409.d8b0.313d Reason: Previous authentication no longer valid
    *Feb 24 16:20:37.810: %DOT11-4-MAXRETRIES: Packet to client f409.d8b0.313d reached max retries, removing the client
    *Feb 24 16:20:39.142: %DOT11-6-ASSOC: Interface Dot11Radio0, Station  f409.d8b0.313d Associated KEY_MGMT[WPA PSK]
    *Feb 24 16:21:40.406: %DOT11-6-ROAMED: Station f409.d8b0.313d Roamed to 544a.00e1.ef70
    *Feb 24 16:21:40.406: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station f409.d8b0.313d Reason: Sending station has left the BSS
    *Feb 24 16:25:45.006: %DOT11-7-AUTH_FAILED: Station f409.d8b0.313d Authentication failed
    *Feb 24 16:25:45.010: %DOT11-4-MAXRETRIES: Packet to client f409.d8b0.313d reached max retries, removing the client
    *Feb 24 16:31:32.954: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b474 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:31:33.654: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.c1e8 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:31:36.866: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.230a.ee6b Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:31:38.538: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.230a.ee2e Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:31:38.666: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b470 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:31:40.526: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.230a.ee16 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:31:42.414: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.230b.9bdf Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:31:51.362: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b461 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:31:53.554: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b464 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:44:45.258: %DOT11-6-ASSOC: Interface Dot11Radio0, Station  f409.d8b0.313d Associated KEY_MGMT[WPA PSK]
    *Feb 24 16:47:39.350: %DOT11-6-ROAMED: Station 6c88.145d.0db8 Roamed to 544a.00e1.ef70
    *Feb 24 16:47:39.350: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 6c88.145d.0db8 Reason: Sending station has left the BSS
    *Feb 24 16:49:26.394: %SYS-5-CONFIG_I: Configured from http by  on 192.168.1.97
    *Feb 24 16:49:26.394: %SYS-5-CONFIG_I: Configured from http by  on 192.168.1.97
    *Feb 24 16:49:26.398: %SYS-5-CONFIG_I: Configured from http by  on 192.168.1.97
    *Feb 24 16:49:26.398: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station f409.d8b0.313d 
    *Feb 24 16:49:26.398: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b464 
    *Feb 24 16:49:26.398: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b461 
    *Feb 24 16:49:26.398: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.230b.9bdf 
    *Feb 24 16:49:26.398: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.230a.ee16 
    *Feb 24 16:49:26.398: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b470 
    *Feb 24 16:49:26.398: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.230a.ee2e 
    *Feb 24 16:49:26.398: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.230a.ee6b 
    *Feb 24 16:49:26.398: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.c1e8 
    *Feb 24 16:49:26.398: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b474 
    *Feb 24 16:49:26.398: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 843a.4b55.12ec 
    *Feb 24 16:49:26.398: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 843a.4b55.1136 
    *Feb 24 16:49:26.398: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 843a.4b5e.cd44 
    *Feb 24 16:49:26.410: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
    *Feb 24 16:49:26.422: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Feb 24 16:49:27.414: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Feb 24 16:49:27.442: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
    *Feb 24 16:49:27.450: %DOT11-4-MAXRETRIES: Packet to client 843a.4b55.12ec reached max retries, removing the client
    *Feb 24 16:49:27.502: %DOT11-4-MAXRETRIES: Packet to client 0017.23a9.b464 reached max retries, removing the client
    *Feb 24 16:49:27.510: %DOT11-4-MAXRETRIES: Packet to client 0017.23a9.b470 reached max retries, removing the client
    *Feb 24 16:49:27.522: %DOT11-4-MAXRETRIES: Packet to client 0017.23a9.c1e8 reached max retries, removing the client
    *Feb 24 16:49:27.530: %DOT11-4-MAXRETRIES: Packet to client 0017.23a9.b461 reached max retries, removing the client
    *Feb 24 16:49:27.530: %DOT11-4-MAXRETRIES: Packet to client 0017.23a9.b474 reached max retries, removing the client
    *Feb 24 16:49:27.594: %DOT11-4-MAXRETRIES: Packet to client 0017.230a.ee2e reached max retries, removing the client
    *Feb 24 16:49:28.134: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.230b.9bdf Associated KEY_MGMT[WPA PSK]
    *Feb 24 16:49:28.442: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    *Feb 24 16:49:29.806: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.230a.ee2e Associated KEY_MGMT[WPA PSK]
    *Feb 24 16:49:35.038: %DOT11-6-ASSOC: Interface Dot11Radio0, Station  f409.d8b0.313d Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:49:37.294: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.230a.ee16 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:49:37.418: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.230a.ee6b Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:49:41.622: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.c1e8 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:49:41.642: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b474 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:49:41.726: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b461 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:49:42.522: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b470 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:49:42.886: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b464 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 16:49:57.310: %DOT11-6-ASSOC: Interface Dot11Radio0, Station BE-AP4 6c88.145d.0db8 Associated KEY_MGMT[WPA PSK]
    *Feb 24 16:50:02.818: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station f409.d8b0.313d Reason: Sending station has left the BSS
    *Feb 24 16:50:06.014: %DOT11-6-ASSOC: Interface Dot11Radio0, Station  f409.d8b0.313d Associated KEY_MGMT[WPA PSK]
    *Feb 24 16:52:37.670: %DOT11-7-AUTH_FAILED: Station 9018.7cb5.01f5 Authentication failed
    *Feb 24 16:57:13.026: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b474 Reason: Sending station has left the BSS
    *Feb 24 16:57:13.034: %DOT11-4-MAXRETRIES: Packet to client 0017.23a9.b474 reached max retries, removing the client
    *Feb 24 16:58:37.262: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b464 Reason: Sending station has left the BSS
    *Feb 24 16:58:43.302: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b461 Reason: Sending station has left the BSS
    *Feb 24 16:58:46.710: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.c1e8 Reason: Sending station has left the BSS
    *Feb 24 16:58:48.338: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b470 Reason: Sending station has left the BSS
    *Feb 24 17:02:27.078: %DOT11-7-AUTH_FAILED: Station 9018.7cb5.01f5 Authentication failed
    *Feb 24 17:04:45.486: %DOT11-6-ASSOC: Interface Dot11Radio0, Station BE-AP4 843a.4b55.12ec Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 17:04:46.514: %DOT11-7-AUTH_FAILED: Station 9018.7cb5.01f5 Authentication failed
    *Feb 24 17:19:47.858: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 6c88.145d.0db8 Reason: Sending station has left the BSS
    *Feb 24 17:19:59.694: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.c1e8 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 17:25:36.682: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b470 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 17:26:40.910: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b470 Reason: Sending station has left the BSS
    *Feb 24 17:27:01.002: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b470 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 17:27:27.390: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b470 Reason: Sending station has left the BSS
    *Feb 24 17:27:47.626: %DOT11-4-MAXRETRIES: Packet to client f409.d8b0.313d reached max retries, removing the client
    *Feb 24 17:27:47.626: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station f409.d8b0.313d Reason: Previous authentication no longer valid
    *Feb 24 17:27:47.630: %DOT11-4-MAXRETRIES: Packet to client f409.d8b0.313d reached max retries, removing the client
    *Feb 24 17:31:49.458: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.c1e8 Reason: Sending station has left the BSS
    *Feb 24 17:32:53.530: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 843a.4b55.12ec Reason: Sending station has left the BSS
    *Feb 24 17:40:59.858: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.c1e8 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 18:08:22.578: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.c1e8 Reason: Sending station has left the BSS
    *Feb 24 18:36:31.482: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.230b.9bdf Reason: Previous authentication no longer valid
    *Feb 24 18:57:16.774: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b470 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 18:57:25.642: %DOT11-7-AUTH_FAILED: Station f409.d8b0.313d Authentication failed
    *Feb 24 18:57:38.958: %DOT11-6-ASSOC: Interface Dot11Radio0, Station  f409.d8b0.313d Associated KEY_MGMT[WPA PSK]
    *Feb 24 18:59:28.442: %DOT11-6-ASSOC: Interface Dot11Radio0, Station BE-AP4 6c88.145d.0db8 Associated KEY_MGMT[WPA PSK]
    *Feb 24 19:23:40.450: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b470 Reason: Sending station has left the BSS
    *Feb 24 19:40:30.433: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 6c88.145d.0db8 Reason: Sending station has left the BSS
    *Feb 24 19:40:30.449: %DOT11-6-ASSOC: Interface Dot11Radio0, Station BE-AP4 6c88.145d.0db8 Associated KEY_MGMT[WPA PSK]
    *Feb 24 19:45:30.009: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 6c88.145d.0db8 Reason: Sending station has left the BSS
    *Feb 24 19:45:38.109: %DOT11-6-ASSOC: Interface Dot11Radio0, Station BE-AP4 6c88.145d.0db8 Associated KEY_MGMT[WPA PSK]
    *Feb 24 19:48:41.953: %DOT11-4-MAXRETRIES: Packet to client 6c88.145d.0db8 reached max retries, removing the client
    *Feb 24 19:48:41.953: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 6c88.145d.0db8 Reason: Previous authentication no longer valid
    *Feb 24 19:48:42.029: %DOT11-4-MAXRETRIES: Packet to client 6c88.145d.0db8 reached max retries, removing the client
    *Feb 24 19:48:45.305: %DOT11-6-ASSOC: Interface Dot11Radio0, Station BE-AP4 6c88.145d.0db8 Associated KEY_MGMT[WPA PSK]
    *Feb 24 19:52:20.877: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
    *Feb 24 19:52:21.877: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
    *Feb 24 19:52:30.957: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
    *Feb 24 19:52:31.957: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
    *Feb 24 19:57:43.173: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 6c88.145d.0db8 Reason: Sending station has left the BSS
    *Feb 24 20:00:09.885: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b433 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:01:08.445: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b465 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:01:25.453: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b453 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:01:47.549: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b449 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:02:07.469: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b456 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:02:23.713: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b5da Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:02:45.761: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b466 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:02:53.133: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b449 Reason: Sending station has left the BSS
    *Feb 24 20:02:57.913: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b456 Reason: Sending station has left the BSS
    *Feb 24 20:03:14.521: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b5db Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:03:24.673: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b466 Reason: Sending station has left the BSS
    *Feb 24 20:03:29.653: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b453 Reason: Sending station has left the BSS
    *Feb 24 20:03:39.125: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b458 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:03:49.093: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b5da Reason: Sending station has left the BSS
    *Feb 24 20:03:51.113: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b5d7 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:03:52.549: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b5da Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:03:54.905: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b433 Reason: Sending station has left the BSS
    *Feb 24 20:04:12.565: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b458 Reason: Sending station has left the BSS
    *Feb 24 20:04:19.213: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b5db Reason: Sending station has left the BSS
    *Feb 24 20:04:22.865: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b465 Reason: Sending station has left the BSS
    *Feb 24 20:04:24.965: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b465 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:04:26.341: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b433 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:04:27.089: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b5d7 Reason: Sending station has left the BSS
    *Feb 24 20:05:29.437: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b5d7 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:06:46.761: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b470 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:06:50.233: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b474 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:07:03.725: %DOT11-6-ASSOC: Interface Dot11Radio0, Station CBP BE 0017.23a9.b461 Reassociated KEY_MGMT[WPA PSK]
    *Feb 24 20:07:52.513: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.230a.ee16 Reason: Previous authentication no longer valid
    *Feb 24 20:08:09.513: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.230a.ee6b Reason: Previous authentication no longer valid
    *Feb 24 20:08:40.685: %DOT11-6-ROAMED: Station f409.d8b0.313d Roamed to 2c3e.cf54.f590
    *Feb 24 20:08:40.685: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station f409.d8b0.313d Reason: Sending station has left the BSS
    *Feb 24 20:09:40.053: %DOT11-7-AUTH_FAILED: Station f409.d8b0.313d Authentication failed
    *Feb 24 20:31:25.833: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b433 Reason: Sending station has left the BSS
    *Feb 24 20:31:29.373: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b5d7 Reason: Sending station has left the BSS
    *Feb 24 20:31:52.053: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b5da Reason: Sending station has left the BSS
    *Feb 24 20:32:29.245: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b465 Reason: Sending station has left the BSS
    *Feb 24 20:33:46.221: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b470 Reason: Sending station has left the BSS
    *Feb 24 20:33:49.717: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b474 Reason: Sending station has left the BSS
    *Feb 24 20:34:03.213: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0017.23a9.b461 Reason: Sending station has left the BSS

    Hi
    if you want to get any higher data rates (802.11n) you have to configure WPA2/AES & not TKIP
    dot11 ssid BE-WAP1
       vlan 15
       authentication open
       authentication key-management wpa version 2
       guest-mode
       wpa-psk ascii 7 password
    interface Dot11Radio0
     encryption vlan 15 mode ciphers aes-ccm
     no encryption vlan 15 mode ciphers tkip
     ssid BE-WAP1
    Also enable 5GHz band as well. Then see if the problem occurs for both bands
    interface Dot11Radio1
     encryption vlan 15 mode ciphers aes-ccm
     ssid BE-WAP1
     channel width 40-above
     no shut
    interface Dot11Radio0.15
     encapsulation dot1Q 15 native
     bridge-group 1
    HTH
    Rasika
    **** Pls rate all useful responses ****

  • 30EA1: Mac version will not disconnect from database

    Hello,
    I was trying the EA1 version on my mac this morning and although I opened a couple of connections to different databases fine, when i did right click / disconnect it seemed to carry on being connected. I didn't run any queries in that database whatsoever. Any thoughts?
    Thanks

    Yes, I experience this behavior as well. I run many queries, and sometimes I can disconnect successfully, but if I ever leave the application alone for more than an unspecified timeout period, it becomes increasingly unresponsive, one of the first things to go awry is the connection options.
    SQLdeveloper Version 3.0.02 Build MAIN-02.37
    Mac OS X 10.6.5
    Java VM 13.3.0
    Regards,
    Geof
    Portland, OR

  • Client disconnection notification for NIO server

    A server accepts connections from clients and registers accepted channels for reading:
    while (true)
        if (selector.select()>0)
            Iterator<SelectionKey> iterator = selector.selectedKeys().iterator();
            while(iterator.hasNext())
                SelectionKey opKey = iterator.next();
                iterator.remove();
                if (opKey.isAcceptable())
                    clientSocketChannel = serverSocketChannel.accept();
                    clientSocketChannel.configureBlocking(false);
                    clientSocketChannel.register(selector, SelectionKey.OP_READ);
    . . .One of the server's clients disconnects from it by means of socketChannel.close() while the servert is locked with selector.select() (that is the server have nothing to read from its clients and nobody is connecting to it).Will the server be unlocked when the client performs socketChannel.close()? If so, what notification/exception will the server receive?

    One of the server's clients disconnects from it by means of socketChannel.close() while the servert is locked with selector.select()The select() will immediately return; the corresponding channel will be readable; and the read() will return -1.

  • How to get data from database to JComboBox

    hi
    i am trying to get data which is in database. here the problem is i am getting only one row in the JcomboBox
    i want all data just like list. i dont know how to get that . below is the code plz any one help me....
    import javax.swing.*;
    import javax.swing.JList.*;
    import java.awt.*;
    import java.awt.event.*;
    import java.lang.String.*;
    import java.lang.Integer.*;
    import java.sql.*;
    public class customer_code extends JFrame implements ActionListener
    Container c=getContentPane();
    JLabel customer_code=new JLabel("Customer Code and Name");
    customer_code()
    super("Customer Details");
    setSize(300,250);
    setVisible(true);
    setLayout(null);
    setLocation(430,310);
    Font f=new Font("SansSerif",1,16);
    Font f1=new Font("SansSerif",0,14);
    customer_code.setBounds(10,20,250,30);
    add(customer_code);
    customer_code.setFont(f);
    ResultSet rs=null;
    String j=null,k=null;
    try
    System.out.println("MySQL Connect Example.");
    Statement st=null;
    Connection con=null;
    Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
    con = DriverManager.getConnection("jdbc:odbc:project","vikky","vishu");
    System.out.println("Connected to the database");
    st=con.createStatement();
    rs=st.executeQuery(" select code as c,Customer_name as n from customer_details ");
    while(rs.next())
    j=rs.getString("c");
    k=rs.getString("n");
    System.out.println(j);
    System.out.println(k);
    String[] names = new String[] {j,k};
    JComboBox comboBox = new JComboBox(names);
    add(comboBox);
    comboBox.setBounds(25,60,250,50);
    comboBox.setFont(f);
    comboBox.addActionListener(this);
    comboBox.setMaximumRowCount(10);
    con.close();
    System.out.println("Disconnected from database");
    catch (Exception e)
    e.printStackTrace();
    public void actionPerformed(ActionEvent event)
    if ("comboBoxChanged".equals(event.getActionCommand()))
    System.out.println("User has selected an item from the combo box.");
    JComboBox comboBox = (JComboBox) event.getSource();
    if(comboBox.getSelectedItem().equals("None"))
    public static void main(String agr[])
    customer_code cd=new customer_code();
    }

    r035198x wrote:
    Also separate that database code from interface display code.
    You should never access the database on the EDT.
    See [Doing Swing Right|http://bytes.com/topic/java/insights/853297-doing-swing-right] for more details.
    Yes! By the time you are working with Swing and JDBC you should already know how to structure code. If not, then you are not ready for these topics and you've jumped the gun.

  • Database holds the session after disconnecting from DB !

    Dear Friends ,
    I am using Oracle10g database (10.2.0.4) as our production server in AIX 6.1 . Recently we purchase
    an application which is used for a banking module . The application user name 'INCHEQS' .
    Now the problem is , when we are connection through this user from the client end then ,
    a lot of user has connected although the users are not connected . i.e., If a user disconnect
    from his session but that session still connected in my database .
    Plz see the output :
    SQL> select count(*) from v$session where username='INCHEQS';
    COUNT(*)
    100
    SQL> select username,status from v$session where username like 'INCHEQS% ;
    USERNAME STATUS
    INCHEQS INACTIVE
    INCHEQS INACTIVE
    INCHEQS INACTIVE
    INCHEQS INACTIVE
    INCHEQS INACTIVE
    INCHEQS INACTIVE
    100 rows selected.
    In the above output of my production database , all the above users are not connected , but the
    session keeps on the database . In this moment , How can I solve the issue . Is there any related
    oracle parameter (Rather than RESOURCE_LIMT) to remove all the above INACTIVE users after a specified time .
    Here I mention that , it is not possible to enable 'RESOURCE_LIMIT' parameter in my Database .Edited by: shipon_97 on Aug 26, 2010 2:04 PM

    It does sound like a connection pooling issue. Does the application have a web server component? Do the number of sessions grow over time or do they hold steady at a certain value.
    You should talk to the support area for the purchased app to see if there are steps to limit the number of sessions, if that is a problem.
    Also, as a workaround you may be able to restart the web server on a regular basis to clear out those sessions. I would only do that if the session count continues to grow over time.

  • How to specifiy the provider to be Oracle.ManagedDataAccess.Client when creating a dynamic connection string with EF Code First from Database?

    I am trying to use the relatively new Code First from Database with the newest EF (6.x) and on an Oracle database (11g, but I have installed the newest ODTwithODAC). First of all, it works fine as long as the connection string is inside the App.Config file. But when I try to build it dynamically in the C# code (or rather, statically at the moment) it fails. I have it working with a dynamically built connection string when doing Model from Database though, so I'm at a loss right now.
    First, I have created a second constructor for the context class that takes a string and does base(connectionString). Then I build the connection string via
    OracleConnectionStringBuilder oracleBuilder = new OracleConnectionStringBuilder();
    oracleBuilder.DataSource = "TEST.BLA.COM";
    oracleBuilder.UserID = "ABC";
    oracleBuilder.Password = "abc";
    oracleBuilder.PersistSecurityInfo = true;
    string connection = oracleBuilder.ToStrin();
    Now trying to open an EntityConnection by giving to it this provider-specific connection string (or even the static one from the App.Config) doesn't work; I get "keyword not supported: user id"). Trying it by creating a context and giving this connection string doesn't work either. I'm pretty sure that this is because I didn't specify the provider to use; after all, it should use the Oracle.ManagedDataAccess.Client provider and not an SQL Server based one.
    I then tried to get around this by using an EntityConnectionStringBuilder on top and specifying the provider keyword there, but then I get "keyword not supported: provider" when using it in the context constructor, and "the 'metadata' keyword is always required" when using it with the EntityConnection constructor.
    As I said above: I bet it's the provider that I have to specify somehow, but I don't know how. The code that does work is the following:
    using (var context = new Model())
    context.Database.Connection.Open();
    context.Database.Connection.Close();
    When I read context.Database.Connection.ConnectionString, it is exactly the provider-specific connection string I created above, but I don't know where to specify the provider again. Do you know of any way to do this? Certainly there must be one.
    PS: I have also posted this question on http://stackoverflow.com/questions/27979454/ef-code-first-from-database-with-managed-oracle-data-access-dynamic-connection because it is quite urgent and I'd like to use Code First from Database. Otherwise I'd have to go "back" to using Model from Database again, which is not ideal because we have updatable views where the .edmx-file has to be edited after every reload of the model, while with Code First from DB inserting into the view automatically works.

    I am trying to use the relatively new Code First from Database with the newest EF (6.x) and on an Oracle database (11g, but I have installed the newest ODTwithODAC). First of all, it works fine as long as the connection string is inside the App.Config file. But when I try to build it dynamically in the C# code (or rather, statically at the moment) it fails. I have it working with a dynamically built connection string when doing Model from Database though, so I'm at a loss right now.
    First, I have created a second constructor for the context class that takes a string and does base(connectionString). Then I build the connection string via
    OracleConnectionStringBuilder oracleBuilder = new OracleConnectionStringBuilder();
    oracleBuilder.DataSource = "TEST.BLA.COM";
    oracleBuilder.UserID = "ABC";
    oracleBuilder.Password = "abc";
    oracleBuilder.PersistSecurityInfo = true;
    string connection = oracleBuilder.ToStrin();
    Now trying to open an EntityConnection by giving to it this provider-specific connection string (or even the static one from the App.Config) doesn't work; I get "keyword not supported: user id"). Trying it by creating a context and giving this connection string doesn't work either. I'm pretty sure that this is because I didn't specify the provider to use; after all, it should use the Oracle.ManagedDataAccess.Client provider and not an SQL Server based one.
    I then tried to get around this by using an EntityConnectionStringBuilder on top and specifying the provider keyword there, but then I get "keyword not supported: provider" when using it in the context constructor, and "the 'metadata' keyword is always required" when using it with the EntityConnection constructor.
    As I said above: I bet it's the provider that I have to specify somehow, but I don't know how. The code that does work is the following:
    using (var context = new Model())
    context.Database.Connection.Open();
    context.Database.Connection.Close();
    When I read context.Database.Connection.ConnectionString, it is exactly the provider-specific connection string I created above, but I don't know where to specify the provider again. Do you know of any way to do this? Certainly there must be one.
    PS: I have also posted this question on http://stackoverflow.com/questions/27979454/ef-code-first-from-database-with-managed-oracle-data-access-dynamic-connection because it is quite urgent and I'd like to use Code First from Database. Otherwise I'd have to go "back" to using Model from Database again, which is not ideal because we have updatable views where the .edmx-file has to be edited after every reload of the model, while with Code First from DB inserting into the view automatically works.

  • How to delete a row from database table in facade client

    Hi all,
    I followed the tutorial in creating a persistence entity from database table, then a session facade. Then I followed the tutorial to create a sample client to test the model. In the session facade, I could use persistEntity method to insert a record to the database. I am just thinking of an extension to the tutorial, i.e., being able to delete the record too. So I created a new method removeEntity in the session facade
    public void removeEntity(Object entity) {
    entity=em.merge(entity);
    em.remove(entity);
    em.flush();
    and called it in the sample client. It was executed without any error, but the record in the table still exists.
    I tried to look around for a solution, but I did not find one. Would anybody here please help out? Many thanks in advance!

    Hi Frank,
    I tried the code snippet, but I got the following exception when executing this code:
    javax.ejb.EJBException: EJB Exception: ; nested exception is:
         java.lang.IllegalStateException: The method public abstract javax.persistence.EntityTransaction javax.persistence.EntityManager.getTransaction() cannot be invoked in the context of a JTA EntityManager.; nested exception is: java.lang.IllegalStateException: The method public abstract javax.persistence.EntityTransaction javax.persistence.EntityManager.getTransaction() cannot be invoked in the context of a JTA EntityManager.
    java.lang.IllegalStateException: The method public abstract javax.persistence.EntityTransaction javax.persistence.EntityManager.getTransaction() cannot be invoked in the context of a JTA EntityManager.
         at weblogic.deployment.BasePersistenceContextProxyImpl.validateInvocation(BasePersistenceContextProxyImpl.java:121)
         at weblogic.deployment.BasePersistenceContextProxyImpl.invoke(BasePersistenceContextProxyImpl.java:86)
         at weblogic.deployment.TransactionalEntityManagerProxyImpl.invoke(TransactionalEntityManagerProxyImpl.java:91)
         at weblogic.deployment.BasePersistenceContextProxyImpl.invoke(BasePersistenceContextProxyImpl.java:80)
         at weblogic.deployment.TransactionalEntityManagerProxyImpl.invoke(TransactionalEntityManagerProxyImpl.java:26)
         at $Proxy141.getTransaction(Unknown Source)
         at model.SessionEJBBean.removeEntity(SessionEJBBean.java:60)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37)
         at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:55)
         at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
         at $Proxy143.removeEntity(Unknown Source)
         at model.SessionEJB_qxt9um_SessionEJBImpl.removeEntity(SessionEJB_qxt9um_SessionEJBImpl.java:142)
         at model.SessionEJB_qxt9um_SessionEJBImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
         at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    javax.ejb.EJBException: EJB Exception: ; nested exception is:
         java.lang.IllegalStateException: The method public abstract javax.persistence.EntityTransaction javax.persistence.EntityManager.getTransaction() cannot be invoked in the context of a JTA EntityManager.; nested exception is: java.lang.IllegalStateException: The method public abstract javax.persistence.EntityTransaction javax.persistence.EntityManager.getTransaction() cannot be invoked in the context of a JTA EntityManager.
         at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.unwrapRemoteException(RemoteBusinessIntfProxy.java:109)
         at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:91)
         at $Proxy0.removeEntity(Unknown Source)
         at model.SessionEJBClient.main(SessionEJBClient.java:71)
    Caused by: java.lang.IllegalStateException: The method public abstract javax.persistence.EntityTransaction javax.persistence.EntityManager.getTransaction() cannot be invoked in the context of a JTA EntityManager.
         at weblogic.deployment.BasePersistenceContextProxyImpl.validateInvocation(BasePersistenceContextProxyImpl.java:121)
         at weblogic.deployment.BasePersistenceContextProxyImpl.invoke(BasePersistenceContextProxyImpl.java:86)
         at weblogic.deployment.TransactionalEntityManagerProxyImpl.invoke(TransactionalEntityManagerProxyImpl.java:91)
         at weblogic.deployment.BasePersistenceContextProxyImpl.invoke(BasePersistenceContextProxyImpl.java:80)
         at weblogic.deployment.TransactionalEntityManagerProxyImpl.invoke(TransactionalEntityManagerProxyImpl.java:26)
         at $Proxy141.getTransaction(Unknown Source)
         at model.SessionEJBBean.removeEntity(SessionEJBBean.java:60)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37)
         at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:55)
         at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
         at $Proxy143.removeEntity(Unknown Source)
         at model.SessionEJB_qxt9um_SessionEJBImpl.removeEntity(SessionEJB_qxt9um_SessionEJBImpl.java:142)
         at model.SessionEJB_qxt9um_SessionEJBImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
         at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Process exited with exit code 0.

  • BEx Error: Automation error: Object invoked has disconnected from clients

    Hi,
    We have a user here that attempts to access a query in BEx (MS Excel), but receives this error message:
    - Runtime error '-2147417848 (80010108)':
      Automation error
      The object invoked has disconnected from its clients.
    Any ideas.
    Thanks,
    John

    Please go through the OSS note 857360..
    https://websmp108.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=857360&_NLANG=E
    This talks about your error..
    Solution
    1) Replace the RFC library
    librfc32.dll
    on the client PC with a current version.
    620: Version >=  6206.6.1938.4727  (620x.x.x.4727).
    640: Version >=  6400.3.79.4740    (640x.x.x.4740).
    There is a version of the 620 and 640 librfc32.dll in the attachments: and we recommend that you use Version 640 (compatible with SAPGUI 620) (see below).
    620 Version: Download librfc32.rar. Rename it librfc32.exe. This file extracts itself automatically.
    640 Version: Download librfc32.zip. You can use WinZip to extract this file.
    Note:
    It seems that newer (delivered) versions of 6.20 librfc32.dll do not contain this fix. In this case, you can also use the 6.40 librfc32.dll. For reasons of compatibility, you should use the following Microsoft DLLs that are available on the PC for this: msvcr71.dll and to be msvcp71.dll (see Note 684106).

  • Cisco AnyConnect Secured Mobility Client not saving the VPN url after disconnecting from session/restarting client

    Hello there.
    I am having a problem with Cisco AnyConnect version 3.1.04072. When one of my colleagues disconnects from the VPN session, closes out the program, and then later on, reopens the client, the address that he manually entered did not save and it's defaulting on the two now-defunct VPN servers listed.
    Here's an example to see if it makes more sense:
    -User opens Cisco AnyConnect. By default, there are two selections available on the pulldown:
    SSLVPN.abcdefg.com
    access.abcdefg.ca
    These two VPN servers are now defunct and we use a new VPN server:
    access.abcdefg.com
    The user has to manually type it in. He is now able to connect. However, when disconnected. Regardless if the program is closed or not, it does not save the new VPN server address, rather goes back to the default two VPN servers listed.
    I've checked XML, HTML, registry keys, sys files, dll files to see if I can change the default servers manually. No sign of it.
    I'm hoping that someone out there knows a solution to fix it.
    Thanks in advance!

    Hi Vergel ,
    You can create Anyconnect client profile on ASA. In this profile , you can define the hostname/IP that you wish to connect , along with hostname/IP that should be displayed on the client.
    In the client profile , you can define these parameters - "HostName" and "HostAddress" as "access.abcdefg.com" so that any user , who tries to connects , will see "access.abcdefg.com" as the name displayed in the anyconnect connect field.
    On the client, the xml profile (C:\ProgramData\Cisco\Cisco AnyConnect Secure Mobility Client\Profile) [Win 7] can be seen using those parameters as follows:-
            <HostEntry>
                <HostName>access.abcdefg.com</HostName>
                <HostAddress>access.abcdefg.com</HostAddress>
            </HostEntry>
    Ref:- http://www.cisco.com/c/en/us/td/docs/security/vpn_client/anyconnect/anyconnect30/administration/guide/anyconnectadmin30/ac03vpn.html#89103
    Additionally, you can try to delete preferences.xml file to remove the redundant hostnames from the anyconnect connect filed.
    Path for preferences.xml is C:\Users\Cisco\AppData\Local\Cisco\Cisco AnyConnect Secure Mobility Client (Win 7),
    Hope this helps.
    Regards,
    Dinesh Moudgil
    P.S. Please rate helpful posts.

Maybe you are looking for