DLM Automation crashes when run

benjtbenjt Posts: 1 New member
in DLM Automation
We had DLM Automation version 1.3 installed and running without issue. I am attempting to upgrade to DLM Automation version 2. The installer finished without errors. However when I run DLM Automation, it crashes with the following details.

Problem Event Name:        CLR20r3

  Problem Signature 01:        RedGate.DLMAutomation.exe

  Problem Signature 02:        2.0.32.1199

  Problem Signature 03:        f9dc7ad5

  Problem Signature 04:        mscorlib

  Problem Signature 05:        4.7.2117.0

  Problem Signature 06:        59cf513d

  Problem Signature 07:        165d

  Problem Signature 08:        ca

  Problem Signature 09:        System.Windows.Markup.XamlParse

  OS Version:        6.2.9200.2.0.0.272.7

  Locale ID:        1033

  Additional Information 1:        6d04

  Additional Information 2:        6d0490a44eb8d1c1579148eaaaae3033

  Additional Information 3:        5764

  Additional Information 4:        5764f50261bcc31ebba0e54970aae0f3

 

Read our privacy statement online:

  http://go.microsoft.com/fwlink/?linkid=190175

 

If the online privacy statement is not available, please read our privacy statement offline:

  C:\Windows\system32\en-US\erofflps.txt


I attempted an upgrade the first time around. Then I noticed and both versions of DLM Automation were installed. I uninstalled both, rebooted, and re-attempted to install version 2. It is still crashing. The error seems to be related to .NET. We have .NET 4.6 SDK installed. I don't know if the SDK versus the runtime makes a difference. The operating system is Windows Server 2012
Tagged:
· Share on Twitter

Answers

  • Andrea_AngellaAndrea_Angella Posts: 66 Silver 4
    We require .NET Framework 4.6.1

    However, with the latest version of DLM, now called SQL Change Automation you no longer need to install DLM Automation on your build agents in order to be able to run your cmdlets. The module will be downloaded from the PowerShell gallery 

    Would you be able to give it a try?
    https://www.powershellgallery.com/packages/SqlChangeAutomation/3.1.3.3059
    Andrea Angella
    Lead Software Engineer | Red Gate
    Website: www.productivecsharp.com
    Twitter: @angella_andrea
    · Share on Twitter
  • DatabaseOperationsDatabaseOperations Posts: 4 New member
    edited January 22, 2019 3:15PM
    I get the same error as well.

    Currently installed on server - 
    - Windows Server 2008 R2 SP1 Datacenter
    - Windows PowerShell 3.0
    - .NET Framework 4.6.1
    - DLMAutomationSuite 1.4

    Requirements are met for DLM 2 as per - https://documentation.red-gate.com/dlma2/requirements

    To upgrade DLM from 1.4 to 2.0, I installed DLM 2.0.32.1199. 
    Install finished successfully, server was restarted,
    However as mentioned in the original post, DLM app crashes.

    Also, after upgrade I tried running the PS cmdlet, it gave this error -
    The term 'Register-DlmSerialNumber' is not recognized as the name of a cmdlet, function, script file, or operable program.

    I uninstalled DLM1.4 completely and reinstalled DLM2.0, still get the same error.

    Server event logs  - 
    ----------------------
    Application: RedGate.DLMAutomation.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.IO.FileNotFoundException
       at System.IO.__Error.WinIOError(Int32, System.String)
       at System.IO.FileStream.Init(System.String, System.IO.FileMode, System.IO.FileAccess, Int32, Boolean, System.IO.FileShare, Int32, System.IO.FileOptions, SECURITY_ATTRIBUTES, System.String, Boolean, Boolean, Boolean)
       at System.IO.FileStream..ctor(System.String, System.IO.FileMode, System.IO.FileAccess, System.IO.FileShare)
       at MS.Internal.AppModel.SiteOfOriginPart.HandleFileSource(Boolean)
       at MS.Internal.AppModel.SiteOfOriginPart.GetStreamAndSetContentType(Boolean)
       at System.IO.Packaging.PackagePart.GetStream(System.IO.FileMode, System.IO.FileAccess)
       at System.IO.Packaging.PackWebResponse+CachedResponse.GetResponseStream()
       at System.IO.Packaging.PackWebResponse.get_ContentType()
       at System.Windows.Media.Imaging.BitmapDecoder.SetupDecoderFromUriOrStream(System.Uri, System.IO.Stream, System.Windows.Media.Imaging.BitmapCacheOption, System.Guid ByRef, Boolean ByRef, System.IO.Stream ByRef, System.IO.UnmanagedMemoryStream ByRef, Microsoft.Win32.SafeHandles.SafeFileHandle ByRef)
       at System.Windows.Media.Imaging.BitmapDecoder.CreateFromUriOrStream(System.Uri, System.Uri, System.IO.Stream, System.Windows.Media.Imaging.BitmapCreateOptions, System.Windows.Media.Imaging.BitmapCacheOption, System.Net.Cache.RequestCachePolicy, Boolean)
       at System.Windows.Media.Imaging.BitmapFrame.CreateFromUriOrStream(System.Uri, System.Uri, System.IO.Stream, System.Windows.Media.Imaging.BitmapCreateOptions, System.Windows.Media.Imaging.BitmapCacheOption, System.Net.Cache.RequestCachePolicy)
       at System.Windows.Media.ImageSourceConverter.ConvertFrom(System.ComponentModel.ITypeDescriptorContext, System.Globalization.CultureInfo, System.Object)
       at MS.Internal.Xaml.Runtime.ClrObjectRuntime.CallProvideValue(System.Windows.Markup.MarkupExtension, System.IServiceProvider)

    Exception Info: System.Windows.Markup.XamlParseException
       at System.Windows.Markup.XamlReader.RewrapException(System.Exception, System.Xaml.IXamlLineInfo, System.Uri)
       at System.Windows.Markup.WpfXamlLoader.Load(System.Xaml.XamlReader, System.Xaml.IXamlObjectWriterFactory, Boolean, System.Object, System.Xaml.XamlObjectWriterSettings, System.Uri)
       at System.Windows.Markup.WpfXamlLoader.LoadBaml(System.Xaml.XamlReader, Boolean, System.Object, System.Xaml.Permissions.XamlAccessLevel, System.Uri)
       at System.Windows.Markup.XamlReader.LoadBaml(System.IO.Stream, System.Windows.Markup.ParserContext, System.Object, Boolean)
       at RedGate.DLMAutomation.App.OnStartup(System.Windows.StartupEventArgs)
       at System.Windows.Application.<.ctor>b__1_0(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.DispatcherOperation.InvokeImpl()
       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.Application.RunDispatcher(System.Object)
       at System.Windows.Application.RunInternal(System.Windows.Window)
       at RedGate.DLMAutomation.App.Main()

    · Share on Twitter
Sign In or Register to comment.