Topic Options
Rate This Topic
#25959 - 04/03/00 12:09 PM "...has been updated by another user..." error in DSO
remedyuser Offline
Stealth Member

Registered: 06/12/01
Posts: 142
Sorry for the incomplete mail a few minutes ago. Pressed the wrong key.

In a DSO environment, I am getting "ARWARN 1203" (record has been updated by
another user since your retrieved it) quite consistently, without any
reason.

Story:
I am trying to set up 3 servers with DSO. On a form, I am doing independent
copy of records created on any server to the two others. Thereafter, changes
on the record on any server is propagated to other two servers by filters.

All is fine, except that I am getting "ARWARNING 1203" frequently, saying
"record has been updated by another user since you retrieved it" when I
should not. Here is an example:
If I submit a record in server A, it transfers to B, C fine. I can update A
and copies on B, C are updated. However, if I try to update copy on C, I get
the "has been updated..." message, even after I refresh the record, click on
another record in results pane and click back on that entry. If I say "yes"
to override the update, it saves the new changes on C and updates A,B fine.
From now on, I can modify this record on C as much as I want without the
warning. However, if I then try to update the entry on A or B, no matter how
many times I refresh the record and try to modify them, they come back with
the "has been updated" warning.

Strange?! It's almost as if DSO transfer sets change flag on DB on the
receiving DB which does not go away even if you get fresh copy of the
record.

There is more to this saga, but does anybody have any insight/experience to
share with me?

All my workflow related to DSO on this form are "symmetrical" in all the
servers. There is no workflow (escalation etc) except the filters to do the
DSO transfer.

I am testing using one Remedy User and wonder if Rememdy User is getting
confused with three records on 3 servers with the same ID.

TIA.
-Rabindra Tripathi
GE Capital IT Solutions
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com


Unsubscribe to: Text is: unsubscribe arslist


Top
#25960 - 04/03/00 12:34 PM Re: "...has been updated by another user..." error in DSO [Re: pramirez]
brian_arnold Offline
Stealth Member

Registered: 06/12/01
Posts: 6

Check the date and time across all servers.

This can occur becasuse remedy checks the date and time in the
"Last-Modified-date", if that date and time istamp copied from other servers is
greater than $TIMESTAMP$ of current server then you get this message.

Regards

Brian





Rabindra Tripathi on 03/04/2000 17:09:21

Please respond to "Action Request System discussion list(ARSList)"


To: ARSLIST@LISTSERV.VISTAIT.COM
cc: (bcc: Brian Arnold/Tertio)
Subject: "...has been updated by another user..." error in DSO




List,
Sorry for the incomplete mail a few minutes ago. Pressed the wrong key.

In a DSO environment, I am getting "ARWARN 1203" (record has been updated by
another user since your retrieved it) quite consistently, without any
reason.

Story:
I am trying to set up 3 servers with DSO. On a form, I am doing independent
copy of records created on any server to the two others. Thereafter, changes
on the record on any server is propagated to other two servers by filters.

All is fine, except that I am getting "ARWARNING 1203" frequently, saying
"record has been updated by another user since you retrieved it" when I
should not. Here is an example:
If I submit a record in server A, it transfers to B, C fine. I can update A
and copies on B, C are updated. However, if I try to update copy on C, I get
the "has been updated..." message, even after I refresh the record, click on
another record in results pane and click back on that entry. If I say "yes"
to override the update, it saves the new changes on C and updates A,B fine.
From now on, I can modify this record on C as much as I want without the
warning. However, if I then try to update the entry on A or B, no matter how
many times I refresh the record and try to modify them, they come back with
the "has been updated" warning.

Strange?! It's almost as if DSO transfer sets change flag on DB on the
receiving DB which does not go away even if you get fresh copy of the
record.

There is more to this saga, but does anybody have any insight/experience to
share with me?

All my workflow related to DSO on this form are "symmetrical" in all the
servers. There is no workflow (escalation etc) except the filters to do the
DSO transfer.

I am testing using one Remedy User and wonder if Rememdy User is getting
confused with three records on 3 servers with the same ID.

