WLCS 3.5 installation on NT

Hi
We'd like to eval WLSC 3.5 and the Campaign Manager.
I installed WL 6 and the WLCS on my NT 4 workstation.
However, when trying to run it, the message as below comes up.
Any suggestions?
TIA,
Alex
Starting WebLogic Server ....
<May 24, 2001 11:55:23 AM GMT+10:00> <Notice> <Management> <Loading configuratio
n file .\config\wlcsDomain\config.xml ...>
log file: D:\bea\WebLogicCommerce3.5\.\config\wlcsDomain\logs\weblogic.log
<May 24, 2001 11:55:30 AM GMT+10:00> <Info> <Logging> <Only log messages of severity
"Error" or worse will be displayed in this window. This can be changed at Admin
Console> wlcsDomain> Servers> wlcsServer> Logging> General> Stdout severity
threshold>
javax.naming.ServiceUnavailableException. Root exception is java.rmi.NoSuchObjectException:
The object identified by [9] could not because found. Either it was
has not been exported or it has been collected by the distributed garbage collector.
at weblogic.rmi.internal.OIDManager.getServerReference(OIDManager.java:401)
at weblogic.jndi.WLInitialContextFactoryDelegate.newLocalContext(WLInitialContextFactoryDelegate.java:315)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:275)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:244)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.ejb20.internal.EJBMBeanFactory.<init>(EJBMBeanFactory.java:101)
at weblogic.management.mbeans.custom.Application.initializeMBean(Application.java:577)
at weblogic.management.mbeans.custom.Application.initializeMBeans(Application.java:497)
at weblogic.management.mbeans.custom.Application.adminLoad(Application.java:286)
at weblogic.management.mbeans.custom.Application.load(Application.java:230)
at weblogic.management.mbeans.custom.Application.load(Application.java:171)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:562)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:548)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:285)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
at $Proxy20.load(Unknown Source)

All fixed by installing a rolling patch
"Alex Reznikov" <[email protected]> wrote:
>
Hi
We'd like to eval WLSC 3.5 and the Campaign Manager.
I installed WL 6 and the WLCS on my NT 4 workstation.
However, when trying to run it, the message as below comes up.
Any suggestions?
TIA,
Alex
Starting WebLogic Server ....
<May 24, 2001 11:55:23 AM GMT+10:00> <Notice> <Management> <Loading configuratio
n file .\config\wlcsDomain\config.xml ...>
log file: D:\bea\WebLogicCommerce3.5\.\config\wlcsDomain\logs\weblogic.log
<May 24, 2001 11:55:30 AM GMT+10:00> <Info> <Logging> <Only log messages
of severity
"Error" or worse will be displayed in this window. This can be changed
at Admin
Console> wlcsDomain> Servers> wlcsServer> Logging> General> Stdout severity
threshold>
javax.naming.ServiceUnavailableException. Root exception is java.rmi.NoSuchObjectException:
The object identified by [9] could not because found. Either it was
has not been exported or it has been collected by the distributed garbage
collector.
at weblogic.rmi.internal.OIDManager.getServerReference(OIDManager.java:401)
at weblogic.jndi.WLInitialContextFactoryDelegate.newLocalContext(WLInitialContextFactoryDelegate.java:315)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:275)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:244)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.ejb20.internal.EJBMBeanFactory.<init>(EJBMBeanFactory.java:101)
at weblogic.management.mbeans.custom.Application.initializeMBean(Application.java:577)
at weblogic.management.mbeans.custom.Application.initializeMBeans(Application.java:497)
at weblogic.management.mbeans.custom.Application.adminLoad(Application.java:286)
at weblogic.management.mbeans.custom.Application.load(Application.java:230)
at weblogic.management.mbeans.custom.Application.load(Application.java:171)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:562)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:548)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:285)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
at $Proxy20.load(Unknown Source)

Similar Messages

Virtual WLC 7.5 - installation problmes (Controller Crashed)

Hi all,
I am installing vWLC on VMware ESXi 5 and the controller crashes after the boot. Everybody has any similar issues?
Thanks in advance.
Remi

Hi e-aguilar,
Eventually I did not go for the 7.5 version, I still had troubles to install it. Instead I downloaded de version 7.4.110.0 (the AssureWave that has an elevated status from Cisco), probably with most fixes. Running now on 2GB RAM and supporting 76 APs over VPN. Works like a charm!
Regards,

URGENT HELP WITH VIRTUAL WLC

