If the IP-Name parameters were not properly configured when developing workflow (i.e., the name you used to log into the server did not match either Server-Name or an IP-Name entry in ar.conf) the workflow will contain static references to the server name used to log in when developing the workflow. This can apply to set fields, push fields, table fields, menus, etc. and is stored in your workflow definitions. The easiest way to explain to find them is to export a def and search the def for all the possible variants of the server name. That will tell you what workflow you need to update.
Axton Grams On Mon, Apr 4, 2011 at 6:44 PM, Raj <[email protected]> wrote: > Hello All, > I am performing disaster recovery testing of our remedy servers. > We have 2 servers, server 2 is a disaster recovery server and server > 1 is the main production server. > database 2 is a clone of database 1. I have adjusted server name > references on server 2 in the ar.conf, armonitor.conf, and arsystem > files. Server 2 is pointed to its proper database 2. > However, when I start server 2 and try to do a search or open any > existing record, it is pulling up info from server1 and at the end it > throws out an (ARERR 90) and mentions Server 1' name. > > Can anyone point out what server name reference(s) I am still > missing? Is there another file, or some data reference in the > database? > Thanks, > Raj > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
