EwWebClient: it is the library required to handle communications with different web services, mainly the welcome screen and the parts data (symbols) portal.
TrJsParser: is the library the software used for parsing the formulas, so if it is not registered any content generated by formulas will not work and show an error instead. This may show up in the drawing sheets associated with wiring diagrams.
These libraries are registered when the application is installed, but the presence of antivirus / firewall software and even some other third party applications and Windows processes may sometimes prevent the registration process. It is also possible that applications tinkering with the registration of libraries may cause this failures when DesignSpark Electrical was already installed and working properly.
There is another library related to these two, TrUiTreeListOcx, which should also be considered when this problem appears.
The most immediate solution is to make sure .NET Framework 4.6 is installed and reinstall DesignSpark Electrical. If this still fails, the libraries can be manually registered. To do this, open an elevated (admin) command prompt and write the following commands:
- For EwWebClient -> Press enter at the end of each new line
regasm "C:\Program Files\Common Files\Trace Software\EwWebClient.dll"
If you're having problems manually entering the above command, extract the attached ZIP & run the file labelled with '-shortcut'. It should prompt you to open the command processor as an admin and automatically run the needed script to register EwWebClient.dll
- For TrJsParser -> regsvr32 "C:\Program Files\Common Files\Trace Software\TrJsParser\TrJsParser.dll"
If you get an error after running the command - "Cannot load TrJsParser", then download the attached file. First you have to rename it as ‘Register TrJsParser DSE.bat’ and then run it.
Once the bat is finished executing, you have to press any key to continue.
- For TrUiTreeListOcx -> regsvr32 "C:\Program Files\Common Files\Trace Software\TrUiTreeListOcx.ocx"
These commands use the default application paths. They are common files so the paths should not change, but if they do the commands have to be modified accordingly.