TIA.
-Rabindra Tripathi
GE Capital IT Solutions
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com


Unsubscribe to: Text is: unsubscribe arslist


Unsubscribe to: Text is: unsubscribe arslist


Top
#25961 - 04/04/00 02:35 PM Re: "...has been updated by another user..." error in DSO [Re: pramirez]
remedyuser Offline
Stealth Member

Registered: 06/12/01
Posts: 142
problem, but I think that's because although the three machines are very
close in their time, they are not exactly in sync.

Playing around, I discovered something I did not know. I realized that if
you tell it to overwrite another user's update, the only fields it will
overwrite are the ones you changed. If there was a field that the other user
changed which you did not modify, it will not put back the unmodified field
into the database to overwrite the other use's change. That is, by
"overwrite", Remedy means overwriting the fields you have changed, not
really overwriting all fields in the database with values on your screen.
This is good. It may be behaving this way because the API to do the update
(SetEntry) will only pass the fields you have changed, not all the fields
you have on your screen.

Anyway, thanks again.
-Rabindra

>From: Brian Arnold
>Reply-To: "Action Request System discussion list(ARSList)"
>
>To: ARSLIST@LISTSERV.VISTAIT.COM
>Subject: Re: "...has been updated by another user..." error in DSO
>Date: Mon, 3 Apr 2000 17:34:53 +0100
>
>Rabindra,
>
>Check the date and time across all servers.
>
> This can occur becasuse remedy checks the date and time in the
>"Last-Modified-date", if that date and time istamp copied from other
>servers is
>greater than $TIMESTAMP$ of current server then you get this message.
>
>Regards
>
>Brian
>
>
>
>
>
>Rabindra Tripathi on 03/04/2000 17:09:21
>
>Please respond to "Action Request System discussion list(ARSList)"
>
>
>To: ARSLIST@LISTSERV.VISTAIT.COM
>cc: (bcc: Brian Arnold/Tertio)
>Subject: "...has been updated by another user..." error in DSO
>
>
>
>
>List,
>Sorry for the incomplete mail a few minutes ago. Pressed the wrong key.
>
>In a DSO environment, I am getting "ARWARN 1203" (record has been updated
>by
>another user since your retrieved it) quite consistently, without any
>reason.
>
>Story:
>I am trying to set up 3 servers with DSO. On a form, I am doing independent
>copy of records created on any server to the two others. Thereafter,
>changes
>on the record on any server is propagated to other two servers by filters.
>
>All is fine, except that I am getting "ARWARNING 1203" frequently, saying
>"record has been updated by another user since you retrieved it" when I
>should not. Here is an example:
>If I submit a record in server A, it transfers to B, C fine. I can update A
>and copies on B, C are updated. However, if I try to update copy on C, I
>get
>the "has been updated..." message, even after I refresh the record, click
>on
>another record in results pane and click back on that entry. If I say "yes"
>to override the update, it saves the new changes on C and updates A,B fine.
>From now on, I can modify this record on C as much as I want without the
>warning. However, if I then try to update the entry on A or B, no matter
>how
>many times I refresh the record and try to modify them, they come back with
>the "has been updated" warning.
>
>Strange?! It's almost as if DSO transfer sets change flag on DB on the
>receiving DB which does not go away even if you get fresh copy of the
>record.
>
>There is more to this saga, but does anybody have any insight/experience to
>share with me?
>
>All my workflow related to DSO on this form are "symmetrical" in all the
>servers. There is no workflow (escalation etc) except the filters to do the
>DSO transfer.
>
>I am testing using one Remedy User and wonder if Rememdy User is getting
>confused with three records on 3 servers with the same ID.
>
>TIA.
>-Rabindra Tripathi
>GE Capital IT Solutions
>______________________________________________________
>Get Your Private, Free Email at http://www.hotmail.com
>
>
>Unsubscribe to: Text is: unsubscribe arslist
>
>
>Unsubscribe to: Text is: unsubscribe arslist

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com


Unsubscribe to: Text is: unsubscribe arslist


Top


Moderator:  Matt Reinfeldt