Solution Designer
   Error: Custom Action Template file not found at defined location?
   Error: Not able to resolve Custom Action Template file path?
   Compilation error: The folder created under Server is a fixed path folder but the installation directory has not been specified?
   Custom File Action: "Execute File" & "WhenToTrigger" property is set to 'On Solution Build' but the program file not launched on Build?
   What is Assembly Cache folder? I am not able to associate few files with this folder?

Installation Manager
   Error: Build Folder does not exists?
   Error: Pinging Installer Service result: failed?
   Receiving Security Policy Violation error while running installation?
   I am not able to run PowerShell scripts using Server Tasks while my Script is running fine when I run script on local machine.

General Information
   Windows PowerShell Execution Policy

Other References
   Frequently Asked Questions
   Common Tasks

Error: Custom Action Template file not found at defined location?

  Please verify that Custom Action Template file location is defined correctly in the application Configuration file.

Error: Not able to resolve Custom Action Template file path?

  Please verify that Custom Action Template file location has been defined in the application Configuration file.

Error: Build Folder does not exist?

  Please verify that you are using a compiled version of Solution file and all Solution content sub-folders are available in the same directory. When you compile & build a solution using Solution Designer, the Solution file along with build contents is stored in a separate directory as specified at the time of creating new solution. With Installation Manager you shall only use the compiled version of Solution file.

Compilation error: The folder created under Server is a fixed path folder but the installation directory has not been specified?

  It is required that you define the actual directory location for a 'Fixed Path Folder' that is missing, therefore this compilation error is displayed. Please don’t use the 'Fixed Path Folder' if you are not sure about the actual location on the target environment rather you should use standard Folder, for that actual path is defined later by the Installation Manager.

Custom File Action: "Execute File" & "WhenToTrigger" property is set to 'On Solution Build' but the program file not launched on Build?

  By default the "WhenToTrigger" property is set to 'After Build Files Deployed' and therefore value of 'CommandLineUtilFullPath' property is set to
'%targetfilepath%' system variable. Please change the 'CommandLineUtilFullPath' property to '%sourcefilepath%'.

Note: To understand implementation behavior of a Custom Action Template and to see the internal variables list, please click on the help link provided with Custom File Action designer.

What is Assembly Cache folder? I am not able to associate few files with this folder?

  Global Assembly is a system defined folder that is created by default for each Web & Application Server. You should only associate .NET Assembly files with GAC folder otherwise File Manager will not allow any other file types in this folder. All .NET Assembly files that are associated with GAC folder should be signed by Strong Name otherwise Solution Designer shall display warning message during compilation.

Error: Pinging Installer Service result: failed?

  Please verify that InstallAce - Installer Service is running on the target computer and port no. is correctly configured on both sides. See Configuration Settings

Receiving Security Policy Violation error while running installation?

  You may receive the Security Policy Violation error if you are trying to install a package that does not comply with server side Security Policy that is configured using InstallAce Configuration File.

I am not able to run PowerShell scripts using Server Tasks while my Script is running fine when I run script on local machine.

  Please verify that Microsoft PowerShell is already installed on the target environment and PowerShell execution is not disabled by the Security Policy. Please also verify that the Script Execution has not been disabled on target server. Script execution can be enabled/disabled using the Configuration file.