We had a problem with Virtual Machine which Cisco Virtual WLC installed. Virtual Machine files were damaged and the system was not start normally. We have had to reinstall the WLC, but after installation impossible to import current license to new one.
how can we install this licence again?

Licenses are tied to the device they're being used on. With a virtual WLC, the license is tied to the unique identifier of the vWLC and when you recreated the vWLC after your VMware problems the new vWLC has a different unique identifier.
It's a similar situation to what happens when a physical controller is faulty and is swapped out by cisco, the replacement will have a different serial number and you'd have to re-host the license to the new serial number.

WLC 2504 installation wizard

Hi,
When running the installation wizard (CLI access), I will be asked about Multicast IP address.
I don't know what answer I can give.
WLC release : 7.6.100.0
Thanks for help...

Hi Alain,
***The multicast address is used by the controller in order to forward traffic to access points. It is important that it does not match another address in use on your network by other protocols. For example, if you use 224.0.0.251, it breaks mDNS used by some third party applications. It is recommended that the address be on the private range (239.0.0.0-239.255.255.255, which does not include 239.0.0.x and 239.128.0.x.)****
Try to use, example : 239.255.99.1
Regards
Dont forget to rate helpful posts

Error installation 3rd party certificate on wlc for webauth

i,
I would like to install a web auth certificate on a 5508. Version 7.6.130
Every time I get an error on web gui or cli like:
Cisco Controller) >transfer download start
Mode............................................. TFTP
Data Type........................................ Site Cert
TFTP Server IP................................... 10.1.126.100
TFTP Packet Timeout.............................. 6
TFTP Max Retries................................. 10
TFTP Path........................................ /wlan/
TFTP Filename.................................... final.pem
TFTP Webauth cert transfer starting.
*TransferTask: Oct 07 14:33:08.162: RESULT_CODE:1
*TransferTask: Oct 07 14:33:12.165: Locking tftp semaphore, pHost=10.1.126.100 pFilename=/wlan/final.pem
*TransferTask: Oct 07 14:33:12.249: Semaphore locked, now unlocking, pHost=10.1.126.100 pFilename=/wlan/final.pem
*TransferTask: Oct 07 14:33:12.249: Semaphore successfully unlocked, pHost=10.1.126.100 pFilename=/wlan/final.pem
*TransferTask: Oct 07 14:33:12.250: TFTP: Binding to remote=10.1.126.100
*TransferTask: Oct 07 14:33:12.266: TFP End: 7959 bytes transferred (0 retransmitted packets)
*TransferTask: Oct 07 14:33:12.266: tftp rc=0, pHost=10.1.126.100 pFilename=/wlan/final.pem
pLocalFilename=cert.p12
*TransferTask: Oct 07 14:33:12.266: RESULT_STRING: TFTP receive complete... Installing Certificate.
TFTP receive complete... Installing Certificate.
*TransferTask: Oct 07 14:33:12.266: RESULT_CODE:13
*TransferTask: Oct 07 14:33:16.269: Adding cert (7895 bytes) with certificate key password.
*TransferTask: Oct 07 14:33:16.309: RESULT_STRING: Error installing certificate.
*TransferTask: Oct 07 14:33:16.309: RESULT_CODE:12
Error installing certificate.
What's funny, when I'm on a 2106 with the same certificate (Version: 7.0.250.0) install, everything works!
Does anyone have an idea to solve this problem?
Regards
Juergen

Hello, please check these links out and see if they help:
https://supportforums.cisco.com/discussion/11376866/error-installing-certificate-help
https://supportforums.cisco.com/discussion/12294996/web-auth-certificate-download-failed-install-certificate
https://supportforums.cisco.com/blog/151061/generate-csr-third-party-cert-and-download-unchained-cert-wireless-lan-controller-wlc

Does WCS come with the 5508 WLC?

Forum
I am providing a quote to a client for a wireless installation. I have two 5508 boxes and about 40 AP's on the quote, as well as associated SmartNet.
I was reading how the Cisco Unified Wireless Network is comprised of:
Controllers
Access Points
The Cisco Wireless Control System (WCS)
Cisco Mobility Services Engine
My questions are:
1. Does WCS come installed on the Controller? Is this something that the customer receives simply by virtue of the fact that they are purchasing the Controller? Or is this a separate piece of software with a cost?
2. What exactly is the Cisco Mobility Services Engine? What does it do that the Controller will not? How would I sell one to a customer?
Thank You
Kevin

