VB.Net, Unable to distribute VB.net App onto Windows 2000 machines

Unable to distribute VB.net App onto Windows 2000 machines

Author	Message
Andr #1 / 7	Unable to distribute VB.net App onto Windows 2000 machines I am trying to distribute a VB.net windows application onto a Windows 2000 machine with the .net framework. Once it has been install and run I get an error: Common Language Debugging Service Application has generated an exception that could not be handeled Process id=0x434(1076), Thread id=0x200(512) I have tryed this on a few of Windows 2000 machines with the same result. It works fine on Windows XP machines with the .net framework. I have also tried loading it onto a machine with just the normal framework, with the framework and the SP1 patch, with the framework and SP1 and all the updates recommended by the windows update site. As well as different types of distribution(the DEBUG and RELEASE types). All with the same result, the same error message every time. Does anyone have any ideas as to how to get it to run?. Andrew.
Wed, 08 Dec 2004 00:09:56 GMT

aka Gregory A. Beame #2 / 7	Unable to distribute VB.net App onto Windows 2000 machines Using COM+? I have heard that this is a problem with .NET on Windows 2000. I have not personally messed with it yet, but I have noticed that COM+ is a problem on Windows 2000 on some of my tests. -- Gregory A. Beamer MVP; MCP: +I, SE, SD, DBA Author: ADO.NET and XML: ASP.NET on the Edge ************************************************************************** Think outside the box! ************************************************************************ ** Quote: > I am trying to distribute a VB.net windows application onto a Windows > 2000 machine with the .net framework. Once it has been install and run > I get an error: > Common Language Debugging Service > Application has generated an exception that could not be handeled > Process id=0x434(1076), Thread id=0x200(512) > I have tryed this on a few of Windows 2000 machines with the same > result. It works fine on Windows XP machines with the .net framework. > I have also tried loading it onto a machine with just the normal > framework, with the framework and the SP1 patch, with the framework > and SP1 and all the updates recommended by the windows update site. As > well as different types of distribution(the DEBUG and RELEASE types). > All with the same result, the same error message every time. > Does anyone have any ideas as to how to get it to run?. > Andrew.
Wed, 08 Dec 2004 00:15:47 GMT

Andr #3 / 7	Unable to distribute VB.net App onto Windows 2000 machines No COM+. Only bog standard .NET controls, plus a custom control which extended the System.Windows.Forms.Control class. But the other .NET application I try to install the same way does not have anything special in it, and it has the same problem. Andrew Quote: > Using COM+? I have heard that this is a problem with .NET on Windows 2000. I > have not personally messed with it yet, but I have noticed that COM+ is a > problem on Windows 2000 on some of my tests. > -- > Gregory A. Beamer > MVP; MCP: +I, SE, SD, DBA > Author: ADO.NET and XML: ASP.NET on the Edge > ************************************************************************** > > Think outside the box! > ************************************************************************ > ** > > I am trying to distribute a VB.net windows application onto a Windows > > 2000 machine with the .net framework. Once it has been install and run > > I get an error: > > Common Language Debugging Service > > Application has generated an exception that could not be handeled > > Process id=0x434(1076), Thread id=0x200(512) > > I have tryed this on a few of Windows 2000 machines with the same > > result. It works fine on Windows XP machines with the .net framework. > > I have also tried loading it onto a machine with just the normal > > framework, with the framework and the SP1 patch, with the framework > > and SP1 and all the updates recommended by the windows update site. As > > well as different types of distribution(the DEBUG and RELEASE types). > > All with the same result, the same error message every time. > > Does anyone have any ideas as to how to get it to run?. > > Andrew.
Wed, 08 Dec 2004 16:42:19 GMT

