WLC 5508 - Failed to connect from LMS 3.2

Hello.
I am trying to include a WLC 5508 in our LMS 3.2.
I have defined the device and credentials, but the LMS server cannot get access to it.
If I try to check de device credentials from the Device Center I get a "failed to connect", but if I a try a telnet session, also from Device Center, I get a connection.
I checked the credentails are OK.
Thank you.

Hi,
You need to download and install the last package : WLC.RME431.v2-1.zip : http://www.cisco.com/cisco/software/cart.html?imageGuId=E3A42793DA29A1B6AC3024C088F9FBC2B324EC8B&i=rs
You must install : MDF 1.37
You must install packages before WLC.RME431.v2-1.zip:
SharedSwimWLC.RME431.v1-2.zip
SharedDcmaWLC.RME431.v1-1.zip
SharedSwimIOS.RME431.v2-5-4.zip
LibSwim.RME431.v2-5-3.zip
LibCommon.RME431.v2-4-2.zip
Elisabeth
WLC.RME431.v2-1.readme:
Supported Devices
=================
Device Type : Cisco 5500 Series Wireless LAN Controllers
Cisco 3750 Switch with Wireless LAN Controller
Devices/Modules Supported :
Cisco 5508 Wireless LAN Controller : 1.3.6.1.4.1.9.1.1069
Cisco 3750 24+2 port 10/100/1000 Switch with integrated Cisco 4402 Wireless Controller: 1.3.6.1.4.1.9.1.747
Features Supported:
Inventory Manager : Yes
Syslog Analyzer : Yes
Config.Mgmt : Yes
Software Mgmt : Yes
Minimum Software : 6.0.188.0
Hardware and Software Requirements
==================================
Hardware and software requirements are the same as those needed for Resource Manager
Essentials 4.3.1 installation.
You must install Resource Manager Essentials 4.3.1 and MDF 1.37 before installing the
device package.
For a detailed list of requirements, as well as instructions for installing Resource
Manager Essentials 4.3.1, go to Cisco.com.
For documentation on Resource Manager Essentials, see:
http://www.cisco.com/en/US/products/sw/cscowork/ps2073/tsd_products_support_series_home.html
Package Dependencies
====================
To install the WLC Package, you must install the
following dependent packages:
SharedSwimWLC.RME431.v1-2.zip
SharedDcmaWLC.RME431.v1-1.zip
SharedSwimIOS.RME431.v2-5-4.zip
LibSwim.RME431.v2-5-3.zip
LibCommon.RME431.v2-4-2.zip

Similar Messages

WLC 5508 Management Interface Connection

I'm setting up a new 5508. I've used the config from a 4402, have successfully connected to the Service port to manage the device, but for some reason cannot connect to the Management interface. In this case, port 1.
The service port is connected to a Catalyst switch and grabbed an ip address (10.2.x.x subnet) no problem. I can access the 5508 via https using the SP. However, port 1 is connected to the same Catalyst switch, but on a different vlan (subnet 10.20.x.x). Both ends show that the interfaces are up, I can ping the interface from any other host on the network, but when I try to manage the device via https I cannot connect. We are using WCS and I cannot add the device from the WCS. About all I can do is ping that interface.
I've probably overlooked something very basic, but I'm baffled.

Thanks for the reply.
No, definitely not that. I have all of those enabled. I have the SP connected to another vlan on the same switch and can manage through that port(https, telnet). I've tried about every combination of trunk port, access port, etc. I'm beginning to suspect the GBICs (10baseT), but both ends show that I am connected at 1000 and I can ping the ip address of the management interface.

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.

SWF verification fails when connected from Edge

Hi
I have couple of files for SWF verification.
I have created a SWFs folder in the application directory on my core server
I have enabled SWFverification to "true" in Application.xml in Core server
My Swf are Created in Flash Player 10.1.135
I have 5 edge servers connected to my core
When i connect to a stream thro an edge , and if i get a connection then subsequent connections through different swfs are not validated .
Any issue in Edge Core connection
Or Should i put the SWfs in Edge Locations also?
PS

