Hi Andrea, I used Windows 2000 Server, so I don't think it is related to Pro vs. Server. My experience is that services and SAPDB behave identical on either product.
In my case, it was strictly a 7.3 minor upgrade issue - and we never had this problem with minor upgrades before. I wanted to be on the latest 7.3 before I attempted our production update to 7.4. I never had this problem when doing minor version upgrades.... And I started using SAPDB almost 24 months ago and have completed at least 10 minor version upgrades... It is a new upgrade problem that only happend with 7.3.0.32. When I upgraded to 7.3.0.29 I don't remember having this problem. I always stop xserver and all SAPDB services before running SDBINST.EXE to do a minor upgrade... Stephen -----Original Message----- From: Andrea Aime [mailto:[EMAIL PROTECTED] Sent: Monday, February 24, 2003 5:45 AM To: [EMAIL PROTECTED] Subject: Re: Win32 - sapdb 7.3.0.29 to 7.3.0.32 upgrade - xserver Stephen Gutknecht (SAPDB) wrote: > I stopped all services and attempted a upgrade from 7.3.0.29 to 7.3.0.32 on > Windows 2000 SP3. > > I ram SDBINST.exe - The upgrade failed attempting to install the xserver > service. I had to reboot then re-run SDBINST.exe again. > > It seems as if the upgrade attempted to _remove_ then _install_ the xserver > service, but the removal was not completed until a reboot was performed. > > Hope this helps someone else. Yes, I got the same problem trying to upgrade to 7.4: for the upgrade to take place I had to remove the x_server, reboot, and then start sdbinst. I wonder why there are these problems: maybe reboot is needed on Win2000 professional but not on Win2000 server? Best regards Andrea Aime _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
