Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!

Reply
rjhale
Helper IV
Helper IV

Problems Installing New Personal Data Gateway

I'm having problems getting the new personal gateway installed on a Windows 7 x64 machine. I've been attempting to install it using domain accounts that have local admin rights on the machine, however; I get the following error every time:

 

Service 'Data Management Gateway Service' (DIAHostService) failed to start. Verify that you have sufficient privileges to start system services.

 

The account(s) that I'm attempting to install with is not the same as my power bi account as our access to power bi is only in our test tenant.

 

I can reproduce this problem with multiple accounts and on multiple computers.  In fact, I have not yet been able to get the gateway installed on a single domain-joined computer which leads me to believe that this may be related to a domain security policy. 

 

Has anyone else run into this?

 

7 REPLIES 7
Eli
New Member

I am having the same issues trying to install the latest PowerBIGatewayInstaller.

Environment is SBS 2008 with SP2 with IE9 and .Net Framework 4.5.1.

See error Log below - It seems v1.9.5865.2\DataManagementGateway.msi fails to install.

any help would be appreciated.

Thanks

 

=== Verbose logging started: 31/03/2016 21:28:30 Build type: SHIP UNICODE 4.05.6002.00 Calling process: C:\Users\existcoadmin.DBC-PERTH\AppData\Local\Temp\2\ejucfvds.suz\PowerBIGatewayInstall.exe ===
MSI (c) (B0:68) [21:28:30:219]: Resetting cached policy values
MSI (c) (B0:68) [21:28:30:219]: Machine policy value 'Debug' is 0
MSI (c) (B0:68) [21:28:30:219]: ******* RunEngine:
******* Product: C:\ProgramData\Package Cache\{1EE5960F-24CC-49CC-B14B-F88A87A38258}v1.9.5865.2\DataManagementGateway.msi
******* Action:
******* CommandLine: **********
MSI (c) (B0:68) [21:28:30:219]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (B0:68) [21:28:30:219]: Grabbed execution mutex.
MSI (c) (B0:68) [21:28:30:222]: Cloaking enabled.
MSI (c) (B0:68) [21:28:30:222]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (B0:68) [21:28:30:222]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (64:E0) [21:28:30:237]: Running installation inside multi-package transaction C:\ProgramData\Package Cache\{1EE5960F-24CC-49CC-B14B-F88A87A38258}v1.9.5865.2\DataManagementGateway.msi
MSI (s) (64:E0) [21:28:30:237]: Grabbed execution mutex.
MSI (s) (64:B0) [21:28:30:238]: Resetting cached policy values
MSI (s) (64:B0) [21:28:30:238]: Machine policy value 'Debug' is 0
MSI (s) (64:B0) [21:28:30:238]: ******* RunEngine:
******* Product: C:\ProgramData\Package Cache\{1EE5960F-24CC-49CC-B14B-F88A87A38258}v1.9.5865.2\DataManagementGateway.msi
******* Action:
******* CommandLine: **********
MSI (s) (64:B0) [21:28:30:239]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (64:B0) [21:28:30:267]: SRSetRestorePoint skipped for this transaction.
MSI (s) (64:B0) [21:28:30:268]: File will have security applied from OpCode.
MSI (s) (64:B0) [21:28:30:335]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\ProgramData\Package Cache\{1EE5960F-24CC-49CC-B14B-F88A87A38258}v1.9.5865.2\DataManagementGateway.msi' against software restriction policy
MSI (s) (64:B0) [21:28:30:335]: SOFTWARE RESTRICTION POLICY: C:\ProgramData\Package Cache\{1EE5960F-24CC-49CC-B14B-F88A87A38258}v1.9.5865.2\DataManagementGateway.msi has a digital signature
MSI (s) (64:B0) [21:28:30:348]: SOFTWARE RESTRICTION POLICY: C:\ProgramData\Package Cache\{1EE5960F-24CC-49CC-B14B-F88A87A38258}v1.9.5865.2\DataManagementGateway.msi is permitted to run at the 'unrestricted' authorization level.
MSI (s) (64:B0) [21:28:30:348]: End dialog not enabled
MSI (s) (64:B0) [21:28:30:348]: Original package ==> C:\ProgramData\Package Cache\{1EE5960F-24CC-49CC-B14B-F88A87A38258}v1.9.5865.2\DataManagementGateway.msi
MSI (s) (64:B0) [21:28:30:348]: Package we're running from ==> C:\Windows\Installer\44f5ac.msi
MSI (s) (64:B0) [21:28:30:349]: Note: 1: 1708
MSI (s) (64:B0) [21:28:30:349]: Product: -- Installation failed.

