Joe, that's a pretty good suggestion about checking the Mid-Tier server. I 
would hope remedy support would have already had him do that :)

I'm just curious though, I'm assuming he would have noticed this being an issue 
when no one could see tickets that were created in production..

Unless, I wonder if maybe the Mid-Tier is pointed to the wrong server, but the 
wrong server is pointed to the right database box. I've never messed much with 
server groups, but could it be that the mid-tier server is pointed to the wrong 
app server? Would this cause an issue? I'm not sure how the licenses are 
handled in such case, but I would assume they would be at the DB level, so 
there wouldn't be an issue like this.

Thanks,

Gary Opela, Jr., RSP
Remedy Engineer
Leader Communications, Inc.
http://www.5pointleader.com
http://www.lcibest.com
Best Product, Best People, Best PriceTM
An ISO 9001:2000 Certified, CMMI(r) Level 3 Rated Company
________________________________
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] 
On Behalf Of Joe DeSouza
Sent: Monday, August 04, 2008 1:24 PM
To: [email protected]
Subject: Re: "You do not have write license" woes

Interesting.. I would go with flusing the Mid-tier cache as well. The fact that 
your Admin users can log into the Admin tool without the warning about licenses 
is indicative that its not what I suggested earlier.

Another thing you may want to check on is, your AR Server that is configured on 
the mid-tier.. This might be a trivial question, but is it the same server or 
have you accidently configured some test unlicensed server on the mid-tier? :-) 
You might want to rule that out that your server configured is the right 
server..

Joe


----- Original Message ----
From: Darrell Reading <[EMAIL PROTECTED]>
To: [email protected]
Sent: Monday, August 4, 2008 2:05:52 PM
Subject: Re: "You do not have write license" woes

Recache that thing and see what happens.  Login as Admin, and refresh the cache.


Darrell Reading Systems Engineer
Phone 479.204.5739
[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>

Wal-Mart Stores, Inc.
805 Moberly Lane, MS-0560-68
Bentonville, AR 72716
Save Money. Live Better

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]<mailto:[email protected]>] On Behalf Of William 
Rentfrow
Sent: Monday, August 04, 2008 12:59
To: [email protected]<mailto:[email protected]>
Subject: Re: "You do not have write license" woes

Also, did I mention it works in the user tool - this is just a mid-tier error.

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]<mailto:[email protected]>] On Behalf Of Walters, 
Mark
Sent: Monday, August 04, 2008 12:40 PM
To: [email protected]<mailto:[email protected]>
Subject: Re: "You do not have write license" woes

Are you using any form of AREA plugin?

Mark

________________________________

From: Action Request System discussion list(ARSList) on behalf of
William Rentfrow
Sent: Mon 04/08/2008 17:21
To: [email protected]<mailto:[email protected]>
Subject: "You do not have write license" woes


**
I have a variety of users who are experiencing a weird error.

Occasionally the server acts as if their license has disappeared when
trying to save an Incident in ITSM 7.03.  They will be working fine one
minute and then they will get the long series of errors that says...

"You do not have application write license (ARERR 9850).  You do not
have write access to field...." followed by every field on the Incident
form.

The irritating thing is the user HAS a license.  This affects both fixed
license and floating license users.  Removing/re-adding their licenses
does not fix the problem.  The only consistent way to fix this is to
delete the user and re-create them - and even THEN it is not 100%
curable.

I have checked the following:

1.) Box has AR Server license
2.) Box has adequate Application licenses, AR User licenses, etc.
3.) User is configured properly
4.) User is not doing something stupid.

BMC Support has been unable to assist in this issue - it's been going on
for months.  Has anyone else run into this?  I don't even know how to
troubleshoot what is going on really since all of the app/workflow/api
stuff seems to be correct.

William Rentfrow, Principal Consultant
[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>
C 701-306-6157
O 952-432-0227

__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___

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

Reply via email to