Session-level exception of type AccLogicError thrown. LineNum=273. SessionId=xx.

Answered Question
Aug 26th, 2010
User Badges:

I'm getting a lot of these warning messages and so far i've been unable to determin what it is.  The events section is pretty useless as I cannot get more information about particular events and have no real idea if this is something to be worried about or not.


Here is a copy paste for a few of these events.



08/25/2010 18:03:3610.1.250.30WarningSession-level exception of type AccLogicError thrown. LineNum=273. SessionId=153.
08/25/2010 18:03:2010.1.250.30WarningSession-level exception of type AccLogicError thrown. LineNum=273. SessionId=152.
08/24/2010 01:24:2510.1.250.30WarningSession-level exception of type AccLogicError thrown. LineNum=273. SessionId=99.
08/24/2010 01:22:3910.1.250.30WarningSession-level exception of type AccLogicError thrown. LineNum=273. SessionId=98.
08/24/2010 01:21:1710.1.250.30WarningSession-level exception of type AccLogicError thrown. LineNum=273. SessionId=97.
08/24/2010 01:19:5610.1.250.30WarningSession-level exception of type AccLogicError thrown. LineNum=273. SessionId=96.
08/24/2010 01:15:0710.1.250.30WarningSession-level exception of type AccLogicError thrown. LineNum=273. SessionId=95.
08/24/2010 01:13:4910.1.250.30WarningSession-level exception of type AccLogicError thrown. LineNum=273. SessionId=94.
08/24/2010 01:12:3010.1.250.30WarningSession-level exception of type AccLogicError thrown. LineNum=273. SessionId=93.


Anyone see this with their WAAS Mobile? Should I be concerned?

Correct Answer by smnambia about 6 years 11 months ago

The Session-level exception warning messages that you are seeing is a message that we display when client session to that particular server is lost.

It is not a performance impacting error.


Session exceptions are typically not even noticed by the end user, in the worst case the client may disconnect and reconnect few seconds later.


We are tracking this issue at our end and have a ddts filed for this ddts number is CSCti68375.It will take 24-48 hours for the ddts to show up on Cisco Bug tool Kit


You could manually wipe the Event log but there is no way to clear the messages from the WAAS Mobile web interface.


Hope the above information helps.Please do let us know if you have any follow-up questions.


Thanks

-Smita


Cisco PDI HelpDesk

http://www.cisco.com/go/pdihelpdesk





  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Bhavin Yadav Thu, 08/26/2010 - 16:47
User Badges:
  • Cisco Employee,

Hi Shaun,

These error messages are pointing towards license limit being reached on mobile server. Please make sure you have enough licenses available for the mobile clients.

Regards.


PS: If this answers your question, please mark this as Answered.

focused Fri, 08/27/2010 - 08:13
User Badges:

Not sure how we could be running out of licenses.  We have 15 users with WAAS Mobile installed and have 200 user license.  How can we run out of licenses with only 15 users?  I've checked and under Licenses it says Provisioned 200 and In Use 15.

Bhavin Yadav Fri, 08/27/2010 - 10:43
User Badges:
  • Cisco Employee,

Hello,

In that case, you may want to open up a case with TAC and have them analyze sysreprots from server side.

When do you see this issue? when you try to connect the client or anytime?

How did this issue started ? did you recently upgarde waas mobile?

Have you installed WAAS mobile on a group of new laptops / pcs recently?

How about the mobile client connections to mobile server? Are they optimiiang traffic while this error message is appearing in the logs?

Regards.

focused Mon, 08/30/2010 - 07:47
User Badges:

The issue seems to be happening randomly.  Just checked the event logs from the weekend and someone at almost 9pm received this error.  At 9pm there are maybe 2-3 users on if that.  So I cannot see it being a license issue.


The issue started a few days ago, on the 24th of August.  The 25th is when we upgraded from 3.5.0 to 3.5.1.


Yes we've been adding new PC's and Laptops every day pretty much as we are rolling this out to our remote workers.  Why?


It appears as if the optimization is still happening, we are getting great results.


Unfortunately we do not have TAC Support on this product, the business has not allowed us to purchase support on this specific product.  So this forum is my only help at this point.

Bhavin Yadav Mon, 08/30/2010 - 15:28
User Badges:
  • Cisco Employee,

Ok. in that case, we will probably need more details and logs.

Can you attach few more lines of logs at the time when you encountered this message?

is this issue caused by one client when it tries to connect to mobile server or this is happening with any client?

Regards.

focused Mon, 08/30/2010 - 15:42
User Badges:

I wish I could tell you what client it is, the log messages really don't tell me anything at all.  The errors and warning are very limited and don't give me any indication who it is.  This would be something for improvement.  We have 5 users connected today and I have no clue which one generated this error.  I can reboot the server tonight if you want and provide you a system report.  Let me know.


Here are more lines of errors as you requested.

