Thanks for the input. I think 6.3 has a problem with the portmapper. There was no portmap.exe with the install.
Haven't got a clue as to what the issue is. I also notice that the installer wanted to put the installation in a slightly different folder than the 5.1.2 install. It put another level there, the server name, then all the files. In effect you still have 5.1.2 installed but yet not installed because the db has been updated. I can connect to the db via sql tool, just cannot get AR System to start. Not giving up yet ... if I do a restore I probably won't get another date for 6 months! Thanks,, Susan On 4/14/07, GRogers <[EMAIL PROTECTED]> wrote:
** Susan, I posted this a couple of weeks ago. The install was for SQL 2000 to 2005, but I thought I would post it anyway because of the correlation to the portmapper issue that you have encountered (step 9 specific). As for why 7 won't start, I didn't experience those issues going from 6.3 P21 to 7.01P1: Eric, Is SQL 2005 supported for 6.03? I didn't think it was. However, I just went through several upgrades with a customer from 5.1.2 to 6.03 on several boxes, but this was under SQL 2000. But, I did do the same steps listed below when I took them from 6.0.3 to 7.0.1 with SQL 2005. I'm not sure of the order that everything was installed in your environment, but the procedure listed below has worked successfully for me, time and time again. Based on not knowing the steps that you have taken to get to this point, this would be my recommendation to follow if the ARSystem DB will even run on SQL 2005. 1) Start with SQL 2000 on the Dev Box. 2) Restore a good 5.1.2 2000 backup to it - Run the scripts "tfserver" etc. to remove server references, the command to change ownership of all forms / views to dbo, and then change the dbowner to ARAdmin. 3) Run the 6.0.3 (NO PATCH) Server install against the SQL 2000 DB. 4) Validate successful implementation by logging into the User Tool. 5) Backup ARSystem DB. 6) Uninstall SQL 2000 7) Install SQL 2005 8) Change dbowner back to ARAdmin - You might have to add that login first in the SQL 2005 Manager (I did). 9) Make sure you reboot your App Server before continuing - (There is a problem with the installer that I have been able to repeat. If you keep running the installers, something gets jacked up with the Portmap.exe. It is almost as though too many registry entries get created (not uninstalled / re-installed). If I reboot after running the installer twice, I will get an Explorer message upon reboot about the Portmap.exe dying. This will cause the Server to go out to lunch because it can't find the correct port mapper entry to use. Just FYI! - I have been able to reproduce this problem numerous times). 10) Run the 6.0.3 Patch 21 Server Install against the SQL 2005 DB 11) Validate successful implementation by logging into the User Tool. Thanks, G. Rogers ----- Original Message ----- *From:* Susan Palmer <[EMAIL PROTECTED]> *Newsgroups:* public.remedy.arsystem.general *To:* [EMAIL PROTECTED] *Sent:* Saturday, April 14, 2007 3:20 PM *Subject:* Re: Upgrade to v6.3 and portmapper will not work - prod server down ** Well ... went ahead and did the v7.0.1P1 install and it cured the portmapper problem. Now the ARS server won't start. There were no errors in the install log until the very end when it was trying to start the service. I find it somewhat humorous that it asks you to do something you cannot to correct the problem, import the samples ... lol The entries from the install log: 17:00:55 Setup created the AR System License File directory: C:\Program Files\Common Files\AR System\Licenses\remsrv 17:00:55 Registry Key successfully set: 17:00:55 Key: Software\Remedy\ARServer\remsrv 17:00:55 Name: ArMonitorConfigFile 17:00:55 Value: C:\Program Files\AR System\remsrv\conf\armonitor.cfg 17:00:55 Installing services... 17:00:55 ****->[ShowMsg]: Installing services... 17:00:59 Portmapper service installed successfully. 17:00:59 Installed server service: Remedy Action Request System Server 17:00:59 Registry Key successfully set: 17:00:59 Key: Software\Remedy\ARServer\remsrv 17:00:59 Name: ServiceName 17:00:59 Value: Remedy Action Request System Server 17:00:59 Registry Key successfully set: 17:00:59 Key: Software\Remedy\ARServer\remsrv 17:00:59 Name: InstPort 17:00:59 Value: 1 17:00:59 Registry Key successfully set: 17:00:59 Key: Software\Remedy\ARServer\remsrv 17:00:59 Name: Language 17:00:59 Value: 17:00:59 ****->[ShowMsg]: Starting services... 17:01:02 ****->[ShowMsg]: Starting AR System Portmapper Service. 17:01:05 Checking for service: AR System Portmapper 17:01:05 Specified service is installed: AR System Portmapper 17:01:05 Trying to start the service: AR System Portmapper 17:01:08 Waited 5 secs for service to start. 17:01:08 Service has been started: AR System Portmapper 17:01:08 ****->[ShowMsg]: Starting AR System Server Service. 17:01:11 Checking for service: Remedy Action Request System Server 17:01:11 Specified service is installed: Remedy Action Request System Server 17:01:11 Trying to start the service: Remedy Action Request System Server 17:01:13 ****->[ERROR]: Failed to start the service: Remedy Action Request System Server 17:01:13 ****->[ERROR]: Unable to start the AR System Server service 17:01:16 ****->[ERROR]: The AR System Server could not be started. You can start it manually using the Services icon in the Control Panel. This error occurred after the installation of the AR System was completed. To correct this error, import the sample applications from the samples subdirectory. 17:01:24 ****->[ERROR]: Failed to complete AR Server installation. I can sql into the database so I know it's up. What could be causing this? Thanks, Susan On 4/14/07, Susan Palmer <[EMAIL PROTECTED]> wrote: > > I need some help !!! > > I just did an upgrade from 5.1.2 to v6.3 on the way to 7. But I cannot > get past 6.3 because I cannot get the portmapper to start. I think part > of the problem is that it's pointing to an executeable that doesn't exist. > I copied the v7 one from the dev server to the prod server but that doesn't > work either. > > There's nothing in the doc or knowledge base about this at all. When I > try to start the portmapper I get an error 913: oxc1 > > I've put a ticket in for support but I don't know if they will call to > help since we have m-f support. > > I would greatly appreciate anyone's help on this. > > Thanks, > Susan > > Windows 2003 > Just upgraded Oracle from 9r2 to 10g today before v6.3 install > > __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
