Confirmed, it works better if the conflicting service is removed first =) On Fri, Jul 8, 2011 at 6:17 PM, etienne massip <etienne.mas...@gmail.com>wrote:
> Not permissions, but I just figured out that the former tomcat service was > still here with the name I failed to set during the installation process, I > guess that's why it failed. > > My bad, sorry. > > > On Fri, Jul 8, 2011 at 6:11 PM, Mark Thomas <ma...@apache.org> wrote: > >> On 08/07/2011 17:01, etienne massip wrote: >> > Hi, >> > >> > Sorry to bother you guys, I see you're voting to release 7.0.18 and I >> tried >> > to install it with Windows installer on 2 machines. >> > >> > I must say I'm very interested by the new option to set a custom service >> > name, but, alas, the installer failed with a custom name both times (no >> > special chars in name), telling me to check my rights and privileges >> (I'm >> > admin on both machines). >> > >> > Eventually, It worked when I reset the service name to its default value >> > >> > First machine is my workstation (windows XP), second is a Windows 2003 >> > server machine; I had previously installed a T7 (.0.14 and .0.16) >> instance >> > via installer on both machines that I uninstalled before running the >> T7.0.18 >> > installer. >> > >> > Just to say. >> >> Works for me. Looks like you do have a permissions problem. The users >> list is the place to get help. >> >> Mark >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: dev-h...@tomcat.apache.org >> >> >