Hi Subhankar,
I have tried a connecting two profilers concurrently to a MobiLink server and have not been able to reproduce errors like this. There should not be a connection limit that would prevent this - if ti couldn't connect at all, you wouldn't see the request coming in.
Which exact version of SQL Anywhere/MobiLink are you using? Are you just using SQL Anywhere clients or do you also have UltraLite clients? Are the server and clients using the same software version?
Thanks,
Jeff Albion
SAP Active Global Support

LMS 4.2 and WLC 5508

Hi all,
Recently I have replaced 2 4400 WLC by 5508 wlc's.
I have also replaced both 4400 in LMS by those new 5508. They have the same ip's, so I have removed the old 4400's from LMS and created 2 new devices.
When checking the device center, LMS tells me Data collection, User tracking, Inventory and Fault discovery has succeeded.
When I check the Reachability status in device center it is ok for ping, telnet, SSH, SNMPV2 read, SNMPV2 write. However I am not able to open the configuration through Config editor. He gives me the pop-up "CEDT0042: No latest configuration file exists for the device in Archive."
When I go and check the archive summary report, I can see for both devices the log below:
NMP: Failed to establish SNMP connection to x.x.x.x - Cause: Device is Unreachable. Check the ReadOnly community string. SNMP: Failed to establish SNMP connection to x.x.x.x - Cause: Device is Unreachable. Check the ReadOnly community string.
Any ideas,
Thanks,
Joris

Hello,
I think I have found the problem. WLC 5508 is not compatible with LMS 4.2.2.
I can find this in the release notes:
Cisco Unified Wireless Network Solution Components
The following components are part of the Cisco UWN Solution and are compatible in this release:
Note For more information on the compatibility of wireless software components across releases, see the Cisco Wireless Solutions Software Compatibility Matrix.
•Cisco IOS Release 15.2(2)JB
•Cisco Prime Infrastructure 1.3
•Mobility Services Engine (MSE) 7.4.100.0 software release and context-aware software
Apparently only Prime 1.3 can manage this device.
Joris

WLC 5508 management interface

Hi, I have a particular wireless design that requires one WLC 5508 to be connected to two seperate swithces. Port 1 of WLC is connected trunk to Switch A and Port 2 of WLC is connected to Switch B. Each switch has its own local VLANS. When I connect 1130s LAPs they need to find the management interface initially and then use only AP management interfaces. since there is only one management interface, if I assign management interface on a vlan that is configured on switch A then APs on switch A join fine but those on switch B keep asking for management interface and from capwap debug on WLC it says that join request was received on wrong ineterface ....
the only work around to this was to make routing between switch A and switch B for the two vlans on which APs reside... but for security purposes - client would like to avoid this
any help much appreciated ..

Hi thanks for your reply,
Yes I agree perfectly with your explanation - On both switches I have UDP forward for 5246 and 5247 and everything works fine.
You understood exactly what's happening for initial discovery the Guest AP asks for managemnt interface through WLC port 2 but managerment IP is on admin side WLC port 1 and then it drops packet saying that it was received on the wrong port. In fact that is why I put an ACL between the Admin switch and guest switch taht allows only 5426 capwap control - just to allow that initial discovery from guest AP to contact Management interface which can only be assigned to one port and in my case it is on the admin switch side. And that is why I had to make a route between the two independent switches.
My question is to know if there is any other way with my given design to eliminate this initial discovery to the management inetrface, as my client would like the admin and guest switches to be completely seperated i.e. without the routing. Is there any way that the guest APs can make contact with the AP management interface on their side only skipping the discovery of the management interface ? the guest APs were primed on the admin side so they know the IP. After the initial discovery, if I remove the routing between admin and guest switch, guest APs keep their connectivity without any problems.

Windows Sharing problem from WLC 5508 to wired LAN

Dear All,
I'm having problem with windows sharing (file/printer sharing) from Wireless lan client which is connected to AP3500 and
WLC 5508 then to Nexus 7010. It's already using ip command, for example \\192.168.84.65
WLC os version 7.0.116.0 (using AP groups)
Nexus os version 4.2(6)
The weird thing is i can connect using windows sharing from wired LAN to wireless user however not vice versa.
for better explanation, here are the scenarios
1. Wireless lan to wired LAN using windows sharing - failed
1. Wired LAN to Wireless lan using windows sharing - success.
I've been analyzing by making sure that all the to end, there would be no firewall within source pc(s) and destination pc(s) and also
the ACL inside Nexus.
Been dying here to find solution for this, due to the customer is using it for file and printer sharing service.
Anyone has idea to solve this problem, i'm looking forward for any suggestion coming.
Arrai.

