Community discussions thread release to the install, upgrade & configuration for the PKS August 2009 Release

Looking forward to a great exchange of ideas and feedback!

View the PKS Overview Beta Podcast

~ Happy Podcasting ~

Release Features

• PKS Media Encoder Service
  • Added Support for Microsoft Expression Encoder 3
• User Interface
  • Updated Network File Store Control Design
  • Updated Silverlight Player Skin Enabling Silverlight 3 Support
• Mashup Webparts
  • Added Web Part for Surfacing Podcast Meta Data on Other SharePoint Sites 

Known Issue(s)

• When upgrading, after the install a duplicate set of "<controls> </controls>" remains in the web.config, delete the tags and reset IIS.
• Unable to set links as the primary file during upload, if links are set as the primary file the PodcastDetail.aspx page will not render correctly.

I can't get the Media Encoder service to start after performing the upgrade steps. I get the following error:

Event Type:    Error
Event Source:    MediaEncoderService
Event Category:    None
Event ID:    0
Date:        9/10/2009
Time:        1:03:11 PM
User:        N/A
Computer:    {computername}
Description:
Service cannot be started. System.NullReferenceException: Object reference not set to an instance of an object.
   at MediaEncoderService.MEConfigWebService.GetValueByKey(String key)
   at MediaEncoderService.MediaEncoderService.MonitorFileSystem()
   at MediaEncoderService.MediaEncoderService.OnStart(String[] args)
   at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

The paths in the configuration are all the same as I set up for the July version.

Incomplete configuration strikes again.

The .config file for the media service isn't retained between versions. This should probably be noted in the upgrade instructions, or setting it could be incorporated in the service's setup (similar to requesting the user account).

Our install in not part of an upgrade but is a new install and we are also experiencing the same error as reported by an earlier poster.  Does anyone have addtional suggestions on how I might troubleshoot this?

Is this a .NET issue?  Please advise.  Thank you!

Log Name:      Application
Source:        MediaEncoderService
Date:          11/17/2009 10:34:25 PM
Event ID:      0
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      computername.domain

Description:
Service cannot be started. System.NullReferenceException: Object reference not set to an instance of an object.
   at MediaEncoderService.MEConfigWebService.GetValueByKey(String key)
   at MediaEncoderService.MediaEncoderService.MonitorFileSystem()
   at MediaEncoderService.MediaEncoderService.OnStart(String[] args)
   at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MediaEncoderService" />
    <EventID Qualifiers="0">0</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-11-18T04:34:25.000Z" />
    <EventRecordID>5831</EventRecordID>
    <Channel>Application</Channel>
    <Computer>computername.domain</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Service cannot be started. System.NullReferenceException: Object reference not set to an instance of an object.
   at MediaEncoderService.MEConfigWebService.GetValueByKey(String key)
   at MediaEncoderService.MediaEncoderService.MonitorFileSystem()
   at MediaEncoderService.MediaEncoderService.OnStart(String[] args)
   at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)</Data>
  </EventData>
</Event>

• Update: 11/18/09  Well, the service Media Encoder service started successfully after updating the registry with the disableloopbackcheck entry Reference Technote 896861 http://support.microsoft.com/kb/896861 and restarting the server afterward.  Maybe the restart resolved the issue -nevertheless wanted to provide and update on this. Thanks!