add the following to the web.config as follows:
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<system.webServer>
<security>
<requestFiltering>
<fileExtensions allowUnlisted="true" >
<remove fileExtension=".mdb" />
<add fileExtension=".mdb" allowed="true"/>
</fileExtensions>
</requestFiltering>
</security>
</system.webServer>
</configuration>
MIME Type must be registered on IIS
Simple, but a little hidden:
The Problem: You ftp a Silverlight App to an IIS website, go to the website in a browser, and get the following error:
Message: Unhandled Error in Silverlight Application
Code: 2104
Category: InitializeError
Message: Could not download the Silverlight application. Check web server settings
The Cause: The Silverlight Mime types (.xaml, .xap and .xbap) are not listed in that websites registered mime types, therefore IIS will not send those files to the browser.
The Solution: Open IIS on the server, go to HTTP headers, click on Mime Types, click “Add New” and add the following:
Extension – Mime Type
.xaml – application/xaml+xml
.xap – application/x-silverlight-app
.xbap – application/x-ms-xbap
Hit Apply and your application will load!
This is kind of an old issue, but since I mostly work on corporate projects, we’re a bit slow on adopting new versions of anything.
I ran into this issue with Microsoft Word 2007 documents, but the same error will occur with any other file type that isn’t properly configured on the web server.
Symptoms
Microsoft Word 2007 documents return a HTTP 404 error when users attempt to download the documents. The web server uses Microsoft IIS 6.0.
Cause
IIS does not have a wildcard mapping for unknown MIME types and the file type is not known to the web server. This prevents IIS 6.0 to serve the file.
Resolution
To resolve the errors, add the missing MIME types to IIS.
Instructions
1. Open IIS Management Console (via Computer Manager->Services and Applications->Internet Information Service)
2. Right click on “Web Sites”.
3. Choose Properties
4. Activate “HTTP Headers” tab
5. Click “File Types” button in the MIME Map groupbox
6. Click “New Type”
7. Enter the MIME type data from the below table
| Associated Extension |
Content type (MIME) (remove any spaces below) |
|---|---|
| docx | application/vnd.openxmlformats- officedocument.wordprocessingml.document |
| pptx | application/vnd.openxmlformats- officedocument.presentationml.presentation |
| xlsx | application/vnd.openxmlformats- officedocument.spreadsheetml.sheet |
Fiddler is a HTTP Debugging Proxy which logs all HTTP traffic between your computer and the Internet. Fiddler allows you to inspect all HTTP Traffic, set breakpoints, and “fiddle” with incoming or outgoing data. Fiddler includes a powerful event-based scripting subsystem, and can be extended using any .NET language.
Fiddler is freeware and can debug traffic from virtually any application, including Internet Explorer, Mozilla Firefox, Opera, and thousands more.
Homepage: http://www.fiddlertool.com/fiddler/
In this article we’ll walk you through the steps of creating FTP sites in Windows Server 2003 using both Internet Services Manager and scripts. The tutorial will also will explain how to perform common administration tasks involving FTP sites and also how to implement FTP User Isolation, a new feature of Windows Server 2003 enables users to have their own separate FTP home directories.
http://www.windowsnetworking.com/articles_tutorials/Creating-Configuring-FTP.html
Este comportamento poderá ocorrer se existir um conflito na porta do sistema. Por predefinição, o IIS utiliza a porta 80 para comunicações HTTP. Se uma aplicação diferente do IIS estiver a ser executada e a utilizar a porta 80 no mesmo endereço IP, poderá receber uma mensagem de erro ao tentar utilizar o gestor do IIS para iniciar o Web site.
Se usa  Skype(por exemplo) pode ou mudar as definições de ligação do Skype ou mudar as do IIS
No Skype vá a Ferramentas> opções>Ligação e desmarque a checkbox que diz Porta 80. Reinicie o skype.
How to install and configure PHP5 with IIS6 on Windows Server 2003 in five easy steps.
Permitindo endereços relativos significa que a sua aplicação poderá usar notações do tipo ..\ nas directivas #Include.
Se estiver actado pode constituir um risco porque um ficheiro Include pode constituir um risco fora da sua root.
No IIS 6.0 os endereços relativos já não estão activos por defeito.
read more
Home