My laptop is getting slow when I run IIS7 and CF9. Honestly, the physical memory of my laptop is just 2G and happening so because of lack of memory. That's why I need to remove IIS7 and install Apache as my web-server. Before installing Apache in window 7, I though it's difficult to install and configure because my OS is window. As we all know, the configuration setting in Apache isn't same as IIS because IIS GUI is quite nice for developers and don't need to configure like add codings in Apache. In Apache, it's a bit messy but I can cool.

Here is the instruction guide of Installation Apache.

1) Download Apache installer

You can download installer under this link Download Apache Installer. For me, my downloaded file is httpd-2.2.17-win32-x86-no_ssl.msi.

2) Install Apache

Install Apache. When you reach the following screen (Server Information)

[More]

This entry was posted on March 25, 2011 at 10:53 PM and has received 4365 views. There are currently 2 comments. Print this entry.

Today I need to install brand-new server so-called window 2008 r2 for Coldfusion multiple-instances. Hardware developer installed only OS and IIS for me. As for me, I need to install Adobe Coldfusion 9 for multiple instances. Installing Adobe Coldfusion 9 is very simple. And I've done step by step installation. Once finished installation, normally Adobe Coldfusion 9 configuration will be come out instead of 404 Error screen as follow.

[More]

This entry was posted on December 15, 2010 at 5:27 PM and has received 3317 views. There are currently 0 comments. Print this entry.

Recently, I've installed Railo on IIS7. Why I need to install Railo? Because, I'm not rich enough to buy Adobe Coldfusion 9 installer for my personal Development. Even Developer Edition isn't complete enough for me what I want to develop. That's why I decided to install Railo on my pc. I'll guide step by step screen-shot explanation.

1) Download Railo under this website. http://www.getrailo.org/index.cfm/download/

2) Install Railo to C:\Railo\

Because, they already wrote not to install Railo in a directory containing space.

3) Need to enable 32 bit application on your IIS 7. if your window system type is 64bits, you can skip this step. 

4) Need to define Handler Mappings. Server > Sites > Default Website. You will see following screen and Click on Handler Mappings.

After clicking, click on Add Script Mapping which located on the top of the right side. After that, you will see one following Dialog-Box. And fill all needed information as follow.

5) Need to add Extension on ISAPI filters. Server > Sites > Default Website. You will see following screen and Click on ISAPI Filters.

After clicking on ISAPI Filters, you will see Dialog box and fill all needed information as follow.

6) Go to C:\Railo\conf\ and create file name as host.xml. And write following coding in this file.

Configure as above message, you can browse Railo Admin as follow : http://localhost:8600/railo-context/admin/server.cfm 

Enjoy it...!!!

Best credit to  : http://groups.google.com/group/railo/browse_thread/thread/949b8156e4006e3c/0f6e1493906da575?lnk=gst&q=railo+on+IIS#0f6e1493906da575

This entry was posted on September 16, 2010 at 5:19 PM and has received 5484 views. There are currently 7 comments. Print this entry.

Today, I need to configure coldfusion9 multi-instance in window 2008. It's my first time to do in my developer life. In this case, my  so-called senior showed me how to configure multi-instance in window 2008. I don't know how's complicated in CF7 and CF8. But in CF9, it's quite easy if you know that. Ok, let's go. First of all, you need to choose number two option (multiserver configuration) when you start installing CF9. Then, proceed as usual installation. After installing, open Coldfusion administration. Scroll down left-side bar and go to ENTERPRISE MANAGER > Instance Manager. After that, click on New Instance Button regarding following screen (screen - 1).

After that, Add New Coldfusion Server form will be came out. And fill all needed information like following screen (screen - 2). Server Name is your new instance name. Just give "Demo" as your new instance name.  Server Directory is where you want to put your application folder. I think, the rest information are just optional.

After creating new instance, open IIS and get ready to create new website (screen - 3).

After that, you need to fill all needed information for new website as following screen (screen - 4). In this screen, just give "Demo" as your new website name. For Physical Path,  choose the path where you stored your application folders. Then you need to assign Port. Default port is 80 but oddly you can't use this port because default website is already used this port number. So you need to choose another port 81 as example.

After that, go to Start Menu and find Web Server Configuration Tool. If you can't get it into Start Menu, go like following hierarchy Start Menu > All Programs > Adobe > Web Server Configuration Tool (screen - 5).

