Advosol Product Versions

The best way to check the installed and the available product version is with using the AdvosolProductVersions utility.
The utility is included in the product setups and can be downloaded as a ZIP file that can be extracted anywhere for execution.
The service URL was changed with the updated web site. Either download the current version or modify the AdvosolProductVersionsNet4.exe.config file to change the configured domain from http://advosol.com to http://info.advosol.com.

Connecting an OPC UA server fails

Most failures to connect to an OPC UA are because of certificates.
Every UA application (server and client) needs to be configured with a certificate and the communication partner (server or client) needs to have the partners certificate defined as trusted.
Read the Certificates chapter in the product manual for a description of the certificate handling.

UA errors often are not reported in detail in the application. Check the UA trace log file for error details. Set the Trace Mask to ALL in the UA configuration for most detailed logging.

Class Not Registered error in connecting to a Classic (DCOM) OPC server.

This error is usually caused by missing OPC Core Components.
On 64 bit machines the 64 bit OPC Core Component version is required for 64 bit applications. 
.Net applications often run in 64 bit mode while Win32 application probably run in 32 bit mode.
The OPC Core Components are usually installed with OPC servers. Many OPC servers are 32 bit and install only the 32 bit OPC Core Components.
On 64 bit machines best uninstall all installed OPC Core Components versions and install only the newest 64 bit version. The Advosol product distribution includes the OPC Core Components setup and it can also be downloaded from the OpcFoundation.org web site.

Visual Studio New Project Wizards

If the wizard fails to start then for some reasons (probably security permissions) the wizard DLLs were not copied into Visual Studio.
For the wizard to work properly the wizard DLL needs to be copied into Visual Studio. This is done within setup by executing the file:
                        C:\Program Files\ADVOSOL\productXXX\WizardYYY\Extensions\InstallWizardExtensionYYY.exe
This utility copies the file:
    C:\Program Files\ADVOSOL\productXXX\WizardYYY\Extensions\DANSrvNet4 Wizard UI.dll
to 
    C:\Program Files\Microsoft Visual Studio VVV\Common7\IDE\PublicAssemblies
You can execute the InstallWizardExtensionYYY.exe utility manually or manually copy the files.

Note:   productXXX stands for the setup directory name of the related Advosol Product
              YYY indicates the wizard version for a particular Visual Studio version
              VVV indicates the Visual Studio version. The directory name may be different in your setup.