查看: 2117|回复: 1
求助SOLIDWORKS2012 SP1安装在Win8.1,64位，怎么破解
阅读权限50
我们不再是孤独的探索者；让我们的手紧紧相连，齐攀科学高峰。
才可以下载或查看，没有帐号？
求助SOLIDWORKS2012 SP1安装在Win8.1,64位，老是破解不了，显示只能使用30天，求高手指点
阅读权限70
只有SW2014SP2才支持win8.1
Powered by Discuz!X3.2Win8 .NET Framework 3.5 离线安装包 中文版
软件类别：升级补丁
软件大小：81.8MB
捆绑插件：无插件
软件语言：简体中文
软件等级：
软件授权：免费软件
制作发行：暂无
更新日期：
论坛转帖：
软件人气：
应用平台：Windows 8 64位
好评度：15
微软在最新的WIN8系统中没有集成.NET 3.5，如果安装的话，必须是在线安装，为了方便不能上网或者上网速度慢的用户安装.NET 3.5，作者制作了这个离线安装包，可自动安装.NET 3.5
如果不想使用工具安装，用下面的方法，也可在WIN8系统中实现离线安装.NET Framework 3.5
首先需要有安装光盘或原始安装文件（目录中的sources\sxs）以管理员权限运行CMD
执行&dism.exe /online /enable-feature /featurename:NetFX3 /Source:G:\sources\sxs& ，其中/Source: 是Win8安装目中的文件夹
注意：这个.net 3.5安装包是专用于win8 64位系统的，Win8 32位系统的，请到下面的页面下载：
Win8 .NET Framework 3.5 离线安装包 中文版
相关软件&相关文章
本类人气榜&文章阅读榜
本周下载榜&总下载榜
Copyright &
AllRights Reserved冀ICP备软件标签：　
SOLIDWORKS 产品
适合设计流程各个方面的 直观解决方案。
最大程度提高您的生产效率并将精力集中在 创新上以更好、更快而且经济高效地 设计产品。
Solidworks软件功能强大，组件繁多。 Solidworks有功能强大、易学易用和技术创新三大特点，这使得SolidWorks 成为领先的、主流的三维CAD解决方案。SolidWorks 能够提供不同的设计方案、减少设计过程中的错误以及提高产品质量。SolidWorks 不仅提供如此强大的功能，而且对每个工程师和设计者来说，操作简单方便、易学易用。
对于熟悉微软的Windows系统的用户，基本上就可以用SolidWorks 来搞设计了。SolidWorks独有的拖拽功能使用户在比较短的时间内完成大型装配设计。SolidWorks资源管理器是同Windows资源管理器一样的CAD文件管理器，用它可以方便地管理CAD文件。使用SolidWorks ，用户能在比较短的时间内完成更多的工作，能够更快地将高质量的产品投放市场。
在目前市场上所见到的三维CAD解决方案中，SolidWorks是设计过程比较简便而方便的软件之一。美国著名咨询公司Daratech所评论：&在基于Windows平台的三维CAD软件中，SolidWorks是最著名的品牌，是市场快速增长的领导者。&
在强大的设计功能和易学易用的操作（包括Windows风格的拖/放、点/击、剪切/粘贴）协同下，使用SolidWorks ，整个产品设计是可百分之百可编辑的，零件设计、装配设计和工程图之间的是全相关的。
SolidWorks 2014新增功能：
1. Replace View Model
替换视图模型
2. Existing View Icons
从用工程图调色板选择更多视图时，SolidWorks会显示哪些视图已经使用，哪些视图还未被使用
3. Display Style Context Menu
在快捷菜单中增加&显示样式&命令
4. High Quality Shaded Views
高品质的阴影视图
5. Angular Running Dimensions
角度标注增强
6. Split Table By Row Count
材料明细表以规定行数拆分
7. Order Independent Transparency
渲染效果可使用内部零件可见，而与透明度无关
8. Sunlight & Sunlight Animations
渲染效果中太阳光的模拟
9. Network Rendering Animations
分布式网络动画渲染
10. CircuitWorks Thermal Properties
在CircuitWorks中电子元器件可加入热力学属性
11. Link To SolidWorks Flow Simulation
在CircuitWorks中的电子元器件的热力学属性直接可以用于Flow Simulation做分析
12. Slots In Hole Wizard
在孔向导中新增槽孔功能
13. Path Length Dimension
路径长度尺寸标注，并可设为驱动尺寸
14. Fixed Length SpLINE
给定样条曲线长度，可对样条曲线进行编辑，但长度不变
15. Style Spline
有更多更简单的样条曲线控制方式（在现场观看SolidWorks工作人员演示此功能非常赞叹，在SolidWorks 2014版本对样条曲线的控制将会更简单，更有用，以后做曲以造型将会更容易，很期待SolidWorks 2014版本赶快发布）
16. Replace Sketch Entities
替换草图实体
17. SolidWorks Electrical Harness
SolidWorks Electrical线束功能，
18. Reuse Existing Harness
现有线束重用
19. Clips In Flattened Representation
线路展平时线夹可见
20. Colored Connector Pins
管脚可加颜色
21. Bolt Mapping
Simulation螺栓映射
22. Results Symmetry
Simulation中用对称简化计算的算例，在显示结果时可以把完整产品结果显示出来，增强展示效果
23. Residual Stress From SolidWorks Plastics
通过Plastics模流分析后产品残余应力可以直接传递到Simulation进行有限元分析（本人非常喜欢这一项新增功能，做塑料件模流分析通过要知道成型后塑件的残余应力并由此引起的变形）
24. Environment Themes
软件环境主题可自定义并随时切换，如工具条的位置排布等
25. History Folder
在特征管理器中新增&历史文件夹&
26. Flexible Assemblies Context Menu
在快捷菜单中新增&装配体柔性&命令，可以更快的定义装配体为刚性或柔性。
27. Streamlined Save As Copy
&Save As Copy&增强，可以Save As Copy to Disk和Save As Copy and Open.
28. eDrawings With Augmented Reality
eDrawings显示增强
29. Sheet Metal Corner Gussets
钣金角加强筋在展开时自动忽略
30. Lofted Bend Transitions
钣金放样转换
31. Smart Mate Delay
智能装配延时，以往做智能装配时拖放零件总时会实时判断当前位置是否匹配，2014版本里面允许用户自定延时时间，直接用户拖放在理想位置时再进行装配，节省很多时间
32. Feature Driven Component Pattern
特征驱动阵列增强
33. Rotate Exploded Views
在做爆炸视图可以让零部件以旋转的方式爆炸，比如拧螺丝时的动作
34. Quick Mate Context Menu
快捷菜单中有&快速装配&命令
当然SolidWorks 2014新增功能远远不只之些，SolidWorks每一个新版本都有将近200个新增功能或功能增强奉献给广大SolidWorks用户。
先把光盘上安装软件复制到电脑上
32 位系统和64 位系统安装方法一样，安装方法一样
第一步，安装虚拟光驱或直接将iso文件解压
第二步，加载solidworks安装程序
输入序列号00 3486 Q5HF FG98
直到安装结束，时间和计算机配置有关，
第三步，运行破解文件 SW.Activator.SSQ.exe
(这个文件在安装包根目录crack文件夹下，有的是直接另外下载破解文件)
第四步，启动软件包
本帖长期更新最新版 请收藏下载！版权声明：本站提的序列号、注册码、注册机、破解补丁等均来自互联网，仅供学习交流之用，请在下载后24小时内删除。
（发现下载取消的,请刷新网页后再下载或到留言里找，也可以加群：咨询）
建议使用以上版本或、浏览器访问本站，获得更好的用户体验。 豫ICP备号-1Keyboard Shortcuts?
Next menu item
Previous menu item
Previous man page
Next man page
Scroll to bottom
Scroll to top
Goto homepage
Goto search(current page)
Focus search box
Change language:
Brazilian Portuguese
Chinese (Simplified)
Windows 系统下的安装
Table of Contents
本节内容适用于 Windows 98/Me 以及 Windows NT/2000/XP/2003。PHP
不能在 16 位平台例如 Windows 3.1 下运行。有时把支持 PHP 的 Windows
平台称为 Win32。自 PHP 4.3.0 开始不再支持 Windows 95。
自 PHP 5.3.0 起不再支持 Windows 98/ME/NT4。
自 PHP 4.3.0 起不再支持 Windows 95。
有两种方法在 Windows 下安装 PHP：或者使用安装。
如果有开发环境例如 Microsoft Visual Studio，也可以 PHP 的源程序。
一旦在 Windows 系统下安装好 PHP 之后，可能需要以实现更多的功能。
互联网上还有一些多合一的安装程序，但是它们没有一个是被 PHP.net 认可的，因为我们相信，从
下载官方 Windows 安装包是系统安全和优化的最好选择。
If you make changes to your PHP.ini file, consider the following.
(I'm running IIS5 on W2K server. I don't know about 2K3)
PHP will not "take" the changes until the webserver is restarted, and that doesn't mean through the MMC.& Usually folks just reboot. But you can also use the following commands, for a much faster "turnaround".& At a command line prompt, type:
iisreset /stop
and that will stop the webserver service.& Then type:
net start w3svc
and that will start the webserver service again.& MUCH faster than a reboot, and you can check your changes faster as a result with the old:
&?php&
phpinfo();
?&
in your page somewhere.
I wish I could remember where I it isn't anything I came up with...
In order to run php scripts with php.exe CGI instead of php4isapi.dll under IIS, following steps can be followed.i) Add a web service extension for PHP using IIS manager. Choose a web service extension name like 'PHP' and add your php.exe path in the 'file location' while adding the required file e.g. 'C:\php\php.exe' in the Add extension dialog box. Don't forget to 'Allow' the extension file.ii) Open php.ini file located at %systemroot%. Set the following variables to the shown values.cgi.force_redirect = 0cgi.redirect_status_env = ENV_VAR_NAMEiii) In your websites, add Application Mapping for '.php' and set the executable path to your php.exe file path. You can test whether PHP is running or not and other PHP settings using the following simple PHP script.&?php&phpinfo();?&Feroz Zahidferozzahid [_at_] usa [_dot_] [_com_]
install php on windows, you can find some help here!Enjoy!!!
For those of you that would like visuals, there's a video tutorial that will help you get PHP5 installed on Windows 2K3 w/ IIS6.It's pretty straight forward.The link to the site, if you're interested, is:The title is:Installing PHP5 on Windows 2003 and IIS6I hope this helps others as it did me.Scott
Just a note following on from Luis D regarding adding the pgp4ts.dll as a Web Server Extension.I just used the latest php-4.3.10-installer.exe from php.net and had the problems where .php files could not be found.In order to get them to work I added and allowed the php.exe as a Web Service Extension and not the php4tx.dll.Cheers,Steve
Note carefully that no matter what it says above, Windows 2000 has been (effectively) desupported in PHP 5.3. However, 5.2 still seems to work, ignoring the spate of dll messages.See: It is highly useful to run the php command line executable (php.exe) from a command line (start/run: cmd.exe) to check whether the compiled php executable will start at all:& & cd \php& & php -vThis is in preference to wondering why IIS/Apache returns some obscure message about missing headers.- Conor
Here's how to run dual PHP instances with PHP 5.2 and any previous PHP on Windows 2003:1. Right-click My Computer, go to Advanced tab, and click on Environment Variables.Add the two installations and their EXT directories to the Path variable. For example, add:c:\c:\php\c:\TMAS\c:\tmas\php\Then, add the newer PHP version's directory as a variable called PHPRC. For example:Variable:PHPRCValue: C:\PHPClick OK to close the Environment Variables window, and click OK to close System Properties.2. In registry, under HKEY_LOCAL_MACHINE&SOFTWARE&PHP, add a REG_SZ key called iniFilePath and give it a valueof the directory where the older PHP is installed. For example:C:\TMAS\PHP3. In IIS, go to the Web Service Extensions. Add both versions' ISAPI module separately to the extensionslist, and allow both.4. In IIS, go to each website utilizing the PHP versions. Set an ISAPI filter if needed. On the Home Directorytab, click Configuration, and add .php, .php3, .phtml, and any other extensions needed (perhaps .html?) tobe filtered through PHP, and specify the ISAPI module version needed for each website.You can now run two versions of PHP. This is because the order of where to look for the .ini file changedbetween previous PHP versions and PHP 5.2, as documented at --------------------------------------------------- php.ini is searched in these locations (in order):& & * SAPI module specific location (PHPIniDir directive in Apache 2, -c command line option in CGI and CLI, php_ini parameter in NSAPI, PHP_INI_PATH environment variable in THTTPD)& & * The PHPRC environment variable. Before PHP 5.2.0 this was checked after the registry key mentioned below.& & * HKEY_LOCAL_MACHINE\SOFTWARE\PHP\IniFilePath (Windows Registry location)& & * Current working directory (for CLI)& & * The web server's directory (for SAPI modules), or directory of PHP (otherwise in Windows)& & * Windows directory (C:\windows or C:\winnt) (for Windows), or --with-config-file-path compile time option ----------------------------------------------------
Oh Man!I installed by Microsoft Installer, manually, whatever I always received de same error from IIS7.HTTP Error 404.3 - Not FoundThe page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map.The IIS7 interface is quite diferent and are not all together like IIS6The 5.3 version have not any of those files: php5stdll, php5isapi.dll. etc.The installer puts others files in handlers and I decided to use them as substitutes. Nothing done!After that, I discovered that installer do not install these files within the sites, but in the root default site configuration of IIS7.So, I copied the root configuration to my site and them it worked (all others procedures were done e.g. copy php.ini to windows folder)
When installing onto the Windows IIS platform, ensure you add the PHPRC Server Variable to point to your PHP.INI file.Also, add '.INI' to the FILEEXT Server Variable. Failure to add these could stop the PHP engine being able to find your PHP.INI file, and none of your modifications will be read.Rob.
If you get 404 page not found on Windows/IIS5, have a look at C:\SYSTEM32\INETSRV\URLSCANThere is a .ini file there that prevents some files from being served by IIS, even if they exist, instead IIS will give a 404. The urlscan logfile (same place) should give you some insight into what parameter is preventing a page from loading, if any.
Thought someone would save some time and headaches by using this post.Our tech department is migrating to Windows 2003 Server and they have some complex security implementations between our Web Servers and our Application (COM) servers.If you have this type of scenario and are receiving the "Warning (null)(): Unable to lookup.... Access is denied." error, it is because the "Identity" in the Web Server's application pool does not have sufficient permissions to connect to the Application (COM) Server.To fix this:- create a new Application Pool- right click the new pool and select "properties"- click on the "Identity" tab- change the permissions from "Network Service" to a user on the Web Server who has access to call the Application (COM) server.- right click the application pool- click "start"- right click your web site- click on the "Home Directory" tab- change the application pool to the new application pool you've just created.- restart IISHopefully this will save someone some time and headaches.
You can have multiple versions of PHP running on the same Apache server. I have seen many different solutions pointing at achieving this, but most of them required installing additional instances of Apache, redirecting ports/hosts, etc., which was not satisfying for me.Finally, I have come up with the simplest solution I've seen so far, limited to reconfiguring Apache's httpd.conf.My goal is to have PHP5 as the default scripting language for .php files in my DocumentRoot (which is in my case d:/htdocs), and PHP4 for specified DocumentRoot subdirectories.Here it is (Apache's httpd.conf contents):---------------------------# replace with your PHP4 directoryScriptAlias /php4/ "c:/usr/php4/"# replace with your PHP5 directoryScriptAlias /php5/ "c:/usr/php5/"AddType application/x-httpd-php .phpAction application/x-httpd-php "/php5/php-cgi.exe"# populate this for every directory with PHP4 code&Directory "d:/htdocs/some_subdir"&& & Action application/x-httpd-php "/php4/php.exe"& & # directory where your PHP4 php.ini file is located at& & SetEnv PHPRC "c:/usr/php4"&/Directory&# remember to put this section below the above&Directory "d:/htdocs"&& & # directory where your PHP5 php.ini file is located at& & SetEnv PHPRC "c:/usr/php5"&/Directory&---------------------------This solution is not limited to having only two parallel versions of PHP. You can play with httpd.conf contents to have as many PHP versions configured as you want.You can also use multiple php.ini configuration files for the same PHP version (but for different DocumentRoot subfolders), which might be useful in some cases.Remember to put your php.ini files in directories specified in lines "SetEnv PHPRC...", and make sure that there's no php.ini files in other directories (such as c:\windows in Windows).And finally, as you can see, I run PHP in CGI mode. This has its advantages and limitations. If you have to run PHP as Apache module, then... sorry - you have to use other solution (the best advice as always is: Google it!).Hope this helps someone.
If you use the installer for Windows (PHP &= 5.2.x) and you want the mysql_* functions to be used, you may have to restart your machine after you install.I was getting the error "Call to undefined function mysql_connect..." However, I knew that my php.ini settings were correct and I was including php_mysql.dll. When I viewed phpinfo(), it was not showing that MySQL was part of the install. My first thought was to restart Apache - this did not change anything. So, then I restarted the machine, viewed phpinfo() again and it was now there.I've manually installed several times on Windows and not had this problem. This was my first time running the installer. I think it may have something to do with setting registry values or changing environment variables. Nonetheless, hope this helps.
This is just to clarify on a posting on this page that states the nescesity of allowing all unknown cgi Extensions in Windows 2003 IIS 6. Although this will work and it should be consider as a quick option for an itranet solution with no web access at all.This poses a very serious security problem and its not the best course of action, in my opinion.& The proper way of making this work will be to actually enable the extension that you want to execute.& After verifying that the .php extension is present, simply go to "Web Service extensions" in the IIS Manager and click on "Add a new web service extension";Once the "new web service extension" opens:1- Add the "extension name" field, please enter "PHP" (or what ever you wanna call it) Other more conservative admins will say call it what it is and always input ".php".& Its up to you!2-Click on the "add" button and browse to the php4ts.dll file on your c:\PHP (default)& and then click open --& OK and set the checkmark under "set extension status to allowed" click OK and thats it!!!If you missed the checkmark moment cause you are just so impatient, like me, then simply select the extension on the web service extensions windows and click ALLOW.This is a very simple process and it will work everytime.I hope this helps, as I have found several things in this forums that are incredibly helpfull!!PS: For the non programmer, it is a good practice to install mysql and a free php forum like bb2 to test how well your php IIS and mysql is working.
This fixes the "The directory name is invalid" error.In IIS 5.1 on Windows XP Pro, Go into the Internet Information Services, and into the properties of the virtual directory where the problem occurs.& On The 'Virtual Directory' tab, click on the 'Configuration...' button.& Select the '.php' extension, and press 'Edit'.& On the bottom, Check the 'Check that file exists' checkbox.
One very helpfull note to Win2003 iis6 users:If you'd like to use isapi in the web service extensions and you're in a development server (or even if your php.ini config file changes frequently), here's what you can do:Php.ini runtime changes:Create a new application pool in iis:iis-&select server-&application pools-&new application pool& & & & & & & && U& & & go to the application pool you've created, properties-&& & check the "Recycle worker process" option, and give it a small value (10 is nice :) ).Now go to your site (or virtual directory site)-& properties-&change the application pool to the newly configured appPool.At this moment, is good to make a iss restart (note this is the only resart needed).Your site is now semi-runtime changed :) You can try it with the usal php info() test. Change something in the php.ini and check the number of requests it takes to use the new configuration.The downside of this approach (wich is still better than to use php-cgi.exe): the process is recycled, so all the configuration in php.ini is read every N requests - with php-cgi.exe, this would happen for every request, so.. is a good solution. Again, be carefull when using this in a production environment, since the load can increase (not sure how much, but it will certainly increase). And keep in the new appPool JUST the php sites that require runtime changes in php.ini !------You've helped me, so I)Tks
If you are installing PHP on Vista just go to David Wang's blog. archive//HOWTO-Install-and-Run-PHP-on-IIS7-Part-2.aspx Magic!
Dirt Simple Install Guide For PHP5/W2K ServersFor those of us out there who still have 2K servers, this is a great 3 min step by step to get you up and running.Thanks to it's author, Darrell Brogdon!
To allow acWEB.sf.net win32-webserver and Eserv 2.98 (www.eserv.ru) web-server run PHP 4.2.2 without problems with FORCE_REDIRECT you should set "cgi.force_redirect = Off" in php.ini in windows directory.
Running on Win2k3 x64 w/ IIS6.& Followed the BASIC setup (unzip, PHPRC, add extension to IIS) and still no go.Wasn't until I enabled x86 that it 'popped':cscript d:\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1No security issues that needed fixing.& Test .php file came up like a champ!
Hello,I had trouble setting up PHP 5 to work IIS 5 (Windows 2000).I keep getting a HTTP 500 error.I checked the php5isapi.dll file path, the permissions and all that but the error did not go way.The way I got it to work was by adding the IUSR_(machine name) and IWAM_(machine name) account to the administrators group and restarting the computer.I hope this helps someone out there.Cheers.
Here is a tutorial on how to get the latest
apache, php/mysql alongwith phpmyadmin installed
in windows vista/xp.
For those having trouble installing PHP 5+ ISAPI for IIS 6 (on Windows 2003 server), who have tried everything on this site and all over the net, with no success (like I did) - try the following before throwing your server out of a 3rd story window.It was the only thing that worked out of all the many solutions I tried.Probably some other solutions would've worked as well, but in my frusterated state of mind, this explanation was the clearest.& My problem was that in addition to adding the the Web service extension, I was not adding the ISAPI extensions for the websites in IIS Manager manaully.& ALSO, remember to reboot after the changes on the site listed above.& It's the only thing he forgot to mention, and depending on your setup, you may need to reboot to register the dll moves and changes made.& (IIS restart will not re-register dlls).
I hadn't installed PHP in years, used the PHP 5.2.9-2 installer.& Selected FastCGI on IIS, I just didn't work.& On both a w2k3 server and on a Vista laptop.First, I forget to install from ZIP, as I had before.& I suggest a notice on the download page. The message "Use of the installer isn't the preferred method for installing PHP." is on the "Windows Installer (PHP 5.1.0 and earlier)" page.& Is that no longer true for "Windows Installer (PHP 5.2 and later)"? Next, I found the recent Microsoft Web Platform Installer (WPI) at It just works.& There are no config settings, it just installed FastCGI on IIS on the W2k3 server and on the Vista laptop.& Took a download+install of the WPI tool, and a few minutes for php install.I'll likely never take a more careful l for a production server I'll install manually. (or use Apache :))
Regarding the "No input file specified." problem where 404 error pages aren't sent if the requested non-existent file ends in .php, this was helpful to me . . . In a nutshell:In IIS Management Console (v5.1 in my case), select "Default Web Site", right-click and select "Properties", "Home Directory" tab, "Configuration..." under Application Settings, "Mappings" tab, select the line for the .php file extension, select "Edit" and check these two things:1) ensure that executable C:\PHP\php5isapi.dll filename is not truncated2) ensure there is a tick in the box next to "Check that file exists".Click OK, OK, OK.Cheers.
I've installed Apache + PHP on a Windows machine of which I'm not an administrator.I found out it was necessary to change the permissions of the httpd.conf file on C:\Program Files\Apache Group\Apache\conf in order to have everything working. Since I'm also using cygwin this was simply done with: &chmod 755 httpd.conf.
PHP 5.2.9.2 Install on XP Pro IIS 5.1 - phpinfo( ) results incorrectTesting Date:& 05.15.09Background:For several days now I, as a newbie, have been unsure if I had installed PHP correctly, or not.& No matter what I did phpinfo( ) reported "Configuratin File Path" as:& “C:\WINDOWS”.& I was left to wonder what was wrong.To help resolve the phpinfo() “issue”, I conducted a series of tests using two scripts:The first is “test-php-ini-loaded.php”; it is stored in c:\inetpub\wwwroot, and has the following code:& & &?php& & $inipath = php_ini_loaded_file();& & if ($inipath) {& & & & echo 'Loaded php.ini: ' . $inipath;& & } else {& & & & echo 'A php.ini file is not loaded';& & }& & ?&The second script is simply calls phpinfo( ).& It is named test.php, is stored in “c:\inetpub\wwroot”,& and has the following code:& & &?php phpinfo( ); ?&My Dev Environment:1. Windows XP Pro SP32. IIS 5.1 / MMC 3.03. PHP 5.2.9.2 – phpMyAdmin not yet installed4. (plus MySQL 5.1, etc.)5. Install location is on my local E: driveThe Tests:Test 1:a. PHPRC environment variable and IniFilePath Registry left in place and activeb. Verified no other copies of php.ini exist on the system other than in my E:\PHP folderc. Renamed php.ini to hold-php.inid. Stopped and started IIS (“net stop iisadmin” and “net start w3svc”)e. Ran “test-php-ini-loaded.php” to check whether my php.ini is loaded.& It is not.f. Ran "test.php".& “Loaded Configuration File” was empty, while “Configuration File (php.ini) Path” showed:& C:\WINDOWS.Test 2:a. Moved php.ini from E:\PHP to C:\WINDOWSb. Stopped and started IISc. Ran "test-php-ini-loaded.php" to check if my php.ini is loaded.& It is not, which surprised me.d. Ran "test.php".& My php.ini is apparently not loaded, or found, by phpinfo( ), even though “Configuration File (php.ini) Path” reports it as being in C:\WINDOWS.e. Note:& Per PHP’s “The configuration file” note, PHP's search order includes:& “Windows directory (C:\windows or C:\winnt) (for Windows), ...”; but it apparently doesn’t or php.ini would have been found and displayed at “Loaded Configuration File”.Test 3:a. Left the solo copy of my php.ini in C:\WINDOWSb. Disabled PHPRC environment variable by renaming it to “Ex-PHPRC and saving the settings (note: for this test& I left the Registry entry for PHP IniFilePath intact)c. Stopped and started IISd. Ran "test-php-ini-loaded.php" to check whether my php.ini is loaded.& Predictably it is not found.e. Ran the "test.php".& Again, my php.ini file is reported as not found in C:\WINDOWS though “Configuration File (php.ini) Path” reports it as being there.Test 4:a. To be thorough and eliminate all possible sources of “mis-direction” I deleted the PHP IniFilePath Registry entry (after backing up the Registry).& The PHPRC environment variable was left disabled.& b. Stopped and started IISc. Ran "test-php-ini-loaded.php" to check whether my php.ini is loaded.& Predictably it is not.d. Ran "test.php".& Again, no change.& My php.ini file is not found “Configuration File (php.ini) Path” reports it as being there.Conclusions:The first conclusion I came to is that, in the default download version of phpinfo( ), “Configuration File (php.ini) Path” is hard-wired to report C:\WINDOWS whether php.ini is there or not.& Further, that C:\WINDOWS is not a default search location (at least not on XP).& However, given an otherwise “proper” setup, phpinfo() reporting C:\WINDOWS as the value for “Configuration File (php.ini) Path” is merely misleading and is not actually harmful or indicative of a failed installation. Thanks go to Peter Guy of
who suggested the testing, and to Daniel Brown of www.php.net for some initial guidance.P.S.& This note is not meant to take anything away from PHP.& It is a fine tool.& The sole purpose of the testing was to confirm that my installation of PHP was correct.
If you get errors like this:PHP Notice: Constant XML_ELEMENT_NODE already defined in Unknown on line 0And many more complaining about XML constants, comment out the line:extension=php_domxml.dllin your php.ini. That extension seems to be compiled into PHP when you get those errors or something else is including the functionality before that dll.
Note to windows server 2003 usersIf you install php5 ISAPI on windows server 2003 / IIS and keep getting a 404 when you try to view a php script don`t just activate "all unknown ISAPI extensions" but also activate "All Unknown CGI Extensions".
On the Windows 2003 & IIS6 platform, you can run different websites on different versions & copies of PHP. This is useful in at least two cases:& 1. You want one website on your box to have register_globals on, but since you're running IIS, you cannot specify that in an .htaccess file. And you definately don't want register_globals on for the rest of the websites.& 2. You want to run different versions of PHP for different websites, or even just different extensions. Say you wanted one site to use 4.0.5 and a different site to use 4.1.11.Its simple, just:& 1. Move your php.ini file from your c:\windows\ directory directly to your php directory (by default that would be c:\php\)& 2. Make sure you don't have a php.ini file in any other location that would supercede the c:\php\php.ini file. Using phpinfo(); is useful here.& 3. Have your alternate version of php (either a different version or a different php.ini) have its own install directory, like c:\php4RG\ or c:\php405\.& 4. In the Home Directory Configuration for your website, specify the .php extension to use a different script, pointing it at the alternate directory.
Note to windows users, if you are trying to install php5 ISAPI on windows server 2003 / IIS and getting a 404 when you try to view a simple php script, even though everything else seems to be right...& click into "web service extensions" from IIS and either add a new web service extension, or click onto "all unknown ISAPI extensions" and click allow.
Under a Windows 2003 and IIS 6.x installation of PHP, it is interesting to note that by default in most cases, the "DefaultAppPool" for the "Default Web Site" is running under the security context of "Network Service" which maybe too restrictive. This results in a 403: Forbidden error every time you try to access a PHP page.You have several options to remedy the problem:an obvious one is to make it run as the "Local System", but that may be too much power for some administrators' tastes. The other option is at the IIS Manager,go to the computer's "Application Pools" folder,and go to the properties dialog box of the "DefaultAppPool",and then to the "Identity" tab, and select the "Configurable" identity of "IWAM_[COMPUTER_NAME]" as the security context. This will make the application pool run the way it did in the previous versions.This solved the repeated problems of the 403 errors. However, do not forget to give permission to "IUSR_[COMPUTER_NAME]" and "IWAM_[COMPUTER_NAME]" appropriate directory permissions for your web directories as stated above.
Still Can't Run PHP Code?After installing php-5.2.5-win32-installer.msi on my Windows XP2. with IIS5.1 it still didn't run PHP files.I eventually found the fix*:1. Goto Control Panel&System&Advanced&Environmental Variables2. Add a New System Variable "PHRC" and set its path as "C:\Program Files\PHP"3. Restart*source: #faq.installation.addtopath
IIS setup: 403 forbidden error.& We had installed two separate different PHP versions - PHP 5.1.4 followed by 5.2.5.We configured 5.2.5 php5isapi.dll to be loaded as the .php file type extension.Despite this, php version 5.1.4 was being loaded.& We renamed 5.1.4's folder and then PHP was not loading at all.There were no visible references to 5.1.4 in the IIS configuration, but in the file \webConfig.xml, there was a reference to 5.1.4's isapi under IISFilters.To fix this problem, we added version 5.2.5's php5isapi.dll to the ISAPI Filter category for the web site, in the IIS control panel.
If you have installed using the msi file, allowed it to configure IIS6 for you using the default directory, and are receiving a 404 error (specifically 404 2 error in your log file), then you need to modify the "application extension" for .php to include the full quoted path.& The default uses the old 8.3 convention which is not considered the same by IIS, and therefor the web extension isn't allowed.
PHPv522 configuration considerations (php.ini) on Win3k(iis6)cgi.force_redirect = 0++ You MUST set this (its commented out by default)two new settings are included...session.save_path = "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\php\session"upload_tmp_dir = "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\php\upload"++ sessions will fail: $_SESSION['something'] unless you deal with permissions on the new location,or simply comment out the session.save_path and go back to default "c:\windows\temp"
If you are using Application Pool Isolation and you're trying to get PHP to run as CGI and you're getting 403 errors, try looking at this article (watch the word wrap):unable-to-run-perl-or-php-in-application-pool-isolation/
First I got a HTTP 405 error, resolving which I got an HTTP 404 error...read on for how this was fixed...Environment:& PHP 5.2.4, IIS 6.0 ISAPI, Windows Server 2003.& Installation:& Simply downloaded the PHP 5.2.4 installer [22,002Kb] - 30 August 2007 and ran it doing next, next until Finish. To get rid of 405 error, ensure that your php directory allows scripts.& Start-&Control Panel-&Administrative Tools-&Internet Information Services-& (select website, navigate to directory with your php and right-click your directory) -& Properties -& Directory TAB -& Change Execute Permissions from "None" to "Scripts" (to allow PHP).To get rid of 404 error, ensure that your executable mapping for the .php extension is properly coded.& Start-&Control Panel-&Administrative Tools-&Internet Information Services-& (select web site) -&Properties-&Home Directory-&Configuration-&Mapping and then change the Executable Path for .php files from C:\Program~\PHP\php5is~1.DLL (or whatever crazy path) to "C:\Program Files\PHP\php5isapi.dll" (IMPORTANT: the quotes from c:\ to end of dll are important since the default install location, Program Files, has a space...in my youth I would yell "Stupid Microsoft"...but now I would more maturely just note that there is an inconsistency with the way that Paths are defined...in definingenvironment variables, for instance, such spaces are OK...).
My experience in running php 4 and php 5 on the same machine with IIS as ISAPI module (tested on XP Pro).1- Extract the ZIP packages of both php 4 & php 5 to c:\php4 & c:\php5, each in its own folder.2- Setup the corresponding php.ini files in c:\php4 and c:\php5, by renaming php.ini-dist to php.ini..3- Add the Web Service Extensions for php4 and php5. For php4 use c:\php4\sapi\php4isapi.dll, php5 use c:\php5\php5isapi.dll..4- Add the following registry keys:HKEY_LOCAL_MACHINE\SOFTWARE\PHP\5\IniFilePath -& c:\php5HKEY_LOCAL_MACHINE\SOFTWARE\PHP\IniFilePath -& c:\php45- Add c:\php4 and c:\php5 to the PATH environment variable, separated by semis.6- Create a session and an uploadtemp folders in any location, then add them in the session.save_path in bothe php ini files (there are two in php4?), and give IUSR_machinename write access to them.7- Associate each web site in IIS with the corresponding php version.8- Reboot..Use phpinfo() to test it in each site.Regards,,
In order to enable your x64 version of Windows 2003 Server executing the php*.dll through IIS, you can execute the script shown here: 36f8964c-cf86-44cf-94a4-f1033.mspx?mfr=trueI've tested it with Windows 2003 Server x64 SP2 and PHP 5.2.3 and it works.Good work,Fabar
IIS6 AND PHP5 on w2k31.download php and unzip to c:\php&& - also create c:\php\sessions2.add c:\php to you path && -right click mycomputer,properties,advance,env variables2.On IIS Manager add web service extension&& -name: php isapi&& -req files: c:\php\php5isapi.dll3.Now let iis know what to do with .php& -On iis Manager,right click Web Sites, properties, home directory tab, configuration button, add button& && executable: c:\php\php5isapi.dll& && extension: .php& && limit to: GET,POST,HEAD4. rename php.ini-recommended to php.ini& you can copy php.ini to c:windows or modify the registry to look for php.ini in c:\php&& to use the registry create a php.reg file with the following inside. after this just double click. do not put the lines.-------------------------------------------------Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\PHP]"IniFilePath"="C:\\php"-------------------------------------------------5. modify php.ini withshort_open_tag = Onextension_dir = "c:\php\ext"cgi.force_redirect = 06. the web sites are going to be using the default pool. this runs under network service. go to c:\php and give the network service& read& execute, list folder content,read& -go to c:\php\sessions and add write and modify access network service
Note regarding PHP4 Installation on IIS5 + Win2KTip: Don't install PHP4 on Directories with spaces in between.I've had problems Installing PHP 4.0.0 on IIS5, Win2k's default web server, spanish version (I live in Colombia). I've had HTTP 500 Errors and I followed all instructions step by step, but nothing seemed to work.I solved the problem eventually, and I think it had something to do with the fact that I have installed PHP4 manually and placed it in the directory "C:\Archivos de programa\php-4.4.0-Win32" ('Archivos de programa' stands for 'Program Files'), a directory with spaces in between.When I added the application mappings for "C:\Archivos de programa\php-4.4.0-Win32/sapi/php4isapi.php", An error would ocurr and a message along with it: "Escriba una ruta de acceso valida", as in "Write a valid access rute", as in "I can't find the file".I thought i had it when I encapsulated it with Doublequotes ("), but that didn't work either.As a final long shot, I copied the php4isapi.dll to the windows/system32 directory and 'WALA!' It worked.I'm not sure, but i suspect that it had to do with spaces in between directory names, so avoid those, or copy the isapi module to another directory.Hope this helps someone!
It's a hard way to get work php on win98/PWS... but with this comment-page I found it out how it works:&br&
- error 403: give read/write rights to the directory. You can do this by clicking the right mouse key on the directory in the explorer.&br&
- html file in a dos box: 1) clean the "doc_root" line in the php.ini file.&& 2) start personal web-manager / go to 'advanced' / make for your web-default-directory a virtual directory with all possible rights.&br&
On my system it works now!
I made the mistake of setting a 'wildcard application map' for PHP on a Windows 2003 / IIS 6.0 / PHP ISAPI installation.& This resulted in "No input file specified" errors whenever I tried to load the default page in my site's directories.& I don't know why this broke things, but it did.If anyone has the same problem, this may be the cause.
I've installed php 5.0.5 with the ISAPI module, as the isapi dll file (php5isapi.dll) resides in the php root directory, I didn't have trouble in my installation (In php4 this dll file is in sapi directory and it should be moved to php root directory). I changed some of my settings in php.ini file and restart IIS Web site,but my changes weren't applied. Then I go to Control Panel&Administrative Tools&Services and restart the IIS Admin Service.Everything worked like a charm...
IIS ISAPI module is not included in the Windows msi installer for version 5.2.9-2.Either use the zip file and set it up manually, or use the installer for version 5.2.9-1 instead.
Been fighting with this for a while.Installing PHP on IIS 6.0 using the ISAPI extension.Note, if you have a web.config file present within the Virtual Directory folder, or otherwise configure the Virtual Directory to run ASP.NET scripts in a specific configuration...IIS will ignore its ISAPI obligations to render your PHP script and then cite a 401.3 error, access denied based on ACL. If you have Integrated Windows Authentication turned on as a second authentication method, the web browser will prompt you for credentials. If you supply some, either from the local machine or from your domain, the website will suddenly work. This will also result in your website loading when you reference it via Localhost. Only works with Localhost, and does not work with any network-access IP.Oddly enough, Anonymous impersonation will FAIL under these conditions! Why? I suspect it is because ASP.NET scripts run under the APPLICATION-POOL USERNAME CONTEXT. Once its kicked into that gear, any hope of using Anonymous user impersonation may go out the window.References:/*******************/Impersonation in ASP.NET: (Look up "Impersonation in ASP.NET (IIS 6.0)" on /Technet/ ) Article Demonstrating how ASP.NET Runs under ApplicationPools: /*******************/This, to date, is my only theory.Filemon/Process Mon will not register any kind of failed file access attempts, everything will appear normally. Even the presence of a BUFFER_OVERFLOW message is normal within the context of SYSINTERNALS traces...But if you download the IIS 6.0 resource kit, pay attention specifically to IISTRACE.Running IISTRACE and hitting your webserver will reveal that the PHP5ISAPI filter DLL is never called! Only the asp filter DLL.The moral of your story? Keep web.config files out of your PHP directories!
Another cause of the "No input file specified" on systems with multiple hosts is that the doc_root setting in the php.ini file has been set to a specific directory.& When using IIS with multiple hosts in distinct top level directories you should comment the doc_root line out.
I have an IIS 6.0 with PHP 5.2.0 as ISAPI-module. Installation went fine, using one of the numerous guides available, however I couldn't get my PHP to load any extensions!It took me quite a while, to find the catch, it seems, that PHP 5.2.0 doesn't like the quotation marks " in some of its directory variables.Thus, changingextension_dir = "c:\php\ext\"toextension_dir = c:\php\ext\did the trick for me...
I found a way to install it properly, on IIS 7:NoteSet IIS to allow 32-bits if you are on 64-bitscscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1Set enviroment variablesPATH to, say, C:\php\PHPRC to, that same dirGo to Web Service Extensions: Add a new extension...Name it for example php, and point it to the php5isapi.dll.Set status to Allowed.Right click Web Sites:On the tab, ISAPI Filters, name it for example php, and point it to the php5isapi.dllThen go to Home directory tab:Click ConfigurationOn Mappings, click add:Executable would be: php5isapi.dllExtension to: .phpClick OK, then OK.Then on the tab Documents click Add:and add there what you want to load as default, say index.phpThen stop, and start IIS.This worked for me on a Windows 2003 Server, and WinXP 64.I hope this saves time for someone.
On IIS7 and Vista I got errors using Appcmd to add the handlers. I also wasn't able to choose FastCGI when adding the handler in the IIS Manager GUI. Removal of CGI from IIS components, a reboot, and re-adding CGI to IIS components allowed selection of FastCGI in the GUI and made it possible to complete the configuration steps.Here is a URL (note the complete URL is presented here as 2 lines) for another tutorial on the process with steps for both GUI and command line configuration: learn.iis.net/page.aspx/246/using-fastcgi-to-host-php-applications-on-iis7/
PHP 5.2.3 under IIS 5.1 (as ISAPI) and Windows XPIf you have trouble trying to get run the combination above using PHP installer please make sure that your executable path for .php file on IIS has been written correctly. Start-&Control Panel-&Administrative Tools-&Internet Information Services-& (then select your web site) -&Properties-&Home Directory-&Configuration-&Mapping and then change the Executable Path for .php files from C:\PHP\php5is~1.DLL to C:\PHP\php5isapi.dll
If you get this error: "Service Unavailable" after installing PHP to a Windows XP x64 Pro, and you followed all the instructions posted in this page, you may want to try checking the ISAPI Filters in your IIS.Make sure your a running the 32-bit version of the Microsoft.NET\Framework\v2.0.50727\aspnet_filter.dll.If you are running the 64-bit version, you will notice that liested item in the ISAPI Filters has a red arrow pointing down. This means that the service failed to load. Delete this item from the list and add a new one. Make sure you use the one located here: %Windows%/Microsoft.NET\Framework\v2.*\aspnet_filter.dll.Also make sure the permissions to your PHP folder have "NETWORK SERVICE", "IUSR_*", "SYSTEM" included.I hope this helps you saving some precious time
I installed php 5.2.3 using the msi package to Windows XP SP2. First time, ISAPI choice defaulted to installing php to c:\program files\php. The IIS Manager & Websites & Home Directory & Extensions used the short filename. Didn't work - message was "module not found". I then removed and installed to c:\php. That worked easily.
i have encountered always the same problem installing php on windows 2003 (it always worked fine with w2k) "php has encountered an access violation at xxxx". tried php5.x and downgrade to php4.x without success. problem was solved only by giving r+w+e permission on php folder to user IIS_WPG
I have found the following procedure to work correctly EVERY time for installing PHP version 5.x.x on Windows 2003 servers. (I have done over 100 of these on Web, Standard & Enterprise)1. Download the current PHP Zip file to a folder of your choosing.2. Download the old Installer.exe (I use 5.0.2)3. Run the installer and accept the defaults in all cases except the IIS server, choose IIS 6.0 or later. The installer will complain that a script map is not registered and ask you if you want to register it. SAY YES!!!4. Run the installer a *second* time, using the same settings as above. This time instead of the complaint that a script is not registered you should see a black dos box open and then close. This is your clue that the install was successful.5. Copy your PHP .zip file to c:\php and extract and overwrite all files from the regular installer.6. Edit c:\windows\php.ini to enable any extensions you may need and to set the extension directory to c:/php/extAll should be good to go. Test by running an info() from the web server.I have used this install on over 100 installs of 2003/IIS web servers. Generally they have been virgin installs, but a few have had existing sites on them. Using the above method I am able to install PHP in under 2 min. Of course, these are windows systems thus your mileage may vary.Note: I just tried to use the new .msi installer without success. Resorted to the above procedure and now have 5.2.0 running on the new server.Note2: PHP powers that be, please make a copy of the old installer available again somewhere easily found by people. I would be screwed if I had not kept an archive copy of the 5.0 installer.
Don't forget if you are getting ACL exceptions to reading the test php page you have created you MUST share the PHP directory or the resources PHP uses to "everyone" but remember use restricted access for security.
IIS 5: If you change the application mappings for PHP (for example, from CGI to ISAPI module), reboot after the change is made.& The PHP Application Mapping change may cause a conflict if ISAPI applications are cached.