WCS is a Windows 2003 application (so not "on the controller") that is completely separate and has to be purchased separately with different levels of licensing for different feature sets.
WCS is most useful when having several WLCs to manage and is offered when you buy a lot of stuff I think.
WCS alone brings better reporting features (graphs, pdf reports, ...) and maps to visualize everything.
MSE is a kind of "calculation appliance" that you link to your WCS to locate all clients and rogues in real-time on the map. Only that. But it's a cool enough feature :-) Without MSE you can only view one client at a time (when entering its mac address in the search field) on WCS maps.
Nicolas

Upgrade two WLC 5508 with HA SSO from 7.5.102.0 to 7.6.130.0 combined with FUS 1.9

The running config is:
- Two WLC5508's in HA SSO setup running version 7.5.102.0
- about 130 x 2602i APs
I need to upgrade to 7.6.130.0 using the pre-download feature to minimize the network downtime.
Is it possible to transfer the 7.6 to the controllers and pre-download 7.6 to all APs, then do the FUS 1.9 upgrade and finally start the actual controller upgrade to 7.6.
So the steps would be:
1. Transfer 7.6 image to primary controller (do not reboot!), so still running 7.4 as active image.
2. Start pre-download of 7.6 image to all APs and wait till all APs have the new image (do not know how long it takes for 130 APs).
3. Upgrade both controllers with FUS 1.9 (HA should upgrade both controllers automatically) (takes about 45 minutes?)
4. Make 7.6 image the active/primary image on controllers and APs and reset controllers.
If the steps above will not work, I would need to upgrade FUS 1.9 which means 1 hour downtime and then start the pre-download to all APs. The pre-download can take a long time I heard, so I need to wait and wait before I can start the 7.6 upgrade, which means another 1 hour downtime.
This way I need two maintenance windows instead of one. So would it be possible to combine the pre-download and FUS?
Regards,
Bjorn

>Do I need to upgrade the FUS 1.9 before the 7.6 image or can I do the FUS afterwards? If I can do it afterwards, I can do the upgrades in the same maintenance window. This way I can start the pre-download the day before, so I am pretty sure the APs have the image at the time of the maintenance window.
>I cannot find any remarks about the required order of installation (FUS -> image or image -> FUS).
Release Notes for Wireless LAN Controller Field Upgrade Software for Release 1.9.0.0 - p2 :
* This release of the Field Upgrade Software is applicable to CISCO WLC's that are installed with the controller software release 6.0 and later.
So strict reading implies that you have to run 7.6 first.
M.

WLC 5508: 802.1 AAA override; Authenication success no dynamic vlan assignment

WLC 5508: software version 7.0.98.0
Windows 7 Client
Radius Server: Fedora Core 13 / Freeradius with LDAP storage backend
I have followed the guide at http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008076317c.shtml with respective to building the LDAP and free radius server. 802.1x authorization and authenication correctly work. The session keys are returned from the radius server and the wlc send the appropriate information for the client to generate the WEP key.
However, the WLC does not override the VLAN assignment, even though I was to believe I set everything up correctly. From the packet capture, you can see that verfication of client is authorized to use the WLAN returns the needed attributes:
AVP: l=4 t=Tunnel-Private-Group-Id(81): 10
AVP: l=6 t=Tunnel-Medium-Type(65): IEEE-802(6)
AVP: l=6 t=Tunnel-Type(64): VLAN(13)
I attached a packet capture and wlc config, any guidance toward the attributes that may be missing or not set correctly in the config would be most appreciated.

