DMProcessConfigXML Uninstall failing

  • Thread starter Thread starter Chris Karcher
  • Start date Start date
C

Chris Karcher

I've got an application that appears to be installed correctly, but
when
I use DMProcessConfigXML to uninstall it, it returns
CONFIG_E_TRANSACTIONINGFAILURE. A description is at:

http://msdn.microsoft.com/library/d...mobilesdk5/html/mob5lrfDMProcessConfigXML.asp

Are there any common reasons that CONFIG_E_TRANSACTIONINGFAILURE would
be returned on an
uninstall? I know my xml isn't the problem, because the same string
(with a different application substituted in) works fine for
uninstalling other apps.
 
Well, like I said earlier, I'm fairly certain the XML isn't the
problem. I'm using the example taken straight off MSDN, with the
application name substituted in for "[AppName]":

<wap-provisioningdoc>
<characteristic type="UnInstall">
<characteristic type="[AppName]">
<parm name="uninstall" value="1"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>

My main question is that are there any common situations when
DMProcessConfigXML will return CONFIG_E_TRANSACTIONINGFAILURE?
 
Did you type App Name properly? Are there any strange characters in the app
name?
String has to match exactely the string displayed in the "Remove Programs"
applet.

Chris Karcher said:
Well, like I said earlier, I'm fairly certain the XML isn't the
problem. I'm using the example taken straight off MSDN, with the
application name substituted in for "[AppName]":

<wap-provisioningdoc>
<characteristic type="UnInstall">
<characteristic type="[AppName]">
<parm name="uninstall" value="1"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>

My main question is that are there any common situations when
DMProcessConfigXML will return CONFIG_E_TRANSACTIONINGFAILURE?
Can you provide your XML? It might provide clues to what the problem is.

---
Jean Chak
Microsoft Corp.
This posting is provided "AS IS" with no warranties, and confers no
rights.
Click to expand...
Click to expand...
 
Yes, I'm sure the name is correct. Wouldn't it return something like
CONFIG_E_ENTRYNOTFOUND if it was misspelled? I should test that and
see what I get back...

An interesting note, after receiving CONFIG_E_TRANSACTIONINGFAILURE, if
I try to remove the program from the Remove Programs util it gives me a
message about the application being in a weird state and that it may
not be able to remove it correctly.

Lisa said:
Did you type App Name properly? Are there any strange characters in the app
name?
String has to match exactely the string displayed in the "Remove Programs"
applet.

Chris Karcher said:
Well, like I said earlier, I'm fairly certain the XML isn't the
problem. I'm using the example taken straight off MSDN, with the
application name substituted in for "[AppName]":

<wap-provisioningdoc>
<characteristic type="UnInstall">
<characteristic type="[AppName]">
<parm name="uninstall" value="1"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>

My main question is that are there any common situations when
DMProcessConfigXML will return CONFIG_E_TRANSACTIONINGFAILURE?
Can you provide your XML? It might provide clues to what the problem is.

---
Jean Chak
Microsoft Corp.
This posting is provided "AS IS" with no warranties, and confers no
rights.


I've got an application that appears to be installed correctly, but
when
I use DMProcessConfigXML to uninstall it, it returns
CONFIG_E_TRANSACTIONINGFAILURE. A description is at:

http://msdn.microsoft.com/library/d...mobilesdk5/html/mob5lrfDMProcessConfigXML.asp

Are there any common reasons that CONFIG_E_TRANSACTIONINGFAILURE would
be returned on an
uninstall? I know my xml isn't the problem, because the same string
(with a different application substituted in) works fine for
uninstalling other apps.
Click to expand...
Click to expand...
Click to expand...
 
Back
Top