Aps not finding secondary controller

I have just installed a secondary WLC 4402 where a client has 1121 APs and 1010 APs and I am slightly confused.
We have 2 CISCO-LWAPP-CONTROLLER entries in DNS
The WLCs are WLC1 and WLC2
The 1010 APs fail over to the secondary controller perfectly well.
The 1121 APs do not fail over.
I have given the APs primary and secondary controller names of WLC1 and WLC2.
Is this due to Option 43 not being configured correctly.
I believe though I have not investigated that there is a single entry for the 1121 APs in the DHCP scope for option 43 of the original conmtroller but there is no entry for the 1010 APs.
They are using the same DHCP scope in a layer 2 implementation.
Any help appreciated

When the ap has joined a wlc, the dns and dhcp option 43 is not used. The information created in the mobility group (mac address, ip address and mobility group name) is used. This is how ap's learn of the other wlc. Setting the ap's primary and secondary and or tertiary wlc is required for ap's to be able to join the other wlc. Option 43 and dns is used if the ap goes throught the proccess of finding a wlc if the primary, secondary and or tertiary wlc is not found. It seems to me that the ap's have properly joined a wlc, there for, you need to verify why the 1121'a are not joining the secondary.
First of all, is the mobility group configured correctly and is ap fallback enabled or not. Also, verify that you can mping and eping the controllers. Is the wlc set to layer 2 or layer 3 mode? I think that the 1121 needs the wlc to be in layer 3, but I will check.
What you should also do is console into the ap and post the log so we can see what errors the ap is getting.
Here is a link. Search for layer 2
http://www.cisco.com/en/US/prod/collateral/wireless/ps5678/ps6306/prod_bulletin0900aecd80321a2c_ps6521_Products_Bulletin.html
Here is a link for AP Fallback:
http://www.cisco.com/en/US/tech/tk722/tk721/technologies_tech_note09186a00807a85b8.shtml

