none
SDL Threat Modeling Tool 3.1.8 Error "The tool encountered a serious problem and needs to close" RRS feed

  • Question

  • Installed Software:

    Microsoft Windows 8 (64 bit - German)
    Microsoft Office 2010 Professional Plus (32 bit - German)
    Microsoft Visio Premium 2010 (32 bit - German)
    SDL Threat Modeling Tool 3.1.8

    Error on Lauch:
    The tool encountered a serious problem and needs to close.
    Please report this problem by posting the threat model you were working on, description of what you were doing at the time, and the file   
    C:\Users\xyz\AppData\Local\Temp\sdltm\sdltm.log
     at http://social.msdn.microsoft.com/Forums/en-US/sdlprocess/threads/.

    Content sdltm.log:

    SDLTM.exe Information: 0 : Starting application, time: Dienstag, 19. März 2013 11:47:49
        Timestamp=45387803591
    SDLTM.exe Information: 0 : Version = 3.1.8.0
        Timestamp=45387811797
    SDLTM.exe Information: 0 : Build Write Date = 17.08.2011 19:53:42
        Timestamp=45387819479
    SDLTM.exe Information: 0 : Build Create Date = 17.08.2011 19:53:42
        Timestamp=45387820409
    SDLTM.exe Information: 0 : Unhandled inner exception
        Timestamp=45476519125
    SDLTM.exe Error: 0 : Exception: System.InvalidOperationException: Diese Implementation ist nicht Teil der FIPS-validierten kryptographischen Algorithmen für die Windows-Plattform.
       bei System.Security.Cryptography.SHA1Managed..ctor()
       bei System.IO.IsolatedStorage.IsolatedStorage.GetHash(Stream s)

    ...

    Tuesday, March 19, 2013 11:55 AM

Answers

  • Workaround:

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy]
    "Enabled"=dword:00000000

    Friday, March 22, 2013 9:10 AM

All replies

  • Workaround:

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy]
    "Enabled"=dword:00000000

    Friday, March 22, 2013 9:10 AM
  • HI,

    I'm facing the same issue and it is not clear to me what the workaround is? could you give more explanation.

    Thursday, February 13, 2014 2:19 PM
  • Check out the new MS Threat Modeling Tool 2014 that has just been released to public. It doesn't have a dependency on Visio anymore. Also, you should be able to convert your old v3 models into the new format (that will require Visio 2007-2014 though).
    Wednesday, April 16, 2014 10:39 PM