Do you know what this error message indicates is incorrect?

You did not provide sufficient information, thus the following may be of minimal use:

https://www.experts-exchange.com/questions/20352224/Integrate-DSL-via-a-Cisco-router-and-a-WSC-card.html?query=wsc+get+provider&clearTAFilter=true

gonzal13(joe)

Specific error messages or more than you showed above?  Maybe something like this?
When you bind to a Windows Script Components (.wsc) file that is written in Extensible Markup Language (XML) and that resides in an HTTP server, you may receive error code 800c0010H.

It helps to know more about your environment and interfaces to zero in on this problem.

Does this have anything to do with this organization and access attempts?
http://www.wsae.org/

I found only one other precise error message as you show above, and it resulted in kernel32 errors; so perhaps more is known that you can post here.

start-run sfc is a good start to ensure system files are intact.

The only other info there is is that this error message was coming up when a NIC was being installed. The error message would come up and the PC would freeze. Does that help?

It does; could be a resource issue.  Have you tried booting in Safe Mode and checking Device Manager for conflicts?

Just a thought here while trying to figure out what WSAE means.  Maybe Windows Scripting  Application Extensions or something similar?  There don't seem to be any hits on google for WSAE.

Windows Scripting is handled by 2 files:
WScript.exe - 32-bit Windows
CScript.exe - 16-bit DOS.

Either of these files can run Visual Basic Script files (.vbs) and also Windows Script files (.wsh and .wsf ).  Windows Script Host also has support for JavaScript and other programming scripts.

The "Get" part could relate to any of the internal commands (GetThis and GetThat) in those .exe files, such as:

GetCurrentThreadId
GetModuleHandle
GetStartupInfo
GetCommandLine
GetVersionEx
GetProcessHeap
GetModuleFileName
GetLastError
GetFullPathName
GetFileType
GetObject
GetDrivename
GetParentFolder
etc.

If the NIC card relies upon some kind of script to install the drivers or initialize it, AND IF Windows Scripting isn't enabled, then possibly an error like this may arise.  Windows Script Host is often disabled for security reasons to prevent malicious scripts from running.  It is installed if you choose a standard installation of Win98 or if you install Internet Explorer 5x.

Check and see if it is disabled:

http://www.sophos.com/support/wsh.html

These are just thoughts and possibly unrelated however, in the absence of any other close hits on google or at Microsoft, it is worth considering.  I would say, however, that any installer routine or initializing process that relies on something like this is rather poorly thought out if it is the case with your problem.

And, referring again to astaec's comment about XML code, the file c:\windows\system\SCROBJ.DLL contains the following error string that relates to XML:

Unexpected XML declaration - declaration must be at the beginning of the file

Another error message string:

The 'public' tag cannot be used with the 'Automation' or 'Event' handlers

MIGHT explain the AE as "Automation Event", or am I throwing darts with the lights off here  :-)

A lot of installer files these days contain something like the following (example is SolidConverter pdf):

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity
    version="1.0.0.0"
    processorArchitecture="X86"
    name="Microsoft.Windows.SolidAutorun"
    type="win32"
/>
<description>Your app description here</description>
<dependency>
    <dependentAssembly>
        <assemblyIdentity
            type="win32"
            name="Microsoft.Windows.Common-Controls"
            version="6.0.0.0"
            processorArchitecture="X86"
            publicKeyToken="6595b64144ccf1df"
            language="*"
        />
    </dependentAssembly>
</dependency>
</assembly>

So, maybe it's a badly written or malformed installer package, or something to do with another error message string in SCROBJ.DLL concerning encoding:

"Cannot convert text to UNICODE for processing".

I'm so happy you're here in this collaboration effort, BillDL, since I'm up to my eyeballs in backlog.
Best wishes all,
":0) Asta

I'm so glad you first mentioned the .wsc file type and .xml content Asta.  It was my first instinct, but I'm still a bit terrified of being totally slated by experts for hitting on a hunch that is so off the track that it ends up looking ridiculous.  This way, we both look ridiculous  :-)

":0)  To much of effective troubleshooting is a step-by-step process, and with all the unknowns and variables at the end-user level; much 'instinct' has to come into play now and again.  Ideally, the collaboration process brings out the hidden information that is the key to solving mysteries; and teamwork works best, in my humble opinion.

Great news!  Thanks for finalizing this.

Thank you, usns.