Even if you have just one station you are installing it onto, it is still considered a "Server".
Please note that it is a far too common event for IT personnel to overstep their authority, and attempt to enforce a policy of not installing anything onto the server, and instead try to start installing Land F/X off of the CD onto each workstation. The 300+MB of Land F/X blocks and databases should be installed onto your File Server, the same as your existing library of DWG files. The Workstation Setup will configure each station to access the core Land F/X files from the server, while running the 800KB of code locally.
Error initializing Setup If you get an "error initializing setup" or any such other error in just starting the setup, you need to download the installer again, or if this is from a CD, we may need to send you a new CD. Other more grave errors attempting to load the installer may require reinstalling Windows Installer 3.1: http://www.microsoft.com/downloads/details.aspx?familyid=889482fc-5f56-4a38-b838-de776fd4138c&displaylang=en.
Script Error, Custom Action PingLFX
The installer uses Windows Management Instructions (WMI) to test the internet connection. This can error out if VBScript is damaged or restricted, WMI is damaged, or the Ping service is stopped or restricted by security software.
You may need to reinstall VBScript here: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=C717D943-7E4B-4622-86EB-95A22B832CAA.
You can use the WMI Diagnostic Utility to troubleshoot WMI, but we have found it is quicker and more reliable to repair it by simply re-registering the components. From a Command window:
- Code: Select all
cd /d %windir%\system32\wbem
for %i in (*.dll) do RegSvr32 -s %i
for %i in (*.exe) do %i /RegServer
The installer will then use Microsoft XML 4.0 in order to validate your Support ID. A firewall can prevent internet access for this crucial operation. Also, it is possible that your XML Services need to be reinstalled by downloading msxml.msi from here: http://www.microsoft.com/downloads/details.aspx?FamilyID=3144b72b-b4f2-46da-b4b6-c5d7485f2b42&DisplayLang=en.
Those have been the only technical issues reported so far with the Server install, and have been exceptionally rare. Note that the most common issue is undoubtedly a Firewall issue. Otherwise, if you are installing onto a Windows 2000 Server, you may very well need to install all of the Microsoft packages mentioned.
--Jeremiah
