• Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Error - Endscene hook failed: Value cannot be null.

    Discussion in 'Archives' started by cheatmaster, Apr 15, 2011.

    1. cheatmaster

      cheatmaster New Member

      Joined:
      Jan 14, 2011
      Messages:
      4
      Likes Received:
      1
      Trophy Points:
      0
      Just recently I reloaded my computer with Windows 7. I have updated directX to the newest version as well as .net framework. Honorbuddy errors out right after I insert my password. I have no Idea what is causing the error. I have attach the log.


      [12:58:58 AM:497] Loading Honorbuddy 2.0.0.4492 settings.
      [12:59:04 AM:503] Authenticating..
      [12:59:05 AM:556] Buddy Sessions: 0/0
      -----
      Shared Sessions: 1/3
      [12:59:07 AM:303] Error - Endscene hook failed: Value cannot be null.
      Parameter name: EndSceneProc passed to Executor constructor was invalid.
      [12:59:07 AM:318] Attached to WoW with ID 4572
      [12:59:15 AM:471] Error saving settings.
      [12:59:15 AM:472] System.TypeInitializationException: The type initializer for 'Styx.Helpers.CharacterSettings' threw an exception. ---> System.Exception: Invalid executor used in GetObjectName
      at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
      at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
      at System.Windows.Forms.Control.Invoke(Delegate method)
      at ..?()
      at ..?(Object o)
      at System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state)
      at System.Threading.ExecutionContext.runTryCode(Object userData)
      at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
      at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
      at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
      at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
      at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)
      --- End of inner exception stack trace ---
      at ..()
      [12:59:15 AM:480]
      [12:59:16 AM:579] Error saving settings.
      [12:59:16 AM:580] System.TypeInitializationException: The type initializer for 'Styx.Helpers.CharacterSettings' threw an exception. ---> System.Exception: Invalid executor used in GetObjectName
      at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
      at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
      at System.Windows.Forms.Control.Invoke(Delegate method)
      at ..?()
      at ..?(Object o)
      at System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state)
      at System.Threading.ExecutionContext.runTryCode(Object userData)
      at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
      at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
      at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
      at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
      at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)
      --- End of inner exception stack trace ---
      at ..()
      [12:59:17 AM:950] System.NullReferenceException: Object reference not set to an instance of an object.
      at BlueMagic.ExecutorRand.Dispose()
      at BlueMagic.ExecutorRand.Finalize()
       

      Attached Files:

      Last edited: Apr 15, 2011
    2. chinajade

      chinajade Well-Known Member Moderator Buddy Core Dev

      Joined:
      Jul 20, 2010
      Messages:
      17,540
      Likes Received:
      172
      Trophy Points:
      63
      Hi, C-master,

      THANKS for the log. There are two known causes for this problem...

      1) You are running the WoWclient as DirectX11 instead of DirectX9. Directions for determining this are located in red letters at the bottom of the first post in the release thread. No "if"s, "and"s, or "but"s--you must use DirectX9. :)

      2) You *must* also run both the WoWclient and Honorbuddy with admin privileges. The safest way to make this guarantee is to right-click on the WoWclient, and select "Run as admin". Once it is up and running do the same for Honorbuddy... right-click and "Run as admin".


      Since you just reloaded Windows 7, you need to make sure .NET 3.5 is turned on and patched up. (.NET 4.0 is the default on Win7 unless you make other arrangements). .NET 3.5 and .NET 4.0 can safely co-exist side-by-side, but HB *must* have .NET 3.5...

      1) Start -> Control Panel -> Programs and Features
      2) Click on "Turn Windows Features on or off" in panel to left side
      3) Make certain "Microsoft .NET Framework 3.5.1" is ticked on
      4) You'll have to reboot once you enable it <mumbles something about 'typical Windoze'>
      5) Go to Windows Update and make sure the .NET Framework 3.5.1 is patched up


      After these things, you should be good to go.

      cheers, and happy sailing,
      chinajade
       
    3. cheatmaster

      cheatmaster New Member

      Joined:
      Jan 14, 2011
      Messages:
      4
      Likes Received:
      1
      Trophy Points:
      0
      Thx chinajade for your help. It look like my game defaulted to dx10. I had the game save on a dif drive so i didnt re-install it. Changed it back to dx9 and is working like a charm.

      Thx again for your help.
       

    Share This Page