tech/music/movies/musings
Show MenuHide Menu

Tag: iis

Moving WordPress from wamp to iis

February 11, 2015

Tried to install using the Microsoft Platform installer but it was only installing MYSQL and failing on PHP setup. This was down to the environment being installed on, which was very locked down. The following error was being generated:

image

The only resolution bar lifting the restrictions on the IIS server being installed onto was to install PHP manually by following the instructions here:

http://php.net/manual/en/install.windows.iis7.php

Unfortunately there was an error after PHP install when trying to view PHP pages.  By trying to launch the php-cgi.exe exe on its own the error became apparent it was down to a missing Visual C++ Resdistributable, available to download below.

http://www.microsoft.com/en-us/download/confirmation.aspx?id=30679

So MYSQL and PHP are now configured on the new host server, the next steps involve moving over the WordPress site from the previous server. The entire WordPress site can be copied from its location on the Apache server folder, in my case this was:

C:\wamp\www\wordpress_site

to an IIS folder on the new host. Once copied IIS has to be configured and this is explained in detail here:

http://www.vsysad.com/2012/04/create-a-wordpress-blog-on-windows-server-2008-r2-iis-7-5-and-mysql/

Final step involves grabbing the MYSQL database hosting the current WordPress site. I used MYSQL dump for this and the following command:

$ mysqldump -u root -p myWordPressDB > myWordPressDB_scripted.sql

This .sql file then has to be run against the MySQL database on the new host. In advance of this if your domain name has changed when moving from old host to new host. Do a find and replace of old with new before running script on new host. Use the following command to run this script:

$ mysql -u [uname] -p[pass] [myWordPressDB] < [myWordPressDB_scripted.sql]

Hopefully your WordPress site is now available on the new host.

HTTP Error 404.3 – Not Found

December 11, 2011
The 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.

If you get this error enable ASPX in Control Panel as shown below:

404.3

Setting up IP Address restrictions on IIS7

January 13, 2011

This guide is very useful for setting up IP restrictions on IIS7. Thanks to Craig Tucker for providing this.

Creating and Configuring Web Sites in Windows Server 2003

November 29, 2010

Thanks to Mitch Tulloch for providing this starter guide for creating websites in IIS 6.0 running on Windows Server 2003.

Click here

IIS Host header names

April 2, 2010

Very useful feature to host several websites under one IP address in IIS, these directions are for IIS 6.0 only:

1.

In IIS Manager, expand the local computer, click the Web Sites folder, right-click the Web site for which you want to assign a host header name, and then click Properties.

2.

Click the Web Site tab.

3.

In the IP Addresslist, select the IP address that you want assigned to this Web site.

4.

Click Advanced.

5.

Under Multiple identities for this Web Site, select the IP address, and then click Edit.

6.

In the Host Header Value box, type the host header name (for example, www.contoso.com).

7.

Click OK twice.

Reference

Getting around limitations of IIS 5.1

March 4, 2010
  1. Increase the 10 concurrent connection limit

    Are you getting 403.9 “Access Forbidden: Too many users are connected” errors on an XP Pro website? You’re limited by default to 10 concurrent connections by design, but this can be increased. First, make sure your default windows script host is set to the console (cscript.exe) one.

     cscript //h:cscript

Next, let’s increase the connection limit to 40.

C:\Inetpub\AdminScripts\adsutil set w3svc/MaxConnections 40

Note that this is a hard-coded limit; it can’t be increased any further unless you like patching windows system files. You can, however, make the IIS connection timeout more aggressive so connections don’t last as long.

  1. Run more than one root website

    IIS 5.1 only allows one root website. This is fine if your websites run under subfolders:

     http://localhost/MyWebsite1
     http://localhost/MyWebsite2

But it’s kind of a pain if your websites must run as root, or need to be tested when running as root:

http://MyWebsite1/
http://MyWebsite2/

In that case, you’d have to edit your hosts file, and switch the default home directory for the default website. But there’s a better way. You can hack up multiple web sites in IIS 5.1 via command line tricks, or you can use this nifty little GUI utility which automates that for you. It works great– you’ll even see multiple websites show up in the IIS manager. But bear in mind that, unlike the server versions of IIS, only one website can be active at any given time.

 

REFERENCE:

http://www.codinghorror.com/blog/archives/000329.html

Configuring SMTP on IIS 5.1

February 18, 2010

Spent this morning trying to configure SMTP on IIS. Took some notes that may help to save you some time.

Before you begin it is best to check that the SMTP server is open for connections on the required port (usually 25):

Try this command: “o myISPsmtpServer 25”, this will tell you straight away if it is open?

If the port is open you can then proceed to configure SMTP on IIS to relay via your ISP’s SMTP Server.

1. Go to the Properties for the SMTP Service and go to Delivery -> Advanced
2. Put the name of your ISP’s SMTP server in the “Smart host” field (for example myISPsmtpServer)
3. Save that
4. Back on the Delivery tab, click on the Outbound Security tab
5. Click on “basic authentication” and specify the username and password you use to access your email.

Testing SMTP on IIS 5.1

February 18, 2010

It is possible to test SMTP on an IIS server by creating an email in .txt file and then pasting it into the C:\Inetpub\mailroot\Pickup\ folder.

The text file should contain something similar to this:

to:tbill@externaldomainname.com
from:testuser@internaldomain.com
subject:This is a test.

this is a test.

Make sure there are no spaces between each colon and the text afterwards or it will end up in the badmail folder. If the email is picked up without error it will  be in theC:\Inetpub\mailroot\Queue\ folder.

Reference:http://support.microsoft.com/?id=297700