Understanding the Startup Sequence: Separated OnInit and OnLoad Sequence These errors occur once the server has been instantiated and initialized and usually occur during the load phase of the server. The other area is server startup errors in FoxPro code. These are thorny issues, but I'm not going to cover them much here. that outright make your server fail before it ever gets a chance to be instantiated. System errors are permissions, invalid progIds, DCOM misconfigurations etc. Startup errors tend to fall into two categories:
#West wind web surge checksite error code
Simulate the user environment you will use on the server locally (if possible) and see what happens.Īlways make sure the app runs locally first because it's a heck of a lot easier to debug code on the development machine where you can step through code, than on a server where you usually cannot. This should be obvious: But always, always run your server locally first, with an environment as close as possible to what you are running on the server. If it's not by all means debug it locally and not on the server. Make sure your local application works obviously, but that's the first line of defense: Make sure the error is indeed specific to your server's environment. If you run into issues here you can also double check your development code to see if you can duplicate the behavior. If you are running in file mode it's often easier to find startup problems, because you tend to run the application in interactive mode which means you get to see errors pop up in the FoxPro Window. You build your application on your development machine, then deploy it on a live server and boom - something goes wrong and the server doesn't start.Įven if you're running in COM mode if you have startup problems with your COM server it's often a good idea to first switch the COM server into File mode, then run as a file mode applications. One of the most common problems people run into with Web Connection application startup errors. In this post I want to talk about server startup problems - specifically FoxPro code startup errors (rather than system startup errors due to permissions/configuration etc.). There are many reasons that this can happen from botched permissions on folders or DCOM to startup errors.
Using the preconfigured configuration should in most cases just make your servers work.īut we live in an imperfect world and things do go bump in the night - and so it can still happen that your Web Connection server won't start up. The configuration is a PRG file that you can customize so if you need configure additional folders, set different permissions or copy files around as part of config - you can do that. This produces a well-known configuration that creates virtuals, scriptmaps and sets common permissions on folders. It's now possible to create a new project and use the built-in configuration features to quickly and reliably configure your application on a server with yourApp.exe CONFIG from the command line. Web Connection 6.0 and later has made it much easier to create a predictable and repeatable installation with Web Connection.
0 kommentar(er)
