Re: IWMWriterPushSink::Connect Error
From: Clint (clint_at_virtualvoodoo.net)
Date: 06/11/04
- Next message: Jeremy Noring: "Re: IWMWriterPushSink::Connect Error"
- Previous message: Jeremy Noring: "Re: Memory leaks of IWMSyncReader"
- In reply to: Becky Weiss [MS]: "IWMWriterPushSink::Connect Error"
- Next in thread: Jeremy Noring: "Re: IWMWriterPushSink::Connect Error"
- Reply: Jeremy Noring: "Re: IWMWriterPushSink::Connect Error"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 11 Jun 2004 09:23:20 -0600
Thanks for your reply. I appreciate any help I can get on this. The
error is actually 0x80072EE6. I've looked around for that error in
general and the only references I can find is an error message:
"msxml4.dll error '80072ee6'
The URL does not use a recognized protocol"
That's not what my error actual says (I found that quote in another
news group) but the error code is the same. Not sure if it's related,
but that is the error I'm getting on the call to connect. My big issue
is I don't know what it means when the connect method throws this error,
so I don't know how to fix it.
Any ideas?
Clint
Becky Weiss [MS] wrote:
> If you mean the error code 0xC00D2EE6, that's
> NS_E_SERVER_UNAVAILABLE ("The server is currently unable
> to handle the request due to a temporary overloading or
> maintenance of the server.")
>
> Becky
>
> This posting is provided AS IS with no warranties and
> confers no rights
>
>
>>-----Original Message-----
>>I'm getting an unexpected error when calling the Connect
>
> method of the
>
>>IWMWriterPushSink. Here is the call:
>>
>>hr = myPushSink->Connect
>
> ((WCHAR*)"http://MYMEDIASERVER:8080/testpoint",
>
>>NULL, false);
>>
>>When I make that call hr ends up equaling -2147012890
>
> (Hex: 80072EE6).
>
>>That hr is not an expected result of the Connect
>
> function (according
>
>>to the SDK). Does anyone know what might be causing
>
> this?
>
>>Your help is appreciated.
>>
>>Clint
>>
>>P.S. I apologize if this is a repost for some, google
>
> groups lost my
>
>>original post for several days, so when it finally
>
> showed up it was
>
>>buried at the bottom of several days worth of posts.
>>.
>>
- Next message: Jeremy Noring: "Re: IWMWriterPushSink::Connect Error"
- Previous message: Jeremy Noring: "Re: Memory leaks of IWMSyncReader"
- In reply to: Becky Weiss [MS]: "IWMWriterPushSink::Connect Error"
- Next in thread: Jeremy Noring: "Re: IWMWriterPushSink::Connect Error"
- Reply: Jeremy Noring: "Re: IWMWriterPushSink::Connect Error"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|