I agree with Roger. I install each version of the user and admin tools in separate directories. Taking extreme care with which versions of the admin tool I use.
No harm using a newer version admin tool to look at an installed instance. It's when a modification happens that can cause issues. Like other admins on this list I have had to scramble to repair an issue caused by what was an inadvertent change that I made using a newer admin tool. Sometimes simply opening the form with the newer tool will cause changes that need to be saved. In my case I said yes to the save even though I had made no form changes. Everything seemed ok but suddenly we had issues with the web display of the form which caused a scramble to repair the damage. We can only offer advice often gained by years of experience. Many on this list have worked with version 3.x to newer. Some even go back to 1.x. It's completely up to you on what you do with our advice. Dave ------------------------- [EMAIL PROTECTED] (Wireless) ----- Original Message ----- From: Action Request System discussion list(ARSList) <[email protected]> To: [email protected] <[email protected]> Sent: Tue Apr 15 10:15:15 2008 Subject: Re: aradmin crashes ** RM, I have a feeling you are relatively new to this forum. If that is not the case please accept my apologies. However, one thing you will find out about most of us ‘old-timers’ is we try to give you the best advice we can. That being said, Susan was just trying to warn you about the dangers of using a higher version admin tool against a lower version server. There are many of us, including myself, that have paid dear penalties for doing this. Having to upgrade your server on the fly because using a higher version admin tool corrupted your data dictionary is no fun. If you have been doing this for a while then you are on of the fortunate ones in my book. As for have multiple versions of admin tools loaded at the present time I have two. What I have always done is load them in different directories. Finally, as for not wanting to know nor caring about the technical reasons as to why this all of sudden started working again, well all I can say is I am glad we are not colleagues. Continued good luck to you in your future Remedy endeavors. Regards, Roger A. Nall Manager, OSSNMS Remedy T-Mobile, USA Desk: 813-348-2556 Cell: 973-652-6723 FAX: 813-348-2565 sf49fanv AIM IM RogerNall Yahoo IM ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Remedy Maniac Sent: Tuesday, April 15, 2008 9:59 AM To: [email protected] Subject: Re: aradmin crashes why do you guys get so exited about small things?!? First rule my grandma taught me: "if you don't try you will never learn" Second rule is from Nitzsche. You know the philosopher: "everything that doesn't kill you, makes you stronger" I don't believe the admin tool could break your server. Someone else does have anything to add on this? I think it will appreciated by everyone. For your info Susan: I am using the admin tool and the user tool both in version 6.3 latest patch against a server version 6.00.01 patch 1454. This for at least one year without any issue against my server. You could even run 2 different versions of the admin tool against a lower server. At the same time ;-) Finally, Warren, just to put you at rest: there is no need to hack the Windows registry. The problem has been solved and has gone as it came. I don't know why and I actually do not care about the technical reasons, but as a matter of fact I am able to use again the admin tool version 6 without problem. rm Warren Baltimore wrote: first off. Try to do a full uninstall first. You may need to clean out your registry also. Second. My mother taught me that if you cant say something nice, don't say anything at all. lets keep the snark down.... OK? On 4/14/08, Susan Palmer <[EMAIL PROTECTED]> <mailto:[EMAIL PROTECTED]> wrote: Biggest rule I was ever taught, which was reinforced over and over and over again and has been given here over and over and over .... was do NOT use an admin tool that is not the same version as ARS. I guess it really wasn't working fine was it? I think your name is just bringing out some of the worse in me. Maybe being less manic will save yourself time in the future. Maybe I just have more of backlog and can't play around and waste time. I try to learn from the list and all the information that people are gracious enough to spend their time posting here. And as long as I'm ranting, maybe some of you need to look in the documentation before asking questions. Susan On Mon, Apr 14, 2008 at 3:15 AM, Remedy Maniac <[EMAIL PROTECTED]> <mailto:[EMAIL PROTECTED]> wrote: dear listers, we have arsystem server 6.001 patch 1454. Because of a migration plan, and in order to test, I installed aradmin Version 7.1.00 and is working fine against my 6.001 But since then any other aradmin tool (6.3 and 6.01) crashes when I try to open a form. I can still check/manage licences. Also I can read server info and so on. Everything can be opened (AL, filters, ...) It's only when I try to open a form that I get an error message such as: "The instruction at "0x04a7e833" referenced memory at "0x00000044". The memory could not be "read". Click on OK to terminate the program Click on CANCEL to debug the program" Any idea why that happens and how to get ride of it. Because now that I tested and saw the ARAdmin 7 I'd like to get back to my previous aradmin. Many thanks rm _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___