Peer to peer within wlc is using default setting which is allowed and as you may know, peer to peer permission only related between wireless client not wired one. CMIIW.

WLC 5508 running 7.4.110.0 unable to tftp upload config from controller

Hi,
Two WLC 5508 running identical code version. One is 50 license Primary, the second is HA. Identical config on both. HA WLC can upload its config to the TFTP or FTP server but Primary cannot. The operation fails for both CLI and GUI and for different protocols i.e. TFTP, FTP.
#### Primary Controller
(Cisco Controller) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.4.110.0
Bootloader Version............................... 1.0.20
Field Recovery Image Version..................... 7.6.95.16
Firmware Version................................. FPGA 1.7, Env 1.8, USB console 2.2
Build Type....................................... DATA + WPS
System Name...................................... PRODWC7309
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
Redundancy Mode.................................. Disabled
IP Address....................................... 10.1.30.210
Last Reset....................................... Power on reset
System Up Time................................... 18 days 18 hrs 51 mins 35 secs
System Timezone Location......................... (GMT+10:00) Sydney, Melbourne, Canberra
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180
Configured Country............................... AU - Australia
Operating Environment............................ Commercial (0 to 40 C)
--More-- or (q)uit
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +34 C
External Temperature............................. +17 C
Fan Status....................................... OK
State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 8
Number of Active Clients......................... 138
Memory Current Usage............................. Unknown
Memory Average Usage............................. Unknown
CPU Current Usage................................ Unknown
CPU Average Usage................................ Unknown
Burned-in MAC Address............................ 3C:08:F6:CA:52:20
Power Supply 1................................... Present, OK
Power Supply 2................................... Present, OK
Maximum number of APs supported.................. 50
(Cisco Controller) >debug transfer trace enable
(Cisco Controller) >transfer upload start
Mode............................................. TFTP
TFTP Server IP................................... 10.1.22.2
TFTP Path........................................ /
TFTP Filename.................................... PRODWC7309-tmp.cfg
Data Type........................................ Config File
Encryption....................................... Disabled
*** WARNING: Config File Encryption Disabled ***
Are you sure you want to start? (y/N) Y
*TransferTask: Jun 02 10:41:15.183: Memory overcommit policy changed from 0 to 1
*TransferTask: Jun 02 10:41:15.183: RESULT_STRING: TFTP Config transfer starting.
TFTP Config transfer starting.
*TransferTask: Jun 02 10:41:15.183: RESULT_CODE:1
*TransferTask: Jun 02 10:41:24.309: Locking tftp semaphore, pHost=10.1.22.2 pFilename=/PRODWC7309-tmp.cfg
*TransferTask: Jun 02 10:41:24.393: Semaphore locked, now unlocking, pHost=10.1.22.2 pFilename=/PRODWC7309-tmp.cfg
*TransferTask: Jun 02 10:41:24.393: Semaphore successfully unlocked, pHost=10.1.22.2 pFilename=/PRODWC7309-tmp.cfg
*TransferTask: Jun 02 10:41:24.394: tftp rc=-1, pHost=10.1.22.2 pFilename=/PRODWC7309-tmp.cfg
pLocalFilename=/mnt/application/xml/clis/clifile
*TransferTask: Jun 02 10:41:24.394: RESULT_STRING: % Error: Config file transfer failed - Unknown error - refer to log
*TransferTask: Jun 02 10:41:24.394: RESULT_CODE:12
*TransferTask: Jun 02 10:41:24.394: Memory overcommit policy restored from 1 to 0
% Error: Config file transfer failed - Unknown error - refer to log
(Cisco Controller) >show logging
*TransferTask: Jun 02 10:41:24.393: #UPDATE-3-FILE_OPEN_FAIL: updcode.c:4579 Failed to open file /mnt/application/xml/clis/clifile.
*sshpmReceiveTask: Jun 02 10:41:24.315: #OSAPI-3-MUTEX_FREE_INFO: osapi_sem.c:1087 Sema 0x2b32def8 time=142 ulk=1621944 lk=1621802 Locker(sshpmReceiveTask sshpmrecv.c:1662 pc=0x10b07938) unLocker(sshpmReceiveTask sshpmReceiveTaskEntry:1647 pc=0x10b07938)
-Traceback: 0x10af9500 0x1072517c 0x10b07938 0x12020250 0x12080bfc
*TransferTask: Jun 02 10:39:01.789: #UPDATE-3-FILE_OPEN_FAIL: updcode.c:4579 Failed to open file /mnt/application/xml/clis/clifile.
*sshpmReceiveTask: Jun 02 10:39:01.713: #OSAPI-3-MUTEX_FREE_INFO: osapi_sem.c:1087 Sema 0x2b32def8 time=5598 ulk=1621801 lk=1616203 Locker(sshpmReceiveTask sshpmrecv.c:1662 pc=0x10b07938) unLocker(sshpmReceiveTask sshpmReceiveTaskEntry:1647 pc=0x10b07938)
-Traceback: 0x10af9500 0x1072517c 0x10b07938 0x12020250 0x12080bfc
#### HA Controller
(Cisco Controller) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.4.110.0
Bootloader Version............................... 1.0.20
Field Recovery Image Version..................... 7.6.95.16
Firmware Version................................. FPGA 1.7, Env 1.8, USB console 2.2
Build Type....................................... DATA + WPS
System Name...................................... PRODWC7310
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
Redundancy Mode.................................. Disabled
IP Address....................................... 10.1.31.210
Last Reset....................................... Software reset
System Up Time................................... 18 days 19 hrs 1 mins 27 secs
System Timezone Location......................... (GMT+10:00) Sydney, Melbourne, Canberra
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180
Configured Country............................... AU - Australia
Operating Environment............................ Commercial (0 to 40 C)
--More-- or (q)uit
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +34 C
External Temperature............................. +17 C
Fan Status....................................... OK
State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 4
Number of Active Clients......................... 0
Memory Current Usage............................. Unknown
Memory Average Usage............................. Unknown
CPU Current Usage................................ Unknown
CPU Average Usage................................ Unknown
Burned-in MAC Address............................ 3C:08:F6:CA:53:C0
Power Supply 1................................... Present, OK
Power Supply 2................................... Present, OK
Maximum number of APs supported.................. 500
(Cisco Controller) >debug transfer trace enable
(Cisco Controller) >transfer upload start
Mode............................................. FTP
FTP Server IP.................................... 10.1.22.2
FTP Server Port.................................. 21
FTP Path......................................... /
FTP Filename..................................... 10_1_31_210_140602_1050.cfg
FTP Username..................................... ftpuser
FTP Password..................................... *********
Data Type........................................ Config File
Encryption....................................... Disabled
*** WARNING: Config File Encryption Disabled ***
Are you sure you want to start? (y/N) y
*TransferTask: Jun 02 10:51:31.278: Memory overcommit policy changed from 0 to 1
*TransferTask: Jun 02 10:51:31.278: RESULT_STRING: FTP Config transfer starting.
FTP Config transfer starting.
*TransferTask: Jun 02 10:51:31.278: RESULT_CODE:1
*TransferTask: Jun 02 10:52:05.468: ftp operation returns 0
*TransferTask: Jun 02 10:52:05.477: RESULT_STRING: File transfer operation completed successfully.
*TransferTask: Jun 02 10:52:05.477: RESULT_CODE:11
File transfer operation completed successfully.
Not upgrading to 7.4.121.0 because of bug CSCuo63103. Have not restarted the controller yet.
Any one else had this issue ? Is there a workaround ?
Thanks,
Rick.