Yes good catch, so I had one setting left off in freeradius that allowed the inner reply attributes back to the outer tunneled accept. I wrote up a medium high level config for any future viewers of this thread:
The following was tested and verified on a fedora 13 installation.   This is a minimal setup; not meant for a "live" network (security issues with cleartext passwords, ldap not indexed properly for performance)
Install Packages
1. Install needed packages.
yum install openldap*
yum install freeradius*
2. Set the services to automatically start of system startup
chkconfig --level 2345 slapd on
chkconfig --level 2345 radiusd on
Configure and start LDAP
1. Copy the needed ladp schemas for radius. Your path may vary a bit
cp /usr/share/doc/freeradius*/examples/openldap.schema /etc/openldap/schema/radius.schema
2. Create a admin password for slapd. Record this password for later use when configuring the slapd.conf file
slappasswd
3. Add the ldap user and group; if it doesn't exisit. Depending on the install rpm, it may have been created
useradd ldap
groupadd ldap
4. Create the directory and assign permissions for the database files
mkdir /var/lib/ldap
chmod 700 /var/lib/ldap
chown ldap:ldap /var/lib/ldap
5. Edit the slapd.conf file.
cd /etc/openldap
vi slapd.conf
# See slapd.conf(5) for details on configuration options.
# This file should NOT be world readable.
#Default needed schemas
include        /etc/openldap/schema/corba.schema
include        /etc/openldap/schema/core.schema
include        /etc/openldap/schema/cosine.schema
include        /etc/openldap/schema/duaconf.schema
include        /etc/openldap/schema/dyngroup.schema
include        /etc/openldap/schema/inetorgperson.schema
include        /etc/openldap/schema/java.schema
include        /etc/openldap/schema/misc.schema
include        /etc/openldap/schema/nis.schema
include        /etc/openldap/schema/openldap.schema
include        /etc/openldap/schema/ppolicy.schema
include        /etc/openldap/schema/collective.schema
#Radius include
include        /etc/openldap/schema/radius.schema
#Samba include
#include        /etc/openldap/schema/samba.schema
# Allow LDAPv2 client connections. This is NOT the default.
allow bind_v2
# Do not enable referrals until AFTER you have a working directory
# service AND an understanding of referrals.
#referral    ldap://root.openldap.org
pidfile        /var/run/openldap/slapd.pid
argsfile    /var/run/openldap/slapd.args
# ldbm and/or bdb database definitions
#Use the berkely database
database    bdb
#dn suffix, domain components read in order
suffix        "dc=cisco,dc=com"
checkpoint    1024 15
#root container node defined
rootdn        "cn=Manager,dc=cisco,dc=com"
# Cleartext passwords, especially for the rootdn, should
# be avoided. See slappasswd(8) and slapd.conf(5) for details.
# Use of strong authentication encouraged.
# rootpw        secret
rootpw
{SSHA}
cVV/4zKquR4IraFEU7NTG/PIESw8l4JI
# The database directory MUST exist prior to running slapd AND
# should only be accessible by the slapd and slap tools. (chown ldap:ldap)
# Mode 700 recommended.
directory    /var/lib/ldap
# Indices to maintain for this database
index objectClass                       eq,pres
index uid,memberUid                     eq,pres,sub
# enable monitoring
database monitor
# allow onlu rootdn to read the monitor
access to *
         by dn.exact="cn=Manager,dc=cisco,dc=com" read
         by * none
