Not Able to Start Zaptest after account activation

Not Able to Start Zaptest after account activation

Home Forums Ask Expert Not Able to Start Zaptest after account activation

Viewing 14 posts - 16 through 29 (of 29 total)
  • Author
    Posts
  • #32552
    Aries Ang
    Participant

      Let me try it out and feedback.

      #32554
      Aries Ang
      Participant

        Hi,

        Unfortunately I still face the same issue. The error in the event log is exactly the same as I posted previously.

        I will wait for your R&D team’s investigation update then.

        Thanks
        Aries

        #32559
        Aries Ang
        Participant

          Is there any good news for me?

          #32560
          Valentin ZAP
          Keymaster

            Hello!

            Our RnD team is working on your case right now. I’ll let you know when they release a beta build for you.

            Thank you,
            ZAPTEST Team

            #32562
            Valentin ZAP
            Keymaster

              Hello!

              Could you let us know – do you use any firewall or security systems (antivirus)? The system could be local to the computer or have global installation (over the network).

              Thank you,
              ZAPTEST Team

              #32563
              Aries Ang
              Participant

                Hi,

                Yes, we are definitely in a firewall and antivirus. It is the same image that are being used organizational wide. If you need more details on these, I won’t be able to answer them, it will require our network and security to assist on this.

                Regards
                Aries

                #32564
                Aries Ang
                Participant

                  Perhaps it will be more effective if we can get on a call together with our security team to get to the bottom of this?

                  If we are OK for this suggestion, can I have your email so that I can send the invite once it is arranged.

                  Thanks
                  Aries

                  #32570
                  Valentin ZAP
                  Keymaster

                    Hello!

                    Sorry for long response! Could you try to replace this library in your ZAPTEST installation folder:

                    1. Close ZAPTEST if open and check processes via “Task Explorer”
                    2. Download this file and replace here: “C:Program Files (x86)ZAP-fiXStandalone

                    PS. You should have the latest public version installed.

                    If you still get experience the issue, please attach the logs:

                    1. Update shortcut icon to use logs director: by using -logs key: ZAPTEST.EXE -logs [path to the folder]

                    logs.png

                    Thank you,
                    ZAPTEST Team

                    #32571
                    Aries Ang
                    Participant

                      Hi,

                      I tried with the .dll file you provided but it still didn’t work.

                      I tried your steps for the logs, but it didn’t work too.

                      But I get different errors this time around:
                      Error1:
                      Faulting application name: ZAPTEST.exe, version: 1.0.0.0, time stamp: 0x5ddd9898
                      Faulting module name: KERNELBASE.dll, version: 10.0.18362.476, time stamp: 0x540698cd
                      Exception code: 0xe0434352
                      Fault offset: 0x001135d2
                      Faulting process id: 0x6218
                      Faulting application start time: 0x01d5a4e770226dd5
                      Faulting application path: C:Program Files (x86)ZAP-fiXStandaloneZAPTEST.exe
                      Faulting module path: C:WINDOWSSystem32KERNELBASE.dll
                      Report Id: 6c329ff9-518f-4a42-b88a-c74bb35d8782
                      Faulting package full name:
                      Faulting package-relative application ID:

                      Error2:
                      Application: ZAPTEST.exe
                      Framework Version: v4.0.30319
                      Description: The process was terminated due to an unhandled exception.
                      Exception Info: System.TypeLoadException
                      at Zap.WpfControlLibrary.Controllers.ZaptestController.InitZaptest(Zap.WpfControlLibrary.Windows.ZaptestWindow, System.String[])
                      at Zap.WpfControlLibrary.Windows.ZaptestWindow.ZaptestWindow_OnInitialized(System.Object, System.EventArgs)
                      at System.Windows.FrameworkElement.RaiseInitialized(System.Windows.EventPrivateKey, System.EventArgs)
                      at System.Windows.FrameworkElement.OnInitialized(System.EventArgs)
                      at Zap.Common.Core.Windows.BaseWindow.OnInitialized(System.EventArgs)
                      at System.Windows.FrameworkElement.TryFireInitialized()
                      at System.Windows.FrameworkElement.EndInit()
                      at MS.Internal.Xaml.Runtime.ClrObjectRuntime.InitializationGuard(System.Xaml.XamlType, System.Object, Boolean)

                      Exception Info: System.Windows.Markup.XamlParseException
                      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 System.Windows.Application.LoadBamlStreamWithSyncInfo(System.IO.Stream, System.Windows.Markup.ParserContext)
                      at System.Windows.Application.LoadComponent(System.Uri, Boolean)
                      at System.Windows.Application.DoStartup()
                      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.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
                      at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(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 MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, 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 DynamicClass.(System.Object)
                      at A.c98bfe3d760ed3a8be3c0b21859cb10e6.c9d44ab54c482c5ea5889e146291d5492(System.Object)
                      at Zap.Zaptest.App.Main()

                      #32573
                      Valentin ZAP
                      Keymaster

                        Hello!

                        Somehow the patch and the installed version are different. It could be the reason because yesterday our Team released a new public version of ZAPTEST.

                        Could you try it? It contains a few improvements regarding your issue.

                        Thank you,
                        ZAPTEST Team

                        #32574
                        Aries Ang
                        Participant

                          Hi,

                          I actually downloaded the latest released version from your website, ZAPTEST_19.6.30!

                          The errors I posted yesterday was with the latest released build.

                          Thanks
                          Aries

                          #32575
                          Valentin ZAP
                          Keymaster

                            Hello!

                            Thank you for the information. Our RnD team is asking for your help to inspect your issue:

                            1. Could you try to remove all configuration folders:

                            • C:Users[USERNAME]DocumentsZAPTESTPreferences
                            • C:Users[USERNAME]AppDataRoamingZAP Technologies, Inc

                            2. Could you try replace this DLL and use -logs command line argument (see my previous post) to retrieve some logs. You should get your log in case of getting KERNELBASE or CLR errors:

                            Thank you,
                            ZAPTEST Team

                            #32576
                            Aries Ang
                            Participant

                              Hi,

                              I had followed your instruction to replace the dll file. This time, the application didn’t even get started.

                              There is not any logs created in the folder that I specified using your cmd logs command in the Target (see screenshot)

                              Can we have a webex concall to go through this once and for all? I don’t think replying messages back and forth as such is effective, it has been near to 4 weeks since this ticket was logged.

                              Thanks
                              Aries

                              #32577
                              Valentin ZAP
                              Keymaster

                                Hello!

                                Sure, I’ll send this information to our managers to schedule the meeting!

                                Thank you,
                                ZAPTEST Team

                              Viewing 14 posts - 16 through 29 (of 29 total)
                              • You must be logged in to reply to this topic.

                              Virtual Expert

                              ZAPTEST

                              ZAPTEST Logo