Programati #4 / 7	Unable to distribute VB.net App onto Windows 2000 machines Why don't you try catching exception in your code. This way you will know which part of the code is throwing exception and why (from the error message). Quote: > No COM+. > Only bog standard .NET controls, plus a custom control which extended > the System.Windows.Forms.Control class. But the other .NET application > I try to install the same way does not have anything special in it, > and it has the same problem. > Andrew > "Cowboy \(aka Gregory A. Beamer\) [MVP]" Quote: > > Using COM+? I have heard that this is a problem with .NET on Windows 2000. I > > have not personally messed with it yet, but I have noticed that COM+ is a > > problem on Windows 2000 on some of my tests. > > -- > > Gregory A. Beamer > > MVP; MCP: +I, SE, SD, DBA > > Author: ADO.NET and XML: ASP.NET on the Edge ************************************************************************** Quote: > > > > Think outside the box! ************************************************************************ Quote: > > ** > > > I am trying to distribute a VB.net windows application onto a Windows > > > 2000 machine with the .net framework. Once it has been install and run > > > I get an error: > > > Common Language Debugging Service > > > Application has generated an exception that could not be handeled > > > Process id=0x434(1076), Thread id=0x200(512) > > > I have tryed this on a few of Windows 2000 machines with the same > > > result. It works fine on Windows XP machines with the .net framework. > > > I have also tried loading it onto a machine with just the normal > > > framework, with the framework and the SP1 patch, with the framework > > > and SP1 and all the updates recommended by the windows update site. As > > > well as different types of distribution(the DEBUG and RELEASE types). > > > All with the same result, the same error message every time. > > > Does anyone have any ideas as to how to get it to run?. > > > Andrew.
Thu, 09 Dec 2004 07:17:05 GMT

Andr #5 / 7	Unable to distribute VB.net App onto Windows 2000 machines Hi, I tried your idea of trying to catch the exception at the start of the application, but the error contines to occur. It seems as if the exception is happening in the CLR before it begins the application, but this only happens on the win 2000 machines. Andrew. Quote: > Why don't you try catching exception in your code. This way you will know > which part of the code is throwing exception and why (from the error > message). > > No COM+. > > Only bog standard .NET controls, plus a custom control which extended > > the System.Windows.Forms.Control class. But the other .NET application > > I try to install the same way does not have anything special in it, > > and it has the same problem. > > Andrew > > "Cowboy \(aka Gregory A. Beamer\) [MVP]" > > > Using COM+? I have heard that this is a problem with .NET on Windows > 2000. I > > > have not personally messed with it yet, but I have noticed that COM+ is > a > > > problem on Windows 2000 on some of my tests. > > > -- > > > Gregory A. Beamer > > > MVP; MCP: +I, SE, SD, DBA > > > Author: ADO.NET and XML: ASP.NET on the Edge > ************************************************************************** > > > > > > Think outside the box! > ************************************************************************ > > > ** > > > > I am trying to distribute a VB.net windows application onto a Windows > > > > 2000 machine with the .net framework. Once it has been install and run > > > > I get an error: > > > > Common Language Debugging Service > > > > Application has generated an exception that could not be handeled > > > > Process id=0x434(1076), Thread id=0x200(512) > > > > I have tryed this on a few of Windows 2000 machines with the same > > > > result. It works fine on Windows XP machines with the .net framework. > > > > I have also tried loading it onto a machine with just the normal > > > > framework, with the framework and the SP1 patch, with the framework > > > > and SP1 and all the updates recommended by the windows update site. As > > > > well as different types of distribution(the DEBUG and RELEASE types). > > > > All with the same result, the same error message every time. > > > > Does anyone have any ideas as to how to get it to run?. > > > > Andrew.
Fri, 10 Dec 2004 15:55:30 GMT

D Talbo #6 / 7	Unable to distribute VB.net App onto Windows 2000 machines I had this problem too after I had updated a 3rd party control. The solution for me turned out to be creating new copies of my forms by copying the code from them into blank classes. I just assumed that the resx file had become corrupted somehow and this forced it to recreate itself. Of course doing this you would also need to repopulate any imagelists or other controls that store their binary data in the resx file. DAz -- Remove NS from email address if replying directly
Fri, 10 Dec 2004 23:54:17 GMT

Andr #7 / 7	Unable to distribute VB.net App onto Windows 2000 machines Problem Solved. It turns out the XP machines have the most recent version of MDAC(2.7) on them, while the 2000 machines only carry 2.6 SP2. So the application has falling over when the connection to the SQL Server was made, but the fault was out side the .NET framework so the error was not caught. Andrew Quote: > I had this problem too after I had updated a 3rd party control. > The solution for me turned out to be creating new copies of my forms > by copying the code from them into blank classes. I just assumed that > the resx file had become corrupted somehow and this forced it to > recreate itself. > Of course doing this you would also need to repopulate any imagelists > or other controls that store their binary data in the resx file. > DAz
Tue, 14 Dec 2004 00:50:15 GMT

Page 1 of 1

[ 7 post ]