Error on App opening

bizwoman
bizwoman used Ask the Experts™
on
We have just purchased AML Scanners, model LDX10 (http://www.barcodepower.com/products/?pid=ldx10)

We cannot get the DC Console installed on any of our machines.  I have verified all the requirements on on the machine.    We are running Windows 7 SP1.  I spent 7 hours yesterday researching the error, but can't find anything on this error.  It looked like it might be a Framework error, but I tried installing and uninstalling Framework 4.6.1, and  I believe 3.5 is part of 7.  

Attached is the error we receive.

Thank you in advance for any kind assistance today, as I am under pressure to get this installed and configured in the next 24 hours!
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Fernando SotoRetired
Distinguished Expert 2017

Commented:
You state, "Attached is the error we receive.", where?

Author

Commented:
Sorry! Here it is.... I am just getting used to this site, and did the "Choose File", and forgot the "Upload File" button.  My apologies.
error-on-dc-console.gif
Fernando SotoRetired
Distinguished Expert 2017

Commented:
I am sorry I thought that you where writing a .Net application to interface with the manufactures interface but from the looks of it this is a self contained application. The error you posted seems to be a error message created by the manufacture and to find out what it means and what to do to correct it you will need to contact the tech support of the manufacture or if they have a trouble shooting guide see if they addressed this in it.
Top Expert 2016

Commented:
You will also require Windows Mobile Device Center x64 which hasn't been updated since 2008 and only supports VISTA!
Top Expert 2016
Commented:
the only i have found regarding your issue was that in case you were using a configuration file, that the configSections must be defined at top. in the below sample the error with the exception was gone after moving the <configSections> above <startup>.

<configuration>
  <startup>
    <supportedRuntime version="v2.0.50727" sku="Client"/>
  </startup>
  <configSections>
    <section name="modules" type="Microsoft.Practices.Composite.Modularity.ModulesConfigurationSection, Microsoft.Practices.Composite"/>
  </configSections>
  <modules>
    <module assemblyFile="Modules/MyNamespace.Modules.ModuleName.dll" moduleType="MyNamespace.Modules.ModuleName.ModuleClass" moduleName="Name"/>
  </modules>
</configuration>

Open in new window


It seems the problem was the <startup> element because when I removed it the application ran fine. I was confused because Visual Studio 2008 added that when I checked the box to utilise the "Client Profile" available in 3.5 SP1.

After some mucking about checking and un-checking the box I ended up with a configuration file like this:

<configuration>
  <configSections>
    <section name="modules" type="Microsoft.Practices.Composite.Modularity.ModulesConfigurationSection, Microsoft.Practices.Composite"/>
  </configSections>
  <modules>
    <module assemblyFile="Modules/MyNamespace.Modules.ModuleName.dll" moduleType="MyNamespace.Modules.ModuleName.ModuleClass" moduleName="Name"/>
  </modules>
  <startup>
    <supportedRuntime version="v2.0.50727" sku="Client"/>
  </startup>
</configuration>

Open in new window


Sara

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial