Brad's profileSharePoint BlogPhotosBlogLists Tools Help

Blog


    October 26

    wmpnetwk.exe running at maximum CPU...

    When I realised I could put my wife's computer to good use and stop her nagging me about how the videos on the Media Centre were not appearing, I thought all of my christmases had come at once. So I kicked off the indexing of the file shares 3 nights ago, and ahhhh.... blissful silence for a day... then

    "Hey Brad, have you done anything to my computer?"

    "Yep, It's serving media up to the Media Centre in the lounge room."

    "Well... I don't know what that means, but it's been running really slow for a day now. Can you have a look at it?"

    *sigh...* "OK"

    Sure enough, there's a process running on it called wmpnetwk.exe that's using all the available juice. There's plenty of information around about the root cause (corrupt media files) and some solutions (uninstall - actually I was hoping for a real solution).

    As most of the people creating the links above will testify, it ends up that WMP is trying to index a corrupt AVI file. but how do you find it? You could use the SYSInternals tools, but there's an easier way...

    Clear the index from the WMP having problems (It's done here - C:\Documents and Settings\<Your login name>\Application Data\Microsoft\Media Index - If you are running vista, then it's C:\Users\<your login name>\AppData\Local\Microsoft), kick off a new index, and see where it stops. The system indexes alphabetically by folder, so if you add the path to the column headings in the video library and order by the path, you'll see the last file successfully indexed. the one after that has a problem. Run it for yourself and see... in my case, I had a 700MB video file that lasted for 35 seconds.

    Killed the WMPlayer and WMPnetwk processes, Deleted the corrupt videos, reindexed, done.

    Brad

    October 25

    Indexing Network Shares thru Media Centre (or for Americans, Center)

    Had some interesting challenges with Media Centre. Most of which I have not blogged about as I've normally found the answer on The Green Button or XP Media Centre, but this one I thought I might, as I think others might be in the same boat and I don't think the solution has been found yet.

    Have you ever tried to share media from your Windows Server to your Media Centre? You can't. Server 2003 or 2008 - neither of them work natively. First a quick rundown on my setup:

    • Windows Vista Ultimate, running Media Centre in the lounge room
    • Windows 2008 Server, storing the media files (My Computer)
    • Windows XP (My Wife's computer)

    I'm using TVersity to share my media from my 2008 Server to my xBox 360. I can't use TVersity to stream media to the Media Centre in the lounge room, because I need to have Vista Media Centre running on both the source and target to do so (There's no MCE 2008 Server). I have looked for a hack or a workaround, tried to copy, deploy and start the required services from a Vista machine to the server, nothing. I have looked at security and reduced it so much that blind freddy could access them as long as he was jacked into the network.

    The Solution? Index the files in the library of my wife's XP computer, running Media Player 11. Don't ask me why it works. It seems that not only does MC need access to the files, it also needs to have them indexed and shared as part of WMP 11 - even if they are not on the same computer, it works.

    Of course, then I hit another problem... but that's the next blog entry... :)

    Brad

    October 24

    First time using SQL 2008? Midnight trap for young players... and me

     

    So I had a client coming over to do some integration work tomorrow (which is now later today) and I had to get SharePoint set up, pointing to their domain. Pfffft no problems, I'll do it just before I go to bed. That was about 6 hours ago now...

    I have a stab at the install... What's this?

    System.Security.Principal.IdentityNotMappedException

    Hmmm... Security. Okay, no problems. It's a VM, running on VMWare over Fedora. It's probably got a dodgy time on the DC. Sure enough, the time's out by about 20 hours. So I bring it back inline, run my script to tell it to get the time from the internet and have another crack.

    Same problem. Okay... what if I just use a local account to run the connection to the local database? That takes the DC out of the equation... but I know it'll bite me later on... oh never mind.

    Same problem. It's now well after midnight and my only friend is the quiet hum of the fridge compressor. Okay, what if it's something to do with the SQL settings? I'm running SQL 2008 Dev edition...

    Aha! Named Pipes and TCPIP are turned off. How is a web app going to communicate with a SQL server no matter where it is except over TCPIP? Sure enough, turning it on did the trick... and changed the error message :) But it's an easy one, and unrelated to this - so if you need the settings, they are here -

    Crack open SQL Server Configuration Manager and drill down to:

    SQL Server Network Configuration
    L>Protocols for MSSQLSERVER

    On the right you will see the services, enable the ones you need. finally, go to the SQL Server Services Folder and restart the server service to have the changes take effect.

    Done!

    Brad

    PS - the error code snip's below to help Google index it and lead other people here looking for the light. This error doesn't appear much in the ones I saw...

     

    10/24/2008 03:12:03  8  INF                      Creating a new farm with config db SharePoint_Config content db SharePoint_AdminContent_f257f33b-5879-4676-bce4-e2b58416c2c6 server hv102 for farm mode
    10/24/2008 03:12:17  8  ERR                      Task configdb has failed with an unknown exception
    10/24/2008 03:12:17  8  ERR                      Exception: System.Security.Principal.IdentityNotMappedException: Some or all identity references could not be translated.
       at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess)
       at System.Security.Principal.NTAccount.Translate(Type targetType)
       at Microsoft.SharePoint.Administration.SPProcessIdentity.GetCurrentSecurityIdentifier()
       at Microsoft.SharePoint.Administration.SPProcessIdentity.GetCurrentSid()
       at Microsoft.SharePoint.Administration.SPProcessIdentity.Update()
       at Microsoft.SharePoint.Administration.SPApplicationPool.Update()
       at Microsoft.SharePoint.Administration.SPWebApplication.CreateDefaultInstance(SPWebService service, Guid id, String applicationPoolId, IdentityType identityType, String applicationPoolUsername, SecureString applicationPoolPassword, String iisServerComment, Boolean secureSocketsLayer, String iisHostHeader, Int32 iisPort, Boolean iisAllowAnonymous, DirectoryInfo iisRootDirectory, Uri defaultZoneUri, Boolean iisEnsureNTLM, Boolean createDatabase, String databaseServer, String databaseName, String databaseUsername, String databasePassword, SPSearchServiceInstance searchServiceInstance, Boolean isPaired, Boolean autoActivateFeatures)
       at Microsoft.SharePoint.Administration.SPAdministrationWebApplication.CreateDefaultInstance