cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

2019 r2 upgrade error

Dear All, we are trying to deploy 2019 r2, and are getting the attached error.  Can someone help.  This error occurs whether we do an upgrade or a fresh install. 

 

Please help

(10) Replies
mfranz
By Level 17 Champion
Level 17 Champion

Hi,

The error is quite generic. Could you please describe the steps you were executing during the implementation?

Best regards,

Markward

We get these errors on Powershell when executing the command .\Config.ps1 "Config\FNMS Windows Authentication.xml".

Hi,

Yes, but surely you have done other things before that?

  • Install the application?
  • Created/migrated DBs?
  • Set-ExecutionPolicy?
  • ...

Best regards,

Markward

Hi ,

Yes.

1) DB created with all 4 databases ( Compliance, Inventory, DataWarehouse and Snapshot)

2) Installed application ( single tier architecture) - Web, Inventory and Batch on the same server

3) Set execution policy - allsigned

4) executed  .\Config.ps1 "Config\FNMS Windows Authentication.xml"

5) then post adding credentials, an error shows up saying failed to authenticate the service account and previously attached error shows up

Hi,

Can you double check if service account have the right credentials?

Also did you correctly configured the IIS server and installed the ASP NET according to documentation?

 

We did.   Its working fine in our Dev environment.  Its only breaking down in production.  Same settings as in Dev.

If it worked in the Dev environment, there must be something different between your environments.

Hi,

This is the main error that we get once we execute the config file.

The message about the Logon/Password indicates that the PowerShell script is attempting to log on to the server with the provided credentials and the logon attempt has failed.  It likely means that when you typed in the password for the Service Account that there was a typo.

It may also mean that due to an automated internal policy that was run, the Password of the service account was changed.

Neither of those two were the issues, but we tried doing another install for the nth time, and it worked.