Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. Visual Basic
  4. Weird error that only happens sometimes..

Weird error that only happens sometimes..

Scheduled Pinned Locked Moved Visual Basic
data-structuresdebugginghelploungeworkspace
6 Posts 3 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • P Offline
    P Offline
    programmervb netc
    wrote on last edited by
    #1

    I am getting an error that I cannot reproduce in the dev environment.. Here is the information I have captured from the deployed app. Please tell me what this means if it means anymore to you than myself. Also it would be cool if you could tell me why my stack trace does not show the line numbers like many other stack traces that I have seen. This error is very random there does not seem to a consistent set of steps that causes it. Error number 5 T Create__Instance__[T](T) An error occurred creating the form. See Exception.InnerException for details. The error is: Exception has been thrown by the target of an invocation. Stack trace at ClientDBv3.My.MyProject.MyForms.Create__Instance__[T](T Instance) at ClientDBv3.frmClientCommon1..ctor() at ClientDBv3.frmMainForm.sCallClientScreen(Int64 lUniqueNumber, String tMode) at ClientDBv3.frmMainForm.btnOpen_Click(Object sender, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) thank you.

    Humble Programmer

    L G 2 Replies Last reply
    0
    • P programmervb netc

      I am getting an error that I cannot reproduce in the dev environment.. Here is the information I have captured from the deployed app. Please tell me what this means if it means anymore to you than myself. Also it would be cool if you could tell me why my stack trace does not show the line numbers like many other stack traces that I have seen. This error is very random there does not seem to a consistent set of steps that causes it. Error number 5 T Create__Instance__[T](T) An error occurred creating the form. See Exception.InnerException for details. The error is: Exception has been thrown by the target of an invocation. Stack trace at ClientDBv3.My.MyProject.MyForms.Create__Instance__[T](T Instance) at ClientDBv3.frmClientCommon1..ctor() at ClientDBv3.frmMainForm.sCallClientScreen(Int64 lUniqueNumber, String tMode) at ClientDBv3.frmMainForm.btnOpen_Click(Object sender, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) thank you.

      Humble Programmer

      L Offline
      L Offline
      Luc Pattyn
      wrote on last edited by
      #2

      Hi, in order to provide line numbers, the EXE (and the DLL files it depends on) need the presence of the PDB files next to the files they relate to. The actual situation and problem description is too vague to work on. :)

      Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]


      I only read code that is properly formatted, adding PRE tags is the easiest way to obtain that.


      P 2 Replies Last reply
      0
      • L Luc Pattyn

        Hi, in order to provide line numbers, the EXE (and the DLL files it depends on) need the presence of the PDB files next to the files they relate to. The actual situation and problem description is too vague to work on. :)

        Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]


        I only read code that is properly formatted, adding PRE tags is the easiest way to obtain that.


        P Offline
        P Offline
        programmervb netc
        wrote on last edited by
        #3

        So I would have to deploy in Debug mode this that correct? If my understanding is correct the only problem that deploying like would cause is that somethings would not be optimized is that a correct assumption.

        Humble Programmer

        L 1 Reply Last reply
        0
        • L Luc Pattyn

          Hi, in order to provide line numbers, the EXE (and the DLL files it depends on) need the presence of the PDB files next to the files they relate to. The actual situation and problem description is too vague to work on. :)

          Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]


          I only read code that is properly formatted, adding PRE tags is the easiest way to obtain that.


          P Offline
          P Offline
          programmervb netc
          wrote on last edited by
          #4

          Do you know what the error could be referring to?

          Humble Programmer

          1 Reply Last reply
          0
          • P programmervb netc

            So I would have to deploy in Debug mode this that correct? If my understanding is correct the only problem that deploying like would cause is that somethings would not be optimized is that a correct assumption.

            Humble Programmer

            L Offline
            L Offline
            Luc Pattyn
            wrote on last edited by
            #5

            deploy a debug build and include the PDB file(s), that is what I recommend. :)

            Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]


            I only read code that is properly formatted, adding PRE tags is the easiest way to obtain that.


            1 Reply Last reply
            0
            • P programmervb netc

              I am getting an error that I cannot reproduce in the dev environment.. Here is the information I have captured from the deployed app. Please tell me what this means if it means anymore to you than myself. Also it would be cool if you could tell me why my stack trace does not show the line numbers like many other stack traces that I have seen. This error is very random there does not seem to a consistent set of steps that causes it. Error number 5 T Create__Instance__[T](T) An error occurred creating the form. See Exception.InnerException for details. The error is: Exception has been thrown by the target of an invocation. Stack trace at ClientDBv3.My.MyProject.MyForms.Create__Instance__[T](T Instance) at ClientDBv3.frmClientCommon1..ctor() at ClientDBv3.frmMainForm.sCallClientScreen(Int64 lUniqueNumber, String tMode) at ClientDBv3.frmMainForm.btnOpen_Click(Object sender, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) thank you.

              Humble Programmer

              G Offline
              G Offline
              Gideon Engelberth
              wrote on last edited by
              #6

              Just on a hunch, are you using the "default form instance" facility that VB.NET provides to help with upgrading VB6 apps? My guess is that there is some problem that is occurring the first time you use frmClientCommon1. Did you do what the error message suggested and look at the InnerException? The inner exception should provide you with more useful information about what is going wrong. Also, as a general tip, think about what is different between the dev environment and production environment. Different connection strings needed? Missing data files? Registry settings? Basically anything that might be set up differently.

              1 Reply Last reply
              0
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


              • Login

              • Don't have an account? Register

              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • World
              • Users
              • Groups