Symptom: The normal installation process does a quiet SQL installation, so it may not be obvious why it has failed. When this happens, we advise first attempting the installation by running WaspManualInstall.bat from the SQLExpress2008R2 folder on the installation media. If that fails as well, run setup.exe from that folder to manually install SQL. When prompted for an instance name, if you are installing the Standard or Professional version of your Wasp program, you must name the instance WASPDBEXPRESS, and you must select Mixed Mode for the authentication when prompted, with the following password:
If the manual installation fails, it will give an error.
One possible message is:
The following error has occurred:
'' is not a valid login or you do not have permission.
The cause of this error is the Windows username being used to run the installation is the same as the machine name for the computer where you are installing the program.
When this occurs, it has likely installed enough of the SQL components that it will not allow you to reinstall with the same instance name. You will first need to go to Control Panel > Programs and Features and uninstall SQL Server 2008 R2 (or 2012). If you have multiple SQL instances installed, make sure to select WASPDBEXPRESS when prompted for which instance to remove.
Solution: During the Configuration phase of the manual installation, when prompted for the Authentication Mode, the bottom portion of that window will be Specify SQL Server administrators. In most configurations, the current username will be displayed. If it shows the same thing before and after the backslash, e.g., JASON\Jason in the image above, then you will need to click the Remove button under the box to remove that user. SQL will require at least one Windows user account to be added as a SQL Server administrator, so you will need to also click Add... and select a different user. If there are no other Windows users currently defined, you will need to add one in Control Panel > User Accounts. If it is not possible to add another user account due to policy restrictions, you would need to instead rename either the computer or the existing user account, then begin the SQL installation again.