6. Remove the slapd.d directory
cd /etc/openldap
rm -rf slapd.d
7. Hopefully if everything is correct, should be able to start up slapd with no problem
service slapd start
8. Create the initial database in a text file called /tmp/initial.ldif
dn: dc=cisco,dc=com
objectClass: dcobject
objectClass: organization
o: cisco
dc: cisco
dn: ou=people,dc=cisco,dc=com
objectClass: organizationalunit
ou: people
description: people
dn: uid=jonatstr,ou=people,dc=cisco,dc=com
objectClass: top
objectClass: radiusprofile
objectClass: inetOrgPerson
cn: jonatstr
sn: jonatstr
uid: jonatstr
description: user Jonathan Strickland
radiusTunnelType: VLAN
radiusTunnelMediumType: 802
radiusTunnelPrivateGroupId: 10
userPassword: ggsg
9. Add the file to the database
ldapadd -h localhost -W -D "cn=Manager, dc=cisco,dc=com" -f /tmp/initial.ldif
10. Issue a basic query to the ldap db, makes sure that we can request and receive results back
ldapsearch -h localhost -W -D cn=Manager,dc=cisco,dc=com -b dc=cisco,dc=com -s sub "objectClass=*"
Configure and Start FreeRadius
1. Configure ldap.attrmap, if needed. This step is only needed if we need to map and pass attributes back to the authenicator (dynamic vlan assignments as an example). Below is an example for dynamic vlan addresses
cd /etc/raddb
vi ldap.attrmap
For dynamic vlan assignments, verify the follow lines exist:
replyItem    Tunnel-Type                                   radiusTunnelType
replyItem    Tunnel-Medium-Type                   radiusTunnelMediumType
replyItem    Tunnel-Private-Group-Id              radiusTunnelPrivateGroupId
Since we are planning to use the userpassword, we will let the mschap module perform the NT translations for us. Add the follow line to check ldap object for userpassword and store as Cleartext-Password:
checkItem    Cleartext-Password    userPassword
2. Configure eap.conf. The following sections attributes below should be verified. You may change other attributes as needed, they are just not covered in this document.
eap
{      default_eap_type = peap      ..... }
tls {
    #I will not go into details here as this is beyond scope of setting up freeradisu. The defaults will work, as freeradius comes with generated self signed certificates.
peap {
    default_eap_type = mschapv2
    #you will have to set this to allowed the inner tls tunnel attributes into the final accept message
    use_tunneled_reply = yes
3. Change the authenication and authorization modules and order.
cd /etc/raddb/sites-enabled
vi default
For the authorize section, uncomment the ldap module.
For the authenicate section, uncomment the ldap module
vi inner-tunnel
Very importants, for the authorize section, ensure the ldap module is first, before mschap. Thus authorize will look like:
authorize
{      ldap      mschap      ...... }
4. Configure ldap module
cd /etc/raddb/modules
ldap
{        server=localhost       identify = "cn=Manager,dc=cisco,dc=com"        password=admin       basedn="dc=cisco,dc=com"       base_filter = "(objectclass=radiusprofile)"       access_attr="uid"       ............   }
5. Start up radius in debug mode on another console
radiusd -X
6. radtest localhost 12 testing123
You should get a Access-Accept back
7. Now to perform an EAP-PEAP test. This will require a wpa_supplicant test libarary called eapol_test
First install openssl support libraries, required to compile
yum install openssl*
yum install gcc
wget http://hostap.epitest.fi/releases/wpa_supplicant-0.6.10.tar.gz
tar xvf wpa_supplicant-0.6.10.tar.gz
cd wpa_supplicant-0.6.10/wpa_supplicant
vi defconfig
Uncomment CONFIG_EAPOL_TEST = y and save/exit
cp defconfig .config
make eapol_test
cp eapol_test /usr/local/bin
chmod 755 /usr/local/bin/eapol_test
8. Create a test config file named eapol_test.conf.peap
network=
{   eap=PEAP eapol_flags=0 key_mgmt=IEEE8021X identity="jonatstr"   password="ggsg" \#If you want to verify the Server certificate the below would be needed   \#ca_cert="/root/ca.pem" phase2="auth=MSCAHPV2"   }
9. Run the test
eapol_test -c ~/eapol_test.conf.peap -a 127.0.0.1 -p 1812 -s testing123

Slow roaming for WGB-client (mobile) on AP/WLC!

A customer of mine have previously had 2 AP1242 set up as root-AP and then an additional AP1252 set up as WGB onboard a (very slow) moving vehicle. This has worked very good.
On the vehicle there is 1 "real" PC and 3-4 additional PLCs or such "dumb" equipments with an static IP-address each. All equipment on the vehicle is connected to an unmanaged Layer2-switch.
Now they have extended the WLAN-installation, and replacing the 2 old and added 5 new APs (all lightweight) and a WLC. The vehicle-WGB is also replaced. All new APs and the new WGB is AP2602 and the WLC is a 2504.
After installing the new CAP2602, the WLC2504 ande the new WGB AP2602 on the vehicle they report that the roaming is too slow for the application that controls the vehicle..... TYhis results in a "Full Stop". Which is rather undesirable!!
I have looked at the configuration of the WGB-AP which is (in principle) unchanged from the AP1252 and also the WLC, But do not see any peculiarities. We also tried to set the channel on all tyhe APs to the same (Meru-style...) but that did not help. The environment of the APs and the vehicle is absolutely guaranteed free from any other interfering WLANs/networks.
Any iseas? I attach the config of the WLC and the WGB.
Best Regards
Göran Blomqvist
Sweden

Hi
I can see your WLAN configured for both WPA/TKIP & WPA2/AES as authentication suites. I would stick only one (WPA2/AES).
Also to test, I would first check it in open authentication & see if that make any difference.
I think in your WGB configuration you have most recommended settings. Here are some useful notes on WGB configuration
http://mrncciew.com/2013/07/24/wgb-roaming-part-1/
http://mrncciew.com/2013/06/16/unified-ap-wgb-with-multiple-vlan/
HTH
Rasika
*** Pls rate all useful responses ****

WLCS 2.0.1 sp2 commercePool failing with demo apps

When I start WLCS, I get the message below after various EJBs are deployed:
Wed Sep 27 13:41:36 PDT 2000:<I> <JDBC Pool commercePool> A connection from pool commercePool was tested during
reserve with a select count(*) from WLCS_IS_ALIVE and failed:
Wed Sep 27 13:41:36 PDT 2000:<I> <JDBC Pool commercePool> SQL Exception: No current connection.
Wed Sep 27 13:41:36 PDT 2000:<I> <JDBC Pool commercePool> This connection will now be refreshed.
Delaying 1 seconds before making a commercePool pool connection.
Wed Sep 27 13:41:37 PDT 2000:<E> <EJB> Could not deploy: '/usr/local/WebLogicCommerce/lib/ebusiness-cmp-deploy.j
ar'
Possible reasons include:
1. The bean or an interface class has been modified but
the deployment descriptor has not been updated
2. The database mappings in the deployment descriptor do not
match the database definition
3. The jar file is not a valid jar file
4. The jar file does not contain a valid bean
weblogic.ejb.common.DeploymentException: Could not setup the persistence store for this bean.; nested exception
is:
weblogic.cmp.rdbms.CMPStartupException: WebLogic RDBMS CMP could not be started due to the following exc
eptions:
0 : Error in Weblogic CMP RDBMS deployment descriptor. Column 'ACCOUNT_ENTRIES', referenced in attribute-map el
ement, was not found in database table.
weblogic.cmp.rdbms.CMPStartupException: WebLogic RDBMS CMP could not be started due to the following exceptions:
0 : Error in Weblogic CMP RDBMS deployment descriptor. Column 'ACCOUNT_ENTRIES', referenced in attribute-map el
ement, was not found in database table.
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Compiled Code)
at weblogic.ejb.utils.ErrorCollectionException.<init>(Compiled Code)
at weblogic.cmp.rdbms.CMPStartupException.<init>(Compiled Code)
at weblogic.cmp.rdbms.PSRdbms_Base.columnsAreInTable(Compiled Code)
at weblogic.cmp.rdbms.PSRdbms_Base.baseSetup(Compiled Code)
at theory.smart.ebusiness.inventory.InventoryRecordImplPSWebLogic_CMP_RDBMS.setup(InventoryRecordImplPSW
ebLogic_CMP_RDBMS.java:117)
at theory.smart.ebusiness.inventory.InventoryRecordImplPSWebLogic_CMP_RDBMS.setup(InventoryRecordImplPSW
ebLogic_CMP_RDBMS.java:104)
at weblogic.ejb.internal.StatefulEJBHome.initializeEntityEjbStore(Compiled Code)
at weblogic.ejb.internal.StatefulEJBHome.setup(Compiled Code)
at weblogic.ejb.internal.EJBHomeImpl.setup(Compiled Code)
at weblogic.ejb.internal.EJBDeploymentImpl.setupBeanHome(Compiled Code)
at weblogic.ejb.internal.EJBDeploymentImpl.deployBeans(Compiled Code)
at weblogic.ejb.internal.EJBDeploymentImpl.deploy(EJBDeploymentImpl.java:335)
at weblogic.ejb.internal.EJBJarDeployment.deploy(EJBJarDeployment.java:231)
at weblogic.ejb.internal.EJBManagerImpl.deploy(Compiled Code)
at weblogic.ejb.internal.EJBManagerImpl.deployNew(EJBManagerImpl.java:352)
at weblogic.ejb.internal.EJBManagerImpl.deploy(EJBManagerImpl.java:319)
at weblogic.ejb.internal.EJBManagerImpl.deployBeans(Compiled Code)
at weblogic.ejb.internal.EJBManagerImpl.<init>(EJBManagerImpl.java:242)
at weblogic.t3.srvr.T3Srvr.start(Compiled Code)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:825)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:99)
at weblogic.Server.main(Server.java:65)
at weblogic.Server.main(Server.java:55)
It seems like a cloudscape problem.
Any Ideas?
Thanks,
Ande

