![]() And I even tried to configure the service to log on as me (and a separate dedicated account as well) but no luck there. Interestingly, when I started Apache manually myself it had no trouble getting access to those files. While that makes sense in general, in my case it doesn't. Presumably the reason is that you don't want your server to be able to access network resources (for security reasons I suppose). Then the service came up fine (albeit without my alias). The Wampserver tray menu would not let me delete that alias because the service was not running, so Steven went into the wamp\alias directory and removed the offending file. Thank you to Steven who did show that the problem in fact was that I had an alias defined on my network drive that was causing the service to fail to start. I do get the standard Windows security popup when I run Start Wampserver, and of course I answer Yes to give it permission to "make changes to this computer". So the problem appears to be that WAMPSERVER is not able to start Apache as a service, although it doesn't appear to be anything wrong with Apache itself. I corrected this and re-ran and now the httpd comes up without any errors and my web server (and PHP and MySQL) are all running fine, provided I am willing to start Apache manually. Sorry I don't have the exact wordings, because that prompted me to check my PHP version and I was not pointing to the latest version. The first time I tried it did pop up many different popups about PHP entry points not being found in the php module. So I tried to run httpd.exe directly from the Apache bin directory. That's about all I can do going down the service path. The wampapache service terminated with service-specific error Incorrect function. Not a whole lot of information, but basically says: If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 1. For more information, review the System Event Log. Windows could not start the wampapache on Local Computer. You get a little more info when you try to start the service there: Then I went to the Control Panel service manager. Trying to start the service from the task manager results in a popup that says: I checked the wampapache service from Task Manager and saw it was "Stopped". I went ahead and did a little more digging though. I think that basically covers all the advice and ideas given so far. Turned off my Windows firewall (at least temporarily for a test) Tried installing the Apache service, although I agree that this is already done. Checked my hosts file and it is set up correctly with 127.0.0.1 localhost I don't have Skype installed on this machine. Checked my port 80 using netstat -aon and the port 80 checker built into the WAMPSERVER manager. Made sure the VC++ 2010 runtime environment is installed (just to be sure I even re-ran the install which did a "repair", although I don't think it actually did anything). Reinstalled WAMPSERVER (currently running 2.2 Apache 2.2.22 PHP 5.4.3 MySQL 5.5.20 (I also have 5.5.24 installed, but MySQL is actually starting up) I've followed what I think are all of the above advice: I do have one of my aliases pointing to the E: drive for the web site I develop. However, I have installed WAMPSERVER on my C: drive anyway, so that change should not affect the base server operation. I now did a "map network drive" to the drive and it is still known as E. ![]() The drive used to be known as drive E: on my system. The hardware change I made was to move an external USB drive that used to connect directly to my PC to my router as a NAS device. I once had WAMPSERVER actually running on this machine, but I recently made a hardware change and now I get stuck at the orange icon. Since then, systemd has arrived in force and is normally used for constructing services that start upon boot.Seems like the topic that just won't end! If you don't feel like rebooting, you can start the service manually with: sudo service teamviewerd.sysv startĢ019 EDIT: This answer was written in 2013. ![]() The service will now start automatically with each boot. Then run sudo update-rc.d teamviewerd.sysv defaults Making sure of this is relatively simple, just copy it to /etc/init.d like so: cd /opt/teamviewer/tv_bin/scriptĭon't forget to make the script non-writable to anyone but the owner! sudo chmod 755 /etc/init.d/teamviewerd.sysv # Description: TeamViewer remote control daemonĪll you need to do is make sure this script runs on startup. ![]() # Short-Description: TeamViewer remote control daemon # Required-Stop: $local_fs $network $named TeamViewer provides a script called teamviewerd.sysv available in /opt/teamviewer/tv_bin/script.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |