Receive: "Add Profile Failure: Invalid Profile XML" error when adding WWAN profile - Windows 7 RRS feed

  • Question

  • I'm trying to import below XML profile to Windows 7 machine and no matter what profile i use (even the one it was on that computer originally it gives me an error.
    netsh mbn add profile interface="Mobile Broadband Connection" name="test.xml"
    test.xml is in c:\temp folder.
    <MBNProfile xmlns="http://www.microsoft.com/networking/WWAN/profile/v1">
    Tried these steps:
    - configured the setting using UI and test connection - it worked.
    - copied that profile from path: C:\ProgramData\Microsoft\WwanSvc\Profiles to c:\temp and renamed it to test.xml
    - closed the connection and run command: netsh mbn delete profile interface="Mobile Broadband Connection" name=TestProfile
    - and then tried to add the profile under changed name (no profile changes made): netsh mbn add profile interface="Mobile Broadband Connection" name="test.xml"
    - received very nice message: Add Profile Failure: Invalid Profile XML
    I'm stuck, help?
    Tuesday, May 24, 2011 7:15 PM

All replies

  • I am receiving exactly the same error: Add Profile Failure: Invalid Profile XML

    First I thought it was something that had changed on the Service Provider network or the SIM card but the problem stays with the Windows 7 machine, even when I swap the SIM.

    We deploy an SOE to a fleet of Lenovo laptops with a mix of Ericsson and Qualcomm WWAN cards. Both worked great with this method of deploying the WWAN profile for 12+ months.

    In the past month or two, we now get this error when running the command:

    netsh mbn add profile interface="Mobile Broadband Connection" name="mynewprofile.xml"

    Please help!



    Wednesday, May 25, 2011 6:06 AM
  • Hey,

    Got an answer. It required some debugging, but I end up finding it.

    When you add that profile, system executes a function which compares Subscription ID tag with the one it has in system already. If one is already there then overwrites the profile, if NULL adds the profile. Problem is, as soon as any of the profiles are configured manually to redistribute later, the Subscription ID tag is encoded. And window doesn't know how to decode it, so it fires an error. 

    The Subscription tag is an IMSI number, when you right click it on your connection and go to properties, you will see it there, 15 digits. Copy it and paste it to the XML file replacing encoded number.

    It works as a charm.

    I leave deployment methods to you... :)

    Not so happy to answer my own question, but what a heck... glad to help even one person :)

    • Proposed as answer by Tilsk Sunday, June 5, 2011 10:00 PM
    Friday, June 3, 2011 10:29 AM

    Hey, thanks for coming back and sharing your findings with me and anybody else having this problem who should come across this posting.

    This one was really starting to annoy me so very grateful for your fix although I'm not sure how we're going to deploy it yet.

    Great troubleshooting, thanks again  :)




    Sunday, June 5, 2011 10:05 PM
  • Make that 2 people :)  Having similar issue under Windows 8.

    EDIT:  under Windows 8 the interface name appears to have been shortened to "Mobile Broadband" instead of "Mobile Broadband Connection"

    Once I deleted all existing profiles using:

    netsh mbn delete profile interface="Mobile Broadband" name="xxx"

    I was able to re-run our profile creation script which was failing with the "Add Profile Failure: Invalid Profile XML" error, and it successfully created the connection, with our customized icon for users to recognise.

    Found  this Microsoft document very helpful  (just allow for the interface name diff on Win8):


    • Edited by Darren_Milne Friday, June 14, 2013 5:00 AM more info
    Friday, June 14, 2013 12:34 AM
  • search the internet for MB_Custguide.docx (MS site)

    it explains how to create an mobile broadband connection with commandline and add your own icon to that connection, works for multiple workstations.

    With the command:

    netsh mbn show ready *

    You can get the subscriberID, the scripts in the document only works for english OS, in other language you have to adjust the FOR line in branding.cmd

    Tuesday, March 18, 2014 3:58 PM