What's new
By:
  • Visit Rebornbuddy
  • Visit Resources
  • Visit API Documentation
  • Visit Downloads
  • Visit Portal
  • Visit Panda Profiles
  • Visit LLamamMagic

DB Does not start - New User

B

Boce

New Member
Joined
Feb 11, 2016
Messages
9
Reaction score
0
I'm sure its something stupid that I missed, but I can't find it.

I followed the instructions in the guide with the exception of the fact that I downloaded the installer vs the zip. I set my client to run in windows mode, and am staring at the character screen. When I fire up DB, I get the UAC prompt, which obviously I accept, and then nothing. I've checked the process list, and do not see a process running for demonbuddy.exe. I"m about to try removing and re-installing DB, but thought I would ask if anyone has seen this before.

Thanks in advance!
 
Oh, one other thing, I'm running on Windows 10, inside of a VM (VMware Workstation 12.1). I doubt it matters but then again it might.
 
Hello Chinajad,

I would gladly attach them, except none were created, unless I'm looking in the wrong location.

DB was installed to %username%\Documents\Demonbuddy

In this directory there are only the 5 following sub directories, none of which being 'Logs' as expected.

Help
Languages
Plugins
Profiles
Rules

Thanks
 
Hi, Boce,

We don't support running Demonbuddy in a VM (although it can be done). Let's take the VM out of the equation, until we get the problem solved.

Let's do a 'clean install' as described here (subsitute 'Demonbuddy' where the article mentions 'Honorbuddy'):

Also, don't forget that both Diablo3 and Demonbuddy must be launched with Windows administrator privileges.
Right-click on each → "Run as administrator"​

cheers,
chinajade
 
Will do, it'll take a little bit. Will update once I have both D3 and DB installed on a physical box.
 
chinajade,

So i went through and did a fresh install of Diablo via the battlenet launcher, I did a 'clean install' of demonbuddy, and still I get the same thing.

Demonbuddy does not launch. If you watch task manager, the DB process will appear for about a second and then disappear. This time around I installed DB to d:\DB\, and still no logs directory. I'm honestly at a loss as to what the issue could be.

At that point I went through and created a new shortcut for Diablo, adding the -launch switch to eliminate the battlenet launcher with no change in behavior.

I also tried disabling Windows Defender's real-time scanning.
 
Thanks chinajade,

But unfortunately I'd already found that article and completed everything except uninstalling Windows Defender.

It is up to date, I've added exclusions for the directory and for the process, and quite frankly, Windows Defender logs do not show any attempt to prevent demonbuddy.exe process from executing.

I agree the symptom is the same as the one mentioned at the beginning of the article, which is how I got there myself, but I'm not convinced this is an AV issue.
 
After digging through the Application log I found the following two errors. They occur everytime I try to start demonbuddy.

ERROR 1:
Log Name: Application
Source: Application Error
Date: 2/11/2016 2:43:55 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: XPS.sal9000.com
Description:
Faulting application name: Demonbuddy.exe, version: 1.1.2923.454, time stamp: 0x56bca811
Faulting module name: KERNELBASE.dll, version: 10.0.10586.103, time stamp: 0x56a853fe
Exception code: 0xe0434352
Fault offset: 0x000bd928
Faulting process id: 0x1344
Faulting application start time: 0x01d1650cec52b426
Faulting application path: D:\DB\Demonbuddy.exe
Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll
Report Id: 3e350e7d-0f49-4f5e-980d-4def8a18a5b3
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-02-11T20:43:55.062385100Z" />
<EventRecordID>1366</EventRecordID>
<Channel>Application</Channel>
<Computer>XPS.sal9000.com</Computer>
<Security />
</System>
<EventData>
<Data>Demonbuddy.exe</Data>
<Data>1.1.2923.454</Data>
<Data>56bca811</Data>
<Data>KERNELBASE.dll</Data>
<Data>10.0.10586.103</Data>
<Data>56a853fe</Data>
<Data>e0434352</Data>
<Data>000bd928</Data>
<Data>1344</Data>
<Data>01d1650cec52b426</Data>
<Data>D:\DB\Demonbuddy.exe</Data>
<Data>C:\Windows\SYSTEM32\KERNELBASE.dll</Data>
<Data>3e350e7d-0f49-4f5e-980d-4def8a18a5b3</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

ERROR 2:
Log Name: Application
Source: .NET Runtime
Date: 2/11/2016 2:43:55 PM
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: XPS.sal9000.com
Description:
Application: Demonbuddy.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException
at Demonbuddy.MainWindow..ctor()

Exception Info: System.Windows.Markup.XamlParseException
at Demonbuddy.App.*​‫‬*​‬‎*​***‫​**​‏‏**‏​**(System.Object, System.Windows.Threading.DispatcherUnhandledExceptionEventArgs)
at System.Windows.Threading.DispatcherUnhandledExceptionEventHandler.Invoke(System.Object, System.Windows.Threading.DispatcherUnhandledExceptionEventArgs)
at System.Windows.Threading.Dispatcher.CatchException(System.Exception)
at System.Windows.Threading.Dispatcher.CatchExceptionStatic(System.Object, System.Exception)
at System.Windows.Threading.ExceptionWrapper.CatchException(System.Object, System.Exception, System.Delegate)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
at System.Windows.Application.RunDispatcher(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window)
at System.Windows.Application.Run(System.Windows.Window)
at Demonbuddy.App.Main()


Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name=".NET Runtime" />
<EventID Qualifiers="0">1026</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-02-11T20:43:55.042252200Z" />
<EventRecordID>1365</EventRecordID>
<Channel>Application</Channel>
<Computer>XPS.sal9000.com</Computer>
<Security />
</System>
<EventData>
<Data>Application: Demonbuddy.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException
at Demonbuddy.MainWindow..ctor()

Exception Info: System.Windows.Markup.XamlParseException
at Demonbuddy.App.*​‫‬*​‬‎*​***‫​**​‏‏**‏​**(System.Object, System.Windows.Threading.DispatcherUnhandledExceptionEventArgs)
at System.Windows.Threading.DispatcherUnhandledExceptionEventHandler.Invoke(System.Object, System.Windows.Threading.DispatcherUnhandledExceptionEventArgs)
at System.Windows.Threading.Dispatcher.CatchException(System.Exception)
at System.Windows.Threading.Dispatcher.CatchExceptionStatic(System.Object, System.Exception)
at System.Windows.Threading.ExceptionWrapper.CatchException(System.Object, System.Exception, System.Delegate)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
at System.Windows.Application.RunDispatcher(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window)
at System.Windows.Application.Run(System.Windows.Window)
at Demonbuddy.App.Main()

</Data>
</EventData>
</Event>
 
Hi again, Boce,

Thanks for this info. Trying to get this report in front of the senior staff. Demonbuddy is not my area of expertise, and Tony will be out a while longer.

cheers,
chinajade
 
Hello Chinajade,

No worries. I did some research myself, and found several similar threads mostly related to HonorBuddy, and all over a year old. for the most part the recommendation was to uninstall C++ and .Net 4 (which I don't even know if you can in Windows 10).

Anyway, I uninstalled all the C++ versions, i.e. 2008/2010/2012, both x86 and x64, and will re-install demonbuddy and let it re-install its prereqs and see what happens. Hopefully I didn't break anything else on this machine by removing all the C++ versions :)

Thanks again for all your assistance.
 
And after uninstalling, and re-installing as outlined in my previous post, DB still crashes on startup, and logs the same two errors in the application log.
 
pm me your Skype and we will teamviewer it
 
You must log in or register to reply here.
Back
Top