error after application installation
-
I have created a Windows application and used the setup wizard for deployment purposes. It runs perfectly well on my machine but after I install the application on another machine and try to start it I get an error that says; "Application has generated an exception that could not be handled. Process ID 0x450 (1104), Thread ID 0x3a8(936)." What have I messed up. Shawn the desparate programmer
-
I have created a Windows application and used the setup wizard for deployment purposes. It runs perfectly well on my machine but after I install the application on another machine and try to start it I get an error that says; "Application has generated an exception that could not be handled. Process ID 0x450 (1104), Thread ID 0x3a8(936)." What have I messed up. Shawn the desparate programmer
-
I have created a Windows application and used the setup wizard for deployment purposes. It runs perfectly well on my machine but after I install the application on another machine and try to start it I get an error that says; "Application has generated an exception that could not be handled. Process ID 0x450 (1104), Thread ID 0x3a8(936)." What have I messed up. Shawn the desparate programmer
You've probably already looked into these but . . . what the heck! Something missing perhaps? Is the expected version of the Framework installed? Do you use Crystal Reports or some other third party software? Config file? If you haven't already, you might want to use the build option that pulls all of the accessed assenblies into the local Bin folder. And no, I can't remember what or where to specify it off the top of my head. Sorry. Good luck! Will
-
I have created a Windows application and used the setup wizard for deployment purposes. It runs perfectly well on my machine but after I install the application on another machine and try to start it I get an error that says; "Application has generated an exception that could not be handled. Process ID 0x450 (1104), Thread ID 0x3a8(936)." What have I messed up. Shawn the desparate programmer
Apart from the framework being installed, ensure that your assembly has sufficient rights to execute on that machine (go to Control Panels -> Admin Tools -> .NET Framework Configuration utility). Errors like this occur because you have (probably) created the assembly on a machine under a userid which had local admin rights so you never saw any problem in development. Installing it onto another machine and running under a user without local admins rights highlights that there is something in your assembly which relies on more than normal rights to execute. This is a very good reason never to develop a program under a local admin id because inevitably you'll find out there is a problem only after deployment.
...Steve1. quod erat demonstrandum 2. "Give a man a fish and you've fed him for a day. Teach him how to fish and you've fed him for life." I read that somewhere once :-)