Configuration error setting up Xbox 360 as media extender with Windows 7 media PC

Anonymous

Currently running Windows 7 x32.

Until recent update to XBox 360, all was working fine using 360 as a media centre extender.

Now fails and when I try to resestablish a connection a configuration error arises.

Network connection seems fine as I can still stream media fine to Xbox dashboard. Media centre seems to find and install extender OK, just fails at configuration.

Have tried with AV and fiewalls disabled (Karspersky) with no success.

Frustrating as was working fine, now the functionaility is lost.

ANy help would be greatly appreciated

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous

For months, I experienced a problem exactly like the one described here, but I've finally fixed it on my machine and I believe I've got to the core of it.

The fix (this is for Windows 7, may also apply to Vista):

Find your 'Users' folder (usually c:\users).
Under 'Users' folder, go to subdirectory 'Default\AppData\Local\Microsoft\Windows Live'.

Note: The directory may not exist, but I've seen the extender problem only on a computer that does have it.

Inside this directory, there are additional subdirectories (e.g. 'Bici' and 'SqmApi'). Inside, there are several files with .sqm extension. THE PROBLEM IS WITH .SQM FILE PERMISSIONS. Specifically, the profile service has no permission to access or copy the files when creating a new profile.
To fix the permission issue, perform the following actions on each of SQM files.

Note: Inheriting parent container permissions will grant Everyone read access to the files.

a. Right click on the file, select Properties.

b. Select Security tab, click on Advanced button

c. Select Permissions tab (selected by default), click on Change Permissions... button.

d. MARK THE CHECKBOX: Include inheritable permissions from this object's parent.

e. Press OK button several times to close all the dialogs.

Then, setup Media Center Extender per regular instructions.

While these steps successfully repaired my computer, they may not apply to every situation. My advice is to run the following diagnostics steps:

Use Control Panel to create a new user account.
Use 'Switch user' (or Log off/Log on) in an attempt to log into this new account. This attempt will fail (if not, you may have a different problem).
Examine 'Application' event log (under 'Windows Logs') for the relevant events.

On my machine, I've got several warnings with Event Id 1509 about the files that couldn't be copied from Users\Default to Users\TEMP due to access denied errors. These were .sqm files with incorrect permissions.

If you like this solution, you may also like our http://docs.com service ;-) The solution presented here can be found in a documenthttp://docs.com/AF1P.

0 comments

52 additional answers

Anonymous

2011-03-23T09:19:04+00:00

I had a similar problem and was getting Event ID 545. I was also getting numerous mcx-1 accounts being created. After trawling the Internet and many days of searching I resolved my issue by removing a piece of software called Trusteer Rapport.

This software is being recommended by many banks. It seems reading the posts that it causes many issues.

On removing it and cleaning out all my mcx-1 accounts (using the Adminsitartor account in Win 7), I tried again and all worked perfectly.

Hope this helps.
Was this answer helpful?

0 comments No comments
Anonymous

2011-03-31T01:25:37+00:00

My issue is that at first, windows 7 was reporting that I might have a firewall issue. I made sure all of my firewalls were shut down, and I plugged in my 1st laptop into the network to see if it made a difference (which it didn't).

Here's what the event viewer is reporting:

**-** <Event xmlns="**http://schemas.microsoft.com/win/2004/08/events/event**">

**-** <System>

<Provider Name="Microsoft-Windows-Media Center Extender" Guid="{7B7838A3-6562-4269-BB7A-97B0D9593882}" />

<EventID>536</EventID>

<Version>0</Version>

<Level>2</Level>

<Task>4</Task>

<Opcode>0</Opcode>

<Keywords>0x8000000000000000</Keywords>

<TimeCreated SystemTime="2011-03-31T00:28:07.548100700Z" />

<EventRecordID>117</EventRecordID>

<Correlation />

<Execution ProcessID="4392" ThreadID="4404" />

<Channel>Media Center</Channel>

<Computer>W7L02</Computer>

<Security UserID="S-1-5-21-2504983043-185075776-3049432315-1000" />

</System>

**-** <EventData>

<Data Name="Error">-2147023606</Data>

</EventData>

</Event>
Was this answer helpful?

0 comments No comments
Anonymous

2011-06-11T01:36:19+00:00

I had a similar problem and was getting Event ID 545. I was also getting numerous mcx-1 accounts being created. After trawling the Internet and many days of searching I resolved my issue by removing a piece of software called Trusteer Rapport.

This software is being recommended by many banks. It seems reading the posts that it causes many issues.

On removing it and cleaning out all my mcx-1 accounts (using the Adminsitartor account in Win 7), I tried again and all worked perfectly.

Hope this helps.

You star. you have just solved this for me. Who would have thought of that I have been searching for hours for a fix for this THANKYOU :)
Was this answer helpful?

0 comments No comments
Anonymous

2011-07-18T01:30:25+00:00

This worked for me.

I found this error in the event log every time I went through the steps to re-install the extender and couldn't get myself to believe that installing an XBOX360 as a media extender had anything to do with the a sqm file in that folder which is named to indicate SQM events for Live.

Man.

here is what was in my event log.

Windows cannot copy file \?\C:\Users\Default\AppData\Local\Microsoft\Windows Live\SqmApi\SqmData720896_00.sqm to location \?\C:\Users\TEMP\AppData\Local\Microsoft\Windows Live\SqmApi\SqmData720896_00.sqm. This error may be caused by network problems or insufficient security rights.

DETAIL - Access is denied.

So: always believe the event log! :-)
Was this answer helpful?

0 comments No comments