Error: invalid executor used in GetObjectName

[glidefever]

Hi,

did anyone got this error before and knows how to help me?
HB always run before on this system, but today I'm experiencing this error....

 

[Tony]

Have you tried a new HB installation?
Is there any log on you subfolder called logs in your HB main folder?

 

[glidefever]

Hi Tony,

of course, there is an Logfile

I'm on Win7 x64 running in an virtual enviroment.

 

[Tony]

Try to run wow exe as admin as well and tell if that worked

 

[glidefever]

Yes it works, if I run WoW under admin rights. Is this ok, to run WoW also as admin?

 

[Tony]

Yep

 

[nvrpunk]

Same error, however, running as administrator does not fix it:

[12:40:20 PM:253] Loading Honorbuddy 2.0.0.4129 settings.
[12:40:21 PM:323] Authenticating..
[12:40:21 PM:903] Buddy Sessions: 0/0
-----
Shared Sessions: 1/3
[12:40:22 PM:798] Error - Endscene hook failed: Value cannot be null.
Parameter name: EndSceneProc passed to Executor constructor was invalid.
[12:40:22 PM:819] Attached to WoW with ID 5160
[12:40:24 PM:357] Error saving settings.
[12:40:24 PM:359] 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:40:24 PM:367]

This is from my logs.

 

[nvrpunk]

Got it, first i needed to set it to direct x 9, as well I had to go to the basic theme or the monitor blinks out due to the game being in DX9 and Windows 7 using DX11, seen this bug before.

As well, had to select the proper profile from a custom one, had to select grind buddy for an xp grind profile etc.

I didn't find everything i needed on the forums guide wise but with a bit of plugging around I did figure it all out between the site and the applications intuitiveness.

There should be a response "Check config.wtf for DX11 API Setting" or such for the last error I got seeing as most people are using dx11 cards etc who would run this.

 

[kentuckyjo]

Dude, thank you for posting that solution... I hadn't used this for quite a while and since stopping I had added a line in my config.wtf to force dx11. My card wouldn't use SLI unless it was on dx11 and was actually taking a performance hit at dx9 Anyways, I never would have checked this. Have some rep.