Invalid access to memory location. Error Code: 0x800703e6

I'm running SBS 2003 sp1 / Exchange 2003 sp1 / ISA 2004 sp1

For no apparent reason Windows Media Services has begun reporting errors and
is failing to read or edit playlist SMIL files, or serve based on their
contents.

WMS was installed originally and it has been running fine for weeks.

In the MMC, any Publishing Point, on the Source tab:

Any playlists (*.wsx) set as the content source are suddenly not displaying
in the detail pane, and the playlist editor displays an error when it is
invoked from the button below the detail pane. The server also cannot play
the playlist any more.

Instead of seeing an expandable tree-view of the contents of the SMIL file,
it simply shows one line looking like this in the left tree-view pane:

-- [icon] Playlist_name.wsx

If we press the Playlist Editor button to call up the editor it displays the
New/Open dialog, but after selecting our choice a message box is displayed:

--------------------------------------------------------------------------------
Windows Media Services

[X icon] Error Description: Invalid access to memory location.
Error Code: 0x800703e6

[ OK
--------------------------------------------------------------------------------

There is no corresponding entry in the Event Log.

The editor window now appears, but each time we add a new element the error
message shown above appears.

However, if we run wmseditor.exe from its folder

C:\WINDOWS\system32\windows media\server\admin\mmc\wmseditor.exe

it works fine, and can load and work with the playlists that the MMC console
is unable to show.

then uninstalled WMS from Add/Remove Programs->Windows Components.
and reinstalled WMS and the problem persists

-John

 

Hello John,
More a question rather than a solution,
I might have missed something if playlists are now supported on the Server,
I'm more familiar with playlists stored client-side.

I am familiar with the general use of Windows Media metafiles, and WVX and
WAX are common file extensions for those. Conceivably if a number of media
files are loaded into the metafile, it becomes a "playlist." Considering that
there is no real restriction on how to name metafiles, I'm wondering if your
WSX are the same thing (which would mean we'd be talking about the same
thing).

If so, then I'd recommend simply deleting and re-making your Publishing
Points. I haven't had to do it more than a few times over the years, but it
happens. Have you installed any recent Service Packs or patches which might
have affect Windows Media Services? - I seem to remember something <very>
recent.

Tony

 

I have tried deleting and re creating the publishing points, i have even
gone as far as to uninstall and re-install the service.
it would be almost impossible for me to track an update. the server has been
running less than a month and multiple service packs an updates have been
installed.

my wsx is a file where i create a list of content to be streamed.

 

Is it in XML format, pointing to the locations of the files?

Tony

 

yes sir.

 

My SOP for troubleshooting these metafiles...

Open Windows Media Player on the client.
1. Try to connect using the path described in the metafile.

Do this
on the WMS server
on a client in the LAN
on a remote WAN client

Each of those steps will try to nail down
- Whether the WMS itself is still functioning properly
- Whether the problem is a firewall problem

Also, SBS2K3 SP1, ISA2004 and Win2K3 SP1 is so new I can't say whether there
is any known and recognized problem as of yet with any of the three of them
individually or when on the same box.

HTH am going to be away from the newsgroups for at least a week...

Tony

 

the problem is with the windows media services itself and the playlist
editor.

the media service needn't be streaming for me to get these symptoms.

It is very frusterating.

 

OK, sorry I can't help you with that.
Am not so knowledgeable troubleshooting the editor as just makiing the files
work.

Good Luck,
Tony

 

anyone else care to take a stab at this?

 

Is there another newsgroup that i should post this in?