Skip to main content

WMS9 Development

As one of my consulting services, I develop WMS9 server plugins. If any of you has ever tried to develop a plugin for the Microsoft Media Server, you know that there is very little documentation for it, and very little support.

Recently, one of my clients setup a new Windows Server 2003 Enterprise system and tried to deploy our plugins to it. As you can imagine, the plugins did not work. While the other Micorosoft supplied plugins worked, my plugins reported error 0xc00d157d. You should try to google for that error code to see what you find.

The WMS log console shows that my plugins are reporting a binding error, yet the popup error message reports that it's a .NET runtime version error. Which path to choose?

For about a week, both me and my client's IT staff looked feverishly for a fix. Sometimes they blamed my code, sometimes we cursed Microsoft, and other times we looked to the heavens ala Google searching. Nothing seemed to work.

When I tried using the fusion log viewer, and with a little super-user configuration, I discovered that the binding error should have been our investigation path. As it turns out, the shipped WMS9 installation has Microsoft.WindowsMediaServices DLL version 9.1.1.3842. I knew this from long ago b/c this update has been around for a long time, and I've avoided it to preserve compatibility with existing systems. I didn't know that Microsoft had decided to put this new version into its latest service pack.

The WMS DLL version that I've been using for the past 2 years is 9.0.0.3693. This was the cutting edge DLL back in the day when we first started deploying the plugins. This was also the version that came with the Platform SDK for Multimedia/WindowsMediaServices9.

What really chaps me is that I pay good money to be an MSDN subscriber. You would think that Microsoft would want to tell the developer world that they are scrapping the old Platform SDK DLL in lieu of a new one that will break compatibility with existing plugins. Then again, you would also expect Microsoft to police their WMS newsgroups and actually answer questions that are more involved than the typical "how do I write a logging plugin." Neither is the case with WMS development.

Popular posts from this blog

Clustered Foolishness

I had morning coffee with a well respected friend of mine recently. Aside from chatting about the usual wifery and family, we touched on the subject of clustered indices and SQL Server performance. A common misconception in the software industry is that a clustered index will make your database queries faster. In fact, most cases will demonstrate the polar opposite of this assumption. The reason for this misconception is a misunderstanding of how the clustered index works in any database server. A clustered index is a node clustering of records that share a common index value. When you decide on an index strategy for your data, you must consider the range of data to be indexed. Remember back to your data structures classes and what you were taught about hashtable optimizations. A hashtable, which is another way of saying a database index, is just a table of N values that organizes a set of M records in quickly accessible lists that are of order L, where L is significantly less than M. ...

Deadly Information

Remember back to 2006 when a young girl killed herself [1] , [4] after being tricked and harassed by a faux boy she found on the Web using MySpace. The trial against the faux boy, an adult woman (Lori Drew), did not result in prosecution for the death of Megan, much to the dismay of many.  Yet, today we read about another trial where someone is being accused of second degree murder because they may have mentioned something slanderous about another person who was later killed by a hit man [2] . In this case, though, the person on trial is a former FBI agent who was working deep cover to infiltrate organized crime. In both cases, someone released information to third parties that resulted in the death of another person.  Neither defendant in either of these cases actually committed the act of murder, though. In the case of the FBI agent, though, the murder charge is being taken seriously. Yet, in the MySpace slander case, the murder charge was not taken seriously. How are t...

Faster Climate Change

CNN reports that a WWF study has found that global climate change is happening faster than predicted in 2007 and that there will not be any arctic ice by 2013, or 2040. [1] Then it goes on to say that global sea level will increase by 1.08 meters by the end of the century, which is 2100, 92 years from now. Quite honestly, nobody really cares what is going to happen to the planet in 98 years. Why? Because in 98 years we (as humans) will either: (1) Obliterate ourselves because God told us to do it. (2) Eat eachother because there will no longer be any land available to grow crops and sustain living quarters for our 50 billion people. (3) Suffocate because our planet will no longer smell nice thanks to 50 billion people producing lots of solid waste in our oceans. (4) Leave the planet because there will no longer be enough fresh water to sustain our lives. Wait a minute. Consider (4) for a moment. Where can we get an abundance of fresh water TODAY? Anyone? Yeah, the arctic! It's goin...