|
|
You're in the
dotnet distributed apps
group:Application Error when starting
dotnet distributed apps:
I've completed my first .Net project and I'm having problems getting it to
run on a client workstation. The client has the .NET framework installed, I'm using .msm files to install Crystal 9 (full product) and Farpoint spread. I used the setup project to create the setup program and it seems to work fine. When I start the application I receive "Application has generated an exception that could not be handled Process id-XXXX Thread id= XXXX". Am I missing a file? How do I find out what I'm missing? I use Microsoft Application Blocks Exception Management in the subroutines and not even getting to my splash. The compiled exe works fine on my development machine so I can only assume it's an issue with missing a reference, but I've checked all of them and they exist on the client machine. Any help would be
Do you see any further information in the event log or any app logs? Try
changing the code to capture all exceptions and logging/displaying more information about the error. For example, enclose your startup/initialization logic in a try..catch. Thanks, Sam -- _______________________________ Sam Santiago ssantiago@n0spam-SoftiTechture.com http://www.SoftiTechture.com _______________________________ [quoted text, click to view] "LisaConsult" <lisaconsult@online.nospam> wrote in message news:E18A5648-3CD2-4C29-BE0F-780E3A1329B6@microsoft.com... > I've completed my first .Net project and I'm having problems getting it to > run on a client workstation. The client has the .NET framework installed, > I'm using .msm files to install Crystal 9 (full product) and Farpoint spread. > I used the setup project to create the setup program and it seems to work > fine. When I start the application I receive "Application has generated an > exception that could not be handled Process id-XXXX Thread id= XXXX". Am I > missing a file? How do I find out what I'm missing? I use Microsoft > Application Blocks Exception Management in the subroutines and not even > getting to my splash. The compiled exe works fine on my development machine > so I can only assume it's an issue with missing a reference, but I've checked > all of them and they exist on the client machine. Any help would be > appreciated. Thanks
Thank you for your response. My start up code is enclosed in a try/catch,
with the catch set to publish with the exception manager (which we have writing to the event log and message to the user). It doesn't display anything to the event log other than what I described. I should mention that the error is coming from Common Language Runtime (CLR) not the applicaiton. Any other ideas? [quoted text, click to view] "Sam Santiago" wrote:
> Do you see any further information in the event log or any app logs? Try > changing the code to capture all exceptions and logging/displaying more > information about the error. For example, enclose your > startup/initialization logic in a try..catch. > > Thanks, > > Sam > > -- > _______________________________ > Sam Santiago > ssantiago@n0spam-SoftiTechture.com > http://www.SoftiTechture.com > _______________________________ > "LisaConsult" <lisaconsult@online.nospam> wrote in message > news:E18A5648-3CD2-4C29-BE0F-780E3A1329B6@microsoft.com... > > I've completed my first .Net project and I'm having problems getting it to > > run on a client workstation. The client has the .NET framework installed, > > I'm using .msm files to install Crystal 9 (full product) and Farpoint > spread. > > I used the setup project to create the setup program and it seems to work > > fine. When I start the application I receive "Application has generated > an > > exception that could not be handled Process id-XXXX Thread id= XXXX". Am > I > > missing a file? How do I find out what I'm missing? I use Microsoft > > Application Blocks Exception Management in the subroutines and not even > > getting to my splash. The compiled exe works fine on my development > machine > > so I can only assume it's an issue with missing a reference, but I've > checked > > all of them and they exist on the client machine. Any help would be > > appreciated. Thanks > >
Can you post some sample code showing what happens during your application
start? Also are you trapping errors at a global scope? The application object has a ThreadException Event and the AppDomain class has an UnhandledException event. Both of these events should be wired up to event handlers in your application. [quoted text, click to view] "LisaConsult" wrote:
> Thank you for your response. My start up code is enclosed in a try/catch, > with the catch set to publish with the exception manager (which we have > writing to the event log and message to the user). It doesn't display > anything to the event log other than what I described. I should mention that > the error is coming from Common Language Runtime (CLR) not the applicaiton. > Any other ideas? > > "Sam Santiago" wrote: > > > Do you see any further information in the event log or any app logs? Try > > changing the code to capture all exceptions and logging/displaying more > > information about the error. For example, enclose your > > startup/initialization logic in a try..catch. > > > > Thanks, > > > > Sam > > > > -- > > _______________________________ > > Sam Santiago > > ssantiago@n0spam-SoftiTechture.com > > http://www.SoftiTechture.com > > _______________________________ > > "LisaConsult" <lisaconsult@online.nospam> wrote in message > > news:E18A5648-3CD2-4C29-BE0F-780E3A1329B6@microsoft.com... > > > I've completed my first .Net project and I'm having problems getting it to > > > run on a client workstation. The client has the .NET framework installed, > > > I'm using .msm files to install Crystal 9 (full product) and Farpoint > > spread. > > > I used the setup project to create the setup program and it seems to work > > > fine. When I start the application I receive "Application has generated > > an > > > exception that could not be handled Process id-XXXX Thread id= XXXX". Am > > I > > > missing a file? How do I find out what I'm missing? I use Microsoft > > > Application Blocks Exception Management in the subroutines and not even > > > getting to my splash. The compiled exe works fine on my development > > machine > > > so I can only assume it's an issue with missing a reference, but I've > > checked > > > all of them and they exist on the client machine. Any help would be > > > appreciated. Thanks > > > >
Can you post some sample code showing what happens during your application
start? Also are you trapping errors at a global scope? The application object has a ThreadException Event and the AppDomain class has an UnhandledException event. Both of these events should be wired up to event handlers in your application. [quoted text, click to view] "LisaConsult" wrote:
> Thank you for your response. My start up code is enclosed in a try/catch, > with the catch set to publish with the exception manager (which we have > writing to the event log and message to the user). It doesn't display > anything to the event log other than what I described. I should mention that > the error is coming from Common Language Runtime (CLR) not the applicaiton. > Any other ideas? > > "Sam Santiago" wrote: > > > Do you see any further information in the event log or any app logs? Try > > changing the code to capture all exceptions and logging/displaying more > > information about the error. For example, enclose your > > startup/initialization logic in a try..catch. > > > > Thanks, > > > > Sam > > > > -- > > _______________________________ > > Sam Santiago > > ssantiago@n0spam-SoftiTechture.com > > http://www.SoftiTechture.com > > _______________________________ > > "LisaConsult" <lisaconsult@online.nospam> wrote in message > > news:E18A5648-3CD2-4C29-BE0F-780E3A1329B6@microsoft.com... > > > I've completed my first .Net project and I'm having problems getting it to > > > run on a client workstation. The client has the .NET framework installed, > > > I'm using .msm files to install Crystal 9 (full product) and Farpoint > > spread. > > > I used the setup project to create the setup program and it seems to work > > > fine. When I start the application I receive "Application has generated > > an > > > exception that could not be handled Process id-XXXX Thread id= XXXX". Am > > I > > > missing a file? How do I find out what I'm missing? I use Microsoft > > > Application Blocks Exception Management in the subroutines and not even > > > getting to my splash. The compiled exe works fine on my development > > machine > > > so I can only assume it's an issue with missing a reference, but I've > > checked > > > all of them and they exist on the client machine. Any help would be > > > appreciated. Thanks > > > >
Can you post some sample code showing what happens during your application
start? Also are you trapping errors at a global scope? The application object has a ThreadException Event and the AppDomain class has an UnhandledException event. Both of these events should be wired up to event handlers in your application. [quoted text, click to view] "LisaConsult" wrote:
> Thank you for your response. My start up code is enclosed in a try/catch, > with the catch set to publish with the exception manager (which we have > writing to the event log and message to the user). It doesn't display > anything to the event log other than what I described. I should mention that > the error is coming from Common Language Runtime (CLR) not the applicaiton. > Any other ideas? > > "Sam Santiago" wrote: > > > Do you see any further information in the event log or any app logs? Try > > changing the code to capture all exceptions and logging/displaying more > > information about the error. For example, enclose your > > startup/initialization logic in a try..catch. > > > > Thanks, > > > > Sam > > > > -- > > _______________________________ > > Sam Santiago > > ssantiago@n0spam-SoftiTechture.com > > http://www.SoftiTechture.com > > _______________________________ > > "LisaConsult" <lisaconsult@online.nospam> wrote in message > > news:E18A5648-3CD2-4C29-BE0F-780E3A1329B6@microsoft.com... > > > I've completed my first .Net project and I'm having problems getting it to > > > run on a client workstation. The client has the .NET framework installed, > > > I'm using .msm files to install Crystal 9 (full product) and Farpoint > > spread. > > > I used the setup project to create the setup program and it seems to work > > > fine. When I start the application I receive "Application has generated > > an > > > exception that could not be handled Process id-XXXX Thread id= XXXX". Am > > I > > > missing a file? How do I find out what I'm missing? I use Microsoft > > > Application Blocks Exception Management in the subroutines and not even > > > getting to my splash. The compiled exe works fine on my development > > machine > > > so I can only assume it's an issue with missing a reference, but I've > > checked > > > all of them and they exist on the client machine. Any help would be > > > appreciated. Thanks > > > >
It also may be related to Application Blocks Exception Management. I
suggest you may compile a sample in Application Blocks Exception Management and deploy it to your client computer. WIll this sample app work on it? Luke
Thats a good idea luke.
Sorry for the multiple posts - I did'nt do that intentionally. [quoted text, click to view] "[MSFT]" wrote:
> It also may be related to Application Blocks Exception Management. I > suggest you may compile a sample in Application Blocks Exception Management > and deploy it to your client computer. WIll this sample app work on it? > > Luke >
Thank you for the reply. If you have further questions on this issue,
please feel free to post here. Luke
Thanks to all for the reply. I finally figured out the error although I'm a
bit confused by it. Here's the deal: When we started the project one developer brought in the AX control PolarZipLight. .Net named the control AXPolarZipLight. However at somepoint when the control wasn't found on my machine (we are not all on the same network so we "passed" the project around), it could not find AXPolarZipLight, so I pulled it from my machine, but .Net brought it in as PolarzipLight (no AX) (First question....Why?). Somewhere in the process of passing the project, we noticed that there were 2 so we got rid of PolarZipLight and just kept AXPolarZipLight because the AX referenced one was the one actually named in the project. But, evidently although it was not reference in the project references, the compile was still using PolarZipLight (no AX). How do I know and how did I find such a crazy thing!?! Well, after trying several things (built HelloWorld app for computer and slowly added components) I still couldn't find the problem and in a point of desperation I put a Try..Catch in the InitializeComponents routine of the form. You can't view a form with that in there, but it does compile and it gave me the tiny bit of insight that I needed. I thought .net was supposed to resolve all of our DLL troubles! I found this more mysterious than dealing with an out of version DLL. Anyway, I'm still not sure how to resolve this so that it compiles and uses the AXPolarZipLight reference rather than the other. Any one run across this? Thanks for all
I have seen similar behavior if you are using integrated SourceSafe with
VStudio. Someone removes a reference, but somehow after another developer checks in the project the reference is re-established. You might want to simply load your project file into Notepad and examine the references that way. The project file is simply an XML file, so it's not a problem to view that way. I have deleted references via Notepad in the past with no problems. Thanks, Sam -- _______________________________ Sam Santiago ssantiago@n0spam-SoftiTechture.com http://www.SoftiTechture.com _______________________________ [quoted text, click to view] "LisaConsult" <lisaconsult@online.nospam> wrote in message news:3EF5D287-B57A-417F-903F-A48703E4A932@microsoft.com... > Thanks to all for the reply. I finally figured out the error although I'm a > bit confused by it. Here's the deal: When we started the project one > developer brought in the AX control PolarZipLight. .Net named the control > AXPolarZipLight. However at somepoint when the control wasn't found on my > machine (we are not all on the same network so we "passed" the project > around), it could not find AXPolarZipLight, so I pulled it from my machine, > but .Net brought it in as PolarzipLight (no AX) (First question....Why?). > Somewhere in the process of passing the project, we noticed that there were 2 > so we got rid of PolarZipLight and just kept AXPolarZipLight because the AX > referenced one was the one actually named in the project. But, evidently > although it was not reference in the project references, the compile was > still using PolarZipLight (no AX). How do I know and how did I find such a > crazy thing!?! Well, after trying several things (built HelloWorld app for > computer and slowly added components) I still couldn't find the problem and > in a point of desperation I put a Try..Catch in the InitializeComponents > routine of the form. You can't view a form with that in there, but it does > compile and it gave me the tiny bit of insight that I needed. I thought ..net > was supposed to resolve all of our DLL troubles! I found this more > mysterious than dealing with an out of version DLL. Anyway, I'm still not > sure how to resolve this so that it compiles and uses the AXPolarZipLight > reference rather than the other. Any one run across this? Thanks for all > the suggestions.
However, I guess my question is, how can I get my machined to set up the
reference the same with AXPolarZipLight so that I can compile it properly? Why do they come in differently on different machines? Is there some setting? Is it the difference between versions of Visual Studio? [quoted text, click to view] "Sam Santiago" wrote:
> I have seen similar behavior if you are using integrated SourceSafe with > VStudio. Someone removes a reference, but somehow after another developer > checks in the project the reference is re-established. You might want to > simply load your project file into Notepad and examine the references that > way. The project file is simply an XML file, so it's not a problem to view > that way. I have deleted references via Notepad in the past with no > problems. > > Thanks, > > Sam > > -- > _______________________________ > Sam Santiago > ssantiago@n0spam-SoftiTechture.com > http://www.SoftiTechture.com > _______________________________ > "LisaConsult" <lisaconsult@online.nospam> wrote in message > news:3EF5D287-B57A-417F-903F-A48703E4A932@microsoft.com... > > Thanks to all for the reply. I finally figured out the error although I'm > a > > bit confused by it. Here's the deal: When we started the project one > > developer brought in the AX control PolarZipLight. .Net named the control > > AXPolarZipLight. However at somepoint when the control wasn't found on my > > machine (we are not all on the same network so we "passed" the project > > around), it could not find AXPolarZipLight, so I pulled it from my > machine, > > but .Net brought it in as PolarzipLight (no AX) (First question....Why?). > > Somewhere in the process of passing the project, we noticed that there > were 2 > > so we got rid of PolarZipLight and just kept AXPolarZipLight because the > AX > > referenced one was the one actually named in the project. But, evidently > > although it was not reference in the project references, the compile was > > still using PolarZipLight (no AX). How do I know and how did I find such > a > > crazy thing!?! Well, after trying several things (built HelloWorld app > for > > computer and slowly added components) I still couldn't find the problem > and > > in a point of desperation I put a Try..Catch in the InitializeComponents > > routine of the form. You can't view a form with that in there, but it > does > > compile and it gave me the tiny bit of insight that I needed. I thought > ..net > > was supposed to resolve all of our DLL troubles! I found this more > > mysterious than dealing with an out of version DLL. Anyway, I'm still not > > sure how to resolve this so that it compiles and uses the AXPolarZipLight > > reference rather than the other. Any one run across this? Thanks for all > > the suggestions. > >
Is AXPolarZipLight also a project from your team? I suggest you may strong
name it. And then remove the reference and add again. Such a problem may be related to that you have multiple version of AXPolarZipLight. Luke
No, PolarZipLight is a 3rd Party DLL. We all installed it from the same
install program. The file is a COM DLL originally used in VB6. We are using different versions of VS.NET (one is enterprise, one is just VB.NET standard). You see, I believe there is something in the import of a Com Object into the project through VS.NET that must be different since by default one comes in as AX, the other as Interop. Until I get a resolution, I'm including both DLLs in the build, but this really is not a long term solution. Thanks. [quoted text, click to view] "[MSFT]" wrote:
> Is AXPolarZipLight also a project from your team? I suggest you may strong > name it. And then remove the reference and add again. Such a problem may be > related to that you have multiple version of AXPolarZipLight. > > Luke >
It seems a COM registry issue. When adding COM component in VS.NET, it will
create the interop assembly and namespace based on the COM registry information. I am not sure if this is caused by that there are different registry information on the two computers. I suggest you may remove both of the two references and add again. Anyway, leave just two same references as they are being now won't cause problems. Luke
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |