Barb,
 
We are using Web Services and have the same issue. We are on patch 17.
Because the boxes connecting via Web Services are secure and we are
updating information we have made the Web Services user an
administrator.  We will be looking at patch 19 as we would like to
remove administrator access from those accounts as soon as possible. On
a separate note, allowing a user to only connect one time has been a
pain. I do not believe this has ever worked properly.

________________________________

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Barb Wagner
Sent: Thursday, December 21, 2006 8:56 AM
To: [email protected]
Subject: Re: Webservices and 9093 errors


** 

Thanks Matt - 

I'm checking to see if patching to v19 is an option ... but am assuming
that we are in the same boat as you ... that I am not going to be able
to do the update due to production concerns. (we are looking at
restricted read to see if we can get by with that for now)

Can anyone on the list confirm that installing patch v19 resolves the
9093's with Web Services?


 Carey Matthew Black <[EMAIL PROTECTED]>




                                Carey Matthew Black
<[EMAIL PROTECTED]> 
                                Sent by: "Action Request System
discussion list(ARSList)" <[email protected]> 

                                12/21/2006 10:27 AM 
        
        Please respond to
[email protected]

 

To

[email protected]     


cc

        


Subject

Re: Webservices and 9093 errors 
                

Barb,

This might be of some interest to you:

ISS01084931:
Opened on: 11/30/2005
"
We have started exploring using Web Services for an easier way to
publish some ARS data to other groups in our organization.


We created a new 'Login Name' for this first group to use to connect
to this WS for read purposes only. I was the only one testing with
this account from my desktop using a Perl (SOAP::Lite) client. The
client was working ok for a while. Then I started getting a connection
error complaining about the user being connected from another IP
address. I am 100% sure I was the only one using the username at the
time.

The web service client reported:
"
Fault :ARERR [9093] User is currently connected from another machine
Faultcode :soapenv:Server.userException
Faultdetail :
"

This looks like a bug to me. (and in a few ways.)

1) This user was not connecting from different IP addresses.
2) The web service's calls to the ARS server should always set the bit
to "override" (if needed, and available) for the user. (I do not see a
way to set that in the AuthenticationInfo header from the client.)


For now, and in this case we were able to simply change this users
license to a Read Restricted to avoid this issue. (Again this is a
read only function.) However in the case of other users who might be
doing submit/modify events... that solution will not work and would
force them to "wait" until the ARS server forgets about their
connection all together. (Which would be an unacceptable delay for the
business processes.)

Please advise as to how we can work together to get this problem fixed.

ARS server v6.3 patch2 (Solaris 2.9)
Mid-tier v6.3 patch 14 (Development only, also Solaris 2.9, same host
as ARS server.)
"




Reported Resolved on: 11/16/06
"
Hi Matt,

Regarding your ticket ISS01084931 and resulting defect - patch 19 for
Mid-tier 6.3 is now generally available
"

I have yet to apply the patch in our prod env. We have had other
support related issues and have yet to stabilize on a patch past v6.3
patch 2 for the ARS server. :(

Maybe the above "workaround" could help you?
Maybe you can let us know if patch 19 actually solves your issue?

-- 
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)

Love, then teach
Solution = People + Process + Tools
Fast, Accurate, Cheap.... Pick two.


On 12/21/06, Barb Wagner <[EMAIL PROTECTED]> wrote:
> **
>
>
> Howdy All
>
>  Does anyone have information/experience with resolving 9093 errors
(user
> already connected) with web services?
>
>  Is there a way to force the web service logout after completing the
call?
>
>  Should a well behaved web service automatically terminate it's
session?
>
>  Just looking for some ideas/suggestions of where we can look to
resolve our
> issue ... also any thoughts on if it's not a Remedy Issue what might
be the
> culprit
>
>  System Info:
>  Remedy v6.3 patch 15 (a little behind on the patches)
>
>  Thanks in advance for any info!
>
>  Barb Wagner
>
>  __20060125_______________________This posting was
> submitted with HTML in it___

________________________________________________________________________
_______
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where
the Answers Are"

__20060125_______________________This posting was submitted with HTML in
it___ 


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

Attachment: graycol.gif
Description: graycol.gif

Attachment: ecblank.gif
Description: ecblank.gif

Reply via email to