.NET errors with PSCommander and Winforms Designer

noahpeltier · June 11, 2021, 3:38pm

I am unable to use the WinForms designer or PScommander for some reason. I found some information in Event viewer that might be helpful in finding out why this is.

NOTE: I’ve seen others having similar issues but you’ve replied that something was updated or fixed, yet I have just done a fresh install of Protools and PSCommander and I am having these issues.

Application: PSCommander.exe
CoreCLR Version: 5.0.321.7212
.NET Version: 5.0.3
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
—> System.NullReferenceException: Object reference not set to an instance of an object.
at pscommander.MainWindow…ctor() in D:\a\1\s\pscommander\pscommander\MainWindow.xaml.cs:line 92
— End of inner exception stack trace —
at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean wrapExceptions, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& hasNoDefaultCtor)
at System.RuntimeType.CreateInstanceDefaultCtorSlow(Boolean publicOnly, Boolean wrapExceptions, Boolean fillCache)
at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, Boolean wrapExceptions)
at System.Activator.CreateInstance(Type type, Boolean nonPublic, Boolean wrapExceptions)
at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture)
at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
at System.Activator.CreateInstance(Type type, Object[] args)
at System.Xaml.Schema.SafeReflectionInvoker.CreateInstanceCritical(Type type, Object[] arguments)
at System.Xaml.Schema.XamlTypeInvoker.CreateInstance(Object[] arguments)
at MS.Internal.Xaml.Runtime.ClrObjectRuntime.CreateInstanceWithCtor(XamlType xamlType, Object[] args)
at MS.Internal.Xaml.Runtime.ClrObjectRuntime.CreateInstance(XamlType xamlType, Object[] args)
at System.Xaml.XamlObjectWriter.Logic_CreateAndAssignToParentStart(ObjectWriterContext ctx)
at System.Xaml.XamlObjectWriter.WriteStartMember(XamlMember property)
at System.Xaml.XamlWriter.WriteNode(XamlReader reader)
at System.Windows.Markup.WpfXamlLoader.TransformNodes(XamlReader xamlReader, XamlObjectWriter xamlWriter, Boolean onlyLoadOneNode, Boolean skipJournaledProperties, Boolean shouldPassLineNumberInfo, IXamlLineInfo xamlLineInfo, IXamlLineInfoConsumer xamlLineInfoConsumer, XamlContextStack`1 stack, IStyleConnector styleConnector)
at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
at System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)
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.<.ctor>b__1_0(Object unused)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(Object obj)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
— End of stack trace from previous location —
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext 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, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
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()
at pscommander.App.Main()

adam · June 11, 2021, 4:56pm

I just looked at the code and I do see a bug but this could happen if:

No license is installed
No config.ps1 file exists

What issue are you seeing with PSScriptPad (WinForm Designer)?

noahpeltier · June 11, 2021, 7:41pm

So PSScriptPad and Winform Designer are coming up for me now after I installed the VScode plugin for Protools which is odd because I’m just operating out of a regular PowerShell prompt. I do have a config and I do have a license installed for ProTools.

noahpeltier · June 11, 2021, 7:47pm

But just to clarify, PSCommander is not working at all which is a shame because I’m VERY excited to use it

adam · June 14, 2021, 12:30pm

Can you please upgrade the module and see if you experience the same issue? I resolved the exception that was being thrown but I’m a bit concerned there might be something else going on.

noahpeltier · June 14, 2021, 2:13pm

Well interestingly enough this morning on a fresh reboot, command started up with windows so I closed it, updated the module from powershell and then ran start-commander. It still seems to be having an issue. I don’t know why it would work on a reboot and then not work again after the module is re-ran.

Application: PSCommander.exe
CoreCLR Version: 5.0.321.7212
.NET Version: 5.0.3
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Windows.Markup.XamlParseException: The invocation of the constructor on type ‘pscommander.MainWindow’ that matches the specified binding constraints threw an exception.
—> System.IO.IOException: The process cannot access the file ‘C:\Users\NoahPeltier\AppData\Roaming\PSCommander\database.db’ because it is being used by another process.
at System.IO.FileStream.ValidateFileHandle(SafeFileHandle fileHandle)
at System.IO.FileStream.CreateFileOpenHandle(FileMode mode, FileShare share, FileOptions options)
at System.IO.FileStream…ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
at LiteDB.Engine.FileStreamFactory.GetStream(Boolean canWrite, Boolean sequencial)
at LiteDB.Engine.StreamPool.<>c__DisplayClass3_0.<.ctor>b__0()
at System.Lazy1.ViaFactory(LazyThreadSafetyMode mode) at System.Lazy1.ExecutionAndPublication(LazyHelper executionAndPublication, Boolean useDefaultConstructor)
at System.Lazy1.CreateValue() at System.Lazy1.get_Value()
at LiteDB.Engine.StreamPool.get_Writer()
at LiteDB.Engine.DiskService…ctor(EngineSettings settings, Int32[] memorySegmentSizes)
at LiteDB.Engine.LiteEngine…ctor(EngineSettings settings)
at LiteDB.ConnectionString.CreateEngine()
at LiteDB.LiteDatabase…ctor(ConnectionString connectionString, BsonMapper mapper)
at LiteDB.LiteDatabase…ctor(String connectionString, BsonMapper mapper)
at pscommander.DataService…ctor() in D:\a\1\s\pscommander\pscommander\Services\DataService.cs:line 26
at pscommander.MainWindow…ctor() in D:\a\1\s\pscommander\pscommander\MainWindow.xaml.cs:line 39
— End of inner exception stack trace —
at System.Windows.Markup.XamlReader.RewrapException(Exception e, IXamlLineInfo lineInfo, Uri baseUri)
at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
at System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)
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.<.ctor>b__1_0(Object unused)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(Object obj)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
— End of stack trace from previous location —
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext 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, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
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()
at pscommander.App.Main()

noahpeltier · June 14, 2021, 2:30pm

So After I pasted that, I saw that the db was in use. I checked and there was another copy of PSCommander running so I closed that out as well. After ending all pwsh and PSCommander instances, I tried again but no dice.

Faulting application name: PSCommander.exe, version: 1.0.0.0, time stamp: 0x600b9eb8
Faulting module name: KERNELBASE.dll, version: 10.0.19041.964, time stamp: 0x812662a7
Exception code: 0xe0434352
Fault offset: 0x0000000000034b89
Faulting process id: 0x4aec
Faulting application start time: 0x01d761281a5b4b8a
Faulting application path: C:\Program Files\WindowsPowerShell\Modules\PSCommander\1.4.6\PSCommander.exe
Faulting module path: C:\windows\System32\KERNELBASE.dll
Report Id: 6f9e6cd4-1173-42a8-a9e8-c3698eeb77f9
Faulting package full name:
Faulting package-relative application ID:

and:

Fault bucket 1763161532993954321, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: PSCommander.exe
P2: 1.0.0.0
P3: 600b9eb8
P4: KERNELBASE.dll
P5: 10.0.19041.964
P6: 812662a7
P7: e0434352
P8: 0000000000034b89
P9:
P10:

Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC0C4.tmp.dmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC1A0.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC1B1.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC1AF.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC1DE.tmp.txt

These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_PSCommander.exe_36e2eea94cba714c402e11d34b9512f45caf88cc_40cbd645_d776b78a-9dac-4596-aa40-845b712bf90d

Analysis symbol:
Rechecking for solution: 0
Report Id: 6f9e6cd4-1173-42a8-a9e8-c3698eeb77f9
Report Status: 268435456
Hashed bucket: 6eaa284afc4081f33878021297bce211
Cab Guid: 0

adam · June 14, 2021, 2:32pm

Do you have some time for a Zoom call tomorrow? I’d love to take a look at see if we can determine what’s happening.

noahpeltier · June 14, 2021, 7:13pm

Might have to schedule something on Thursday, I’m booked tomorrow and Wed, that alright?

Vmaxxer · July 1, 2021, 6:39pm

By the way, I’m seeing this same issue so any info would be great to see.

-John

Topic		Replies	Views
PSScriptpad Winforms Designer Failed to Create Component 'SplitContainer': System.NullReferenceException PowerShell Pro Tools Help	3	336	December 12, 2022
Powershell Tools Form Designer will not open in Visual Code PowerShell Pro Tools Help	6	864	May 21, 2021
Debugger seems to break "Invoke-Command" Universal Automation	5	613	February 23, 2022
PowerShell Pro Tools - Failed to load designer error message when opening existing 'designer.ps1' file PowerShell Tools	3	742	March 4, 2022
WPF Form Designer Problems PowerShell Tools	12	2520	August 19, 2021

.NET errors with PSCommander and Winforms Designer

Related topics