I too have been unable to install the Office 2010 SP2 update on either a Win7 or a Win 8 system. Researching the errors I got led me to discover the following:
1. Many people are encountering errors during the SP2 installation. Some were able to get around it by downloading the self-installing package and bypassing Windows Update. Some were able to get it installed by first doing a Repair on Office 210 itself
first, and then installing SP2. But many others have not been able to install it at all.
2. Apparently a common and insurmountable issue that prevents SP2 from installing is the lack of the MSOCACHE directory. This directory normally gets installed on a machine during the original install of Office, and contains all the install files used
during the installation. Apparently the idea behind creating MSOCACHE was to allow subsequent updates without requiring the user to have the original source CD available.
The problem is that if MSOCACHE is deleted, which is an option many people choose, you can then no longer do any updates to Office.
I am one of those people.
I found a posting that described a way to recreate MSOCACHE from the source CD. I did that, and the SP2 update actually got farther - it started to install stuff but then stopped and asked for a particular file. I found the file on the CD and
pointed the installer to it, but it said the file was not found and quit. So my install still failed.
The last response I got at the Microsoft Answers site was to wait until SP2 is debugged. It's not clear to me this will ever happen, but we'll see.
Birk Binnard http://www.birkbinnard.com

AP Impersonation on WLC

Has anyone seen the WLC reporting its own APs as impersonating APs? I checked the forum and found one conversation relating to this and my 802.11a is set to Country already. But I am see ing this on the B/G side. Any thoughts?

