Troubleshooting
The following troubleshooting tips can help resolve some common Esri Business Analyst Server installation and post installation issues. If you don't find the answer you are looking for, you can also search the Business Analyst Resource Center.
Installation and Post Installation Troubleshooting
A dialog box appears indicating the setup features are unavailable due to missing dependencies.
How do I create a log of the installation?
How do I create a log of the post installation?
When I launch the setup, a prompt appears stating Business Analyst Server requires .NET Framework 4.0.
Business Analyst Server requires Microsoft .NET Framework 4.0. If the .NET Framework is not installed, the Business Analyst Server installation process will not proceed. Install the .NET Framework 4.0 then double-click the Business Analyst Server Setup.exe.
A dialog box appears indicating the setup features are unavailable due to missing dependencies.
See Feature dependencies to determine which dependencies your machine is missing.
How do I create a log of the installation?
The example below creates a log of the installation at C:\. However, the log can be created anywhere on the local machine.
msiexec /I <path to ArcGIS Business Analyst Server media>\setup.msi /L*V C:\ArcGIS_Server.logHow do I create a log of the post installation?
The log file of the post installation is always enabled and the log files can be found at C:\Documents and Settings\<your account>\Local Settings\Temp for Windows Server 2003. For Windows Server 2008/Windows Server 2008 R2, the location is C:\Users\<your account>\AppData\Local\Temp.
For Esri Business Analyst Server Post Installation, the log file name is BAServerPostInstall.log.
I get an error stating Failed: Can't get security for $:\BAServerRepository. Check your access rights.
During the Business Analyst Server Post Installation, this message may appear for the file-based repository setup that can occur if the drive type is FAT32 and you're using the Windows 2003 Server operating system. FAT32 uses a different security model that results in an error. To fix the problem, check the properties for the drive location that you specified in the setup and change the repository location to an NTFS drive type.