locked
dirsync 6862 instalation failed RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi, i can`t install dirsync on Windows 2012 R2 with Update 1

    Error - "The minimum version of Windows Powershell required is 2.0..."

    How to resolve it?

    Tuesday, June 10, 2014 12:29 AM

Answers

  • Question
    Sign in to vote
    4
    Sign in to vote

    Hello,

    I just found out the problem, it is with non-english regional. The setup program tries to match PowerShell version "2.0"/"4.0" to version "2,0"/"4,0". Notice the comma difference!

    The solution is to set the Windows number regional format in control panel to "English (United States)" and log off and back on. After this, you can continue with installing it.

    Wednesday, June 11, 2014 9:49 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I just wanted to confirm as per Markus response. The problem has been identified with the latest Directory Sync Version and it has been fixed. The next version of the Directory Sync Tool will work fine and will be available when we push this out to Prod.

    Thanks for everyone's patience, pleased to hear that most of you have been able to continue with the adoption through changing the regional settings.

    Regards,

    James.

    Tuesday, July 15, 2014 11:10 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Just tried Win 2012 and 2008 R2, same problem
    Tuesday, June 10, 2014 5:12 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Same problem here, on two seperate 2008r2 servers.

    Other has Powershell 3.0 installed, and other 2.0.

    On server with 3.0 version of powershell, all possible updates were installed from MS update.

    Older version of Dirsync ( 6567.0018 ) installed fine. 

    Also tried to update it with 6862 after that, same error occured.

    Nothing came to eventlog.

    Tuesday, June 10, 2014 6:41 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    We are also having this problem on a Windows Server 2008 r2. (Powershell 3.0 installed)

    Can anyone please provide me with a url to Dirsync version 6567.0018 ?

    Thanks!

    Tuesday, June 10, 2014 11:20 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    same over here

    

    • Edited by fastBONE Tuesday, June 10, 2014 12:47 PM added image
    Tuesday, June 10, 2014 12:44 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Just tried on Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2 (brand new install), all failed with the same Powershell error message. Of course Powershell 2.0 is installed and working.

    I think the current build is completely broken and Microsoft should release a fixed version or provide a workaround.

    Does anyone have a link to older build?

    Tuesday, June 10, 2014 4:34 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I got the same problem, I have try everything with Windows Server 2012 R2.

    /Christian

    Tuesday, June 10, 2014 8:40 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Same problem here, brand new Windows Server 2012 R2. I tried after installing previous of Pshell, same issue.
    Wednesday, June 11, 2014 9:30 AM
  • Question
    Sign in to vote
    4
    Sign in to vote

    Hello,

    I just found out the problem, it is with non-english regional. The setup program tries to match PowerShell version "2.0"/"4.0" to version "2,0"/"4,0". Notice the comma difference!

    The solution is to set the Windows number regional format in control panel to "English (United States)" and log off and back on. After this, you can continue with installing it.

    Wednesday, June 11, 2014 9:49 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hello,

    I just found out the problem, it is with non-english regional. The setup program tries to match PowerShell version "2.0"/"4.0" to version "2,0"/"4,0". Notice the comma difference!

    The solution is to set the Windows number regional format in control panel to "English (United States)" and log off and back on. After this, you can continue with installing it.

    Thanks a lot, it works now :)
    • Proposed as answer by Tenterb Wednesday, June 11, 2014 4:09 PM
    Wednesday, June 11, 2014 9:59 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks a lot :)
    Wednesday, June 11, 2014 10:00 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Merci beaucoup à Slata

    Thanks ^^

    Ma patience à des limites... que je ne connais pas.

    Wednesday, June 11, 2014 4:11 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks Zsolt Eperjesi !!!!
    Thursday, June 12, 2014 9:29 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    10x a lot, I reinstalled the server before checking this post to no avail

    It is not admissible that MS does such a fail in a global solution like this

    Thursday, June 19, 2014 9:52 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    THX! works for me also.

    Regards, Dmitriy Ilyin

    Friday, June 20, 2014 7:46 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    By the way, this is a known issue that will be fixed soon.

    Cheers,
    Markus

    Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation

    Thursday, July 10, 2014 8:24 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I just wanted to confirm as per Markus response. The problem has been identified with the latest Directory Sync Version and it has been fixed. The next version of the Directory Sync Tool will work fine and will be available when we push this out to Prod.

    Thanks for everyone's patience, pleased to hear that most of you have been able to continue with the adoption through changing the regional settings.

    Regards,

    James.

    Tuesday, July 15, 2014 11:10 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    I just found out the problem, it is with non-english regional. The setup program tries to match PowerShell version "2.0"/"4.0" to version "2,0"/"4,0". Notice the comma difference!

    The solution is to set the Windows number regional format in control panel to "English (United States)" and log off and back on. After this, you can continue with installing it.

    I can confirm that this is a workaround on a Windows Server 2012 R2 U1 box. Just change the  format in control Panel an sign in new.

    Cheers
    Al

    Wednesday, July 16, 2014 10:00 AM