Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- Technology and Support
- DevNet Hub
- DevNet Collaboration
- Collaboration Knowledge Base
- Finesse desktop loading problem (on the browser)
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
326
Views
0
Helpful
0
Comments
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 01-24-2014 03:21 PM
This document was generated from CDN thread
Created by: Olivier MENAN on 24-10-2011 08:46:22 AM
Hello,
Does anyone have ever had the same problem as me?
It's the following.
When agent AgentId/Password and Extention are correct, Finesse shows only "loading" definitevely.
I don't no why.
Can you help me?
Regards,
Subject: RE: Finesse desktop loading problem (on the browser)
Replied by: David Lender on 24-10-2011 12:00:09 PM
I have seen this problem and found that restarting Tomcat and reloading the page resolved the issue.
To restart Tomcat, i use WinSCP to the Finesse server, and then use Putty to start the console and enter the following command:
controlcenter.sh "Cisco Tomcat" restart
If that doesn't resolve the issue suggest you look at the logs.
Finesse logs are located in the subdirectories under /opt/cisco/desktop/logs on the box. The ones we typically look at are in the webservices
Subject: RE: Finesse desktop loading problem (on the browser)
Replied by: Olivier MENAN on 24-10-2011 12:51:44 PM
Hello,
I restarted tomcat service, no change.
The first line of error logs are the following:
0000000001: 172.31.15.34: Oct 17 2011 17:22:57.130 +0200: %_Infrastructure Initialization, completed-3-org.apache.commons.digester.Digester: Parse Error at line 309 column 17: The content of element type "struts-config" must match "(data-sources?,form-beans?,global-exceptions?,global-forwards?,action-mappings?,controller?,message-resources*,plug-in*)".
org.xml.sax.SAXParseException: The content of element type "struts-config" must match "(data-sources?,form-beans?,global-exceptions?,global-forwards?,action-mappings?,controller?,message-resources*,plug-in*)".
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
Thank you for your intervention.
Regards,
Subject: RE: Finesse desktop loading problem (on the browser)
Replied by: David Lender on 25-10-2011 09:28:04 AM
That error is benign¿it shows up in everyone¿s error log. This appears to be a client-side issue. This normally happens if your Extension is not registered properly (as it takes 60 seconds to timeout). Are you waiting for the error message to come (waiting a couple of minutes)??? It would help if you can post the entire latest log file.
Subject: RE: Finesse desktop loading problem (on the browser)
Replied by: Olivier MENAN on 28-10-2011 04:49:19 AM
Hello David,
Sorry, I was out of office for the last two days, that the reason why you got no answer.
the entire log file is the following:
0000000001: 172.31.15.34: Oct 17 2011 17:22:57.130 +0200: %_Infrastructure Initialization, completed-3-org.apache.commons.digester.Digester: Parse Error at line 309 column 17: The content of element type "struts-config" must match "(data-sources?,form-beans?,global-exceptions?,global-forwards?,action-mappings?,controller?,message-resources*,plug-in*)".
org.xml.sax.SAXParseException: The content of element type "struts-config" must match "(data-sources?,form-beans?,global-exceptions?,global-forwards?,action-mappings?,controller?,message-resources*,plug-in*)".
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.commons.digester.Digester.parse(Digester.java:1548)
at org.apache.struts.action.ActionServlet.parseModuleConfigFile(ActionServlet.java:708)
at org.apache.struts.action.ActionServlet.initModuleConfig(ActionServlet.java:670)
at org.apache.struts.action.ActionServlet.init(ActionServlet.java:329)
at javax.servlet.GenericServlet.init(GenericServlet.java:212)
at sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:269)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:301)
at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:162)
at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:115)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1167)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:993)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4149)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4458)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.access$000(ContainerBase.java:123)
at org.apache.catalina.core.ContainerBase$PrivilegedAddChild.run(ContainerBase.java:145)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:769)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:850)
at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:724)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:493)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1206)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:314)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:722)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:516)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:583)
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:597)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Thank you for all.
Regards,
Subject: RE: Finesse desktop loading problem (on the browser)
Replied by: David Lender on 28-10-2011 12:33:34 PM
We will need additional logs in order to assist:
/opt/cisco/desktop/logs/desktop/*.*
/opt/cisco/desktop/logs/webservices/*.*
/opt/cisco/desktop/logs/finesseconfig/*.*
/usr/local/thirdparty/jakarta-tomcat/logs/*.out
/usr/local/thirdparty/jakarta-tomcat/logs/*.log
You can zip them up and attach them to this thread.
Subject: RE: Finesse desktop loading problem (on the browser)
Replied by: Olivier MENAN on 28-10-2011 02:13:05 PM
Hello David,
You can find in attached files the requested logs.
Regards,
Subject: RE: Finesse desktop loading problem (on the browser)
Replied by: Olivier MENAN on 28-10-2011 02:17:07 PM
David,
Thank you a lot
Regards,
Subject: RE: Finesse desktop loading problem (on the browser)
Replied by: Olivier MENAN on 21-11-2011 10:45:04 AM
Sorry, It was only a firewall problem.
Regards,
Subject: How to add marquee under tab on finesse desktop ?
Replied by: Olivier MENAN on 06-05-2013 06:38:12 AM
Hell everybody, Assuming the attached file, I'm trying to add the marquee with my company logo under tab button. Any body can help me? Thank you. Regards,
Subject: RE: How to add marquee under tab on finesse desktop ?
Replied by: Kevin Pickard on 06-05-2013 10:14:16 AM
Olivier the Marquee is a gadget that is part of Upstream Works for Finesse. We can help… Please call Karen Miller @ 905 660-0969 x368.
Subject: RE: How to add marquee under tab on finesse desktop ?
Replied by: Olivier MENAN on 06-05-2013 10:18:16 AM
Hello Kevin.
Thank youPlease, can you give me the full phone number ?
Regards,
Subject: RE: How to add marquee under tab on finesse desktop ?
Replied by: Kevin Pickard on 06-05-2013 10:24:11 AM
Olivier we are located in Canada so the country code is 1. The full number would be +1 905-660-0969 extension 368.
Subject: RE: How to add marquee under tab on finesse desktop ?
Replied by: Olivier MENAN on 06-05-2013 10:28:11 AM
Thank you. I'm calling her !!
Created by: Olivier MENAN on 24-10-2011 08:46:22 AM
Hello,
Does anyone have ever had the same problem as me?
It's the following.
When agent AgentId/Password and Extention are correct, Finesse shows only "loading" definitevely.
I don't no why.
Can you help me?
Regards,
Subject: RE: Finesse desktop loading problem (on the browser)
Replied by: David Lender on 24-10-2011 12:00:09 PM
I have seen this problem and found that restarting Tomcat and reloading the page resolved the issue.
To restart Tomcat, i use WinSCP to the Finesse server, and then use Putty to start the console and enter the following command:
controlcenter.sh "Cisco Tomcat" restart
If that doesn't resolve the issue suggest you look at the logs.
Finesse logs are located in the subdirectories under /opt/cisco/desktop/logs on the box. The ones we typically look at are in the webservices
Subject: RE: Finesse desktop loading problem (on the browser)
Replied by: Olivier MENAN on 24-10-2011 12:51:44 PM
Hello,
I restarted tomcat service, no change.
The first line of error logs are the following:
0000000001: 172.31.15.34: Oct 17 2011 17:22:57.130 +0200: %_Infrastructure Initialization, completed-3-org.apache.commons.digester.Digester: Parse Error at line 309 column 17: The content of element type "struts-config" must match "(data-sources?,form-beans?,global-exceptions?,global-forwards?,action-mappings?,controller?,message-resources*,plug-in*)".
org.xml.sax.SAXParseException: The content of element type "struts-config" must match "(data-sources?,form-beans?,global-exceptions?,global-forwards?,action-mappings?,controller?,message-resources*,plug-in*)".
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
Thank you for your intervention.
Regards,
Subject: RE: Finesse desktop loading problem (on the browser)
Replied by: David Lender on 25-10-2011 09:28:04 AM
That error is benign¿it shows up in everyone¿s error log. This appears to be a client-side issue. This normally happens if your Extension is not registered properly (as it takes 60 seconds to timeout). Are you waiting for the error message to come (waiting a couple of minutes)??? It would help if you can post the entire latest log file.
Subject: RE: Finesse desktop loading problem (on the browser)
Replied by: Olivier MENAN on 28-10-2011 04:49:19 AM
Hello David,
Sorry, I was out of office for the last two days, that the reason why you got no answer.
the entire log file is the following:
0000000001: 172.31.15.34: Oct 17 2011 17:22:57.130 +0200: %_Infrastructure Initialization, completed-3-org.apache.commons.digester.Digester: Parse Error at line 309 column 17: The content of element type "struts-config" must match "(data-sources?,form-beans?,global-exceptions?,global-forwards?,action-mappings?,controller?,message-resources*,plug-in*)".
org.xml.sax.SAXParseException: The content of element type "struts-config" must match "(data-sources?,form-beans?,global-exceptions?,global-forwards?,action-mappings?,controller?,message-resources*,plug-in*)".
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.commons.digester.Digester.parse(Digester.java:1548)
at org.apache.struts.action.ActionServlet.parseModuleConfigFile(ActionServlet.java:708)
at org.apache.struts.action.ActionServlet.initModuleConfig(ActionServlet.java:670)
at org.apache.struts.action.ActionServlet.init(ActionServlet.java:329)
at javax.servlet.GenericServlet.init(GenericServlet.java:212)
at sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:269)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:301)
at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:162)
at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:115)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1167)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:993)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4149)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4458)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.access$000(ContainerBase.java:123)
at org.apache.catalina.core.ContainerBase$PrivilegedAddChild.run(ContainerBase.java:145)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:769)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:850)
at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:724)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:493)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1206)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:314)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:722)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:516)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:583)
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:597)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Thank you for all.
Regards,
Subject: RE: Finesse desktop loading problem (on the browser)
Replied by: David Lender on 28-10-2011 12:33:34 PM
We will need additional logs in order to assist:
/opt/cisco/desktop/logs/desktop/*.*
/opt/cisco/desktop/logs/webservices/*.*
/opt/cisco/desktop/logs/finesseconfig/*.*
/usr/local/thirdparty/jakarta-tomcat/logs/*.out
/usr/local/thirdparty/jakarta-tomcat/logs/*.log
You can zip them up and attach them to this thread.
Subject: RE: Finesse desktop loading problem (on the browser)
Replied by: Olivier MENAN on 28-10-2011 02:13:05 PM
Hello David,
You can find in attached files the requested logs.
Regards,
Subject: RE: Finesse desktop loading problem (on the browser)
Replied by: Olivier MENAN on 28-10-2011 02:17:07 PM
David,
Thank you a lot
Regards,
Subject: RE: Finesse desktop loading problem (on the browser)
Replied by: Olivier MENAN on 21-11-2011 10:45:04 AM
Sorry, It was only a firewall problem.
Regards,
Subject: How to add marquee under tab on finesse desktop ?
Replied by: Olivier MENAN on 06-05-2013 06:38:12 AM
Hell everybody, Assuming the attached file, I'm trying to add the marquee with my company logo under tab button. Any body can help me? Thank you. Regards,
Subject: RE: How to add marquee under tab on finesse desktop ?
Replied by: Kevin Pickard on 06-05-2013 10:14:16 AM
Olivier the Marquee is a gadget that is part of Upstream Works for Finesse. We can help… Please call Karen Miller @ 905 660-0969 x368.
Subject: RE: How to add marquee under tab on finesse desktop ?
Replied by: Olivier MENAN on 06-05-2013 10:18:16 AM
Hello Kevin.
Thank youPlease, can you give me the full phone number ?
Regards,
Subject: RE: How to add marquee under tab on finesse desktop ?
Replied by: Kevin Pickard on 06-05-2013 10:24:11 AM
Olivier we are located in Canada so the country code is 1. The full number would be +1 905-660-0969 extension 368.
Subject: RE: How to add marquee under tab on finesse desktop ?
Replied by: Olivier MENAN on 06-05-2013 10:28:11 AM
Thank you. I'm calling her !!
Labels:
Getting Started
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
Customers Also Viewed These Support Documents