Results 1 to 7 of 7
  1. #1
    Buddy
    Join Date
    12.01.2012
    Posts
    118

    Default Error attaching to Diablo 3

    [16:31:59.628 N] Error attaching to Diablo III, Reason:System.IO.FileNotFoundException: Could not load file or assembly 'fasmdll_managed.dll' or one of its dependencies. The specified module could not be found.
    File name: 'fasmdll_managed.dll'
    at Zeta.MemoryManagement.ExternalProcessReader..ctor( Process proc)
    at Zeta.ZetaDia.TryInitialize(Process proc, String& reason)

    Any solutions ?

    Thanks ahead
    Hope for the best, plan for the worst

  2. #2
    Super Moderator
    Legen *wait for it* dary

    Join Date
    15.01.2010
    Location
    Athens,Greece
    Posts
    78,188

    Default

    install net framework and the Visual C stuff as described on release thread

  3. #3
    Buddy
    Join Date
    28.04.2012
    Location
    Dallas, Texas
    Posts
    87

    Default

    Quote Originally Posted by hellrazor113 View Post
    [16:31:59.628 N] Error attaching to Diablo III, Reason:System.IO.FileNotFoundException: Could not load file or assembly 'fasmdll_managed.dll' or one of its dependencies. The specified module could not be found.
    File name: 'fasmdll_managed.dll'
    at Zeta.MemoryManagement.ExternalProcessReader..ctor( Process proc)
    at Zeta.ZetaDia.TryInitialize(Process proc, String& reason)

    Any solutions ?

    Thanks ahead

    [09:37:23.338 N] Logging in...
    [09:37:23.882 N]
    [09:37:23.908 N] Error attaching to Diablo III, Reason:System.IO.FileNotFoundException: Could not load file or assembly 'fasmdll_managed, Version=1.0.421.78, Culture=neutral, PublicKeyToken=f20f8f99ca0718ca' or one of its dependencies. The system cannot find the file specified.
    File name: 'fasmdll_managed, Version=1.0.421.78, Culture=neutral, PublicKeyToken=f20f8f99ca0718ca'
    at Zeta.MemoryManagement.ExternalProcessReader..ctor( Process proc)
    at Zeta.ZetaDia.TryInitialize(Process proc, String& reason)

    WRN: Assembly binding logging is turned OFF.
    To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
    Note: There is some performance penalty associated with assembly bind failure logging.
    To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

    same here!

    Quote Originally Posted by Tony View Post
    install net framework and the Visual C stuff as described on release thread

  4. #4
    Super Moderator
    Legen *wait for it* dary

    Join Date
    15.01.2010
    Location
    Athens,Greece
    Posts
    78,188

    Default

    check my reply above

  5. #5
    Buddy
    Join Date
    12.01.2012
    Posts
    118

    Default

    **Solved, I'am sorry i only downloaded the first link! +1 Tony
    Hope for the best, plan for the worst

  6. #6
    Buddy
    Join Date
    23.07.2012
    Posts
    43

    Default

    Quote Originally Posted by hellrazor113 View Post
    **Solved, I'am sorry i only downloaded the first link! +1 Tony

    i have the same problem.. what should i do?

  7. #7
    Super Moderator
    Legen *wait for it* dary

    Join Date
    15.01.2010
    Location
    Athens,Greece
    Posts
    78,188

    Default

    Quote Originally Posted by jer0me5 View Post
    i have the same problem.. what should i do?
    Installation Errors? Try DemonBuddyWizard <---click me

 

 

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts
  •