Categories missing for one user

[JT01]

Hi All,

I have a user that has no categories listed in LiveCycle Workspace inside of "Start Process".  A normal user would see something similiar to this:

The user in question has only Favorities and nothing else.  She is the only user that I have seen that has this issue as I don't even think you can hide categories for specific users or groups.  This user is able to login to workspace, she can check tracking but has nothing listed in "Start Process". 

I am running out of ideas to try, has anyone run across this and found a solution?

[Michael_Stewar2]

Is anything listed in the server log when this user logs into Workspace? 

[JT01]

Actually yes.  It's not when the user logs into Workspace but its when they click on "Start Process" and attempt to load the categories.

-------------------------------------

2012-08-27 11:19:09,774 INFO  [STDOUT] (http-0.0.0.0-8080-66) [LCDS] Unknown AMF type '117'.

flex.messaging.io.UnknownTypeException: Unknown AMF type '117'.

          at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:233)

          at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:135)

          at flex.messaging.io.amf.Amf3Input.readObjectOneLevelDown(Amf3Input.java:1042)

          at flex.messaging.io.amf.Amf3Input.readScriptObject(Amf3Input.java:778)

          at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:157)

          at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:135)

          at flex.messaging.io.amf.Amf3Input.readObjectOneLevelDown(Amf3Input.java:1042)

          at flex.messaging.io.amf.Amf3Input.readScriptObject(Amf3Input.java:791)

          at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:157)

          at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:135)

          at flex.messaging.io.amf.Amf3Input.readObjectOneLevelDown(Amf3Input.java:1042)

          at flex.messaging.io.amf.Amf3Input.readArray(Amf3Input.java:699)

          at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:161)

          at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:135)

          at flex.messaging.io.amf.Amf3Input.readObjectOneLevelDown(Amf3Input.java:1042)

          at flex.messaging.io.amf.Amf3Input.readScriptObject(Amf3Input.java:778)

          at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:157)

          at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:135)

          at flex.messaging.io.amf.Amf0Input.readObjectValue(Amf0Input.java:124)

          at flex.messaging.io.amf.Amf0Input.readObjectValueOneLevelDown(Amf0Input.java:537)

          at flex.messaging.io.amf.Amf0Input.readArrayValue(Amf0Input.java:364)

          at flex.messaging.io.amf.Amf0Input.readObjectValue(Amf0Input.java:128)

          at flex.messaging.io.amf.Amf0Input.readObject(Amf0Input.java:95)

          at flex.messaging.io.amf.AmfMessageDeserializer.readObject(AmfMessageDeserializer.java:232)

          at flex.messaging.io.amf.AmfMessageDeserializer.readBody(AmfMessageDeserializer.java:206)

          at flex.messaging.io.amf.AmfMessageDeserializer.readMessage(AmfMessageDeserializer.java:126)

          at flex.messaging.endpoints.amf.SerializationFilter.invoke(SerializationFilter.java:171)

          at flex.messaging.endpoints.BaseHTTPEndpoint.service(BaseHTTPEndpoint.java:330)

          at flex.messaging.MessageBrokerServlet.service(MessageBrokerServlet.java:376)

          at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)

          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)

          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

          at com.adobe.idp.um.auth.filter.CSRFFilter.doFilter(CSRFFilter.java:86)

          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)

          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

          at com.adobe.idp.dsc.provider.impl.lcr.RemotingCookieSSOFilter.doFilter(RemotingCookieSSOFilter.java:130)

          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)

          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

          at com.adobe.idp.dsc.provider.impl.lcr.RemotingSSOFilter.doFilter(RemotingSSOFilter.java:77)

          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)

          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

          at com.adobe.idp.um.auth.filter.PortalSSOFilter.doFilter(PortalSSOFilter.java:91)

          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)

          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

          at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)

          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

          at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)

          at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)

          at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183)

          at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95)

          at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)

          at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)

          at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)

          at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

          at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)

          at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)

          at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)

          at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)

          at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)

          at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:451)

          at java.lang.Thread.run(Thread.java:662)

[Michael_Stewar2]

To help narrow it down a little further:

• Is this a completely out of the box Workspace installation?
• Which version of Workspace (ES2/2.5/ADEP/3)?
• What is different about this user in terms of permissions? Are you expecting them to see an additional start point?

[JT01]

The workspace has been recompiled in flash builder but only colors and images were changed.

ADEP ES3 - SP1

The user has the same permissions that all of our internal domain members (~2000) are assigned by giving the group "All principals in a domain xxx" the role of LiveCycle Workspace User and the same group permissions to the service that has the taskmanager endpoint is associated with it.

[A__Phillips · Accepted solution]

This is actually a bug in LiveCycle. You will need to contact support to get the quick fix for this. The issue is when a user has a process in their favorites category then the categories will not display, as soon as you remove the processes from the favorites category and then logout and log back into worksapce everything should display correctly again.

[JT01]

Thanks for the clue about it being because of the user's favorites, it allowed me to duplicate the issue on my test environment.  In my case the user wasn't a heavy LiveCycle user so the favorite they had added was no longer an active and existing process therefore we couldn't remove it from the favorites category within workspace(another bug?).

As an alternative, since I knew the problem was favorite related, I decided to try and delete the user's favorite information from the database itself.  This fixed the problem that I was unable to resolve in workspace for the reason stated above.  For anyone that might come across this and want to go this route, the table that contains the favorite information is "TB_WS_PROPERTIES", look for the "PROPERTY_NAME" column that contains the user's refprincipalid and the last portion of the property_name will contain favorites.  Each user will not have many entries and all favorites are stored in the same row so it should be relatively easy to find.

[Shashank_Kapoor]

The fix for this bug (and some others) would be available in following quick fixes:

1. 10.0.3-COR-002
2. 10.0.3-PRM-002

The fixes have also been included in the ES3 SP2