it is not our current prod.  It is the environment that is going to be
prod.  Dev Cache Mode is checked.  The fields I added where not there.  I
closed out of the admin tool and came back in.

On Mon, Jul 12, 2010 at 1:40 PM, jham36 <jha...@gmail.com> wrote:

> Is this a production environment?  I see this error if I make a change
> to Prod sometimes.  In our dev environment we have Dev Cache Mode
> turned on.
> What is probably happening is that the change is submitted to the
> database and then there is a timeout in the admin tool while waiting
> for the server to re cache everything.
> If you close your workflow and re-open it after this error, you should
> see that it was updated properly.
>
> James
>
> On Jul 12, 1:23 pm, Kevin Begosh <kbeg...@gmail.com> wrote:
> > okay so I remember seeing this before but I cannot remember what I did to
> > solve the issue.  I am am trying to change workflow objects, forms,
> filters
> > etc... via the admin tool and I keep getting the ARERR 92 timeout during
> > database update .......
> >
> > The environment I am in is a Server group configuration with 3 AR Servers
> > sharing the same DB.
> >
> > Has anyone else out there had this issue?
> >
> > Windows 2003 server, SQL 2005 DB.
> >
> > Do you have to take them out of server groups and then make the changes
> and
> > then put them back, something like that?
> >
> > --
> > Kevin Begosh
> >
> >
> ___________________________________________________________________________
> ____
> > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org
> > attend wwrug10www.wwrug.comARSlist: "Where the Answers Are"
>
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
>



-- 
Kevin Begosh

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

Reply via email to