MSI (s) (64:B0) [21:28:30:350]: Windows Installer installed the product. Product Name: . Product Version: . Product Language: . Installation success or error status: 1613.

MSI (s) (64:B0) [21:28:30:353]: MainEngineThread is returning 1613
MSI (s) (64:E0) [21:28:30:353]: No System Restore sequence number for this installation.
This installation package cannot be installed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service.
C:\ProgramData\Package Cache\{1EE5960F-24CC-49CC-B14B-F88A87A38258}v1.9.5865.2\DataManagementGateway.msi
MSI (s) (64:E0) [21:28:30:353]: User policy value 'DisableRollback' is 0
MSI (s) (64:E0) [21:28:30:353]: Machine policy value 'DisableRollback' is 0
MSI (s) (64:E0) [21:28:30:353]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (64:E0) [21:28:30:353]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (64:E0) [21:28:30:354]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (64:E0) [21:28:30:354]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (64:E0) [21:28:30:354]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (64:E0) [21:28:30:354]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (64:E0) [21:28:30:355]: Restoring environment variables
MSI (c) (B0:68) [21:28:30:356]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (B0:68) [21:28:30:356]: MainEngineThread is returning 1613
=== Verbose logging stopped: 31/03/2016 21:28:30 ===

 

 

 

ashishrj
Power Participant
Power Participant

@rjhale Even I was unable to login. But this works in my case.

Try giving your PC name and password while setting up Data Management Gateway.

For eg in my case it was

username: ashish\ACER

password : ******** (Password used for login into windows)

 

Note: If you do not have a password for your PC then create one and try again. It should work as in my case!

I found a rather unusual workaround for the problem that I was having.  It appears that the installer fails out if the virtual service account for the diahostservice is not a member of the security policy "Log on as a Service" prior to running the installer.  I was able to add the "NT Service\diahostservice" account to that policy before running the installer by doing the following:

 

1.  Create the data management service manually to begin:
sc create diahostservice binpath= c:\windows\system32\diahostservice.exe

2.  Add the nt service\diahostservice account to the "Log on as a service" security policy

3.  Delete the service that we setup manually in step one:
sc delete diahostservice

4.  Add whichever AD account you're going to use to run the service to the "Access this computer from
the network" security policy

5.  Install the data management gateway

 

I realize this should not be necessary, but I could not find which domain security policy was preventing the service from installing properly.

Hi I am having the same issue on Windows 7 64bit on a corporate domain, we added the rights to my user account to log in as a service, but no success.

 

Tried to add the NT Service/ diahostservice account to the "Log as a Service" AD policy but not sure how to add such user to my existing domain.

 

Not sure what other Active Directory policy might be affecting the installation?  

 

Thanks!

ToddChitt
Super User
Super User

Verify that the local account you are using on the machine has priviledges to "Run as a Service". That solved it for me.

 

-Todd Chitt

That was a good suggestion, however; it did not resolve the problem for me. Here is what I tried:

 

1. Added my account to the local security policy "Log on as a Service"

2. Rebooted

3. Ran the installer again which resulted in that same error message

 

Again, I was able to reproduce this error on multiple machines after running through the same steps I listed above.

 

Any other suggestions?

 

Thanks again.

 

andre
Memorable Member
Memorable Member

I have run in to this issue before at a customer who had an AD policy to prevent all accounts to be able to log in as a service.  I am not an AD guru so I can't give you a veryt detailed answer, but the customer had to exclude the specific machines from enforcing this policy before the Gateway was able to work.

 

Please escalate to your AD admins and they should know how to fix it. 

Helpful resources

Announcements
April AMA free

Microsoft Fabric AMA Livestream

Join us Tuesday, April 09, 9:00 – 10:00 AM PST for a live, expert-led Q&A session on all things Microsoft Fabric!

March Fabric Community Update

Fabric Community Update - March 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors
Top Kudoed Authors