08/30/2010 15:54:5310.1.250.30WarningSession-level exception of type AccEncodeError thrown. LineNum=3133. SessionId=164.
08/27/2010 20:54:1310.1.250.30WarningSession-level exception of type AccLogicError thrown. LineNum=273. SessionId=115.
08/26/2010 02:49:5810.1.250.30InformationThe Delta Cache File is running with a full size of 460800 blocks
08/26/2010 02:49:5710.1.250.30InformationThe server license check succeeded.
08/26/2010 02:49:5710.1.250.30InformationStarting WAAS Mobile Server (Version: 2626).
08/26/2010 02:49:5710.1.250.30InformationEvent logging was initialized
08/26/2010 02:44:2510.1.250.30InformationShutting down WAAS Mobile Server.
08/25/2010 18:03:3610.1.250.30WarningSession-level exception of type AccLogicError thrown. LineNum=273. SessionId=153.
08/25/2010 18:03:2010.1.250.30WarningSession-level exception of type AccLogicError thrown. LineNum=273. SessionId=152.
08/24/2010 01:24:2510.1.250.30WarningSession-level exception of type AccLogicError thrown. LineNum=273. SessionId=99.
08/24/2010 01:22:3910.1.250.30WarningSession-level exception of type AccLogicError thrown. LineNum=273. SessionId=98.
08/24/2010 01:21:1710.1.250.30WarningSession-level exception of type AccLogicError thrown. LineNum=273. SessionId=97.
08/24/2010 01:19:5610.1.250.30WarningSession-level exception of type AccLogicError thrown. LineNum=273. SessionId=96.
08/24/2010 01:15:0710.1.250.30WarningSession-level exception of type AccLogicError thrown. LineNum=273. SessionId=95.
08/24/2010 01:13:4910.1.250.30WarningSession-level exception of type AccLogicError thrown. LineNum=273. SessionId=94.
08/24/2010 01:12:3010.1.250.30WarningSession-level exception of type AccLogicError thrown. LineNum=273. SessionId=93.
08/24/2010 01:08:1410.1.250.30WarningSession-level exception of type AccLogicError thrown. LineNum=273. SessionId=92.
08/24/2010 01:06:3110.1.250.30WarningSession-level exception of type AccLogicError thrown. LineNum=273. SessionId=91.
08/24/2010 01:05:2010.1.250.30WarningSession-level exception of type AccLogicError thrown. LineNum=273. SessionId=90.
08/24/2010 01:01:2710.1.250.30WarningSession-level exception of type AccLogicError thrown. LineNum=273. SessionId=89.
08/24/2010 01:00:2410.1.250.30WarningSession-level exception of type AccLogicError thrown. LineNum=273. SessionId=88.
08/24/2010 00:59:3610.1.250.30WarningSession-level exception of type AccLogicError thrown. LineNum=273. SessionId=87.
08/24/2010 00:58:1710.1.250.30WarningSession-level exception of type AccLogicError thrown. LineNum=273. SessionId=86.
08/24/2010 00:57:2910.1.250.30WarningSession-level exception of type AccLogicError thrown. LineNum=273. SessionId=85.
08/24/2010 00:56:4110.1.250.30WarningSession-level exception of type AccLogicError thrown. LineNum=273. SessionId=84.
Bhavin Yadav Mon, 08/30/2010 - 15:56
User Badges:
  • Cisco Employee,

Well,  I am not sure if reboot will resolve this issue. I am not sure how feasible it is in your setup but if possible, try to re-install 3.5.1 and reapply the licenses. This might fix the problem. The error message is not giving us a whole lot of details. I am not sure how much sysreprot will help us, too. if you want, attach sysreport to this one and I will look at it and try to update you.

Regards.

focused Mon, 08/30/2010 - 15:59
User Badges:

I just did the update last week, not really keen on doing it again.  I'd like to know what these errors are and there should be some way to understand these errors. Why else would they be there? Makes no sense.


These errors did show up before the upgrade which was a uninstall, install of the new version and apply the configuration.

Will attach the sysreport tonight.


Thanks

Shaun

Correct Answer
smnambia Tue, 08/31/2010 - 11:42
User Badges:

The Session-level exception warning messages that you are seeing is a message that we display when client session to that particular server is lost.

It is not a performance impacting error.


Session exceptions are typically not even noticed by the end user, in the worst case the client may disconnect and reconnect few seconds later.


We are tracking this issue at our end and have a ddts filed for this ddts number is CSCti68375.It will take 24-48 hours for the ddts to show up on Cisco Bug tool Kit


You could manually wipe the Event log but there is no way to clear the messages from the WAAS Mobile web interface.


Hope the above information helps.Please do let us know if you have any follow-up questions.


Thanks

-Smita


Cisco PDI HelpDesk

http://www.cisco.com/go/pdihelpdesk





focused Tue, 08/31/2010 - 11:51
User Badges:

Thanks for the clarification.  Is there anyway I could have looked this up?  The warnings and information in the log are not even clickable to see what the error is.  Doesn't help when we cannot troubleshoot or check our own error logs.


Thanks

smnambia Tue, 08/31/2010 - 12:31
User Badges:

The only way to look it up would be to check the Cisco Bugtool kit and see if there was any ddts opened for this warning message.


Totally agree it would be nice to have either a error/warning guide book or even if the waas-mobile web interface could provide more information.


I have sent your response to the WaasMobile product team.They will surely look into this request.


Thanks

-Smita


Cisco PDI HelpDesk

http://www.cisco.com/go/pdihelpdesk

Actions

This Discussion