I have just now. Trying to spin up a local instance for development purposes and am getting this error on initial login. Did you find a solution?

Hi @myoung were you able to find a solution? Thank you!

I’m also facing this problem, and bumping the thread in the hopes that someone has found a fix. I’ve just created a local development instance, and like @mikezeiser, am encountering this error at initial login.

I think the only thing notable about my instance creation is that ran into the issue described here ( “Login Failed for user 'IIS APPPOOL\DefaultAppPool") https://stackoverflow.com/questions/53726493/app-pool-login-failed-message-in-new-acumatica-version. The solution given in that thread did not work for me, but I followed instructions found here https://learn.microsoft.com/fr-ca/archive/blogs/ericparvin/how-to-add-the-applicationpoolidentity-to-a-sql-server-login to add a SQL Server login for the DefaultAppPool. After that, I was at least able to load the Acumatica login page, but, alas, unable to log in.

Same problem as ​@sarahfedco. Even had the same DefaultAppPool issue. Now I’m stuck with the “startTwoFactorPipeline” error. Occurred installing 2024r2 build 4 on a development machine.

Update … solved this error by editing the permissions for the system level DefaultAppPool user using SSMS tool for SQL Server. The user needs role membership to: db_data_reader, db_data_writer, and db_ddladmin. Now I can login and reset the default admin user password.

My response was crafted with AI assistance, tailored to provide detailed and actionable guidance for your query.

• Check Two-Factor Authentication Setup:

  • Ensure 2FA is enabled correctly in the system configuration.
  • Verify the user's 2FA settings under their account configuration.

• Review Server Configuration:

  • The error suggests a potential server-side issue. Check if the 2FA pipeline is correctly configured in the application server or authentication service.

• Inspect Network or Firewall Settings:

  • Ensure that all required endpoints for 2FA are reachable, especially if the service uses external providers (e.g., Google Authenticator or SMS services).

• Check Logs:

  • Review the server logs for more detailed error messages. This can help identify if the issue is due to a missing configuration, timeout, or integration problem.

• Restart Services:

  • If changes were made recently to the authentication settings, a restart of the relevant Acumatica services might resolve the issue.

​@brothe58 Well at least I’m not alone! Unfortunately though, I’ve already manually created the IIS APPPOOL\DefaultAppPool login--my settings in SQL Server Management Studio look the same as your screenshot, and I’m getting the “startTwoFactorPipeline” error. You didn’t have to do anything else besides create the login in SSMS?

​@sarahfedco I did end up having to add the db_owner role, too. I’m really not sure why Acumatica is not granting the AppPool MSSQL permissions out of the box. I can’t recommend this setting on a production server, but if it’s your local machine only for development, I feel okay about it.

That did the trick! This is indeed a local machine. Thank you so much for taking the time to help!