Get an Error: HRESULT: 0x80041114.
WMPTalk.com Forum Index WMPTalk.com
Discuss Windows Media Player
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web wmptalk.com
Get an Error: HRESULT: 0x80041114.

 
Post new topic   Reply to topic    WMPTalk.com Forum Index -> DRM
Author Message
Darryl A. J. Staflund
Guest
Posted: Thu Aug 12, 2004 10:18 pm    Post subject: Get an Error: HRESULT: 0x80041114. Reply with quote
Hi everyone,

I have had my DRM encryption and license server up and running for a couple
of months now. The information it uses is stored in an Oracle database.

Because our project wishes to support Internationalization, I modifed CHAR
and VARCHAR2 fields in our database to NCHAR and NVARCHAR2 respectively, and
then changed our ODP.NET parameter specifications to the appropriate data
type. Everything seems to work except for the signing of the header during
the encryption process. When I attempt to sign the header, I get the
following error:

System.Web.Services.Protocols.SoapException --->
System.ApplicationException ---> System.ApplicationException --->
System.ApplicationException ---> System.ApplicationException --->
System.Runtime.InteropServices.COMException (0x80041114): Exception from
HRESULT: 0x80041114. at WMRMOBJSLib.WMRMHeaderClass.Sign(String bstrPrivKey)
at ...

Because I supposed this error resulted from the change in character
representation that occurred when I made the changes above, I backed my
database changes out and reset the ODP.NET parameter specifications to their
original values.

The problem persists, though, and I do not know what is wrong. I diffed the
appropriate files to see if I might have damaged some code and even threw
exception to ensure that the appropriate values were being used to create
and sign the header. I didn't find anything.

Does anyone know what the root of this problem might be? 0x80041114, byt
the way, is Microsoft's return value signifying an invalid private key
value.

Thanks,
Darryl Staflund

Back to top
Darryl A. J. Staflund
Guest
Posted: Thu Aug 12, 2004 11:00 pm    Post subject: Re: Get an Error: HRESULT: 0x80041114. Reply with quote
I think I have identified the problem, and I believe it has to do with the
tool I am using to work with Oracle. I could also be due to my lack of
understanding of how Oracle handles CHAR/NCHAR conversion and
VARCHAR2/NVARCHAR2 conversion. It turns out that the DDL created by the
tool in question after CHARs/VARCHAR2s were converted to NCHARs/NVARCHAR2s
had effectively doubled the length of the DRM strings. The following is a
question I posted to another newgroup in response to this finding. Thanks
for your help everyone.

Darryl

Hi there,

I do not know if this is a bug or not but it did catch me offguard so I am
posting my observations here. I am using 5.1.6 BTW.