Thanks Stephen, In my deployments of 7.4.110.0 version I have not seen this issue so may be controller reboot will fix it (we do have HA to minimize the impact). I will keep the thread updated with findings and may request TAC for the special release 7.4.121.0 if the still not happy with 7.4.110.0
Rick.

WLC 5508 , AP client dhcp address different from WLAN interface VLAN subnet?

Hope the title makes sense, here's my situation: I have multiple businesses on 1 WLC 5508, there's a LAG to my core switch with seperate interfaces for each, broken up by vlans.
My question is: if i have a WLAN setup to use interface "Company A" which is vlan 10 with an ip of 10.0.1.5 which then points to 10.0.1.10 for dhcp.
Can the WLAN client connecting to the Company A WLAN use an IP in a different IP range?(192.168.1.10?) can the wlc route? from the perspective of the DHCP server where doers the request come from? (10.0.1.5?)
Can the DHCP server 10.0.10.10 on vlan 10 respond back with and ip on a different subnet to assign to the client to use and still be fully fonctioning? would the default gateway for the client need to be 10.0.1.5? So the clients ip would be 192.168.1.10 /24 with a gateway of 10.0.1.5 (ip adress fo vlan10 interface on WLC) And if multiple clients on the same subnet wanted to talk to each other woudl the WLC know how to route them to each other without passing through the default gateway?
Sorry if this is confusing I'm having a bit of a hard time explaining it in works, i can try and draw somethign up if it makes more sense.
thanks
Eric

I think if you want these clients to stick to a WLAN configured on a VLAN that has a different IP addressing you could configure your VLAN with the normal IP addressing then add on the SVI the 2nd IP_Class_default_gateway.
E.G.
Vlan 10
interface vlan 10
ip address 10.0.10.1 255.255.255.0
ip address 192.168.1.1 255.255.255.0 secondary
Clients that receive IP address from 192.168.1.0/24 network will be able to reach 192.168.1.1 and all traffic will pass right.

WLC 5508 disable wlan client still connected

I have one wlc 5508 running on latest IOS 7.116, there is one wlan abc which i have disable status and disable broadcast, but randomly still i can see from wlc dashboard there is one client connected to this wlan abc. The moment i check on the client details, there is no client connected to that wlan and when return to dashboard, no more client connected to that wlan abc. This happened in randomly, it is bug or something else?

I would guess that the client entry also indicates "probing" as status. It means that the client is not connected. It is actually probing, so it"s looking for that SSID that it probably associated to in the past (so it remembers about it)

WLC-5508 Authorization failed to create SSID

Hi All,
I have two WLC-5508 for 50 AP's deployed. One is primary controller & other is secondary.
Recently noticed an unknown "authorization failed, no sufficient privileges for user" message poping up while making configuration changes
in WLC. Specificly when trying to create an new SSID. WLC Authentication is local. This message poped up earlier once or twice but it didnt prevent
from making changes that time.
How to troubleshoot ?
Regards
Gautam

Do you have any radius configured on the WLC by chance. If so can you make sure you don't have management checked there. I have not seen that issues with the 5508 and any of the 7.x code as of yet.
Sent from Cisco Technical Support iPhone App

AP disconnected from WLC 5508

Dear All,
Greetings!!!!!
We have WLC 5508 installed in our premises to which 80 1242AG APs are connected. Few days ago, all the APs all of a sudden disconnected from Controller and rejoined after 12 to 15 hours. when we try to investigate, there was regulatory domain conflict occur. But we didn't understand that those APs were configured with the same config before. How come they got diconnected and now rejoined without changing any configration in WLC?
Logs for both AP and WLC has been attahched here.
Kindly guide us!!!

Then the APs should of not of disassociated from the WLC. If all these APs are local to where the WLC resides, then I really don't know why the APs would of disassociated. Take a look at the monitor tab and then look at statistics and then ap join. There should be a history unless the WLC was rebooted or the log was cleared. The only other thing I could think of is if there was a duplicate address on a device that had the same IP address as the management interface of the WLC.
Sent from Cisco Technical Support iPhone App

WLC failed to connect to WCS by snmp

Hi fellows,
I've a solution implemented that contains 1 WCS and 3 WLC.
For some unknown reason, started from some point, one of the WLC started to fail to connect by snmp to the WCS, given the next error "
%AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1037 Could not connect to LDAP server 2, reason: 49 (Invalid credentials)."
I've made upgrade for the last version of firmware on all WLC's, have rewritten the credentials of SNMP, but the problem remains with only one of the WLC's, all others are working fine.
The SNMP is v.3.
The version of WCS is 6.0.132.0.
Any ideias?
Best regards,
Luis Matos

Hi Scott Fella,
Thanks for your answer.
When the problem appears, the version of the wlc was 6.0.182. We 've made upgrade to version 7.0.116.0 to try to resolve the problem, but the problem remains.
The 2 others WLC that is working fine, have the version 6.0.182.
There isn't any FW between the WLC's and WCS.
Best Regards,
Luis Matos

