Hi Ali,

First, you are seeing this issue because SQL Server does not support the use of built-in system accounts (like Local System and Network Service) for Windows Authentication. You can do one of the following two things:

First option:

Create an AD user account to run the Forms Routing Service and IIS FormsAppPool. This will make Windows Authentication work. If you are unfamiliar with how to change service identities, the easiest way to make that change will be to uninstall Forms, reinstall Forms, and enter the AD account info during the installation when prompted by the install wizard.

Second option:

1. Create a "SQL server authentication account" for use with Laserfiche. Give it the "dbcreator" role and set a strong, auto-generated password with a minimum of 24 characters. There are many good password generators online such as this one.
   See: Create a login with SQL Server Management Studio.
2. Set the SQL Server authentication mode to "SQL Server and Windows Authentication mode". Restart the SQL Server service so the change takes effect.
   See: Change server authentication mode with SQL Server Management Studio.
3. In FormsConfig, under Authentication select "Use SQL Server Authentication". It will then display Username and Password fields. Provide the credentials for the SQL account you created in Step 1. Specify your database and then click "Save".

With that said, if this is a Production system for more than a few users, we strongly recommend you do not install any Laserfiche applications on the same server as SQL Server. This goes for any applications, not only Laserfiche. SQL can be incredibly resource hungry and can cause performance issues for any other services on the same server. There are also security considerations. If you have the option, I would definitely put Forms on its own instance with other Laserfiche web apps. All of the instructions above are valid regardless of where you install Forms.