On-Premises Data Gateway installation error when updating to a new version

[gtrajesh]

I was trying to update my data gateway which was running v14.16 to the latest version. I tried uninstalling the old version and tried to run the new version as administrator but I was thrown an error when the installation was happening. Please find below the log related to the error.
I even added my current account to the global objects in the local securities policy, user rights assignment . We tried rebooting the system three times. Nothing worked so far. Any suggestion would be appreciated.

Action start 20:45:43: StartServiceToCreateUser.
SFXCA: Extracting custom action to temporary directory: C:\Windows\Installer\MSI7050.tmp-\
SFXCA: Binding to CLR version v4.0.30319
Calling custom action Microsoft.PowerBI.DataMovement.CustomActionUtils!Microsoft.PowerBI.DataMovement.CustomActionUtils.CustomActions.StartServiceToCreateUser
CustomActionStarted (action=StartServiceToCreateUser,build=3000.68.15)
CustomActionCompleted (action=StartServiceToCreateUser,build=3000.68.15,duration=2975)
MSI (s) (E0:C8) [20:45:46:781]: Doing action: AddLogonAsServiceRight
MSI (s) (E0:C8) [20:45:46:781]: Note: 1: 2205 2: 3: ActionText 
Action ended 20:45:46: StartServiceToCreateUser. Return value 1.
MSI (s) (E0:EC) [20:45:46:783]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI7DEE.tmp, Entrypoint: AddLogonAsServiceRight
Action start 20:45:46: AddLogonAsServiceRight.
SFXCA: Extracting custom action to temporary directory: C:\Windows\Installer\MSI7DEE.tmp-\
SFXCA: Binding to CLR version v4.0.30319
Calling custom action Microsoft.PowerBI.DataMovement.CustomActionUtils!Microsoft.PowerBI.DataMovement.CustomActionUtils.CustomActions.AddLogonAsServiceRight
CustomActionStarted (action=AddLogonAsServiceRight,build=3000.68.15)
CustomActionCompleted (action=AddLogonAsServiceRight,build=3000.68.15,duration=32)
Exception thrown by custom action:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Management.ManagementException: Invalid class 
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
at System.Linq.Enumerable.<CastIterator>d__97`1.MoveNext()
at System.Linq.Enumerable.First(IEnumerable`1 source)
at Microsoft.PowerBI.DataMovement.CustomActionUtils.CustomActions.get_ServiceUsername()
at Microsoft.PowerBI.DataMovement.CustomActionUtils.CustomActions.AddLogonAsServiceRight(Session session)
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object parameters, Object arguments)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object parameters, CultureInfo culture)
at Microsoft.Deployment.WindowsInstaller.CustomActionProxy.InvokeCustomAction(Int32 sessionHandle, String entryPoint, IntPtr remotingDelegatePtr)
CustomAction AddLogonAsServiceRight returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 20:45:47: AddLogonAsServiceRight. Return value 3.
Action ended 20:45:47: INSTALL. Return value 3.

[gtrajesh]

Hi @lbendlin ,

Happy new year! 🙂

It looks like the system is up to date on the windows updates.

Windows Update

[lbendlin]

This should do (the second one is what you need).

Next - is the gateway machine fully up to date on Windows updates? If not then please apply them all.

[gtrajesh]

Hi @lbendlin ,

The currently all the below version of VCRedist are installed. Do I need to install the latest version or would one of this do?

VcRedist Version

[lbendlin]

did you install the latest VC_Redist ?

[gtrajesh]

Hi @lbendlin ,

Yes, all the required minimum requirements as well as the recommended ones are satisfied. Plus, all the related considerations have also been checked and is okay. 

[lbendlin]

No,  you cannot login as the service account as you don't have the password.

Have you completed @v-stephen-msft 's checklist?

[gtrajesh]

Hi @lbendlin , @v-stephen-msft ,

I was able to verify that the current .NET framework version run on the machine is 4.8.03761. The windows version is 64-bit version of Windows Server 2012 R2 Datacenter with current TLS 1.2 and ciphers and 20GB memory. I was able to verify that the user that I am logged in as is under the global object in local policy. Please find below the images of the information sought.

Do I have to login as the service account that is currently running the on-premises data gateway, NT Service\PBIEgwService?

.Net FrameworkMemoryTLS

[v-stephen-msft]

Hi @gtrajesh ,

Requirements and considerations for installing the gateway are as follows, please check:

Requirements
Minimum requirements

• .NET Framework 4.6 (Gateway release August 2019 and earlier)
• .NET Framework 4.7.2 (Gateway release September 2019 and later)
• A 64-bit version of Windows 8 or a 64-bit version of Windows Server 2012 R2 with current TLS 1.2 and cipher suites
• 4 GB disk space for performance monitoring logs (in default configuration)

Recommended

• An 8-core CPU
• 8 GB of memory
• A 64-bit version of Windows Server 2012 R2 or later
• Solid-state drive (SSD) storage for spooling.

Related considerations

• Gateways aren't supported on Server Core installations.
• The user installing the gateway must be the admin of the gateway.
• The gateway can't be installed on a domain controller.
• If you're planning to use Windows authentication, make sure you install the gateway on a computer that's a member of the same Active Directory environment as the data sources.
• Don't install a gateway on a computer, like a laptop, that might be turned off, asleep, or disconnected from the internet. The gateway can't run under any of those circumstances.
• If a gateway uses a wireless network, its performance might suffer.
• You could install other applications on the gateway machine, but this may degrade gateway performance. If you do install other applications on the gateway machine, be sure to monitor the gateway closely to check if there's any resource contention.
• You can install up to two gateways on a single computer: one running in personal mode and the other running in standard mode. You can't have more than one gateway running in the same mode on the same computer.

Reference: Requirements

Best Regards,

Stephen Tao

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[lbendlin]

Next step is to confirm you have this:

• A 64-bit version of Windows Server 2012 R2 with current TLS 1.2 and cipher suites

[gtrajesh]

@lbendlin ,thanks for getting back on this. Yes, it has not been updated since it was set up initially. Thanks for the tips. 🙂

On the screen the error message states that "The on-premises data gateway installation has failed: Please view the error logs, fix the error and then try reinstalling again."

Yes, to access this server we have to use a proxy. We have installed the .net framework 4.8. Below is a screenshot of the version of the .net that is currently running in the system.

.Net Framework version details

[lbendlin]

wow, 14.16. That is rather ... old. You will want to keep the gateway rendering engine in sync with the service and the desktop as much as possible to avoid (vastly) different refresh results. As you can see from the installer we're now on 68.15

The error message you posted complains about not being able to login with the service account. What is the error message that you get on the screen?  Is your company network requiring a proxy? Also please confirm that you have installed .Net 4.8