After that, you will get following screen (screen - 6). In this screen, you will get Web Server Configuration box then click Add button.

Then, you need to fill all needed information into this box (screen - 7). You don't need to change for JRun Host. JRun Server dropdown, you will see "Admin", "Cfusion" and "Demo". You need to choose "Demo" because it's either your new instance or new website. In Web Server, you don't need to choose other web servers because you will need to use IIS as our Default Web Server. In IIS Website, you will see "All" and "Demo". In this case, you need to choose "Demo" as your website. After that, click Ok button. After that, prompt will display that you need to restart your website. Don't worry click "OK" as restarting your website.

After After all, open your Internet Explorer and type "http://localhost:81" then your website will be coming up smoothly. And, open Task Manager and to go Process tab, then will see new process is running as your website. How's easy.!! Special thanks to Mr_Nil who also guide me about that.

This entry was posted on April 23, 2010 at 7:28 AM and has received 1872 views. There are currently 0 comments. Print this entry.

Today is my first time to install Coldfusion 9 into Window 2008 server. When I was in myanmar, to install cf8 in window 2000 or 2005 is quite easy to install and to configure website in older IIS. In window 2008, everything are new such as IIS, security and so on. So, I need to install cf9 into 2008. After installing in window 2008, everything is so smooth. Once I browse Coldfusion Administrator, I encounter the weird problem. That's Internal Server Error like following image.

That's why I browse for seeking some solution how happen like that. This 500 status code most likely causes:

• IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred.
• IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly.
• IIS was not able to process configuration for the Web site or application.
• The authenticated user does not have permission to use this DLL.
• The request is mapped to a managed handler but the .NET Extensibility Feature is not installed.

That's why I think of it might be cause of whether my window's system type or not. So, I decided to empathize to solve this system type. Lately, I found that I need to "Enable 32-bit applications" to "true".

After change it, everything is as smooth as lace now..!!

This entry was posted on April 14, 2010 at 7:28 AM and has received 1733 views. There are currently 0 comments. Print this entry.

In these days, using SSL layer at website is the most popular. Because, it's save, reliable and cannot be attacked by virus easily. Ok, I'll describe how to configure SSL in IIS 6. Create certificate First of all, open your Internet Service Manager (ISM) or Internet Information Services (IIS) Manager.

Double click on your sever, and expand all websites configured in your Server.

Open one website and click properties on it. And click on Directory Security tab, then click on Server Certificate.

At that time, Web Server Certificate Wizard box will appear, and then click Next. Then, choose Create a new certificate. Then, click next. And, give your certificate name in textbox, and then click next again.

And, type your organization name and unit. Then, type the common name for your site. And, choose Country, State and City.

And, choose the directory where you want to save your certificate file. Then, click next, and click on finish button. Install the certificate and set up an SSL Web site Open the IIS, and expand websites configured at your server. Click on the website, you want to install certificate.

Click the Directory Security tab. Under Secure Communications, click Server Certificate. This starts the Certificate Installation Wizard. Click Next to continue.

Select Process the pending request and install the certificate and click Next.

Type the location of the certificate that you downloaded in the "Issue and download a certificate" section, then click Next. The Wizard displays the Certificate Summary. Verify that the information is correct, then click Next to continue.

Click Finish to complete the process.

Configure and test On the Website, type 443 on SSL Port.

On the Directory Security tab, under Secure Communications, note that there are now three available options. To set the Web site to require secure connections, click Edit. The Secure Communications dialog box appears.

Select Require Secure Channel (SSL) and click OK.

Click Apply and then OK to close the property sheet. Surf your site Access the site through HTTP by typing http://localhost/yoursite/ in the browser. You receive an error message that resembles the following:

HTTP 403.4 - Forbidden: SSL required.

Try to browse to the same Web page using a secured connection (HTTPS) by typing https://localhost/yoursite in the browser. You may receive a security alert that states that the certificate is not from a trusted root CA. Click Yes to continue to the Web page. If the page appears, you have successfully installed your certificate.

Try it.

Big Credit : http://support.microsoft.com/kb/299875

This entry was posted on February 3, 2010 at 6:32 AM and has received 780 views. There are currently 0 comments. Print this entry.

If you're being web-developer using Microsoft platform, you must know the status code of IIS. Here you go.

HTTP

1xx - Informational

