nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Login bug: Invalid login

mattpr

My user account has stopped working in TeamSite (version 5.5.2). From the login page I receive the error message "Invalid Login"

Logging into tsadmin with another account I get the following error in Configuration>Access>Edit Roles when trying to lookup my user account:

Error: 500
Location: /iw/tsadmin/editroles
Internal Servlet Error:

com.interwoven.api.utility.IWInternalError: user lookup failed with error code 1
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:245)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:220)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:122)
at com.interwoven.api.access.IWUserRemoterImpl_Stub.lookupByName(Unknown Source)
at com.interwoven.api.access.IWUser.lookupByName(IWUser.java:58)
at com.interwoven.api.access.IWUser.lookupByName(IWUser.java:77)
at com.interwoven.teamsite.admin.EditRolesServlet.doGet(EditRolesServlet.java:104)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at com.interwoven.framework.base.FrameworkServlet.service(FrameworkServlet.java:66)
at com.interwoven.framework.auth.AuthServlet.service(AuthServlet.java:96)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:405)
at org.apache.tomcat.core.Handler.service(Handler.java:287)
at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)
at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:797)
at org.apache.tomcat.core.ContextManager.service(ContextManager.java:743)
at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:213)
at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:423)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501)
at java.lang.Thread.run(Thread.java:484)

I have looked through all the logs and cannot find anything that points to the problem. Has anyone else ever seen this bug?

Find more posts tagged with

Comments

brandon1

Have you looked at the physical role file and see what you uid looks like? It is possible that the file itself is hosed.

Current Project: TS 6.1
Environment: Solaris

Migrateduser

brandon's got a good point -- also, as which role are you attempting to log in? Have you successfully logged in with the same role but a different user ID? ... different role but same user ID?

Dave

Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP1 on W2K
(3) TS 5.5.2 SP2 on Win2K

mattpr

Thanks for your quick replies. Yes, I have looked at the physical role (*.uid) files. I am running TS5.5.2 on Win2K. My account is named as mydomain\myaccount and I am an admin role. I have successfullly logged in as another user it is only my account that appears to be hosed. But the physical file seems fine in a text editor. I guess I could try to look at it in a hex editor in case there are some hidden control characters in the file.

I also wonder whether this bug is addressed in a service pack. I should probably check that I am running SP2.

Edited by mattpr on 11/04/04 09:44 AM (server time).

mattpr

For anyone in the same position. This is how I resolved it. Using the command line iwuser:

iwuser mydomain\myusername

returns a result of no such user in the database. This is the first I have heard of any database, but it makes sense that the information in the uid files is then compiled into a dictionary of some sort for an easy lookup.

iwuser -c mydomain\myusername

This command re-created my user account. That was enough. The uid permissions were picked up from the uid file.

Edited by mattpr on 11/09/04 12:41 PM (server time).

Migrateduser

For those wanting fuller information, check out KB article #52405

Also, similar symptomology on windows is sometimes the result of a caching problem (see KB 49604). For what it's worth, the cache seems to update much more quickly with 6.1. At least that's been my experience.