Search In: Doc:Documentation:
Altium DesignerAltium 365Altium MCAD CoDesignerAltium On-Prem Enterprise ServerAltium CircuitMakerCompany DashboardAltium Infrastructure Server
Close
Search Search on Documentation

Possible Installation Issues

Created: October 27, 2016 | Updated: May 21, 2017

Vault Message

This documentation page references Altium Vault, which has been discontinued. All your PCB design, data management and collaboration needs can now be delivered by Altium Designer and a connected Altium 365 Workspace.

The following is a list of possible issues that could be encountered when installing the Altium Vault. This list will be expanded as any further potential issues are identified.

  • The Altium Vault can ONLY be installed and run on a PC running Windows 7 or above, as its Operating System. It cannot be installed on a PC running Windows XP. In addition, it cannot be installed on a PC running basic versions of the OS (Core, Home, Starter, Base).
  • Due to the observed unpredictable behavior of antivirus software, it is recommended to disable such software during the installation of the Altium Vault.
  • The Altium Vault relies on a number of Microsoft runtime components for successful operation and access, in some situations these may not be present on the target machine. If you receive an error message about a missing library (DLL) when you attempt to sign into an Altium Vault, it indicates that there are missing Microsoft runtime components. To-date, this is only known to occur on Windows Server 2008 R2 x64 Datacenter. Use this link to download and install these missing components: http://www.microsoft.com/en-us/download/confirmation.aspx?id=29 
  • If the computer is also running Microsoft Exchange Server, you might receive an HTTP Error 503 error when you first attempt to log in. The installation of the Exchange Server can change the Internet Information Services (IIS) configuration in a way that conflicts with the Vault. To resolve this, the following changes must be made to the applicationHost.config file:

<handlers accessPolicy="Read, Script">
...

<add name="kerbauth" image="C:\Program Files\Microsoft\Exchange Server\V15\Bin\kerbauth.dll" preCondition="bitness64" />
<add name="WSMan" image="C:\Windows\system32\wsmsvc.dll" preCondition="bitness64" />
<add name="exppw" image="C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\auth\exppw.dll" preCondition="bitness64" />
<add name="cafe_exppw" image="C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\bin\exppw.dll"  preCondition="bitness64" />

...
</handlers>

For information about the ApplicationHost.config file, refer to this article. For information on editing the file, refer to this article.

 

 

 

 

 

 

 

 

 

 

 

If you find an issue, select the text/image and pressCtrl + Enterto send us your feedback.