opa11.dat - associated with Windows Media Player

[Hoib]

Hi -

I'm on an AMD64 desktop with Win XP Pro SP2. I've been trying to update MS
Excel 2003 with the latest security fix KB923088. Getting a 1406 error
about halfway through the update. On the MS site, among other things,
Method 4 suggests checking your Office Activation datastore stored in
OPA11.DAT. You are to pull up the properties sheet and adjust some
permission settings on the Security Tab.

When I navigate to OPA11.DAT, I see the file is associated with Windows
Media Player 10 because it's icon is the typical round-multi-colored disc
you'd see for a multimedia file and its type is listed as a "Video CD Movie"
over in the right hand pane. In fact I just noticed as you'd expect that
somehow all the .DAT files have that association. Back to OPA11, not only
is the association messed up but the properties panel has NO Security Tab
for me to open and adjust. I've got to figure out how to get that
association changed back to whatever association (no association???) should
be effective so I can reveal the security tab and change the permissions. I
note too that my other older Win XP Pro PC has the same goofed up
association.

Anyone know anything about this? I've Googled it and am coming up with a
lot of entries but nothing specific on how to revert this association.

H

 

[Rick Rogers]

Hi,

Control Panel/Folder Options/File types tab, simply delete the .dat file
association. Those files, by the way, shouldn't have any associated programs
as they can be used by many different programs.

As to the security tab, in a Pro system you must undo simple file sharing
under Folder Options/View for it to show. In a Home system, you must restart
in Safe mode and use the Administrator logon to see it. If you feel that you
are somewhat technically proficient, you could also use cacls from a command
prompt.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org

 

[Hoib]

How very interesting!!! I learn something every day! Thank you, Rick.

As it turns out, it's not the answer anyway, but of course, I had to check
it to be sure. Permissions are set "wide open"... so whatever is bothering
the install, it's something else. Back to the KB to look some more...

H