WordPress 2.1 Image Upload Problem May 5, 2008
Posted by scoopseven in IIS, WordPress.add a comment
After upgrading to Fast-CGI, my WordPress 2.1 image upload tool started asking for a password every time a image was uploaded. Turned out to be a permissions issue with WP/Fast-CGI-IIS that was solved by following the steps below from Joseph Scott’s Blog.
- Edit upload_tmp_dir option in php.ini. In my case I created an uploads folder in the wwwroot: upload_tmp_dir = “c:\inetpub\wwwroot\uploads”
- Create the c:\inetpub\wwwroot\uploads folder and grant the IUSR full control of it
- Create the uploads folder in your wp-content folder, for me this was in c:\inetpub\wwwroot\wordpress-trunk\wp-contents\uploads, then grant the IUSR full control of it
- Restart the IIS service (to pick up the php.ini change)
IIS 6 Timeouts – or not timing out – doesn’t timeout – the damn timeouts don’t work! February 26, 2008
Posted by scoopseven in IIS.add a comment
When IIS acts up, and won’t timeout requests. When IIS Tracer keeps saying Preproc Headers, and the requests pile up and never finish. When you’d love to kick IIS in the head because requests won’t time out. When IIS 6 requests don’t time out. (I tried really hard here people!) Check the IIS 6 Metabase. Make sure you’ve enabled IIS so that you can edit the MetaBase directly (It’s in /system32/inetsrv/MetaBase.xml) and check for these three line items.
HeaderWaitTimeout=”30″
ConnectionTimeout=”240″
MinFileBytesPerSec=”240″
The first two settings are in seconds. The third is explained by M$ as… “The time-out period is calculated by dividing the size of the entire response (including headers) by the value of the MinFileBytesPerSec property to obtain a maximum allowable response time, in seconds. For example, a 2-KB response (2,048 bytes) is allowed 8.5 seconds to complete if MinFileBytesPerSec has the default value of 240 bytes per second.” Great. More details on these settings can be found here.
Make sure you check these setting immediately as problems start to appear. I’ve had the MetaBase file revert back to defaults as a result of changing configurations in IIS, changing/editing application pools and who knows what else. Also, after these settings have been changed/edited/added in the MetaBase, reboot. They don’t seem to kill any already running requests or take effect unless the computer is rebooted.
XML Parsing Error IIS IE Firefox Coldfusion February 12, 2008
Posted by scoopseven in ColdFusion, IIS.add a comment
While loading a page in my browser, IE or FireFox, I kept getting this odd error message… “XML Parsing Error – Not Well Formed”. The odd thing was that I was loading a HMTL page, no XML. I tried changing the DocType tag, making my Javascript XML complaint (duh!) and I could not get this error to go away. I read something re: ASP causing the problem, so I disabled that in IIS, nothing. Turns out in a background process, I was calling a web service where the following code was used.
<cfheader name=”Content-Type” value=”text/xml; charset=utf-8″>
So CF had my browsers thinking that my non-XML / HTML page was in fact XML. Easy fix, I just added this tag as the first line in my HMTL page:
<cfheader name=”Content-Type” value=”text/html”>
And the world was right again 
Http keep-alives January 23, 2008
Posted by scoopseven in IIS.add a comment
I’ve been trying to read about iis type problems. I’ve read a bunch about keep-alives, and don’t totally understand ‘em. Anyway, here is a thread of general cf interest:
http://www.codefund.com/505/slow-response-on-static-content-5058292.shtm
also interesting… but of no direct value
http://www.alagad.com/files//dmfile/caseReport.html
ah-ha ah-ha … maybe a point in here:
(talks about optimization, but made an interesting point about -size- of requests and cookies etc. I’ll bet we are now returning huge requests for every object, and we might be able to sizably streamline them – especially from the newsletters if we think hard enough about it.)
Updating CFMX 6.1 January 2, 2007
Posted by scoopseven in ColdFusion, IIS.add a comment
Hotfixes since 6.1 Updater http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=b3a939ce
Newest supported JVM 1.4.2_05
http://java.sun.com/products/archive/j2se/1.4.2_05/index.html
for those having troubles installing a new JRE (like I did): With MX 6.1 you have to install the whole SDK, not only JRE, because ColdFusion needs a ‘Hot-Spot JVM’ which is not included in the JRE. If you only install the JRE and change the path in jvm.config to the new location, ColdFusion will start with an ‘error 2′ and you’ll get an errormessage in {CFMX root}/runtime/logs/default-err.log like ‘Error: no `server’ JVM at c:/Program Files…’ -Posted By Juerg Anderegg | 5/15/04 7:35 AM on Forta.com
STEPS:
1) Install Java SDK
2) Update the java.home path in jvm.config (rather than cfadmin) to point to new JRE
3) Apply ColdFusion 6.1 Updater
4) Apply Hotfixes
- Hot fix available for null, null errors ( Article b3c51ba1 )
- Hot fix available for cfchart output not displaying with IIS 6 ( Article 38824ea2 )
- Hot fix for client variables ( Article 19590 )
- Hot Fix to upgrade web server connectors ( Article 238944b1 )
- Hot fix to resolve slow memory leak when enabling Debug Logging ( Article 1ea55f4a )
- Hot fix to upgrade DataDirect Sequelink ODBC Server to version 5.4 ( Article e917887 )
- Hot fix for cfdump throwing unknown type error for cfcatch structure ( Article 1a9c83c )
- Hot fix for ColdFusion not responding to requests ( Article 19536 )
- Hot fix for ColdFusion Administrator navigation frame on an SSL site ( Article 19597 )
