Tuesday, October 25, 2011

Unable to download a .jad file hosted on IIS7

If you are trying to host a .jad file and are unable to download it on IIS7, you need to add the following Mime Type.

mime type: jad

text: text/vnd.sun.j2me.app-descriptor

 

How to Add a Mime Type

1. Go to IIS7

2. Select your website

3. Open Mime Types at the IIS section on the features view

4. On the top right corner there is a link to add

5. Input the details

File Name Extension: jad

MIME type: text/vnd.sun.j2me.app-descriptor

 

Funny its already done for .jar files. :)

HTTP Error 403.14 – Forbidden The Web server is configured to not list the contents of this directory FIX!

Setting up a website and keep getting this error

"HTTP Error 403.14 – Forbidden The Web server is configured to not list the contents of this directory”
Here is how to resolve the error. Actually Step 3 is the real true fix :).

1. create a website
 use this command
> %windir%\system32\inetsrv\AppCmd ADD SITE /name:MyNewSite /id:3 /bindings:http/*:81: /physicalPath:c:\inetpub\mynewsite

Output:
SITE object "MyNewSite" added
APP object "MyNewSite/" added
VDIR object "MyNewSite/" added

2. run this command to install the ASP.net version you are running, in this case i was running v4.0

%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis -i

or

C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis -i

3. then change your new website's application's pool to 'DefaultAppPool'

4. Thats the only way to have that error sorted.

I would think that since you installed the ASP.net 4.0 from the command then when you assign it as the pool it should work, so now you still have to assign your application website application's pool to 'DefaultAppPool'. Anyway that's microsoft for you.

HTTP Error 403.14 – Forbidden The Web server is configured to not list the contents of this directory FIX!

Setting up a website and keep getting this error

"HTTP Error 403.14 – Forbidden The Web server is configured to not list the contents of this directory”
Here is how to resolve the error. Actually Step 3 is the real true fix :).

1. create a website
 use this command
> %windir%\system32\inetsrv\AppCmd ADD SITE /name:MyNewSite /id:3 /bindings:http/*:81: /physicalPath:c:\inetpub\mynewsite

Output:
SITE object "MyNewSite" added
APP object "MyNewSite/" added
VDIR object "MyNewSite/" added

2. run this command to install the ASP.net version you are running, in this case i was running v4.0

%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis -i

or

C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis -i

3. then change your new website's application's pool to 'DefaultAppPool'

4. Thats the only way to have that error sorted.

I would think that since you installed the ASP.net 4.0 from the command then when you assign it as the pool it should work, so now you still have to assign your application website application's pool to 'DefaultAppPool'. Anyway that's microsoft for you.

HTTP Error 503. The service is unavailable FIX!

Wake up one ealry morning, try accessing your website and you get this error "HTTP Error 503. The service is unavailable"

Well, someone/something stopped your default application pool.

How to restart the application pools.

1. Open IIS7

2. Expand your Server

3. Click on Application pools, just before your sites

4. Select the application pool to start, In this case its the default application pool.

5. Go to Application Pool tasks on the far right menu and start it.

Easy :)

HTTP Error 503. The service is unavailable FIX!

Wake up one ealry morning, try accessing your website and you get this error "HTTP Error 503. The service is unavailable"

Well, someone/something stopped your default application pool.

How to restart the application pools.

1. Open IIS7

2. Expand your Server

3. Click on Application pools, just before your sites

4. Select the application pool to start, In this case its the default application pool.

5. Go to Application Pool tasks on the far right menu and start it.

Easy :)