Since you also say you do not know what may have gone on here, there is a possibility there might be integartions or non-ARSystem tables in the ARSystem tablespace or other dependents. If I were you I would spend some time studying all such possibilities before just blowing away the staging and the dev environments and attempting to rebuild them.. You would require such information anyway, as it is a good idea to clone these environments to production maintaining the same installation directory structure etc as a lot of the out of the box applications store directory install paths within the application data For eg the EIE, help files, etc.. All these would fail to work if the paths are different and if the database is restored from prod to dev or staging.. Joe
----- Original Message ---- From: LJ Longwing <[EMAIL PROTECTED]> To: [email protected] Sent: Tuesday, August 12, 2008 3:44:13 PM Subject: Re: Rebuilding Remedy 6.3 ** Well....Remedy is licensed in the windows world by MAC of the NIC, and the lic file (in 6.3) is stored by default in C:\Program Files\Common Files\AR System\Licenses\<servername>\arsystem.lic, this shouldn't be touched if you are just reinstalling Remedy....if you are rebuilding the entire box...you'll want a copy of that file...it should contain all of the licenses currently applied to the server, including help desk. ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Masha Bench Sent: Tuesday, August 12, 2008 1:28 PM To: [email protected] Subject: Rebuilding Remedy 6.3 ** Greeting Listers, I come to you with several questions and concerns. Here is my story to start with. I inherited Remedy (ARS + HelpDesk) about 6 months ago (before I was just a user on the system). People that set it up couple of years ago are long gone. Since its original creators, this app has been passed around A LOT! Right now we have prod, stage and dev environments working, from which only prod is running without too many hiccups. Stage was a play box for third party software developers/integrators and is no longer allowing any users to sign in. Dev is still running but needs to be restarted daily if you want to log in (ARS Service hangs on restart). Here come the questions and concerns: I am thinking very hard right now about rebuilding both stage and dev environments. On one hand I could try to figure out what is going on with the logging in failures on dev, but then I am not sure what else is tweaked to death in there… Stage. The only other option that I see aside from rebuilding stage is playing with configuration files and see if that makes any difference, but I have no idea what was done to it before during third party integration process. So (keep in mind these are stage and dev) If I do decide to rebuild stage completely what about the licenses? Do I just send the license file to BMC and wait or can I back it up and then restore it to the new system? If I just back it up the new rebuild will have to happen on the old machine (which is OK) because of the Host ID, right? What do I do with HelpDesk licenses? Any help is appreciated. Masha _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
