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; } } }

After installation, cannot login

AlbertChan1

Hi,

I'm now setting up WorkSite MP into my PC (Windows Server 2003 Enterprise)
I've installed "WorkSite MP Server" and "WorkSite MP Web Components", configured the system as whatever said in Installation Guide (e.g. create database, library, trustee... etc)
But when I try login the site (http://localhost:8080/worksitemp/login), it shows error in browser:

The server is temporarily busy serving other requests.

and has a Java runtime error in Tomcat console:

com.imanage.cms.exceptions.cmsconnection.CmsConnectionPoolNotAvailableException: CmsConnection pool is not available
...

What things i've missed?

Albert

Find more posts tagged with

Comments

rajit

Albert,

Please check if all the necessary services are started in the config manager. At the least the CMS service for the
library should be running, if not other services.

Rajit

JTNeville

There's too many things to check to list here, but here are the most common issues:

1) Different versions of server and webapp being run. All version of the MP suite need to be the same revision (i.e. 4.1, not 4.0 and 4.1)
2a) DNS not configured properly for multiserver environment
2b) Firewall cutting off traffic between CMS/SQL box and Webapp/Tomcat
2c) CMS library not added in config tool (localhost:8080/worksitemp/config.jsp)
3) IMPM not started.

Need more info on how you set it up to take it any further.

AlbertChan1

Hi all,

Thanks for your kindly replies.
I've fulfilled most of your suggestions (all servers started, webapp & server run in same PC)
But for 2c),
in Deployment Manager > CMS Configuration, i've input:

CMS Cluster Name = (my cluster name, say "PC001")
Library Name = (my CMS library name, say "worksitemp")
Proxy User Login Id/Password = (left blank)
Cache Manager Login Id/Password = (left blank)

- are these settings ok?
- need to change other settings in the Config site?
- need to run "Commit", "Deploy" or "Rebuild" after changing any settings?
- when login, just left blank in "Domain" ?

Thanks,
Albert

JTNeville

If you haven't reset the password to blank (in configuration manager), by default they are the names themselves:

in example:

Proxyuser = proxyuser
CacheManager = cachemanager

All small, no spaces.

For the longest time I assumed they were case sensitive but at a recent class Brian said they weren't. Limited testing seems to indicate they are indeed not case sensitive, but I haven't spend the time to do a rigorous test of all system passwords to verify 100%.

Dada

Hi,
I am facing the same problem after installing WorkSite MP server and WorkSite MP Web components on same server (Windows 2000). I successfully created the library and configured the library as per the documentation. I checked all the servers are running. Whenever I am trying to log in worksitemp using http://<hostip>:<port>/worksitemp I am getting "A WorkSite MP resource required for the requested item is currently unavailable."
Following is the snippet from the log.

