Saturday, September 21, 2013

Magento run on IIS and Installation

The purpose of this blog is to Magento install on IIS
  1. First download Microsoft Web Platform Installer 4.6 
  2. Install below application by web installer
    1. IIS
    2. URL Rewrite 2.0
    3. PHP 5.4.14 for IIS
    4. MySQL windows 5.1
  3. If you OS is 64 bit than replace below curl 64 bit in   C:\Program Files (x86)\iis express\PHP\v5.4\ext
  4. Download Magento from here
  5. Copy Magento folder in C:\inetpub\wwwroot
  6. Browse Magento application by IIS. There is like on right site.
  7. Below image will come as install Magento. You have to choose location, Time Zone and Default Currency.
  8. If you will get error of rewrite error. Please set user permission

  9. Configuration step, enter details as below and take care while entering table prefix and create database in MySQL
  10. Follow Below steps while using “Create Admin Account”
  11. If you are not able to login with your user name and password on admin panel than please modify your code  as per below step
    1. Go to Magento\app\code\core\Mage\Core\Model\Session\Abstract
    2. Open the file Varien.php
    3. Remove  call_user_func_array(‘session_set_cookie_params’, $cookieParams); line
    4. Update below method
  12. Please add web.config file at magento root folder for URL rewrite and update Use Web Server Rewrites setting from  System-> Configuration->Web   
  13. If you are getting error of “Exception printing is disabled” than please follow below step
    1. Locate the root directory where your Magento is installed. Search for “errors” directory.
    2. Change the filename of local.xml.sample to local.xml
    3. Reload the page where it shows error message, you will see a full list of error message – The purpose of rename local.xml is to allow the full error message to be shown.
    4. Now, locate magento_directory/lib/Zend/Cache/Backend/File.php and look for:
    5. Now, go to Magento root directory and create a new directory with the name “tmp”.
    6. Refresh the error page and see if the issue solved.