Disable-Admin-Ops is set to F I set the port using: set ARTCPPORT [portid]
It's not a server group.... On Thu, Feb 12, 2015 at 10:04 AM, Grooms, Frederick W < frederick.w.gro...@xo.com> wrote: > Are you in a server group or have the config entry Disable-Admin-Ops > turned on? > > Are you using a specific port for your server? If so set the ARTCPPORT > environment variable first > export ARTCPPORT=123456 > > Fred > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] On Behalf Of Warren R. Baltimore II > Sent: Thursday, February 12, 2015 8:41 AM > To: arslist@ARSLIST.ORG > Subject: Re: USER_CACHE Problems > > ** > I did bounce the Remedy system after the problem started. It didn't work > though.... I've been trying the following command: > > # ./arreload -a "[userid]" -p "[password]" -u "User" -s "[servername]" > -f -d > > I get the following: > > Action Request System Reload Cache Manager Version 6.03.00 patch 016 > Remedy, a BMC Software company. > Copyright (c) 1991 - 2005 BMC Software, Inc. > All rights reserved. > Summary of command line arguments: > User form : User > Group form : > Admin user : [userid] > Update server: [servername] > Flush items from CURRENT server only > Verifying Admin access to 'source' server -- [servername] > FAILED! > Message not in catalog; Message number = 329 (ARERR 329) > [servername] > > ARERR 329 : > Invalid password or authentication string for an existing user > The password you have specified for the user name is not recognized. The > problem can be > either with the password or with the authentication string (if using NT > authentication, the > authentication string is the NT domain) or both. Enter the password > defined for this user > name to access the system as that user. > > I've used both Demo with a Fixed license and Admin privs. as well as my > own user id that also has admin privs. Am I missing something? > > > -----Original Message----- > On Thu, Feb 12, 2015 at 9:26 AM, Grooms, Frederick W wrote: > The logged in status for a user is only in memory (not stored in the > database) so have you restarted the AR System? > > When using the arreload utility make sure to turn off the max number of > records returned limit (if you have one set on the server) before running > or you will only get that number of users loaded into the user_cache > > Fred > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] On Behalf Of Misi Mladoniczky > Sent: Thursday, February 12, 2015 7:58 AM > To: arslist@ARSLIST.ORG > Subject: Re: USER_CACHE Problems > > Hi, > > Have you tried the arreload-program? > arreload -u User -f -a adminuser -p adminpassword > > The -f is supposed to flush the cache before reloading it. > > Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011) > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] On Behalf Of Warren R. Baltimore II > Sent: Thursday, February 12, 2015 8:06 AM > To: arslist@ARSLIST.ORG > Subject: Re: USER_CACHE Problems > > ** > Gave it a shot....no joy in mudville I'm afraid.... Thanks for the idea > though! > > -----Original Message----- > On Thu, Feb 12, 2015 at 8:37 AM, Karthik wrote: > ** > Deleting and recreating their user record works? > > - Karthik > > -----Original Message----- > On 12 February 2015 at 18:29, Warren R. Baltimore II wrote: > ** > ARS 6.3 > Oracle 10x > Sun OS 5.1 > > A little help please! > > My legacy server is showing an issue that I have not dealt with before. > > A couple of days, my database started showing some problems related to > tablespace. This caused a bunch of weird issues. The tablespace issue has > been resolved. A couple of my users had closed their clients during that > time and when they came back received the error message that they were > still logged on and would they like the other session closed. They would > answer in the affirmative, but when they would then log back on, they would > get the same message. I then tried to kick them off from the admin tool, > but they would still get the message. > > I then triggered (I think) a re-cache by adding a display only checkbox > and then doing a modify all against all users with that checkbox checked. > I did this based on kbase articles that talked about this type of issue. > However I still have a couple of users who are getting this message. > > User logs don't show a need for them to be released, in fact they just > show them logging in as normal. > > They are able to work by just closing (using the x to close the window). > None the less, it is very annoying! > > Any ideas? > > Thanks! > > -- > Warren R. Baltimore II > Remedy Developer > 410-533-5367 > > > > > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > > > > -- > Warren R. Baltimore II > Remedy Developer > 410-533-5367 > _ARSlist: "Where the Answers Are" and have been for 20 years_ > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > -- Warren R. Baltimore II Remedy Developer 410-533-5367 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
