I have installed ( gem install taskjuggler), but now I have no idea how to start it. $ taskjuggler taskjuggler: command not found $ gem taskjuggler ERROR: While executing gem.

(RuntimeError) Unknown command taskjuggler this one was on the taskjuggler page, with no explanation: $ gem 'taskjuggler', '~>3.2.0' ERROR: While executing gem. (RuntimeError) Unknown command taskjuggler, Also, the tells nothing about how to run it. How do I run this program? --update: $PATH bash: /usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games: No such file or directory.

Installation manuelle de PHP sous Windows. Choix du serveur Web. IIS est fourni avec Windows. Sur un serveur Windows. Windows php installer version was 5.2.0. Download Windows installer; Python 2.2.0 - 2001-12-21. Download Windows installer; Python 2.0.1 - 2001-06-22. Download Windows installer; Download Windows debug.

Re: Manual Configuration, pathing errors in IIS and ISAPI setup Chris @ 11-Oct-2006 and phpmanual at pbb dot dds dot nl @ 07-Oct-2004 are both correct. Problem is not with PHP but with IIS (mine is v5.1). Installed PHP into C: Program Files PHP, and set environment variable PATH to path as stated. When selecting the installation of php5isapi.dll via IIS Administrator, IIS would insert the path as: 'C: Program Files PHP php5isapi.dll' (note the quotes and space in directory name) All scripts ran and produced a HTTP 500 error. Replaced ISAPI path in IIS with: C: PROGRA~1 PHP php5isapi.dll (note the removal of the quotes and spaces, and the replacement of the path with 8.3 format names) All scripts ran w/o problems. Thanks to all! I hope someone can report if a similar problem exists with IIS6/7.

In response to phpmanual at pbb dot dds dot nl: You are absolutly correct. I found this out while trying to install PHP4 with Apache2 on XPPro. Here are 3 general guidelines that I have found to be correct: - Path may not have spaces. Change C: Program Files to C: Progra~1 If you don't understand this, go to start-->run-->command (not cmd).

Type cd and hit enter. Then type dir.

You should see all your directory names there. - Paths should not be enclosed by quotes. - Use forward slashes (/) and not backslashes ( ). On two recent installation attempts on iis6 on win2k3 i followed the php manual and windows configuration steps exactly and php would still not run. On the first install i had to give the USER account (not IUSR) read execute permissions to this file, c: php sapi php4isapi.dll. Using filemon i saw that it was being accessed and access was denied.

Steps: - right click on this file >properties >security >add >location (select the server -not domain if listed) >advanced >find now >Users (usually the last item) >click OK - select Read & Execute >apply also a complete computer restart was required in each install. In the Note Titled 'Windows Server 2003 (x64 bits) + IIS 6.0' in step 1 when adding your new.php extension, it will not work unless after you click on the 'Home Directory' you make sure that your 'Execute permissions:' are set to 'Scripts Only'. By default, on my machine, the permissions were set to 'None' not allowing php to run.

Also, for more security it might be wise to Add the new extension just to your default site instead of the whole Web Sites folder in IIS. This would only apply if you were hosting multiple sites and had a site you didn't want scripts to run on. Installing PHP5.2.1 in IIS 6.0 bring me some troubles too. First i need to use full tag to make it your php script works and second the IIS didn't want to load the extension in the ext folder.

I cheked the configuration a couple of thousand of time and everything seen to be ok. I fixed up given read access in the 'ext' folder to de 'IUSER/PCNAME' user or to everyone/PCNAME user to the same folder. Just in case i did the same in the rest of the folder inside the php folder. I wish nobody loose an all day in the same thing, like me. Excuse my english please.

RE: phpmanual at pbb dot dds dot nl @ 07-Oct-2004 11:29 You are correct. I just had the same issue; I was following the PHP installation instructions and some very helpful WIMP instructions. I was trying to keep things tidy by putting my PHP directory in C: Program Files PHP. I set the PATH variable, ISAPI filter config and extension in Application Configuration, but was getting the 'Specified module could not be found' error. Changed the PHP directory to C: PHP and reconfigured everything, did an iisreset, and it started working immediately. Good catch, and thank you!

Your PHP.INI file is not required to be in the C: WINDOWS folder in XP. The trick is to make sure that the PHP.INI can be found. If you fail to reboot after adding the PHP folder to the path and creating the PHPRC environment variable, the file will likely not be found.

If you can't reboot, then try creating the registry entries as described in the following document: When you execute 'phpinfo();' pay special attention to the data returned in 'Loaded Configuration File'. If it does not show a path and a the PHP.INI file name, the file is not being loaded.

The path of C: WINDOWS in the Configuration File Path section is the default location where PHP looks for the INI file and does not mean that the file must be located there; in fact, the following document suggest that you leave the configuration file in the C: PHP folder. Trying to install PHP 5.3.3 VC9 Non-Thread-Safe on Windows 2008 Server running IIS 7.5.

Followed the instructions carefully but still got a 500 error trying to open the classig phpinfo page. After a lot of searching I discovered that everything worked fine after changing the php.ini directive fastcgi.logging from 0 to 1, contrary to what the directions said. I wonder if it was a typo on the instructions or if something changed after a few versions. Hope this saves someone a couple of hours of searching. I wasted a lot of time trying to figure out the problem of not being able to display my 'test.php' demo script to work, the file lay in my IIS 5 ' C: inetpub wwwroot' folder.

The file contents of test.php were: phpinfo(); Windows php installer version was 5.2.0 Problem lay in the minute dumb feature of windows explorer being used t change(rename) text file extension from 'test.txt' to 'test.php'. The resultant name looked by the IIS was still 'test.php.txt'. I used command line to change the filename to 'test.php' and it displayed in my browser. Worked right away. Okay, I'm a total newbie to this, so my findings may be wrong, but this is what I found out.

The manual says 'do not have spaces in the path (like C: Program Files PHP) as some web servers will crash if you do'. Indeed, when using this with PHP5 on WinXP, I got the error message 'The specified module could not be found.' However, the problem seems not to lie in the SPACE in the pathname, but in the QUOTES that Windows adds when a space is in the pathname! This is what I found: 'C: Program Files php5 php5isapi.dll' -- doesn't work C: php5 php5isapi.dll -- works 'C: php5 php5isapi.dll' -- doesn't work C: Progra~1 php5 php5isapi.dll -- works 'C: Progra~1 php5 php5isapi.dll' -- doesn't work C: Program Files php5 php5isapi.dll -- doesn't work, because it's not accepted by Internet Information Services I don't know if this all is a problem with Internet Information Services or with PHP, but it would be nice if it was more documented in the PHP manual. If you are running websites within an Application Pool (which is now the default for IIS6 under 2K3) you need to make sure that your PHP directory (e.g.

C: PHP) has read permissions for the user assigned to the Application Pool. In the IIS snap-in, choose Application Pools 2. Right-click on DefaultAppPool (or other, if you have one defined) and choose Properties 3.

Click the Identity tab 4. The Principles Of Engineering Materials Barrett Pdf To Word more. Make a note of the user name set as the security account for this application pool (e.g. 'Network Service') 5. Browse to your PHP directory and grant that user read permissions for the entire directory.

In my case, I had to add permissions for the user 'NETWORK SERVICE' to get PHP scripts to work. Otherwise I received 401/403 authorization errors when trying to load them in a remote browser.

Note also that first tried adding IUSR permissions to the PHP directory, but that had no effect.