Location can't find clients

Unanswered Question
Dec 16th, 2008

In this Location is Reachable state and synchronizes seamlessly with the controllers. But do not get any client. The error that appears is as follows:

192.168.20.6: Internal error in location server. Error Message:Server response: [Solid JDBC 04.50.0133]SOLID SQL Error 13: illegal column name 'AESMOBILESTATIMLOCATION.CHANGEDON'

Does anyone could help me? What could be happening?

Thank you.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
wesleyterry Tue, 12/16/2008 - 09:46

What version of the location appliance are you running?

What version of WCS?

It looks to me like the Location appliance is either referencing a column that does not exist in the SOLID database (on WCS?) or it is maybe recieving data with that column name and doesn't have anywhere to put it.

I would think this is either a serious database corruption/bug or the location appliance and WCS are at incompatible versions....?

slandeira Tue, 12/30/2008 - 08:56

The versions are:

Location 4.0.38.0

WCS 4.1.91.0

Controllers 4.1.185.0

In the matrix don't show these incompatible versions.

¿Database corruption? ¿server error??

Scott Fella Tue, 12/30/2008 - 09:02

That is not compatible... 4.0.38.0 is too high of a firmware for 4.1.185:

http://www.cisco.com/en/US/docs/wireless/location/2700/release/notes/larn4038.html#wp39483

If you keep your wlc & wcs at that firmware, then you need to load 3.0.42 on the LB.

http://www.cisco.com/en/US/docs/wireless/location/2700/release/notes/larn3042.html#wp998995

Any version 3.1 or higher will require WCS to be at least 4.2.x code.

slandeira Fri, 01/09/2009 - 05:01

Hello,

I tried to change the version of 4.0.38 to 3.0.42 but I can not make it run.

The error I get is:

[[email protected] locserver]# /etc/init.d/locserverd start

Starting locserverd: [ OK ]

[[email protected] locserver]# /etc/init.d/locserverd status

Getting the status locserverd: com.aes.client.AesClientException: Request to server failed, reason: java.security.PrivilegedActionException: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed

at com.aes.client.AesClientAdminImpl.getServerInfo(Unknown Source)

at com.aes.server.cli.CmdGetServerInfo.run(Unknown Source)

at com.aes.server.cli.CmdGetServerInfo.main(Unknown Source)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:585)

at com.zerog.lax.LAX.launch(DashoA8113)

at com.zerog.lax.LAX.main(DashoA8113)

What could be happening?

I attached a file with the upgrade process.

¡¡PLEASE HELP!

jamespiljay Thu, 01/15/2009 - 17:07

If you have had success in uninstalling the incompatible code and now have the proper code installed, try the following, the db is most likely corrupt:

/etc/init.d/locserverd stop

cd /opt/locserver/db/linux

mv server-eng.db ./server-eng.db.old

/etc/init.d/locserverd start

Dave Anthony David Wed, 02/25/2009 - 02:13

I had same error to..

[[email protected] linux]# /etc/init.d/locserverd status

Getting the status locserverd: com.aes.client.AesClientException: Request to server failed, reason: java.security.PrivilegedActionException: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed

at com.aes.client.AesClientAdminImpl.getServerInfo(Unknown Source)

at com.aes.server.cli.CmdGetServerInfo.run(Unknown Source)

at com.aes.server.cli.CmdGetServerInfo.main(Unknown Source)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at com.zerog.lax.LAX.launch(DashoA8113)

at com.zerog.lax.LAX.main(DashoA8113)

slandeira Wed, 02/25/2009 - 03:05

In my case the problem fix with the upgrade version of the Controllers. Make sure that no problems of incompatibility between the versions of WCS, WLC and location.

Actions

This Discussion