I am yet to hear of any users complaining of ARERR 333 but this is what I see 
in in catalina.out log file in Tomcat.

ERROR (333): You have no access to field; 1
        at com.bmc.arsys.api.ProxyJRpcBase.verifyStatus(Unknown Source)
        at com.bmc.arsys.api.ProxyJRpcBase.verifyStatus(Unknown Source)
        at com.bmc.arsys.api.ProxyJRpcBase.a(Unknown Source)
        at com.bmc.arsys.api.ProxyJRpcBase.arCall(Unknown Source)
        at com.bmc.arsys.api.ProxyJRpc.ARGetListEntryWithFields(Unknown Source)
        at com.bmc.arsys.api.ARServerUser.getListEntryObjects(Unknown Source)
        at com.remedy.arsys.session.Login.getForcedChangePasswordFlag(Unknown 
Source)
        at com.remedy.arsys.session.Login.isPasswordChangeRequired(Unknown 
Source)
        at com.remedy.arsys.stubs.SessionData.<init>(Unknown Source)
        at com.remedy.arsys.stubs.SessionData.<init>(Unknown Source)
        at com.remedy.arsys.session.Login.initSessions(Unknown Source)
        at com.remedy.arsys.session.Login.establishSession(Unknown Source)
        at com.remedy.arsys.session.Login.establishSession(Unknown Source)
        at com.remedy.arsys.stubs.GoatServlet.postInternal(Unknown Source)
        at com.remedy.arsys.stubs.GoatHttpServlet.doGet(Unknown Source)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
        at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
        at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
        at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
        at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
        at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
        at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
        at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
        at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
        at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874)
        at 
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
        at 
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
        at 
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
        at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
        at java.lang.Thread.run(Thread.java:595)

I know that field 1 is the Request ID, and that some user may be trying to 
access a record with insufficient privileges, ,but something tells me that this 
is happening at application level. And not at the user level i.e. the user is 
performing some legal action that is resulting in this error because of 
application design.. Is anyone using ITSP 4 and has seen this error happen in 
their logs and were able to pinpoint the source of it?

Joe



_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
      

Reply via email to