This problem has persisted for us at more than one customer site since the summer of 2006 and has persisted with every revision up to and including 4.0.206.0 (most recent at this time).
Have you opened up a case with Cisco TAC on this? If so, what is their response?
I believe that items like these will only get fixed if TAC gets enough pushback on them and understands that the problem is not specific to a particular installation site - which it is not.
A few observations:
I have not observed this when using the older 1010 series (AireSpace) access points.
I have seen this when using the AIR-LAP1131AG access points in both lightweight out-of-the-box as well as in autonomous-converted-to-LWAP. We also have lightweight out-of-the-box AIR-LAP1242AG access points at one of these installations.
It has also been observed in installations using AIR-AP1231's converted to LWAP.
We also see chronic AP Disassoc false alarms which (possibly) are somehow related to the other false alarm.
I suspect that in installations where there is a higher density of access points, where more access points will be detected by other access points (i.e.: multi-floor installations where RF coverage travels through the floor, academic environments with one AP per classroom to meet user density, etc.) that this problem may be more pronounced.
Also, I am wondering if the "virtual" MAC address assigned to each SSID broadcast by the each AP (where the radio MAC address is incremented for each SSID on the AP), if there ends up being an overflow of the AP's neighbor table (for example: 8 SSID = 8 MAC addresses * the number of adjacent APs can result in a fairly large table for each AP.
Or could there be problems with the system correlating virtual MAC addresses to the actual underlying AP?
- John

Using MS SQL Server 2000 for WLCS 3.50 DB

I'm using WebLogic 6.0sp1 with Commerce Server 3.5 and I've successfully
installed the demo. I would like to create another commerce server
installation, this time using Microsoft SQL Server 2000 as the database
instead of Cloudscape. I've downloaded and installed the BEA jDriver
for MS SQL 7/2000 and tested it using dbping. My question is: where are
the db scripts for creating and populating the commerce database? I've
found the WLCS_320_DB_DDL_1.1.zip file on the BEA downloads site, but
I'm concerned that this schema is for Version 3.20 of Commerce Server.
Is there a similar file for WLCS 3.50? If not, is it safe to use this
one?
If this is posted in the wrong place, please let me know and I'll repost
to the appropriate newsgroup as required.
Sincerely,
Michael Schulz

Hi Michael,
At this time SQL Server 2000 is not certified for WLCS 3.5. Since the
schema has changed between 3.2 and 3.5, running the 3.2 scripts is not a
good idea.
I can tell you that certification is in progress for SQL Server 2000. Your
best bet is to contact your Sales Representative to get an idea of when
certification might be coming.
I hope this helps.
- Ginny
"Michael Schulz" <[email protected]> wrote in message
news:[email protected]..
I'm using WebLogic 6.0sp1 with Commerce Server 3.5 and I've successfully
installed the demo. I would like to create another commerce server
installation, this time using Microsoft SQL Server 2000 as the database
instead of Cloudscape. I've downloaded and installed the BEA jDriver
for MS SQL 7/2000 and tested it using dbping. My question is: where are
the db scripts for creating and populating the commerce database? I've
found the WLCS_320_DB_DDL_1.1.zip file on the BEA downloads site, but
I'm concerned that this schema is for Version 3.20 of Commerce Server.
Is there a similar file for WLCS 3.50? If not, is it safe to use this
one?
If this is posted in the wrong place, please let me know and I'll repost
to the appropriate newsgroup as required.
Sincerely,
Michael Schulz

WLC 4402 username and password expires automatically

