Results 1 to 5 of 5

Thread: Process id=0xe0c(3596) thread id=0xe10(3600)

  1. #1

    Thread Starter
    Junior Member
    Join Date
    Mar 2006
    Posts
    24

    Question Process id=0xe0c(3596) thread id=0xe10(3600)

    Hi All,

    I am after writing a Visual Basic.NET Windows Form application using Visual Studio.NET 2003.

    The application runs perfectly for me however when the end-user trys to run it they get the following error:

    Process id=0xe0c(3596) thread id=0xe10(3600)

    I've done a bit of rooting around and some people were suggesting that it could be an issue with the .NET Framework. However the user has installed the 1.1 and 2.0 framework and still the same error.

    Any help would be much appreciated.

    Thanks,
    Colm

  2. #2
    I'm about to be a PowerPoster! mendhak's Avatar
    Join Date
    Feb 2002
    Location
    Ulaan Baator GooGoo: Frog
    Posts
    38,170

    Re: Process id=0xe0c(3596) thread id=0xe10(3600)

    Do you have error handling in your application?

    If you do, then go back and introduce a global error handler which writes the errors to a text file or something convenient to you. You can then see what the problem is.

  3. #3

    Thread Starter
    Junior Member
    Join Date
    Mar 2006
    Posts
    24

    Re: Process id=0xe0c(3596) thread id=0xe10(3600)

    I have try/catch statements for things where I thought errors might happen. I think this is a generic thing and I'm not sure how I would handle it

  4. #4
    I'm about to be a PowerPoster! mendhak's Avatar
    Join Date
    Feb 2002
    Location
    Ulaan Baator GooGoo: Frog
    Posts
    38,170

    Re: Process id=0xe0c(3596) thread id=0xe10(3600)

    I meant, a global error handler. It should be able to catch any error in your app.

    If you're using C#, here's an example:
    http://www.pluralsight.com/blogs/cra...6/13/1455.aspx

  5. #5

    Thread Starter
    Junior Member
    Join Date
    Mar 2006
    Posts
    24

    Re: Process id=0xe0c(3596) thread id=0xe10(3600)

    Sorted this one. Turns out the issue is with the Windows security set-up for applications that are run on a network. This link helped me sort the issue. Hope it helps.

    http://blogs.msdn.com/shawnfa/archiv.../20/57023.aspx

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width