2005-02-18 14:46:12,828 INFO [http8080-Processor1] com.imanage.workteam.appservices.auth.LoginServlet - Received POST request from Host: ctp-vi0206, Url: /worksitemp/login, ContentLength: 59
2005-02-18 14:46:12,828 INFO [http8080-Processor1] com.imanage.workteam.appservices.auth.LoginServlet - datasource:null, operation:null, objectId:null, sessionId:531FD2C886CFBE9D633886FC3F81A194
2005-02-18 14:46:12,875 INFO [http8080-Processor1] com.imanage.workteam.exceptions.InitFailedException - A WorkSite MP resource required for the requested item is currently unavailable.
A WorkSite MP resource required for the requested item is currently unavailable.
Context: Initialization
Details: Initialization of an application service (like library connection pool or cache) or subsystem has failed.
Action: Please try again later. If this problem persists, contact your support staff.
com.imanage.workteam.exceptions.InitFailedException(com.imanage.cms.exceptions.cmsconnection.CmsConnectionPoolNotAvailableException:CmsConnection pool is not available)
Underlying StackTrace:
com.imanage.cms.exceptions.cmsconnection.CmsConnectionPoolNotAvailableException: CmsConnection pool is not available
at com.imanage.cms.fc.cmsconnection.CmsConnectionPool.getConnectionOnce(CmsConnectionPool.java:856)
at com.imanage.cms.fc.cmsconnection.CmsConnectionPool.getConnectionViaVirtualConnection(CmsConnectionPool.java:792)
at com.imanage.cms.fc.cmsconnection.UserConnection.getConnectionImpl(UserConnection.java:45)
at com.imanage.cms.fc.cmsconnection.CmsConnectionVirtual.getConnection(CmsConnectionVirtual.java:375)
at com.imanage.cms.fc.cmsconnection.CmsConnectionVirtual.validateConnection(CmsConnectionVirtual.java:208)
at com.imanage.cms.fc.cmsconnection.UserConnection.<init>(UserConnection.java:36)
at com.imanage.cms.fc.cmsconnection.CmsConnectionPool.getConnection(CmsConnectionPool.java:743)
at com.imanage.cms.t2.jom.impl.PoolManager.getLoggedOnLibraryFor(PoolManager.java:212)
at com.imanage.cms.t2.jom.impl.DefaultReconnector.getLibraryByName(DefaultReconnector.java:28)
at com.imanage.cms.t2.jom.impl.EnterpriseSessionImpl.getLoggedOnTrustee(EnterpriseSessionImpl.java:137)
at com.imanage.cms.t2.jom.impl.SessionImpl.logonImpl(SessionImpl.java:86)
at com.imanage.cms.t2.jom.impl.EnterpriseSessionImpl.logon(EnterpriseSessionImpl.java:23)
at com.imanage.cms.api.workteam.impl.EnterpriseSessionImpl.logon(EnterpriseSessionImpl.java:38)
at com.imanage.workteam.appservices.session.CmsEnterpriseSessionProxy.openCmsSession(CmsEnterpriseSessionProxy.java:81)
at com.imanage.workteam.appservices.session.CmsSessionProxy.connect(CmsSessionProxy.java:101)
at com.imanage.workteam.appservices.session.AppSession.connect(AppSession.java:139)
at com.imanage.workteam.appservices.session.AppSessionManager.createSession(AppSessionManager.java:504)
at com.imanage.workteam.appservices.session.AppSessionManager.createSession(AppSessionManager.java:439)
at com.imanage.workteam.BaseServlet.createSession(BaseServlet.java:289)
at com.imanage.workteam.appservices.auth.LoginServlet.tryLogin(LoginServlet.java:222)
at com.imanage.workteam.appservices.auth.LoginServlet.processLogin(LoginServlet.java:135)
at com.imanage.workteam.appservices.auth.LoginServlet.serviceBody(LoginServlet.java:86)
at com.imanage.workteam.AbstractBaseServlet.service(AbstractBaseServlet.java:181)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:432)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:356)
at com.imanage.workteam.AbstractBaseServlet.doForward(AbstractBaseServlet.java:571)
at com.imanage.workteam.appservices.auth.LoginServlet.processStaleSession(LoginServlet.java:159)
at com.imanage.workteam.appservices.auth.LoginServlet.processLogin(LoginServlet.java:140)
at com.imanage.workteam.appservices.auth.LoginServlet.serviceBody(LoginServlet.java:86)
at com.imanage.workteam.AbstractBaseServlet.service(AbstractBaseServlet.java:181)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2422)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:163)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:199)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:700)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:584)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
at java.lang.Thread.run(Thread.java:536)

Thanks
Tushar

JTNeville

CMS connection issues are almost always one of the above listed items. Connectivity between the webapp and IMPM is critical, so the passwords, dns names and library names must all be synced and entered appropriately in both applications, even when on the same computer. The MP installation PDF has a step by step process you can follow. With all the possible 'gotchas' it is hard to give any better advice without having access to your installation.

Dada

Hi,

The connection problem is solved. Now I am getting "User must be Context-Switched".
Could anyone please tell me if I am missing some configuration?

Thanks & Regards
Tushar

Dada

The snippet from the log file is as follows.

