Below are solutions to login errors commonly encountered:
Cause(s): The username and password provided does not match with the username and password stored within the Users control of Assembly Planner.
Solution(s): User needs to be added through the Users control in Assembly Planner, user should confirm they’re using the correct password, and/or administrator should reset the user’s password.
Cause(s): The user has not been given necessary permissions to the database.
Solution(s): In most cases, user needs to be added to the Active Directory group specified in the server Setup Details provided by IT.
Cause(s): Server does not have sufficient hard disk space to store the .mdf, .ldf, and/or backup files.
Solution(s): IT should increase the server hard disk space.
Cause(s): Assembly Planner has been upgraded to the latest Microsoft.NET platform, but the user has not uninstalled and then reinstalled the application.
Solution(s): User should uninstall Assembly Planner from the Control Panel, and then reinstall.
Cause(s): The SQL Server service isn’t running.
Solution(s): Run the SQL Server Configuration Manager as administrator. Find all lines with the Start Mode set to “Automatic” and the State set to “Stopped”. Right click on each of these lines and select Start.
Cause(s): One or more files is missing from the Click Once package on the server.
Solution(s): IT should compare the number of files (including .deploy, .manifest, etc.) that are in the latest version folder inside the application directory on the server to the number of files provided in the installation or update package. In some cases, zip file extractions have only partially completed and in other cases, the AssemblyPlanner.exe.deploy file has been blocked by the anti-virus running on the server (without producing a warning or error message).
Causes(s): AssemblyPlanner.config file using authentication of application instead of SQL Authentication of Proplanner User name.
Solution(s): Review connection string lines is AssemblyPlanner.config file is pointing correctly to the Server and Database with the correct User ID and Password.