Hi,
We are facing issue with Cisco WLC 4402 (Cisco AireOS Version 4.2.205.0) and username and password expired automatically. It happens very often. We are not able to retreive the password, so everytime we need to reset(factory default) the Cisco WLC4402 and doing fresh installation.
Whether it is the hardware issue or software bug.
Also is there any possibility of recover the username and [password with resetting the cisco wlc4402.
Kindly suggest on this issue.
Regards
S.Manikandan

Hmmm.. Strange!! are we using any TACACS to manage?? or just the management username and password??
I guess after 5.2 WLC code or so we have the option of resetting the password without losing the config!!
Regards
Surendra

Authentication eap-tls on ACS or local EAP WLC over Lwapp and 7921

Hi All,
I install WLC to provide Wlan architecture and the project was extended for VoWLAN. we have 7921 and E51 running over the wide WLAN architecture.
Computer using Data over wirless are working over PEAP done by ACS and CA signed certificate + user secret on PC is link to the domain account and secret stay the login and password. Our problem is that user and password is link via ACS to Active Directory. The policy of password is to change frequently.
For the Phone we are actually running authentication over Leap but I'm working to define the best security solution for us.
I confront PEAP and Eap-TLS for now:
1) PEAP check the authentication of ACS via certificate trust and authenticate via MS-Chapv2 and the secret password known by user. My problem here is the phone can only be static what is potentially not acceptable
2) Eap-tls which is the best secured security due to the double side certificate authentication + (login / password) on the phone
so I need to manage here Certificate Management ? I mean I can use either the MIC CA certificate on the phone or User CA defined one which I can put on ACS or Local EAP WLC and the put the ACS CA trust on the Phone.
If I understood well I have to put User.cer and ACS_CA.cer on each phone and pout the User_CA on the ACS ?
I have already Certificate on the ACS signed by CA (like veri-signed) so I must create CSR for any phones to be able to use the same CA ?
I'm thinking to use also the local Eap certificate of Controller to manage all of that to avoid every potential money to pay to the trust CA of ACS
can you help me to know if I understood everything good ? I would be please to exchange experience on that
thanks ;)
bye

I am currently using EAP-TLS authentication on my wireless users using ACS 3.2. I have had that problem before. This is what I did...
Setup a Microsoft Certificate server as my
CA. You can use same machine wih your ACS and CA.
Then, generate certificate signing request from ACS then request a server certificate from CA then copy and install a certificate to ACS. On the ACS, go to global authentication setup check the EAP-TLS cetificate. If it failed to respond means that the server certificate is not properly setup.
On the windows xp clients, connect your machine using wired LAN, then request a certificate from CA(the same CA that you have use to your ACS) using IE (ex. http://CAip/certsrv), but this time request a client certificate. The name you should put when requesting the cert must be you local windows user, use 1024, choose microsoft base cryptographic provider 1.0. then installl the certificate on the client. Verify you client certificate it i was installed properly.
At that poit you should be able to connect you r wireless client using EAP-TLS.

Prime Infrastructure 2.2- problems: Wired Detailed Device Inventory report not running / Cisco 5500 WLCs no listed in subgroup

New installation of Prime Infrastructure 2.2.0 (PI-VA-2.2.0.0.158.ova)
installed fixes/software/device packs:
PI 2.2.1 Poodle Fix (installed)
PI 2.2.1 Maintenance Release (installed,ncs stopped,rebooted)
Prime Infrastrucutre 2.2 Device Pack 3 (installed,ncs stopped,rebooted)
Licences installed (ncs stopped,rebooted)
Added all devices via Bulk Import (Inventory>Device Management>Network Devices)
Problem 1:
The Cisco 5500 WLCs are not listed in Inventory>Device Management>Network Devices (see screen shot) but listed under "All Devices"!
The Cisco 4400 WLCs and the 8500 WLCs are listed within their subgroup.
Devices are in "Managed State"
Problem 2: fixed! (Browser issue)
Problem 3:
Unable to run "Wired Detailed Device Inventory" report because I get the error message: Failed to run report: Unable to retrieve data for: Chassis Information (if Chassis Information is selected, if System Information is selected I get the error message with ...retrieve data for:System Information)
All devices do have an "Admin Status = Managed" and the Last Inventory Collections Status = Completed.
Has anyone the same issues or a tip for me?
Another topic, the "User Defined Fileds" are not exported when with running a "Device Export" (Inventory > Device Management > Network Devices). ;-(
BR
Bastian

Hallo Bastian,
I think you still have browser issue, Using IE is still the best with Prime.
I have exactly same prime 2.2 and installed fixes/software/device packs.
I have no problem I can see all views. I use now IE 11, with Chrome 42.0.2311.90 and firefox 37.01 I have problems too with lots of views. You have not tell what browser + version you have.
Since you have same prime 2.2 as me. I have other problems, can you check yours?
Can you see a functional CLI template page at Configuration > Templates > Features & Technologies:
https://supportforums.cisco.com/discussion/12481691/can-cisco-prime-22-still-do-simple-ad-hoc-deployment-job-cli-over-all-switches
Do you have SNMP Connectivity Failed while Verify Credentials has no errors all green and checked.
https://supportforums.cisco.com/discussion/12494786/snmp-request-exceeds-internal-data-buffer-512-bytes-prime-22-asa-5545

WLCS 3.5 installation on NT

Similar Messages

Maybe you are looking for