IIS error: duplicate set items with the type of "mimemap" cannot be added when only the unique set parameter fileextensionlistener is set to pai.mp4.

Original http://www.cnblogs.com/zsz417/archive/2011/10/18/2216442.html

Previously, we added support for MP4 and other file types in the configuration of a site. After reinstalling the system, we found thatCodeAn error is reported. The error content is the title. The details are as follows:

 

The problem is that you need to add these settings to each machine, which is not conducive to team collaboration. Therefore, you have to embody these changes in the Code. The specific implementation method is as follows:

Added

?

1234567

<Staticcontent> <Mimemap fileextension = ". MP4" Mimetype = "Video/MP4" /> <Mimemap fileextension = ". M4a" Mimetype = "Video/MP4" /> <Mimemap fileextension = ". M4v" Mimetype = "Video/m4v" /> <Mimemap fileextension = ". OGV" Mimetype = "Video/Ogg" /> <Mimemap fileextension = ". Webm" Mimetype = "Video/webm" /> </Staticcontent>

After modification, the Service continues to run normally.

Not long ago, my computer C disk space was insufficient. After several tossing times, I had no choice but to reload the disk, and allocated a lot of space to the C disk. The system also changed to 64-bit. If you re-run the website today, an error is returned:

Configuration error: When the unique parameter fileextensionsetting is set to ipv.mp4, duplicate set items of the "mimemap" type cannot be added.

What's strange is that the Code is still running normally on another machine, So Baidu asks for the answer. Cloud IIS applicationsProgramIf the pool is in the integration mode, you can change it to the classic mode, but it will not work after you try it.

Of course, Google has also checked it. This time it is strange that Google cannot find it (some keywords are blocked again ?).

At this time, I thought about how to solve it myself. It seems that the extension settings are repeated. In this case, you can delete the field configuration, find that the program runs normally, and still support the. MP4 file.

It turns out that iis7.5's default file extension support has increased, and what's worse is Baidu's various interpretations. No such solution has been mentioned.

However, to be consistent with everyone, a redundant configuration is added here:

?

1234567

< Staticcontent > < Remove Fileextension = ". MP4" /> < Remove Fileextension = ". M4a" /> < Remove Fileextension = ". M4v" /> < Mimemap Fileextension = ". MP4" Mimetype = "Video/MP4" /> < Mimemap Fileextension = ". M4a" Mimetype = "Video/MP4" /> < BR > ...... </ Staticcontent >