Similar Messages

  • 1131 and 1141 APs not finding the controller

    We have deployed about 40 of these and about half have found the controller. The others have not. I have used option 43 in the past but lately they were able to find the contrller without that. I also took out the lwapp-controller name out of dns as we have 4 buildings of these etc. Should I put the controller name in dns and what is that default name.
    thanks
    Gary

    If the AP's are not on the same subnet as the controller, and you are not using Over the Air Provisioning, then you need to use DHCP Option 43, put your DNS entry back in, or set the controller address manually via the console port on the AP.
    The host name for the DNS entry is CISCO-LWAPP-CONTROLLER. If you're adding that entry, then you might want to also add CISCO-CAPWAP-CONTROLLER pointing to the same address. While I believe that all current AP's will try to resolve CISCO-LWAPP-CONTROLLER (even if they are CAPWAP APs), this may not be the case in the future.
    We use the DNS feature and then set the AP's appropriate primary/secondary controller after it joins.
    Here's a good article about the AP join process:
    http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a00806c9e51.shtml
    Here's a good article about troubleshooting AP's that won't join:
    http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a00808f8599.shtml

  • BEA-000802: Could not find secondary on remote server

              I have a WebLogic cluster setup with two WebLogicServers, Admin Server and LoadBalancer
              with HttpClusterServlet.
              The first time I log into my web application I get the following error on managedServer
              1:
              ####<Jun 3, 2003 5:27:01 PM EDT> <Notice> <Cluster> <freerider1> <managedServer_1>
              <main> <<WLS Kernel>> <> <BEA-000102> <Joining cluster cluster on 237.0.0.1:7001>
              ####<Jun 3, 2003 5:27:01 PM EDT> <Notice> <WebLogicServer> <freerider1> <managedServer_1>
              <main> <<WLS Kernel>> <> <BEA-000330> <Started WebLogic Managed Server "managedServer_1"
              for domain "mydomain" running in Production Mode>
              ####<Jun 3, 2003 5:27:01 PM EDT> <Notice> <WebLogicServer> <freerider1> <managedServer_1>
              <main> <<WLS Kernel>> <> <BEA-000365> <Server state changed to RUNNING>
              ####<Jun 3, 2003 5:27:01 PM EDT> <Notice> <WebLogicServer> <freerider1> <managedServer_1>
              <main> <<WLS Kernel>> <> <BEA-000360> <Server started in RUNNING mode>
              ####<Jun 3, 2003 5:27:03 PM EDT> <Info> <WebLogicServer> <freerider1> <managedServer_1>
              <ListenThread.Default> <<WLS Kernel>> <> <BEA-000213> <Adding address: 165.218.167.197
              to licensed client list>
              ####<Jun 3, 2003 5:29:10 PM EDT> <Info> <WebLogicServer> <freerider1> <managedServer_1>
              <ListenThread.Default> <<WLS Kernel>> <> <BEA-000213> <Adding address: 165.218.167.196
              to licensed client list>
              ####<Jun 3, 2003 5:29:10 PM EDT> <Info> <HTTP> <freerider1> <managedServer_1>
              <ExecuteThread: '12' for queue: 'weblogic.kernel.Default'> <<anonymous>> <> <BEA-101047>
              <[ServletContext(id=23107068,name=smc,context-path=/smc)] /*: init>
              ####<Jun 3, 2003 5:29:10 PM EDT> <Info> <HTTP> <freerider1> <managedServer_1>
              <ExecuteThread: '12' for queue: 'weblogic.kernel.Default'> <<anonymous>> <> <BEA-101047>
              <[ServletContext(id=23107068,name=smc,context-path=/smc)] /*: Using standard I/O>
              ####<Jun 3, 2003 5:29:23 PM EDT> <Error> <Kernel> <freerider1> <managedServer_1>
              <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-000802>
              <ExecuteRequest failed
              weblogic.utils.NestedError: Could not find secondary on remote server - with
              nested exception:
              [weblogic.cluster.replication.NotFoundException: Unable to find object 823670646633126749].
              weblogic.cluster.replication.NotFoundException: Unable to find object 823670646633126749
                   at weblogic.cluster.replication.ReplicationManager.getPrimary(ReplicationManager.java:867)
                   at weblogic.cluster.replication.ReplicationManager.updateSecondary(ReplicationManager.java:712)
                   at weblogic.servlet.internal.session.ReplicatedSessionData.syncSession(ReplicatedSessionData.java:486)
                   at weblogic.servlet.internal.session.ReplicatedSessionContext.sync(ReplicatedSessionContext.java:176)
                   at weblogic.servlet.internal.ServletRequestImpl.syncSession(ServletRequestImpl.java:2440)
                   at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3633)
                   at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2573)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
              --------------- nested within: ------------------
              weblogic.utils.NestedError: Could not find secondary on remote server - with nested
              exception:
              [weblogic.cluster.replication.NotFoundException: Unable to find object 823670646633126749]
                   at weblogic.servlet.internal.session.ReplicatedSessionData.syncSession(ReplicatedSessionData.java:494)
                   at weblogic.servlet.internal.session.ReplicatedSessionContext.sync(ReplicatedSessionContext.java:176)
                   at weblogic.servlet.internal.ServletRequestImpl.syncSession(ServletRequestImpl.java:2440)
                   at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3633)
                   at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2573)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
              Does anybody know this problem? Any help on this greatly appreciated.
              Thanks, Marcel
              

    Hello Rozi,
              I've got the same error that you.
              Have you find out what is causing it?
              Thank you.

  • APs not associating with Controller after upgrade

    This is pretty bad.
    I've been upgrading our controllers to 4.2.209.0 without any problems untill today. The controller upgraded fine but, the APs aren't showing up anywhere. They aren't associating with any controller. I've shut/no shut the PoE ports. They show connected. The WCS says they are not associated with any controller. What should I do. Roll back the image? Will this help?
    Thanks Pat.

    Surendra,
    Thanks for the response. I got this from debug dhcp detail
    DHCP: QScan: Timed out Selecting state%Unknown DHCP problem.. No allocation possible
    I was pretty desparate at the time so, I wasn't able to trouble-shoot any further. After I saw the DHCP debug I deleted the normal DHCP server address, created a scope for the APs and configured it on the AP management interface and the APs got addresses. After the APs got their addresses, the clients got their addresses from the regular DHCP server. I will try again with the upgrade as I rolled back to 4.2.112.0. Atleast I know I can get an ip from the controller if I need.
    Do you know of any reason why my APs weren't getting addresses. Even when I rolled back they weren't getting addresses. The config hadn't changed.
    Thanks, Pat.

  • LAP 1142 not finding 4404 controller

    My 4404 is has it's 4 gig ports connected to my 6509e via port-channel.
    My 1142 is also connected to the 6509e and it set in vlan 11.
    The management interface of my 4404 has an address in vlan 11 and is set to tag vlan 11.
    When I power up the 1142, I can see it via cdp on the 6509e, but when I go to WCS and look at APs, it says none detected.
    Any ideas?

    1.  What is the firmware of the WLC?
    2.  What is the error logs from the LAP and the WLC?
    3.  Is the NTP server of the WLC set correctly?
    4.  Can the LAP ping the Management IP address of the WLC?

  • 3502i APs not joining controller

    So basically my infrastructure consists of four 4402 WLCs running on 7.0.235.3. I'm trying to get new access points to join to the environment, but I am having difficulty doing so. All currently joined APs work fine and are operating well. I'm getting a red, green, off blink code which means it's trying to join, but never does. The other one I get a constantly blinking green but it never joins either. I've setup option 43 in DHCP, added cisco-capwap-controller entries in DNS thinking it was because those are missing, and still cannot get these two access points to join. Can anyone think why it would not be joining?
    The access points and WLC are all on the Same VLAN by the way.

    Hello,
    In a Cisco Unified Wireless network, the LAPs  must first discover and       join a WLC before they can service wireless clients.
    Originally, the controllers only operated in Layer 2 mode. In Layer  2       mode, the LAPs are required to be on the same subnet as the management       interface and the Layer 3 mode AP-manager interface is not present on  the       controller. The LAPs communicate with the controller using Layer 2       encapsulation only (ethernet encapsulation) and do not Dynamic Host       Configuration Protocol (DHCP) an IP address.
    When Layer 3 mode on the controller was developed, a new Layer 3       interface called AP-manager was introduced. In Layer 3 mode, the LAPs  would       DHCP an IP address first and then send their discovery request to the       management interface using IP addresses (Layer 3). This allowed the  LAPs to be       on a different subnet than the management interface of the controller.  Layer 3       mode is the dominate mode today. Some controllers and LAPs can only  perform       Layer 3 mode.
    However, this presented a new problem: how did the LAPs find the       management IP address of the controller when it was on a different  subnet?
    In Layer 2 mode, they were required to be on the same subnet. In  Layer       3 mode, the controller and LAP are essentially playing hide and seek  in the       network. If you do not tell the LAP where the controller is via DHCP  option 43,       DNS resolution of "Cisco-lwapp-controller@local_domain", or statically       configure it, the LAP does not know where in the network to find the  management       interface of the controller.
    In addition to these methods, the LAP does automatically look on  the       local subnet for controllers with a 255.255.255.255 local broadcast.  Also, the       LAP remembers the management IP address of any controller it joins  across       reboots. Therefore, if you put the LAP first on the local subnet of  the       management interface, it will find the controller's management  interface and       remember the address. This is called priming. This does not help find  the       controller if you replace a LAP later on. Therefore, Cisco recommends  using the       DHCP option 43 or DNS methods.
    When the LAPs discover the controller, they do not know if the       controller is in Layer 2 mode or Layer 3 mode. Therefore, the LAPs  always       connect to the management interface address of the controller first  with a       discovery request. The controller then tells the LAP which mode it is  in the       discovery reply. If the controller is in Layer 3 mode, the discovery  reply       contains the Layer 3 AP-manager IP address so the LAP can send a join  request       to the AP-manager interface next.
    Note: By default both management and AP-manager interfaces are  left           untagged on their VLAN during configuration. In case these are tagged,  make           sure they are tagged to the same VLAN in order to properly receive  discovery           and join response from the WLC.
    The LWAPP AP goes through this process on startup for Layer 3       mode:
    The LAP boots and DHCPs an IP address if it was not previously           assigned a static IP address.
    The LAP sends discovery requests to controllers through the various           discovery algorithms and builds a controller list. Essentially, the  LAP learns           as many management interface addresses for the controller list as  possible via:
    DHCP option 43 (good for global companies where offices and             controllers are on different continents)
    DNS entry for             cisco-capwap-controller (good for local             businesses - can also be used to find where brand new APs join)
    Note: If you use CAPWAP, make sure that there is a DNS entry for                 cisco-capwap-controller.
    Management IP addresses of controllers the LAP remembers             previously
    A Layer 3 broadcast on the subnet
    Over the air provisioning
    Statically configured information
    From this list, the easiest method to use for deployment is to  have           the LAPs on the same subnet as the management interface of the  controller and           allow the LAP’s Layer 3 broadcast to find the controller. This method  should be           used for companies that have a small network and do not own a local  DNS           server.
    The next easiest method of deployment is to use a DNS entry with           DHCP. You can have multiple entries of the same DNS name. This allows  the LAP           to discover multiple controllers. This method should be used by  companies that           have all of their controllers in a single location and own a local DNS  server.           Or, if the company has multiple DNS suffixes and the controllers are  segregated           by suffix.
    DHCP option 43 is used by large companies to localize the  information           via the DHCP. This method is used by large enterprises that have a  single DNS           suffix. For example, Cisco owns buildings in Europe, Australia, and  the United           States. In order to ensure that the LAPs only join controllers  locally, Cisco           cannot use a DNS entry and must use DHCP option 43 information to tell  the LAPs           what the management IP address of their local controller is.
    Finally, static configuration is used for a network that does not           have a DHCP server.You can statically configure the information  necessary to           join a controller via the console port and the AP’s CLI. For  information on how           to statically configure controller information using the AP CLI, refer  to           Manually            Configuring Controller Information Using the Access Point CLI.
    For a detailed explanation on the different discovery algorithms  that           LAPs use to find controllers, refer to           LAP            Registration with WLC.
    For information on configuring DHCP option 43 on a DHCP server,  refer           to           DHCP            OPTION 43 for Lightweight Cisco Aironet Access Points Configuration           Example.
    Send a discovery request to every controller on the list and wait  for           the controller's discovery reply which contains the system name,  AP-manager IP           addresses, the number of APs already attached to each AP-manager  interface, and           overall excess capacity for the controller.
    Look at the controller list and send a join request to a controller           in this order (only if the AP received a discovery reply from it):
    Primary Controller system name (previously configured on             LAP)
    Secondary Controller system name (previously configured on             LAP)
    Tertiary Controller system name (previously configured on             LAP)
    Master controller (if the LAP has not been previously configured             with any Primary, Secondary, or Tertiary controller names. Used to  always know             which controller brand new LAPs join)
    If none of the above are seen, load balance across controllers             using the excess capacity value in the discovery response.
    If two controllers have the same excess capacity, then send the             join request to the first controller that responded to the discovery  request             with a discovery response. If a single controller has multiple  AP-managers on             multiple interfaces, choose the AP-manager interface with the least  number of             APs.
    The controller will respond to all discovery requests without             checking certificates or AP credentials. However, join requests must  have a             valid certificate in order to get a join response from the  controller. If the             LAP does not receive a join response from its choice, the LAP will  try the next             controller in the list unless the controller is a configured  controller             (Primary/Secondary/Tertiary).
    When it receives the join reply, the AP checks to make sure it has           the same image as that of the controller. If not, the AP downloads the  image           from the controller and reboots to load the new image and starts the  process           all over again from step 1.
    If it has the same software image, it asks for the configuration  from           the controller and moves into the registered state on the controller.
    After you download the configuration, the AP might reload again to           apply the new configuration. Therefore, an extra reload can occur and  is a           normal behavior.

  • ACL migration Error : 1210 could not find a domain controller for domain "Test Domain" (Old Domain)

    Hi
    We are migrating from old domain to new domain. Before live migration, we are trying to check the ACE/ACL migration through SubInACL. We are running the SubInACL on a cluster, which is a member of the Old Domain (Test Domain). We are able to resolve and
    ping both Old Domain and the New domain from this cluster machine. We have created a network share on this cluster, which is accessible to all Domain Users of the Old Domain. Both Domains have two way forest level trust. we are trying to migrate
    the ACL of this share (\\ClusterMachine\testshare$) to the new domain using SubInACL. We are trying to run the below command to get it done.  
    subinacl /outputlog=C:\Users\Administrator\Desktop\Migrationlog.txt /subdirectories
    \\ClusterMachine\testshare$\*.* /migratetodomain=OldDomain=NewDomain=mappingfile.txt
    Mapping file contains : Domain Users=NewDomain_Users
    But we are geeting the Error that "1210 could not find a domain controller for domain "Test Domain". Error finding domain name : 1210 the format of the specified computer name is invalid. Current Object "\\ClusterMachine\testshare$"
    will not be processed."

    Hello,
    how in detail is DNS set up in each domain?
    Any problems when using nslookup to verify?
    Best regards
    Meinolf Weber
    MVP, MCP, MCTS
    Microsoft MVP - Directory Services
    My Blog: http://blogs.msmvps.com/MWeber
    Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
    Twitter:  

  • Did not find repository information for controller

    Hi Experts,
    We are getting following error in Production system. Could you please tell what can be the root cause behind it. I know when someone deploys this error comes. But in Production No one is deploying any Application.
    Please tell me what can be any other problem.
    Exception occured during processing of Web Dynpro application  /material_wd/ChangeRawMeridianApp. See exception stacktrace for details.
    [EXCEPTION]
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Did not find repository information for controller ChangePackManualCompView
    at com.sap.tc.webdynpro.progmodel.components.Component.getController(Component.java:572)
    at com.sap.tc.webdynpro.progmodel.components.Component.getController(Component.java:548)
    at com.sap.tc.webdynpro.clientserver.uielements.adaptbase.AbstractAdapter.findViewElement(AbstractAdapter.java:124)
    at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.handleUIElementEvent(HtmlClient.java:2037)
    at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.updateEventQueue(HtmlClient.java:550)
    at com.sap.tc.webdynpro.clientserver.phases.TransportIntoDataContainerPhase.execute(TransportIntoDataContainerPhase.java:48)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
    at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:512)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:52)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1549)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1363)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDoProcessing(AbstractExecutionContextDispatcher.java:154)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppProcessing.doService(DispatchHandlerForAppProcessing.java:35)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
    at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToApplicationDoProcessing(ExecutionContextDispatcher.java:114)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:80)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:618)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:649)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingPortal(ApplicationSession.java:584)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:311)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:743)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:258)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:259)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:202)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
    at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToDispatcherContext(ExecutionContextDispatcher.java:146)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:92)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:104)
    at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.dispatch(ApplicationHandle.java:275)
    at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:71)
    at com.sap.tc.webdynpro.portal.pb.impl.LocalApplicationProxy.sendDataAndProcessActionInternal(LocalApplicationProxy.java:962)
    at com.sap.tc.webdynpro.portal.pb.impl.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:297)
    at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1638)
    at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:361)
    at com.sap.portal.pb.PageBuilder$PhaseListenerImpl.doPhase(PageBuilder.java:2062)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:220)
    at com.sap.tc.webdynpro.clientserver.phases.PortalDispatchPhase.execute(PortalDispatchPhase.java:52)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
    at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:512)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:52)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1549)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1363)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDoProcessing(AbstractExecutionContextDispatcher.java:154)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppProcessing.doService(DispatchHandlerForAppProcessing.java:35)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
    at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToApplicationDoProcessing(ExecutionContextDispatcher.java:114)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:80)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:618)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:649)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:570)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:309)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:743)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:258)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:259)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:202)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
    at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToDispatcherContext(ExecutionContextDispatcher.java:146)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:92)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:104)
    at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
    at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:61)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:486)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
    at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:243)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
    at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
    at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)

    Hi,
    Some one might be deployed WDJ application with controller name ChangePackManualCompView which is already exist in some other application with diff name space
    Did not find repository information for controller
    Thanks,
    Sreeni.

  • Unhandled Exception "Could not find any available Domain Controller"

    Hi,
    I keep on having exchange 2010 loosing contact to domain controllers.
    "Unhandled Exception "Could not find any available Domain Controller.". EventID 1. Once I restart the sever, this error disappear and reappear again after a few days.
    When I run AD setting, the result shows as below. Update version is currently as at 14.02.0342.003. And boths DCs have 100% uptime.
    PS C:\> Get-ADServerSettings | fl
    RunspaceId                                
    : 9392eb25-bcdc-462e-816b-2d5626c572a5
    DefaultGlobalCatalog                      
    : DC2.com.au
    PreferredDomainControllerForDomain        
    DefaultConfigurationDomainController      
    : dc1.com.au
    DefaultPreferredDomainControllers         
    : {DC2.com.au}
    UserPreferredGlobalCatalog                
    UserPreferredConfigurationDomainController :
    UserPreferredDomainControllers            
    RecipientViewRoot                         
    ViewEntireForest                          
    : True
    WriteOriginatingChangeTimestamp           
    : False
    WriteShadowProperties                     
    : False
    Identity                                  
    IsValid                                   
    : True
    Could you please help as this exchange server has our management team and their outlook keep on going offline.
    Thanking you in advance.
    Cheers,
    Pwint

    I have another issue. I was trouble shooting exchange bin folder for permission and as a result of it Exchange transport service stopped and couldn't restart. I quickly changed to local service account and able to restart. Fixed the transport roles folder
    permission but don't know the password of network service account so I can't change it back. I can send and receive emails internally and externally but I am worried that by running with local account maybe not recommended? Is it safe to reset network service
    password? Thanks. I am freaking out... Regards, Pwint

  • APs not joining controller errors

    I keep getting errors on different APs not joining controllers:
    Jan  5 15:54:40.097: %CAPWAP-3-ERRORLOG: Go join a capwap controller
    *Jan  5 15:54:40.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.x.x.x peer_port: 5246
    *Jan  5 15:54:40.001: %CAPWAP-5-CHANGED: CAPWAP changed state to 
    *Jan  5 15:54:41.778: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.x.x.x  peer_port: 5246
    *Jan  5 15:54:41.780: %CAPWAP-5-SENDJOIN: sending Join Request to 10.x.x.x
    *Jan  5 15:54:41.780: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
    *Jan  5 15:54:41.787: %DTLS-5-ALERT: Received WARNING : Close notify alert from 10.x.x.x
    *Jan  5 15:54:41.788: %DTLS-5-PEER_DISCONNECT: Peer 10.x.x.x  has closed connection.
    *Jan  5 15:54:41.788: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 10.x.x.x :5246.
    Any ideas?  I'm not sure why the peer is disconnecting the connection.  The controller that is linked to It happens on 1242 and 1231 APs mostly.  I've had it happen on a 1142 and 1252 once, but after a reboot it joined fine.
    I'm running 6.0.188.0 on 6 WISMs.  The ap-manager that these APs keep trying to join only has 5 APs on it.

    Can you get a sniffer trace of the port-channel to one of the WiSM, and if possible, the console of the AP?  Also, check the MAC address of the AP(s) that are not joining to see if they start with something other than 00:, you may also want to check the MAC of the gw for those AP for the same thing.
    The defect I'm thinking of is CSCte01087

  • APs continually registering with secondary controller

    Hi All,
    For some reason all of the APs on a particular controller deregister from it and register with their secondary controller. Both controllers are running version 4.1.171.0 and I cannot see any issues on the LAN that would disrupt comms between the APs and their primary controller.
    Any pointers will be greatly appreciated.
    Many Thanks
    Scott

    Hi Eric,
    I haven't tried either of those but I will do as soon as.
    I'm using names for the first and second controllers (I'm haven't spec'd a third due to the controllers being geographically distant).
    These particular APs had been quite stable until I upgraded the controllers to said s/w version around a month ago, though APs on other upgraded controllers are fine. Also no matter where the APs are registered to they report (via WCS) that they are running vers 3.2.195.10 s/w, however interrogating the relevant controller directly says they are running vers 4.1.171.0.
    I was also in the midst of adding some new APs; these were autonomous ones that I converted (at my desk) and specified the suspect controller for them to register with during the conversion, the new APs registered ok with the controller and I set the same controller as their primary and set them aside for installation. After your reply to my initial query I've booted one of the newly converted ones again and they have registered with a random controller elsewhere on our network (I'm using option 43) rather than their primary.
    Apologies for the info overload, hopefully you can make some sense out of it.
    Many Thanks
    Scott

  • Can not find out Ethernet Controler & SM Bus Controller Driver for P 1000-1404TU Notebook PC

    Hi ;
    I just purchase a laptop as subject, i installed window 7 64bit and some drivers, but remain 2 drivers as bellow i can not find out in HP Website
    Ethernet Controler (wire LAN adapter)
    SM Bus Controller.
    Could some one help me ?
    Many thanks .
    This question was solved.
    View Solution.

    Hi,
    Please try:
    1. http://ftp.hp.com/pub/softpaq/sp52501-53000/sp52799.exe
    2.  http://ftp.hp.com/pub/softpaq/sp56501-57000/sp56517.exe
      & http://ftp.hp.com/pub/softpaq/sp46501-47000/sp46748.exe
    Regards.
    BH
    **Click the KUDOS thumb up on the left to say 'Thanks'**
    Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

  • Unable to execute Test-Mailflow cmdlet. Could not find any available Domain Controller

    I started receiving this error in SCOM while testing Exchange 2007 Mail flow. Normally the tests work just fine, and when I execute"test-mailflow" on the offending server, it works just fine. The alert doesn't have enough details to find out what
    is wrong. Can anyone help out?
    Alert Description:
    Unable to execute Test-Mailflow cmdlet. Could not find any available Domain Controller
    Environment: SCOM 2012 R2 UR4
    MP: Exchange 2007 MP, latest update
    Monitor: Exchange 2007 Test Local Mail Flow Monitor
    Brody Kilpatrick

    Hi,
    After you execute"test-mailflow" on the offending server, please also look into event logs to check is there any errors or warnings. SCOM is a tool to collect information, from my point of view, this message is collected from Exchange server, so
    you may need to check event viewer.
    In addition, please also make sure your Exchange environment is under monitored. And have you followed the Exchange 2007 MP guide to configure the MP?
    Make sure the Client Access Server is under monitored, you may check the Application Event log on the Client Access Server, and make sure there are no errors or warnings indicating a problem with the Client Access Server.
    Regards,
    Yan Li
    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 Subscriber Support, contact [email protected]

  • APs randomly will not join the controller

    Hi all,
    In short, APs will join the controller immediately using the recovery image, but once it downloads 7.6.100 and reboots, it either cannot join the controller or will take up to 40 minutes.
    The AP is in local mode. The AP 1040 eventually joined the controller, 40 minutes after we deleted all the files off the flash which is unacceptable.
    *Apr  9 15:38:15.842: %CAPWAP-5-SENDJOIN: sending Join Request to 10.10.10.10
    *Apr  9 15:38:15.851: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.
    *Apr  9 15:38:15.851: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
    *Apr  9 15:38:15.851: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
    *Apr  9 15:38:15.851: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 10.10.10.10
    *Apr  9 15:38:16.304: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
    *Apr  9 15:38:16.362: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Apr  9 15:38:16.427: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller CONTROLLER-DC
    I also had our technician console into a 2602 and we were seeing exact same errors.
    SUMMARY OF THIS CASE:
    --AP is 1042 and wlc is on 7.6.100.0
    --using dhcp option 43 but the AP has static ip
    --checked the private config on the AP and it was not sending the discovery request to the desired  WLC
    --cleared the private config
    --primed the AP to desired WLC
    --AP sending join request but receiving the following errors:
    Apr  4 14:37:47.000: CAPWAP-3-ERRORLOG Go join a capwap controller
    *Apr  4 14:36:47.000: CAPWAP-5-DTLSREQSEND DTLS connection request sent peer_ip: 10.10.10.11 peer_port: 5246
    *Apr  4 14:36:47.169: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_handshake.c:90 First fragment for seq 2 is missing
    *Apr  4 14:37:17.205: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2176 Max retransmission count reached!
    --cleared the flash except rcv
    --ap started downloading the image from the wlc but once it reboots the same errors appear again
    --research made on the error message and apparently we are hitting a bug:
    https://tools.cisco.com/bugsearch/bug/CSCul08933/?reffering_site=dumpcr

    Hi Leo,
    Next the information, I omitted some serial number and descriptions due to confidentiality matters.
    (Cisco Controller) >show sysinfo
    Manufacturer's Name.............................. Cisco Systems Inc.
    Product Name..................................... Cisco Controller Product Version.................................. 7.6.100.0 Bootloader Version............................... 1.0.1 Field Recovery Image Version..................... 6.0.182.0 Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27 Build Type....................................... DATA + WPS
    System Name...................................... ABCDEF System Location..................................
    System Contact...................................
    System ObjectID.................................. 1.3.6.1.4.1.9.1.1069 Redundancy Mode.................................. Disabled IP Address....................................... XXXXXXX Last Reset....................................... Software reset System Up Time................................... 32 days 14 hrs 1 mins 41 secs System Timezone Location......................... (GMT -5:00) Eastern Time (US and Canada) System Stats Realtime Interval................... 5 System Stats Normal Interval..................... 180
    Configured Country............................... CA  - Canada Operating Environment............................ Commercial (0 to 40 C)
    Internal Temp Alarm Limits....................... 0 to 65 C Internal Temperature............................. +40 C External Temperature............................. +21 C Fan Status....................................... OK
    State of 802.11b Network......................... Enabled State of 802.11a Network......................... Enabled Number of WLANs.................................. 5 Number of Active Clients......................... 2215
    Burned-in MAC Address............................ F0:F7:55:2B:4A:80 Power Supply 1................................... Present, OK Power Supply 2................................... Absent Maximum number of APs supported.................. 500
    (Cisco Controller) >show time
    Time............................................. Mon Apr 14 08:40:08 2014
    Timezone delta................................... 0:0 Timezone location................................ (GMT -5:00) Eastern Time (US and Canada)
    NTP Servers
        NTP Polling Interval.........................     36000
         Index     NTP Key Index                  NTP Server                  NTP Msg Auth Status
           1              0                                              A.B.C.D                        AUTH DISABLED
    AP>sh ver
    Cisco IOS Software, C3500 Software (AP3G1-K9W8-M), Version 15.2(4)JB3, RELEASE SOFTWARE (fc1) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2013 by Cisco Systems, Inc.
    Compiled Wed 18-Dec-13 21:36 by prod_rel_team
    ROM: Bootstrap program is C3500 boot loader
    BOOTLDR: C3500 Boot Loader (AP3G1-BOOT-M), Version 15.2 [chayan-apn-0411 116]
    AP uptime is 2 days, 17 hours, 15 minutes System returned to ROM by reload System image file is "flash:/ap3g1-k9w8-mx.152-4.JB3/ap3g1-k9w8-xx.152-4.JB3"
    Last reload reason:
    cisco AIR-CAP3502I-A-K9 (PowerPC460exr) processor (revision A0) with 98294K/32768K bytes of memory.
    Processor board ID XXXXXXXX
    PowerPC460exr CPU at 666Mhz, revision number 0x18A8 Last reset from reload LWAPP image version 7.6.100.0
    1 Gigabit Ethernet interface
    2 802.11 Radios
    32K bytes of flash-simulated non-volatile configuration memory.
    Base ethernet MAC Address: 70:81:05:9E:F7:36
    Part Number                          : 73-12175-05
    PCA Assembly Number                  : 800-32268-05
    PCA Revision Number                  : A0
    PCB Serial Number                    : XXXXXXX
    Top Assembly Part Number             : 800-32891-01
    Top Assembly Serial Number           : FGL1534S7LP
    Top Revision Number                  : A0
    Product/Model Number                 : AIR-CAP3502I-A-K9  
    Configuration register is 0xF
    AP>sh ip int br
    Interface                  IP-Address      OK? Method Status                Protocol
    BVI1                       X.Y.W.Z                YES TFTP   up                    up     
    Dot11Radio0                unassigned      NO  unset  up                    up     
    Dot11Radio1                unassigned      NO  unset  up                    up     
    GigabitEthernet0           unassigned      NO  unset  up                    up     
    GigabitEthernet0.1         unassigned      YES unset  up                    up     
    AP>sh inventory
    NAME: "AP3500", DESCR: "Cisco Aironet 3500 Series (IEEE 802.11n) Access Point"
    PID: AIR-CAP3502I-A-K9 , VID: V01, SN: XXXXXXX

  • I have a compaq 6200 pro i can not find the driver for SM bus controller.

    I down graded the 6200 pro with the i3 chip  to winXP and now I can not find the driver for the SM bus controller does this system have a sm bus controller?

    Hi: Please click on the device in the device manager. Then click on the details tab. Post the top string of characters you see. Those will identify the type and model of the missing device and I can send you the link to the drivers. It is either your AMT driver, TPM driver or IMEI driver. In the meantime, install the chipset driver and reboot if you have not done so already. http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=12454&prodSeriesId=5037900&prodNameId=5037902&swEnvOID=1093&swLang=13&mode=2&taskId=135&swItem=vc-88640-1 Paul

Maybe you are looking for