Error while connecting to an OData Feed from Excel 2013 PowerPivot . Error: Failed to connect to the server. Reason: The payload kind 'BinaryValue' of the given data feed is not supported

I am trying to connect to a Odata Data feed from Excel 2013 Power Pivot
The datasource is in sharepoint site eg: https://sitename/Shared%20Documents/datafeed.atomsvc
getting below error
Error message:
Failed to connect to the server. Reason: The payload kind 'BinaryValue' of the given data feed is not supported.
============================
Call Stack:
============================
   at Microsoft.Data.DataFeedClient.DataFeedODataReader.ValidatePayloadKind(ODataPayloadKind payloadKind, ODataMessageReader odataMessageReader)
   at Microsoft.Data.DataFeedClient.DataFeedODataReader.InterceptODataException(Action action)
   at Microsoft.Data.DataFeedClient.DataFeedODataReader..ctor(IODataResponseMessage responseMessage, Int64 maxReceivedMessageSize)
   at Microsoft.Data.DataFeedClient.DataFeedODataReader.CreateReader(IWebResponse webResponse, Int64 maxReceivedMessageSize, Boolean applySlashUpdatingBaseUriResolver)
   at Microsoft.Data.DataFeedClient.ODataHelper.GetCollectionsFromServiceDocumentUrl(Uri serviceDocumentUrl, DataFeedConnection connection)
   at Microsoft.Data.DataFeedClient.DataFeedConnection.Open()
   at Microsoft.AnalysisServices.BackEnd.RelationalDataSourceConnection.InitializeConnectionObject(String connectionIdentifier)
   at Microsoft.AnalysisServices.BackEnd.RelationalDataSourceConnection.InitializeConnectionObject(String connectionIdentifier)
   at Microsoft.AnalysisServices.BackEnd.RelationalDataSourceConnection.Open(String& connectionIdentifier)
   at Microsoft.AnalysisServices.BackEnd.RelationalDataSourceConnection.Open()
   at Microsoft.AnalysisServices.Common.DataSourceBasic.ClickTestConnection(Object progressControl)
Appreciate suggestions/answers
NOTE: The error is showing only while using Excel 2013 powerpivot
its working good with Excel 2010 powerpivot

Anita,
Please look into using Power Query to use OData as a source in Power Pivot.
Thanks!
Ed Price, Power BI & SQL Server Customer Program Manager (Blog,
Small Basic,
Wiki Ninjas,
Wiki)
Answer an interesting question?
Create a wiki article about it!

Failed to obtain/create connection from connection pool after redeploy

I have a web application (.war) that uses a jdbc connection pool. The application works fine, however after I redeploy it using the administration console I get "Failed to obtain/create connection from connection pool [ Datavision_Pool ]. Reason : null" followed by "Error allocating connection : [Error in allocating a connection. Cause: null]" from javax.enterprise.resource.resourceadapter and I am forced to restart the instance. I am running Sun Java System Application Server 9.1 (build b58g-fcs)
using a connection pool to a Microsoft SQL 2000 database using inet software's JDBC drivers. I need to be able to redeploy applications without having to restart the instance. Any help is appreciated.

I have turned on some additional diagnostics and found out some answers and a work-around, but I think that there may be a bug in the way JDBC connection pool classes are loaded. The actual error was a null pointer in the JDBC driver class in the perpareStatement method. The only line in this method is "return factory.createPreparedStatement( this , sql );" and the only possible NPE would be if the factory was null, which should be impossible because it is a static variable and it is initialized when the class is loaded. The problem occurs because we deploy the JDBC driver .jar file within our .war file, for use when a client doesn't have or want to use connection pooling. Apparently, the connection pool must have picked up some of these classes and when the .war was redeployed, the reference to the factory was lost for existing connections (not sure how). If I remove the JDBC .jar file from the .war, it works, but that wasn't an ideal solution, the other way to get it to work was to change the sun-web.xml file to have <class-loader delegate="true">. We previously had it set to false in version 8.1 because of interference with a different version of the apache Tiles classes, which has now been addressed in version 9.1.
I still think there is an issue, because the connection pool should never use the application specific classloaders. Am I wrong to believe this?

WLC 5508 - Failed to connect from LMS 3.2

Similar Messages

Maybe you are looking for