WBFS Manager 3.0.1 x86 Fatal error

Discussion in 'Wii - Backup Loaders' started by r3dcat, Jan 29, 2010.

Jan 29, 2010
  1. r3dcat
    OP

    Newcomer r3dcat Advanced Member

    Joined:
    Jul 28, 2009
    Messages:
    64
    Country:
    Australia
    I have been using WBFS Manager 3.0.1 on WinXP SP3 for a while now with no problem but recently I have started getting a fatal error every time I try running 3.0.1 and I have no idea why ???

    I have installed WBFS Manager 3.0 and that runs ok but I would prefer to run WBFS Manager 3.0.1 ... any ideas anyone ???

    This is the error log below:

    Fatal error occurred. Please send the following information to the application developer at wbfsmanager@gmail.com (You can copy this text by pressing Ctrl+C): Version 3.0.1.0, OS: Microsoft Windows NT 5.1.2600 Service Pack 3 Message: 'Commands:UICommands.CreateChannel' value cannot be assigned to property 'Command' of object 'System.Windows.Controls.Button'. Configuration system failed to initialize Error at object 'CreateChannelButton' in markup file 'WBFSManager;component/ui/mainwindow.xaml'.
    InnerException: Configuration system failed to initialize
    Stack trace: at System.Windows.Markup.XamlParseException.ThrowException(String message, Exception innerException, Int32 lineNumber, Int32 linePosition, Uri baseUri, XamlObjectIds currentXamlObjectIds, XamlObjectIds contextXamlObjectIds, Type objectType)
    at System.Windows.Markup.XamlParseException.ThrowException(ParserContext parserContext, Int32 lineNumber, Int32 linePosition, String message, Exception innerException)
    at System.Windows.Markup.BamlRecordReader.ThrowExceptionWithLine(String message, Exception innerException)
    at System.Windows.Markup.BamlRecordReader.CreateInstanceFromType(Type type, Int16 typeId, Boolean throwOnFail)
    at System.Windows.Markup.BamlRecordReader.GetElementAndFlags(BamlElementStartRecord bamlElementStartRecord, Object& element, ReaderFlags& flags, Type& delayCreatedType, Int16& delayCreatedTypeId)
    at System.Windows.Markup.BamlRecordReader.BaseReadElementStartRecord(BamlElementSta
    tRecord bamlElementRecord)
    at System.Windows.Markup.BamlRecordReader.ReadElementStartRecord(BamlElementStartRe
    ord bamlElementRecord)
    at System.Windows.Markup.BamlRecordReader.ReadRecord(BamlRecord bamlRecord)
    at System.Windows.Markup.BamlRecordReader.Read(Boolean singleRecord)
    at System.Windows.Markup.TreeBuilderBamlTranslator.ParseFragment()
    at System.Windows.Markup.TreeBuilder.Parse()
    at System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)
    at System.Windows.Application.LoadBamlStreamWithSyncInfo(Stream stream, ParserContext pc)
    at System.Windows.Application.LoadComponent(Uri resourceLocator, Boolean bSkipJournaledProperties)
    at System.Windows.Application.DoStartup()
    at System.Windows.Application.b__0(Object unused)
    at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)
    at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
    at System.Windows.Threading.Dispatcher.WrappedInvoke(Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
    at System.Windows.Threading.DispatcherOperation.InvokeImpl()
    at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
    at System.Threading.ExecutionContext.runTryCode(Object userData)
    at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(
    ryCode 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.Windows.Threading.DispatcherOperation.Invoke()
    at System.Windows.Threading.Dispatcher.ProcessQueue()
    at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
    at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
    at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
    at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)
    at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
    at System.Windows.Threading.Dispatcher.WrappedInvoke(Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
    at System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Boolean isSingleParameter)
    at System.Windows.Threading.Dispatcher.Invoke(DispatcherPriority priority, Delegate method, Object arg)
    at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
    at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
    at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
    at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
    at System.Windows.Threading.Dispatcher.Run()
    at System.Windows.Application.RunDispatcher(Object ignore)
    at System.Windows.Application.RunInternal(Window window)
    at System.Windows.Application.Run(Window window)
    at System.Windows.Application.Run()
    at WBFSManager.AppMain.Main()
     
  2. Scuba156

    Member Scuba156 GBAtemp Fan

    Joined:
    Jan 19, 2010
    Messages:
    340
    Country:
    Australia
    Same thing happens to me with 3.1, it use to work fine then one day it just started throwing a fatal error on boot. i reverted back to 3.0, but i have tried uninstalling, clearing the registry and reinstalling 3.1 but it just throws up the fatal error
     
  3. nitrostemp

    Member nitrostemp GBAtemp Maniac

    Joined:
    Mar 15, 2009
    Messages:
    1,265
    Country:
    Australia
    probly need the newer .net framework
     
  4. Scuba156

    Member Scuba156 GBAtemp Fan

    Joined:
    Jan 19, 2010
    Messages:
    340
    Country:
    Australia
    I have the latest on Windows 7, but that wouldnt explain why it once worked then stopped all of a sudden
     
  5. nitrostemp

    Member nitrostemp GBAtemp Maniac

    Joined:
    Mar 15, 2009
    Messages:
    1,265
    Country:
    Australia
    running 64bit or 32?
     
  6. Scuba156

    Member Scuba156 GBAtemp Fan

    Joined:
    Jan 19, 2010
    Messages:
    340
    Country:
    Australia
    32 bit here, but the OP is also running 32bit Win XP SP3
     
  7. r3dcat
    OP

    Newcomer r3dcat Advanced Member

    Joined:
    Jul 28, 2009
    Messages:
    64
    Country:
    Australia
    I have already tried re-installing latest .net framework as well as uninstalling and manually removed all registry reference before re-installing again ... neither has fixed the problem!
     
  8. nitrostemp

    Member nitrostemp GBAtemp Maniac

    Joined:
    Mar 15, 2009
    Messages:
    1,265
    Country:
    Australia
    go run windows 7 in a virtual
     
  9. Sailent
    This message by Sailent has been removed from public view by Cyan, Nov 30, 2015, Reason: removing unnecessary necrobump and its replies.
    Nov 30, 2015
  10. Xenon Hacks
    This message by Xenon Hacks has been removed from public view by Cyan, Nov 30, 2015, Reason: removing unnecessary necrobump and its replies.
    Nov 30, 2015
  11. Sailent
    This message by Sailent has been removed from public view by Cyan, Nov 30, 2015, Reason: removing unnecessary necrobump and its replies.
    Nov 30, 2015
  12. Xenon Hacks
    This message by Xenon Hacks has been removed from public view by Cyan, Nov 30, 2015, Reason: removing unnecessary necrobump and its replies.
    Nov 30, 2015
  13. Wiimm
    This message by Wiimm has been removed from public view by Cyan, Nov 30, 2015, Reason: removing unnecessary necrobump and its replies.
    Nov 30, 2015

Share This Page