Thu Feb 24 11:35:43.812: INFO [RpcConnectionListener-default] RpcManagerThread.run:Accepted connection from socket, name=ctp-vi0206, address=172.18.34.223:4749
Thu Feb 24 11:35:43.812: INFO [Session-18539] RpcSession: Starting Session
Thu Feb 24 11:35:43.812: INFO [Session-18539] Processing <msg=CmsSessionInitialize><from=ctp-vi0206[172.18.34.223:4749]><lib=><ctxSwitchEnabled=false>
Thu Feb 24 11:35:43.812: INFO [Session-18539] Finished processing <msg=CmsSessionInitialize><resultCode=0>
Thu Feb 24 11:35:43.812: INFO [Session-18539] Processing <msg=CmsGetChallenge><from=ctp-vi0206[172.18.34.223:4749]><lib=portald><ctxSwitchEnabled=false>
Thu Feb 24 11:35:43.812: INFO [Session-18539] Finished processing <msg=CmsGetChallenge><resultCode=0>
Thu Feb 24 11:35:43.812: INFO [Session-18539] Processing <msg=CmsSessionAuthentication><from=ctp-vi0206[172.18.34.223:4749]><lib=portald><ctxSwitchEnabled=false>
Thu Feb 24 11:35:43.859: INFO [Session-18539] Finished processing <msg=CmsSessionAuthentication><resultCode=0>
Thu Feb 24 11:35:43.859: INFO [Session-18530] Processing <msg=CmsPing><from=ctp-vi0206[172.18.34.223:4740]><lib=><currentTrustee=202><ctxSwitchEnabled=false>
Thu Feb 24 11:35:43.859: INFO [Session-18530] Finished processing <msg=CmsPing><resultCode=0>
Thu Feb 24 11:35:43.859: INFO [Session-18530] Processing <msg=CmsGetLibraryList><from=ctp-vi0206[172.18.34.223:4740]><lib=><currentTrustee=202><ctxSwitchEnabled=false>
Thu Feb 24 11:35:43.859: INFO [Session-18530] Finished processing <msg=CmsGetLibraryList><resultCode=0>
Thu Feb 24 11:35:43.859: INFO [Session-18530] Processing <msg=CmsGetSessionTrusteeSids><from=ctp-vi0206[172.18.34.223:4740]><lib=><currentTrustee=202><ctxSwitchEnabled=false>
Thu Feb 24 11:35:43.859: INFO [Session-18530] message threw exception
com.imanage.cms.exceptions.base.SystemException: User must be Context-Switched
at com.imanage.cms.t1.service.cmsbeans.CmsGetSessionTrusteeSidsBean.execute(CmsGetSessionTrusteeSidsBean.java:66)
at com.imanage.cms.t1.service.CmsServiceBean.processMessage(CmsServiceBean.java:157)
at com.imanage.cms.t1.service.CmsMsgProcessor.processMessage(CmsMsgProcessor.java:165)
at com.imanage.cms.t1.service.CmsMsgProcessor.processMessage(CmsMsgProcessor.java:139)
at com.imanage.cms.t1.service.CmsServiceBeanContainer.processMessage(CmsServiceBeanContainer.java:40)
at com.imanage.cms.t1.net.rpc.RpcSession.processMessage(RpcSession.java:546)
at com.imanage.cms.t1.net.rpc.RpcSession$RpcSessionThread.run(RpcSession.java:460)
at com.imanage.cms.fc.base.ImThread.callRun(ImThread.java:808)
at com.imanage.cms.fc.base.ImThread.executeOneLoop(ImThread.java:931)
at com.imanage.cms.fc.thread.ThreadHWRunner.run(ThreadHWRunner.java:141)
at java.lang.Thread.run(Unknown Source)

Please help me out as I could not log into the system.

Thanks
Tushar

JTNeville

You need to call your support engineer in this one I'm guessing. I've never seen it.

Migrateduser

Hello,
I have exactly same problem as Albert has.
I set up WorkSite MP Server and Webcomponent 4.1 at same machine without domain.
I configured CMS service and Library succefully.
In web configuration, I entered cluster name and library name corractly, then clicked "save" button.
I verified impm service is running along with CMS service at configuration manager.
I tried to log in at http://localhost:8080/worksitemp with ID:administrator, PW:<local admin password>, and Domain:<blank> or <local computer name>.
Every time I try to log on, I get exacly same error message as Albert has above.
Would you please help me?
Did Albert solve this problem??

Migrateduser

Can you please take a look at WOM logs at the client side? they are located at <worksitemp-webapp-context-dir>/WEB-INF/logs. These logs will have more information on what is failing. Also check server logs located at <mpserver-install-dir>/logs/<hostname>/*.log, the most important one for connection issues is cms.ImCmsSvc.<hostname>.log. The logs are a bit cryptic, but the exceptions will most of the times will lead to the correct cause. I will try to help if you can post the logs.

-bijoy

Migrateduser

I found this kind of error mainly can be solved by checking the logs under tomcat/web-inf/logs and mp_server logs.
eg. yesterday I face same problem "connection pool not available", finally I find the problem in tomcat/web-inf/logs
thanks the upper