These status codes indicate a provisional response. The client should be prepared to receive one or more 1xx responses before receiving a regular response.

• 100 - Continue.
• 101 - Switching protocols.

2xx - Success

This class of status codes indicates that the server successfully accepted the client request.

• 200 - OK. The client request has succeeded.
• 201 - Created.
• 202 - Accepted.
• 203 - Non-authoritative information.
• 204 - No content.
• 205 - Reset content.
• 206 - Partial content.
• 207 - Multi-Status (WebDav).

3xx - Redirection

The client browser must take more action to fulfill the request. For example, the browser may have to request a different page on the server or repeat the request by using a proxy server.

• 301 - Moved Permanently
• 302 - Object moved.
• 304 - Not modified.
• 307 - Temporary redirect.

4xx - Client Error

An error occurs, and the client appears to be at fault. For example, the client may request a page that does not exist, or the client may not provide valid authentication information.

• 400 - Bad request.
• 401 - Access denied. IIS defines several different 401 errors that indicate a more specific cause of the error. These specific error codes are displayed in the browser but are not displayed in the IIS log:
  • 401.1 - Logon failed.
  • 401.2 - Logon failed due to server configuration.
  • 401.3 - Unauthorized due to ACL on resource.
  • 401.4 - Authorization failed by filter.
  • 401.5 - Authorization failed by ISAPI/CGI application.
  • 401.7 – Access denied by URL authorization policy on the Web server. This error code is specific to IIS 6.0.
• 403 - Forbidden. IIS defines several different 403 errors that indicate a more specific cause of the error:
  • 403.1 - Execute access forbidden.
  • 403.2 - Read access forbidden.
  • 403.3 - Write access forbidden.
  • 403.4 - SSL required.
  • 403.5 - SSL 128 required.
  • 403.6 - IP address rejected.
  • 403.7 - Client certificate required.
  • 403.8 - Site access denied.
  • 403.9 - Too many users.
  • 403.10 - Invalid configuration.
  • 403.11 - Password change.
  • 403.12 - Mapper denied access.
  • 403.13 - Client certificate revoked.
  • 403.14 - Directory listing denied.
  • 403.15 - Client Access Licenses exceeded.
  • 403.16 - Client certificate is untrusted or invalid.
  • 403.17 - Client certificate has expired or is not yet valid.
  • 403.18 - Cannot execute requested URL in the current application pool. This error code is specific to IIS 6.0.
  • 403.19 - Cannot execute CGIs for the client in this application pool. This error code is specific to IIS 6.0.
  • 403.20 - Passport logon failed. This error code is specific to IIS 6.0.
• 404 - Not found.
  • 404.0 - (None) – File or directory not found.
  • 404.1 - Web site not accessible on the requested port.
  • 404.2 - Web service extension lockdown policy prevents this request.
  • 404.3 - MIME map policy prevents this request.
• 405 - HTTP verb used to access this page is not allowed (method not allowed.)
• 406 - Client browser does not accept the MIME type of the requested page.
• 407 - Proxy authentication required.
• 412 - Precondition failed.
• 413 – Request entity too large.
• 414 - Request-URI too long.
• 415 – Unsupported media type.
• 416 – Requested range not satisfiable.
• 417 – Execution failed.
• 423 – Locked error.

5xx - Server Error

The server cannot complete the request because it encounters an error.

• 500 - Internal server error.
  • 500.12 - Application is busy restarting on the Web server.
  • 500.13 - Web server is too busy.
  • 500.15 - Direct requests for Global.asa are not allowed.
  • 500.16 – UNC authorization credentials incorrect. This error code is specific to IIS 6.0.
  • 500.18 – URL authorization store cannot be opened. This error code is specific to IIS 6.0.
  • 500.19 - Data for this file is configured improperly in the metabase.
  • 500.100 - Internal ASP error.
• 501 - Header values specify a configuration that is not implemented.
• 502 - Web server received an invalid response while acting as a gateway or proxy.
  • 502.1 - CGI application timeout.
  • 502.2 - Error in CGI application.
• 503 - Service unavailable. This error code is specific to IIS 6.0.
• 504 - Gateway timeout.
• 505 - HTTP version not supported.

http://support.microsoft.com/kb/318380/

This entry was posted on May 20, 2009 at 6:32 AM and has received 1323 views. There are currently 0 comments. Print this entry.