Several of our sites are running into errors generating an internal certificate after running an upgrade. We've run a diff of the logs of the working sites against the non-working sites, and the problem sites all have the following two sections in the logs where working sites do not:
(Only present in non-working sites)
SI (s) [TIME]: PROPERTY CHANGE: Deleting AI_RollbackAccount property. Its current value is 'NopUser{75F0C14F-C0D9-4FC4-A878-08678788386D}'.
MSI (s) [TIME]: PROPERTY CHANGE: Adding AI_CreateAccount property. Its value is 'NopUser76998DA4D493DD032D80BD53E542E611E3FB357A80802000B7968B0776689322B10A7ED0BAF7EE256F4E08AC4194F65B76E1C11FA48D958ADFA08107013807D8Nabancard LLC User account used by various windows services 65600S-1-5-32-5441{75F0C14F-C0D9-4FC4-A878-08678788386D}2021.52.0931.0'.
MSI (s) [TIME]: Doing action: AI_CreateAccount
Action ended TIME: AI_RollbackAccount. Return value 1.
Action start TIME: AI_CreateAccount.
MSI (s) [TIME]: PROPERTY CHANGE: Deleting AI_CreateAccount property. Its current value is 'NopUser76998DA4D493DD032D80BD53E542E611E3FB357A80802000B7968B0776689322B10A7ED0BAF7EE256F4E08AC4194F65B76E1C11FA48D958ADFA08107013807D8Nabancard LLC User account used by various windows services 65600S-1-5-32-5441{75F0C14F-C0D9-4FC4-A878-08678788386D}2021.52.0931.0'.
MSI (s) [TIME]: PROPERTY CHANGE: Adding AI_CommitAccounts property. Its value is 'NopUser{B1A899C4-8A16-4C75-932D-D1B9B6D67FCE}'.
MSI (s) [TIME]: Doing action: AI_CommitAccounts
Action ended TIME: AI_CreateAccount. Return value 1.
Action start TIME: AI_CommitAccounts.
MSI (s) [TIME]: PROPERTY CHANGE: Deleting AI_CommitAccounts property. Its current value is 'NopUser{B1A899C4-8A16-4C75-932D-D1B9B6D67FCE}'.
Action ended TIME: AI_CommitAccounts. Return value 1.
MSI (s) [TIME]: PROPERTY CHANGE: Adding AI_RollbackAccount property. Its value is 'postgresNopUser{75F0C14F-C0D9-4FC4-A878-08678788386D}'.
MSI (s) [TIME]: Doing action: AI_RollbackAccount
Action start TIME: AI_RollbackAccount.
Later:
(Only present in non-working sites)
MSI (s) [TIME]: Executing op: ActionStart(Name=AI_CommitAccounts,Description=Commit the creation of user accounts on the local computer,)
MSI (s) [TIME]: Executing op: CustomActionSchedule(Action=AI_CommitAccounts,ActionType=11777,Source=BinaryData,Target=**********,CustomActionData=**********)
MSI (s) [TIME]: Executing op: ActionStart(Name=AI_RollbackAccount,Description=Rolling back the creation of user accounts on the local computer,Template=Account: [1])
MSI (s) [TIME]: Executing op: CustomActionSchedule(Action=AI_RollbackAccount,ActionType=11521,Source=BinaryData,Target=**********,CustomActionData=**********)
MSI (s) [TIME]: Executing op: ActionStart(Name=AI_CreateAccount,Description=Creating user account on the local computer,Template=Account: [1])
MSI (s) [TIME]: Executing op: CustomActionSchedule(Action=AI_CreateAccount,ActionType=11265,Source=BinaryData,Target=**********,CustomActionData=**********)
MSI (s) [TIME]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI760B.tmp, Entrypoint: CreateAccount
The NopUser mentioned in the logs is the windows user that runs our service. It is has been set up in the installer (both in the original version and in the upgrade) under Users and Groups with "Delete user profile folder when user account is deleted" as unchecked and and Error Policy of "Skip user creation if the user already exists" Within our custom actions we have a step to assign the "Log on as a service" policy setting .
Wade will add details about the cert issue.