none
FIM Service installation ended prematurely RRS feed

  • Question

  • Hi all,

    Im trying to install FIM 2010 R2. The sync service and portal are not a problem, but when I want to install the service, it fails. I fill in all the required information and press the "install" button. It starts installing, but when the "copying new files" appears, the statusbar stops around 90%, and start to Roll back and the installation failes.

    I tried installing with verbose logging which gives me the following(don't know if this has anything to do with it tbh):

    ---------------------------------------------------------------------------------------------

    MSI (s) (34:54) [13:02:30:442]: Hello, I'm your 32bit Elevated custom action server.
    CAQuietExec: 
    CAQuietExec:  URL reservation delete failed, Error: 2
    CAQuietExec:  The system cannot find the file specified.
    CAQuietExec: 
    CAQuietExec: 
    CAQuietExec:  Error 0x80070001: Command line returned an error.
    CAQuietExec:  Error 0x80070001: CAQuietExec Failed
    CustomAction DeleteResourceEndpointAcl returned actual error code 1603 but will be translated to success due to continue marking

    [....]

    Calling custom action Microsoft.IdentityManagement.ServerCustomActions!Microsoft.IdentityManagement.ServerCustomActions.CustomActions.AddServiceToPerformanceMonitors
    Adding FIMService account to 'Performance Monitor Users' group
    Property name = 'ServiceAccount', value = 'XXXX\XXXX.
    DomainName='XXXX'
    AccountName='XXXX'
    Domain AD found
    Exception thrown by custom action:
    System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Runtime.InteropServices.COMException (0x800706AB): The network address is invalid.

    ---------------------------------------------------------------------------------------------

    Any help is appreciated.


    MCTS, MCPD


    • Edited by Robin Gaal Monday, September 10, 2012 8:12 AM
    Monday, September 10, 2012 8:03 AM

Answers

  • Hi Ross,

    The DNS suffix in the network card advanced configuration was wrong. It was registred to the production domain (prod.customer.com) instead of the acceptance domain(accept.customer.com).

    Hope this helps.


    MCPD

    • Marked as answer by Robin Gaal Monday, February 18, 2013 9:51 AM
    Monday, February 18, 2013 9:51 AM

All replies

  • I've seen this happen when “Authenticated Users” group is NOT a member of the built-in group “Pre-windows 2000 Compatible Access". Could you check that..?

    Regards, Soren Granfeldt
    blog is at http://blog.goverco.com | twitter at https://twitter.com/#!/MrGranfeldt

    Tuesday, September 11, 2012 8:03 AM
  • Hi Soren,

    I will check this out asap. Do you refer to domain groups or local machine groups?


    MCTS, MCPD

    Tuesday, September 11, 2012 9:40 AM
  • Both domain groups...

    Regards, Soren Granfeldt
    blog is at http://blog.goverco.com | twitter at https://twitter.com/#!/MrGranfeldt

    Tuesday, September 11, 2012 10:00 AM
  • Hi Soren,

    The “Authenticated Users” group was already a member of the “Pre-windows 2000 Compatible Access" group, so this is not the issue I'm experiencing.


    MCTS, MCPD

    Tuesday, September 11, 2012 11:05 AM
  • Okay. and just to be sure - you did log off and on to refresh security tokens right?  I'm pretty sure that this error has to do with local security settings on the box that you're installing on, so check GPO's/permission for any suspicous "lock-down" settings.

    Let me know how this turns out. 

    Regards, Soren Granfeldt
    blog is at http://blog.goverco.com | twitter at https://twitter.com/#!/MrGranfeldt

    Tuesday, September 11, 2012 11:15 AM
  • Yeah, relogged multiple times, and added the account which I use for installing to the local administrator set. My collegue thought it has something to do with the netsh urlacl's. I will check this out this evening.

    MCTS, MCPD

    Tuesday, September 11, 2012 12:03 PM
  • None of the above solutions solved this problem. Any more ideas?

    MCTS, MCPD

    Tuesday, September 11, 2012 7:05 PM
  • Hmm, no quite; the FIM service is a domain account, right?

    Regards, Soren Granfeldt
    blog is at http://blog.goverco.com | twitter at https://twitter.com/#!/MrGranfeldt

    Tuesday, September 11, 2012 8:15 PM
  • Yep.. Still no solution found for this problem.

    MCTS, MCPD



    • Edited by Robin Gaal Thursday, September 13, 2012 8:23 AM
    • Proposed as answer by M.Irfan Thursday, September 13, 2012 12:18 PM
    Thursday, September 13, 2012 6:00 AM
  • Hi,

    1: You can install service by Domain Administrator.But the best practice is create a new user who is the member of domain admins.

    2: The account which you are using must have owner write in SQL also.

    I understand your problem. When you installed the SQL you was logging on with local Admin account not with the domain Admin.

    Please try to create new user and give the rights of domain admin. And in the SQL in security section add this user with full rights.

    And also plase mention answered if it work. Thank you.


    Muhammad Irfan

    • Proposed as answer by M.Irfan Thursday, September 13, 2012 9:22 PM
    Thursday, September 13, 2012 12:20 PM
  • Hi,

    I don't use a local admin account... Used a non-domain-admin domain account with a lot of group memberships(security aspects). I've just requested the domain admin rights. I'll keep you updated.


    MCTS, MCPD

    Friday, September 14, 2012 7:52 AM
  • I am wondering if it work or not?

    Fim Forum

    Friday, September 14, 2012 3:57 PM
  • Nope, didn't work.. Still no progress in this issue.

    MCTS, MCPD

    Monday, September 17, 2012 6:45 AM
  • Hi again,

    Please tell me the account which are using and the member of which one group?

    Regards,


    M. Irfan

    Tuesday, September 18, 2012 11:24 AM
  • Domain admin, and a bunch of additional rights, db owner on the sql instance, datareader, datawriter etc.. I have the feeling it has something to do with the enviroment(dns problem etc.) Launched a MS support ticket, they are investigating the case right now. I'll keep you updated on the progress.

    MCTS, MCPD

    Tuesday, September 18, 2012 2:19 PM
  • Hi Again,

    Oh sorry you are facing problem. Thank you for sharing.

    Regards,


    M. Irfan

    Tuesday, September 18, 2012 5:38 PM
  • Still no solution found, anyone with an idea?

    MCTS, MCPD

    Tuesday, September 25, 2012 11:10 AM
  • Just wanted to let you know we solved the problem. It was a dnssuffix related problem.


    MCTS, MCPD

    • Proposed as answer by Ross Currie Thursday, February 14, 2013 6:36 AM
    Monday, October 1, 2012 7:02 AM
  • What you did , can you share steps for that ?

    Thanks,

    Monday, December 17, 2012 10:24 AM
  • Robin, having a similar issue, would be great if you shared some of the steps to resolve.

    - Ross Currie


    FIMSpecialist.com | MCTS: FIM 2010

    Thursday, February 14, 2013 6:36 AM
  • Hey Ross,

    My issue was resolved, the account i was using for installation was not in the domain user group in AD

    Account used for installation must be a Domain User & Local Admin.

    Please check

    Regards,
    Varun Kohli

    Sunday, February 17, 2013 6:51 AM
  • Hi Ross,

    The DNS suffix in the network card advanced configuration was wrong. It was registred to the production domain (prod.customer.com) instead of the acceptance domain(accept.customer.com).

    Hope this helps.


    MCPD

    • Marked as answer by Robin Gaal Monday, February 18, 2013 9:51 AM
    Monday, February 18, 2013 9:51 AM
  • Hi Robin,

    Thanks for that - turns out that this was the issue. We had a similar environment to yours, where we were operating in a development environment and the default server configuration was for a production environment.

    Very frustrating - not the sort of thing I would have easily figured out, so I'm lucky you'd already encountered it.

    Varun - the account definitely had the right access, which was why it was so surprising that it was erroring when trying to add a user to the group. Clearly, it was the DNS issue leading the installer astray.

    Thanks again Robin, I've written a detailed account on my site of how I solved this issue for anyone who encounters this in the future.

    - Ross Currie


    FIMSpecialist.com | MCTS: FIM 2010

    Tuesday, February 19, 2013 4:12 AM
  • Hi Ross,

    Thanks for the credits on your blog. Glad to hear I was not the only one experiencing this problem.

    Robin


    MCPD



    • Edited by Robin Gaal Tuesday, February 19, 2013 12:58 PM
    Tuesday, February 19, 2013 12:34 PM
  • Hi,

    I have the same pb : the installation ended prematurely.

    I have check your three issus but nothing for me the pb is the same.

    I activate the log for msiexec and maybe is a language pb but I can't found the issue and I don't if it's exactly this.

    you can see the log, if someone can help me ...

    Action 14:59:43: InstallServices. Installing new services
    InstallServices: Service: 
    Action 14:59:45: RollbackPSExtension. 
    Action 14:59:45: InstallPSExtension. 
    Action 14:59:45: DeployAndPopulateDatabase. 
    Action 14:59:58: UpgradeDatabase. 
    Action 15:03:11: SetServiceRecoveryActions. 
    CAQuietExec:   ChangeServiceConfig2 r‚ussite(s)
    Action 15:03:11: StartServices. Starting services
    StartServices: Service: Forefront Identity Manager Service
    Action 15:03:17: RollbackInstallCommonPortal. Rollback solution packs
    Action 15:03:17: InstallCommonPortal. Deploying solution packs
    CAQuietExec:  Microsoft.IdentityManagement.SolutionPackUtility.exe will deploy and/or retract the FIM solution packs. This operation may take long time in a SharePoint farm environment. 
    CAQuietExec:  Executing all administrative timer jobs in preparation for FIM solution pack deployment.
    CAQuietExec:  Ex‚cution de Mise … jour du groupe de processus de traitement SharePointc5f0e7e4-0d86-478f-8d20-221613cfd924.
    CAQuietExec:  Le travail Mise … jour du groupe de processus de traitement SharePointc5f0e7e4-0d86-478f-8d20-221613cfd924 a ‚chou‚ avec l'erreur suivante. Ce travail va ˆtre ignor‚. chec de la connexion … un port IPCÿ: Le fichier sp‚cifi‚ est introuvable.
    CAQuietExec:   
    CAQuietExec:  Ex‚cution de Mise … jour du groupe de processus de traitement SharePointe967be64-3e49-4364-8455-678216363533.
    CAQuietExec:  Le travail Mise … jour du groupe de processus de traitement SharePointe967be64-3e49-4364-8455-678216363533 a ‚chou‚ avec l'erreur suivante. Ce travail va ˆtre ignor‚. chec de la connexion … un port IPCÿ: Le fichier sp‚cifi‚ est introuvable.
    CAQuietExec:   
    CAQuietExec:  L'op‚ration s'est d‚roul‚e avec succŠs.
    CAQuietExec:  
    CAQuietExec:  Deploying microsoftilmportalcommondlls.wsp
    CAQuietExec:  Ex‚cution de solution-deployment-microsoftilmportalcommondlls.wsp-0.
    CAQuietExec:  Ex‚cution de Mise … jour du groupe de processus de traitement SharePointc5f0e7e4-0d86-478f-8d20-221613cfd924.
    CAQuietExec:  Le travail Mise … jour du groupe de processus de traitement SharePointc5f0e7e4-0d86-478f-8d20-221613cfd924 a ‚chou‚ avec l'erreur suivante. Ce travail va ˆtre ignor‚. chec de la connexion … un port IPCÿ: Le fichier sp‚cifi‚ est introuvable.
    CAQuietExec:   
    CAQuietExec:  Ex‚cution de Mise … jour du groupe de processus de traitement SharePointe967be64-3e49-4364-8455-678216363533.
    CAQuietExec:  Le travail Mise … jour du groupe de processus de traitement SharePointe967be64-3e49-4364-8455-678216363533 a ‚chou‚ avec l'erreur suivante. Ce travail va ˆtre ignor‚. chec de la connexion … un port IPCÿ: Le fichier sp‚cifi‚ est introuvable.
    CAQuietExec:   
    CAQuietExec:  L'op‚ration s'est d‚roul‚e avec succŠs.
    CAQuietExec:  
    CAQuietExec:  Adding feature for microsoftilmportalcommondlls.wsp
    CAQuietExec:  Ex‚cution de Mise … jour du groupe de processus de traitement SharePointc5f0e7e4-0d86-478f-8d20-221613cfd924.
    CAQuietExec:  Le travail Mise … jour du groupe de processus de traitement SharePointc5f0e7e4-0d86-478f-8d20-221613cfd924 a ‚chou‚ avec l'erreur suivante. Ce travail va ˆtre ignor‚. chec de la connexion … un port IPCÿ: Le fichier sp‚cifi‚ est introuvable.
    CAQuietExec:   
    CAQuietExec:  Ex‚cution de Mise … jour du groupe de processus de traitement SharePointe967be64-3e49-4364-8455-678216363533.
    CAQuietExec:  Le travail Mise … jour du groupe de processus de traitement SharePointe967be64-3e49-4364-8455-678216363533 a ‚chou‚ avec l'erreur suivante. Ce travail va ˆtre ignor‚. chec de la connexion … un port IPCÿ: Le fichier sp‚cifi‚ est introuvable.
    CAQuietExec:   
    CAQuietExec:  L'op‚ration s'est d‚roul‚e avec succŠs.
    CAQuietExec:  
    Action 15:03:27: RollbackInstallFIMPortal. Rollback FIM Portal solution pack
    Action 15:03:27: InstallFIMPortal. Deploying FIM Portal solution pack
    CAQuietExec:  Microsoft.IdentityManagement.SolutionPackUtility.exe will deploy and/or retract the FIM solution packs. This operation may take long time in a SharePoint farm environment. 
    CAQuietExec:  Executing all administrative timer jobs in preparation for FIM solution pack deployment.
    CAQuietExec:  Ex‚cution de Mise … jour du groupe de processus de traitement SharePointc5f0e7e4-0d86-478f-8d20-221613cfd924.
    CAQuietExec:  Le travail Mise … jour du groupe de processus de traitement SharePointc5f0e7e4-0d86-478f-8d20-221613cfd924 a ‚chou‚ avec l'erreur suivante. Ce travail va ˆtre ignor‚. chec de la connexion … un port IPCÿ: Le fichier sp‚cifi‚ est introuvable.
    CAQuietExec:   
    CAQuietExec:  Ex‚cution de Mise … jour du groupe de processus de traitement SharePointe967be64-3e49-4364-8455-678216363533.
    CAQuietExec:  Le travail Mise … jour du groupe de processus de traitement SharePointe967be64-3e49-4364-8455-678216363533 a ‚chou‚ avec l'erreur suivante. Ce travail va ˆtre ignor‚. chec de la connexion … un port IPCÿ: Le fichier sp‚cifi‚ est introuvable.
    CAQuietExec:   
    CAQuietExec:  L'op‚ration s'est d‚roul‚e avec succŠs.
    CAQuietExec:  
    CAQuietExec:  Deploying microsoftidentitymanagement.wsp
    CAQuietExec:  Ex‚cution de solution-deployment-microsoftidentitymanagement.wsp-0.
    CAQuietExec:  Ex‚cution de Mise … jour du groupe de processus de traitement SharePointc5f0e7e4-0d86-478f-8d20-221613cfd924.
    CAQuietExec:  Le travail Mise … jour du groupe de processus de traitement SharePointc5f0e7e4-0d86-478f-8d20-221613cfd924 a ‚chou‚ avec l'erreur suivante. Ce travail va ˆtre ignor‚. chec de la connexion … un port IPCÿ: Le fichier sp‚cifi‚ est introuvable.
    CAQuietExec:   
    CAQuietExec:  Ex‚cution de Mise … jour du groupe de processus de traitement SharePointe967be64-3e49-4364-8455-678216363533.
    CAQuietExec:  Le travail Mise … jour du groupe de processus de traitement SharePointe967be64-3e49-4364-8455-678216363533 a ‚chou‚ avec l'erreur suivante. Ce travail va ˆtre ignor‚. chec de la connexion … un port IPCÿ: Le fichier sp‚cifi‚ est introuvable.
    CAQuietExec:   
    CAQuietExec:  L'op‚ration s'est d‚roul‚e avec succŠs.
    CAQuietExec:  
    CAQuietExec:  An exception occurred while running Microsoft.IdentityManagement.SolutionPackUtility.exe: la langue n'est pas prise en charge par le serveur.
    CAQuietExec:  An error occurred while deploying FIM portal solution packs. 
    CAQuietExec:  Error 0xfffffffa: Command line returned an error.
    CAQuietExec:  Error 0xfffffffa: CAQuietExec Failed
    CustomAction InstallFIMPortal returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    Action ended 15:03:42: InstallExecute. Return value 3.
    Action 15:03:42: Rollback. Rolling back action:
    Rollback: Deploying FIM Portal solution pack
    Rollback: Rollback FIM Portal solution pack


    Friday, February 22, 2013 2:23 PM
  • Can you create an english log:)?

    Find me on linkedin: http://nl.linkedin.com/in/tranet

    Friday, February 22, 2013 2:55 PM
  • hoo yeah ... I forget that a part is in french.

    I don't know if I can create a english log with msiexec?

    Friday, February 22, 2013 3:00 PM
  • I have translated a part ( more french log are repeated): 

    Action 14:59:43: InstallServices. Installing new services
    InstallServices: Service: 
    Action 14:59:45: RollbackPSExtension. 
    Action 14:59:45: InstallPSExtension. 
    Action 14:59:45: DeployAndPopulateDatabase. 
    Action 14:59:58: UpgradeDatabase. 
    Action 15:03:11: SetServiceRecoveryActions. 
    CAQuietExec:   ChangeServiceConfig2 r‚ussite(s)
    Action 15:03:11: StartServices. Starting services
    StartServices: Service: Forefront Identity Manager Service
    Action 15:03:17: RollbackInstallCommonPortal. Rollback solution packs
    Action 15:03:17: InstallCommonPortal. Deploying solution packs
    CAQuietExec:  Microsoft.IdentityManagement.SolutionPackUtility.exe will deploy and/or retract the FIM solution packs. This operation may take long time in a SharePoint farm environment. 
    CAQuietExec:  Executing all administrative timer jobs in preparation for FIM solution pack deployment.
    CAQuietExec:  Executing update SharePointc5f0e7e4-0d86-478f-8d20-221613cfd924.
    CAQuietExec:  the work of update SharePointc5f0e7e4-0d86-478f-8d20-221613cfd924 failed‚with the error. This task will be ignore echec connexion port IPCÿ: can't found the specified file.
    CAQuietExec:   
    CAQuietExec:  executinf update  SharePointe967be64-3e49-4364-8455-678216363533.
    CAQuietExec:  the work of update SharePointe967be64-3e49-4364-8455-678216363533  failed‚with the error. This task will be ignore echec connexion port IPCÿ: can't found the specified file.
    CAQuietExec:   
    CAQuietExec:  Success
    CAQuietExec:  
    CAQuietExec:  Deploying microsoftilmportalcommondlls.wsp
    CAQuietExec:  Ex‚cution de solution-deployment-microsoftilmportalcommondlls.wsp-0.
    CAQuietExec:  Executing update SharePointc5f0e7e4-0d86-478f-8d20-221613cfd924.
    CAQuietExec:  Le travail Mise … jour du groupe de processus de traitement SharePointc5f0e7e4-0d86-478f-8d20-221613cfd924 a ‚chou‚ avec l'erreur suivante. Ce travail va ˆtre ignor‚. chec de la connexion … un port IPCÿ: Le fichier sp‚cifi‚ est introuvable.
    CAQuietExec:   
    CAQuietExec:  Ex‚cution de Mise … jour du groupe de processus de traitement SharePointe967be64-3e49-4364-8455-678216363533.
    CAQuietExec:  Le travail Mise … jour du groupe de processus de traitement SharePointe967be64-3e49-4364-8455-678216363533 a ‚chou‚ avec l'erreur suivante. Ce travail va ˆtre ignor‚. chec de la connexion … un port IPCÿ: Le fichier sp‚cifi‚ est introuvable.
    CAQuietExec:   
    CAQuietExec:  L'op‚ration s'est d‚roul‚e avec succŠs.
    CAQuietExec:  
    CAQuietExec:  Adding feature for microsoftilmportalcommondlls.wsp
    CAQuietExec:  Ex‚cution de Mise … jour du groupe de processus de traitement SharePointc5f0e7e4-0d86-478f-8d20-221613cfd924.
    CAQuietExec:  Le travail Mise … jour du groupe de processus de traitement SharePointc5f0e7e4-0d86-478f-8d20-221613cfd924 a ‚chou‚ avec l'erreur suivante. Ce travail va ˆtre ignor‚. chec de la connexion … un port IPCÿ: Le fichier sp‚cifi‚ est introuvable.
    CAQuietExec:   
    CAQuietExec:  Ex‚cution de Mise … jour du groupe de processus de traitement SharePointe967be64-3e49-4364-8455-678216363533.
    CAQuietExec:  Le travail Mise … jour du groupe de processus de traitement SharePointe967be64-3e49-4364-8455-678216363533 a ‚chou‚ avec l'erreur suivante. Ce travail va ˆtre ignor‚. chec de la connexion … un port IPCÿ: Le fichier sp‚cifi‚ est introuvable.
    CAQuietExec:   
    CAQuietExec:  Success
    CAQuietExec:  
    Action 15:03:27: RollbackInstallFIMPortal. Rollback FIM Portal solution pack
    Action 15:03:27: InstallFIMPortal. Deploying FIM Portal solution pack
    CAQuietExec:  Microsoft.IdentityManagement.SolutionPackUtility.exe will deploy and/or retract the FIM solution packs. This operation may take long time in a SharePoint farm environment. 
    CAQuietExec:  Executing all administrative timer jobs in preparation for FIM solution pack deployment.
    CAQuietExec:  update SharePointc5f0e7e4-0d86-478f-8d20-221613cfd924.
    CAQuietExec:  Update SharePointc5f0e7e4-0d86-478f-8d20-221613cfd924 echec with the error. This task will be ignore echec connexion port IPCÿ: can't found the specified file.
    CAQuietExec:   
    CAQuietExec:  Update SharePointe967be64-3e49-4364-8455-678216363533.
    CAQuietExec:  update SharePointe967be64-3e49-4364-8455-678216363533 echec with the error. This task will be ignore echec connexion port IPCÿ: can't found the specified file.
    CAQuietExec:   
    CAQuietExec: Success
    CAQuietExec:  
    CAQuietExec:  Deploying microsoftidentitymanagement.wsp
    CAQuietExec:  Ex‚cution of solution-deployment-microsoftidentitymanagement.wsp-0.
    CAQuietExec:  Update SharePointc5f0e7e4-0d86-478f-8d20-221613cfd924.
    CAQuietExec:  Update SharePointc5f0e7e4-0d86-478f-8d20-221613cfd924 echec with the error. This task will be ignore echec connexion port IPCÿ: can't found the specified file.
    CAQuietExec:   
    CAQuietExec:  Update SharePointe967be64-3e49-4364-8455-678216363533.
    CAQuietExec:  update SharePointe967be64-3e49-4364-8455-678216363533 echec with the error. This task will be ignore echec connexion port IPCÿ: can't found the specified file.
    CAQuietExec:   
    CAQuietExec:  Success
    CAQuietExec:  
    CAQuietExec:  An exception occurred while running Microsoft.IdentityManagement.SolutionPackUtility.exe: the language is not supported by the serveur.
    CAQuietExec:  An error occurred while deploying FIM portal solution packs. 
    CAQuietExec:  Error 0xfffffffa: Command line returned an error.
    CAQuietExec:  Error 0xfffffffa: CAQuietExec Failed
    CustomAction InstallFIMPortal returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    Action ended 15:03:42: InstallExecute. Return value 3.
    Action 15:03:42: Rollback. Rolling back action:
    Rollback: Deploying FIM Portal solution pack
    Rollback: Rollback FIM Portal solution pack

    Friday, February 22, 2013 3:21 PM
  • I should try some different language settings since the log is complaining about it... Try to configure the server to use the english language instead of french..


    Find me on linkedin: http://nl.linkedin.com/in/tranet

    Friday, February 22, 2013 5:56 PM
  • I try to install MUI for windows 2008 R2 and the result is the same ...

    I desperate ... :(


    Monday, February 25, 2013 5:20 PM
  • So as I don't found my solution, I have reinstall all and now it's good.

    Thanks you very much for your help and your time Robin.

    Thursday, February 28, 2013 1:05 PM
  • Another reason for rolling back during deployment of the application packs on SharePoint is, that the languages don't match. SharePoint and FIM MUST be installed in the same language versions.
    Tuesday, April 8, 2014 8:24 AM
  • This post is still relevant today. I'm running through an install on SharePoint 2016 and Windows Server 2016 and had the same issue. My DNS environment here is a little messy (READ: very messy) and we have 5 or 6 DNS suffixes put in via GPO. I created a GPO at the OU of my server to only have one suffix and the MSI installation finished without a hitch.
    Thursday, March 7, 2019 1:57 PM