I used <PRODUCT> yesterday to change CHAR fields to NCHAR and VARCHAR2
fields to NVARCHAR2 in a test database of mine and conversion went smoothly
(NB: The database's character set is AL16UTF16.)

I then generated a DDL dump of my schema objects using <PRODUCT> and went
home for the night. After testing yesterday's changes, I decided to switch
back to CHAR and VARCHAR2, so I used 'vi' to replace all instances of
'nchar' to 'char' and 'nvarchar2' to 'varchar2'. I then deleted the objects
of my schema and then ran the modified DDL script.

After that my code broke, and after investigating the problem for some time,
I found that the original DDL dump created by <PRODUCT> (made after I used
<PRODUCT> to change CHAR to NCHAR and VARCHAR2 to NVARCHAR2) had effectively
doubled the lengths of changed columns. Columns that originally looked like
this:

field_name char(5)
field_name_2 varchar2(5)

became

field_name nchar(10)
field_name_2 nvarchar2(10)

Is this a normal Oracle operation (NB: I could be as I have not worked with
NCHAR and NVARCHAR2 before.)? Or was the DDL generated incorrectly?

Thanks,
Darryl Staflund


"Darryl A. J. Staflund" <darryl.staflund@shaw.ca> wrote in message
news:#Pp3piJgEHA.644@tk2msftngp13.phx.gbl...
Quote:
Hi everyone,

I have had my DRM encryption and license server up and running for a
couple
of months now. The information it uses is stored in an Oracle database.

Because our project wishes to support Internationalization, I modifed CHAR
and VARCHAR2 fields in our database to NCHAR and NVARCHAR2 respectively,
and
then changed our ODP.NET parameter specifications to the appropriate data
type. Everything seems to work except for the signing of the header
during
the encryption process. When I attempt to sign the header, I get the
following error:

System.Web.Services.Protocols.SoapException ---
System.ApplicationException ---> System.ApplicationException ---
System.ApplicationException ---> System.ApplicationException ---
System.Runtime.InteropServices.COMException (0x80041114): Exception from
HRESULT: 0x80041114. at WMRMOBJSLib.WMRMHeaderClass.Sign(String
bstrPrivKey)
at ...

Because I supposed this error resulted from the change in character
representation that occurred when I made the changes above, I backed my
database changes out and reset the ODP.NET parameter specifications to
their
original values.

The problem persists, though, and I do not know what is wrong. I diffed
the
appropriate files to see if I might have damaged some code and even threw
exception to ensure that the appropriate values were being used to create
and sign the header. I didn't find anything.

Does anyone know what the root of this problem might be? 0x80041114, byt
the way, is Microsoft's return value signifying an invalid private key
value.

Thanks,
Darryl Staflund




Back to top
Tim [MS]
Guest
Posted: Fri Aug 13, 2004 8:52 pm    Post subject: Re: Get an Error: HRESULT: 0x80041114. Reply with quote
This posting is provided "AS IS" with no warranties, and confers no rights.
The use of any included script samples are subject to the terms specified
at http://www.microsoft.com/info/cpyright.htm

Darryl,

I noticed you mentioned ODP.Net and used .NET coding styles. So I am
assuming you are using .NET Is this correct?

..NET is not supported by the Windows Media Rights Manager SDK because of
interoperability problems like this.

Tim [MS]



"Darryl A. J. Staflund" <darryl.staflund@shaw.ca> wrote in message
news:Osel75JgEHA.3192@tk2msftngp13.phx.gbl...
Quote:
I think I have identified the problem, and I believe it has to do with the
tool I am using to work with Oracle. I could also be due to my lack of
understanding of how Oracle handles CHAR/NCHAR conversion and
VARCHAR2/NVARCHAR2 conversion. It turns out that the DDL created by the
tool in question after CHARs/VARCHAR2s were converted to NCHARs/NVARCHAR2s
had effectively doubled the length of the DRM strings. The following is a
question I posted to another newgroup in response to this finding. Thanks
for your help everyone.

Darryl

Hi there,

I do not know if this is a bug or not but it did catch me offguard so I am
posting my observations here. I am using 5.1.6 BTW.

I used <PRODUCT> yesterday to change CHAR fields to NCHAR and VARCHAR2
fields to NVARCHAR2 in a test database of mine and conversion went
smoothly
(NB: The database's character set is AL16UTF16.)

I then generated a DDL dump of my schema objects using <PRODUCT> and went
home for the night. After testing yesterday's changes, I decided to switch
back to CHAR and VARCHAR2, so I used 'vi' to replace all instances of
'nchar' to 'char' and 'nvarchar2' to 'varchar2'. I then deleted the
objects
of my schema and then ran the modified DDL script.

After that my code broke, and after investigating the problem for some
time,
I found that the original DDL dump created by <PRODUCT> (made after I used
PRODUCT> to change CHAR to NCHAR and VARCHAR2 to NVARCHAR2) had
effectively
doubled the lengths of changed columns. Columns that originally looked
like
this:

field_name char(5)
field_name_2 varchar2(5)

became

field_name nchar(10)
field_name_2 nvarchar2(10)

Is this a normal Oracle operation (NB: I could be as I have not worked
with
NCHAR and NVARCHAR2 before.)? Or was the DDL generated incorrectly?

Thanks,
Darryl Staflund


"Darryl A. J. Staflund" <darryl.staflund@shaw.ca> wrote in message
news:#Pp3piJgEHA.644@tk2msftngp13.phx.gbl...
Hi everyone,

I have had my DRM encryption and license server up and running for a
couple
of months now. The information it uses is stored in an Oracle database.

Because our project wishes to support Internationalization, I modifed
CHAR
and VARCHAR2 fields in our database to NCHAR and NVARCHAR2 respectively,
and
then changed our ODP.NET parameter specifications to the appropriate
data
type. Everything seems to work except for the signing of the header
during
the encryption process. When I attempt to sign the header, I get the
following error:

System.Web.Services.Protocols.SoapException ---
System.ApplicationException ---> System.ApplicationException ---
System.ApplicationException ---> System.ApplicationException ---
System.Runtime.InteropServices.COMException (0x80041114): Exception from
HRESULT: 0x80041114. at WMRMOBJSLib.WMRMHeaderClass.Sign(String
bstrPrivKey)
at ...

Because I supposed this error resulted from the change in character
representation that occurred when I made the changes above, I backed my
database changes out and reset the ODP.NET parameter specifications to
their
original values.

The problem persists, though, and I do not know what is wrong. I diffed
the
appropriate files to see if I might have damaged some code and even
threw
exception to ensure that the appropriate values were being used to
create
and sign the header. I didn't find anything.

Does anyone know what the root of this problem might be? 0x80041114,
byt
the way, is Microsoft's return value signifying an invalid private key
value.

Thanks,
Darryl Staflund








Back to top
Darryl A. J. Staflund
Guest
Posted: Fri Aug 13, 2004 9:30 pm    Post subject: Re: Get an Error: HRESULT: 0x80041114. Reply with quote
Hi there,

I confirmed with my Oracle tool provider that the problem was with their
tool used to create DDL off of Oracle's data dictionary and not with ODP.NET
or with the DRM SDK, so they have supplied me with a fax and everything is
working well. I am indeed using .NET with the DRM SDK and have not had any
problems whatsover. I have a member from Microsoft visiting with me today
with regard to DRM SDK and the Windows Media Format SDK 9.5 beta, so I will
confirm with him about interoperability problems with .NET.

Thanks,
Darryl


"Tim [MS]" <msalias@microsoft.com> wrote in message
news:OHLGxXVgEHA.4092@TK2MSFTNGP10.phx.gbl...
Quote:
This posting is provided "AS IS" with no warranties, and confers no
rights.
The use of any included script samples are subject to the terms specified
at http://www.microsoft.com/info/cpyright.htm

Darryl,

I noticed you mentioned ODP.Net and used .NET coding styles. So I am
assuming you are using .NET Is this correct?

.NET is not supported by the Windows Media Rights Manager SDK because of
interoperability problems like this.

Tim [MS]



"Darryl A. J. Staflund" <darryl.staflund@shaw.ca> wrote in message
news:Osel75JgEHA.3192@tk2msftngp13.phx.gbl...
I think I have identified the problem, and I believe it has to do with
the
tool I am using to work with Oracle. I could also be due to my lack of
understanding of how Oracle handles CHAR/NCHAR conversion and
VARCHAR2/NVARCHAR2 conversion. It turns out that the DDL created by the
tool in question after CHARs/VARCHAR2s were converted to
NCHARs/NVARCHAR2s
had effectively doubled the length of the DRM strings. The following is
a
question I posted to another newgroup in response to this finding.
Thanks
for your help everyone.

Darryl

Hi there,

I do not know if this is a bug or not but it did catch me offguard so I
am
posting my observations here. I am using 5.1.6 BTW.

I used <PRODUCT> yesterday to change CHAR fields to NCHAR and VARCHAR2
fields to NVARCHAR2 in a test database of mine and conversion went
smoothly
(NB: The database's character set is AL16UTF16.)

I then generated a DDL dump of my schema objects using <PRODUCT> and
went
home for the night. After testing yesterday's changes, I decided to
switch
back to CHAR and VARCHAR2, so I used 'vi' to replace all instances of
'nchar' to 'char' and 'nvarchar2' to 'varchar2'. I then deleted the
objects
of my schema and then ran the modified DDL script.

After that my code broke, and after investigating the problem for some
time,
I found that the original DDL dump created by <PRODUCT> (made after I
used
PRODUCT> to change CHAR to NCHAR and VARCHAR2 to NVARCHAR2) had
effectively
doubled the lengths of changed columns. Columns that originally looked
like
this:

field_name char(5)
field_name_2 varchar2(5)

became

field_name nchar(10)
field_name_2 nvarchar2(10)

Is this a normal Oracle operation (NB: I could be as I have not worked
with
NCHAR and NVARCHAR2 before.)? Or was the DDL generated incorrectly?

Thanks,
Darryl Staflund


"Darryl A. J. Staflund" <darryl.staflund@shaw.ca> wrote in message
news:#Pp3piJgEHA.644@tk2msftngp13.phx.gbl...
Hi everyone,

I have had my DRM encryption and license server up and running for a
couple
of months now. The information it uses is stored in an Oracle
database.

Because our project wishes to support Internationalization, I modifed
CHAR
and VARCHAR2 fields in our database to NCHAR and NVARCHAR2
respectively,
and
then changed our ODP.NET parameter specifications to the appropriate
data
type. Everything seems to work except for the signing of the header
during
the encryption process. When I attempt to sign the header, I get the
following error:

System.Web.Services.Protocols.SoapException ---
System.ApplicationException ---> System.ApplicationException ---
System.ApplicationException ---> System.ApplicationException ---
System.Runtime.InteropServices.COMException (0x80041114): Exception
from
HRESULT: 0x80041114. at WMRMOBJSLib.WMRMHeaderClass.Sign(String
bstrPrivKey)
at ...

Because I supposed this error resulted from the change in character
representation that occurred when I made the changes above, I backed
my
database changes out and reset the ODP.NET parameter specifications to
their
original values.

The problem persists, though, and I do not know what is wrong. I
diffed
the
appropriate files to see if I might have damaged some code and even
threw
exception to ensure that the appropriate values were being used to
create
and sign the header. I didn't find anything.

Does anyone know what the root of this problem might be? 0x80041114,
byt
the way, is Microsoft's return value signifying an invalid private key
value.

Thanks,
Darryl Staflund









Back to top
 
Post new topic   Reply to topic    WMPTalk.com Forum Index -> DRM All times are GMT
Page 1 of 1

 
 You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum



Microsoft Office Forum New Topics
Powered by phpBB