Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX/NT Operations and Administration | ||||||||
Changed: | ||||||||
< < | Note: The information here is generally obsolete since WinAppxD has been replaced by the APPX Login Manager. | |||||||
> > | Note: The information here is generally obsolete since WinAppxD has been replaced by the APPX Login Manager. | |||||||
Contents:
| ||||||||
Line: 78 to 78 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
7. My WinAppxD gets stuck regularly. As you say above, sometimes I can restart it without a reboot, and sometimes I can't. I don't have time for reboots in the middle of the day. What can I do?
II. APPX Client/Server session management1. A user has just called me to say that they are hung. What should I do?
2. The user process is hung, and I haven't been able to resolve the problem, so I need to kill that client/server session. How do I do that?
3. How do I manually kill an APPX server process? In many instances, an APPX server process may be killed by doing the following: | |||||||
> > |
7. My WinAppxD gets stuck regularly. As you say above, sometimes I can restart it without a reboot, and sometimes I can't. I don't have time for reboots in the middle of the day. What can I do?
II. APPX Client/Server session management1. A user has just called me to say that they are hung. What should I do?
2. The user process is hung, and I haven't been able to resolve the problem, so I need to kill that client/server session. How do I do that?
3. How do I manually kill an APPX server process? In many instances, an APPX server process may be killed by doing the following: | |||||||
Go to the server on which WinAppxD and the APPX server processes run, and log in as Administrator. |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX/NT Operations and Administration | ||||||||
Added: | ||||||||
> > | Note: The information here is generally obsolete since WinAppxD has been replaced by the APPX Login Manager. | |||||||
Contents:
| ||||||||
Line: 76 to 78 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
7. My WinAppxD gets stuck regularly. As you say above, sometimes I can restart it without a reboot, and sometimes I can't. I don't have time for reboots in the middle of the day. What can I do?
II. APPX Client/Server session management1. A user has just called me to say that they are hung. What should I do?
2. The user process is hung, and I haven't been able to resolve the problem, so I need to kill that client/server session. How do I do that?
3. How do I manually kill an APPX server process? In many instances, an APPX server process may be killed by doing the following: | |||||||
> > |
7. My WinAppxD gets stuck regularly. As you say above, sometimes I can restart it without a reboot, and sometimes I can't. I don't have time for reboots in the middle of the day. What can I do?
II. APPX Client/Server session management1. A user has just called me to say that they are hung. What should I do?
2. The user process is hung, and I haven't been able to resolve the problem, so I need to kill that client/server session. How do I do that?
3. How do I manually kill an APPX server process? In many instances, an APPX server process may be killed by doing the following: | |||||||
Go to the server on which WinAppxD and the APPX server processes run, and log in as Administrator. | ||||||||
Deleted: | ||||||||
< < | ||||||||
Bring up the NT task list, and look for an APPX.EXE listed with the process ID you want to kill (usually, this will be one given to you by the user, from their client's Windows title bar) | ||||||||
Deleted: | ||||||||
< < | ||||||||
Highlight it and click "End Task". | ||||||||
Deleted: | ||||||||
< < | ||||||||
If another box pops up, saying that the application is not responding, click "End Task" there as well. | ||||||||
Changed: | ||||||||
< < |
4. A user just called me to say that her APPX Client window just disappeared, or there was a power outage or system malfunction, that caused their APPX Client session to end unexpectedly. Do I need to do anything?
5. All of my users except for one have gone home for the night, and I am sure they have turned off their PC's. I still see three (or four, or ten) APPX.EXE processes in the server's task list. Why are they there?
6. How can I determine which APPX.EXE processes on my server are orphans?
7. That command-line "kill" mechanism is too time-consuming and error-prone. Is there a better alternative?
8. I look in my NT task manager and see that an APPX.EXE process is consuming 95% (or more) of the CPU. Why do I get these runaway processes?
III. Other NT Operations and Administration Issues1. Printing to a printer produces blank pages.
2. File fragmentation. Extensive file activity can lead to thousands of fragment per file, over time. This cannot help performance and could lead to problems. In lieu of a script to periodically verify and (if no errors found) export and re-import all of the files for all version and application or datbase and application combinations or the pain of full backup and restore, some use Executive Software's DiskKeeper product to do this task, say, after every full nightly backup. | |||||||
> > |
4. A user just called me to say that her APPX Client window just disappeared, or there was a power outage or system malfunction, that caused their APPX Client session to end unexpectedly. Do I need to do anything?
5. All of my users except for one have gone home for the night, and I am sure they have turned off their PC's. I still see three (or four, or ten) APPX.EXE processes in the server's task list. Why are they there?
6. How can I determine which APPX.EXE processes on my server are orphans?
7. That command-line "kill" mechanism is too time-consuming and error-prone. Is there a better alternative?
8. I look in my NT task manager and see that an APPX.EXE process is consuming 95% (or more) of the CPU. Why do I get these runaway processes?
III. Other NT Operations and Administration Issues1. Printing to a printer produces blank pages.
A complete list of valid form_ids can be gotten by clicking on winprint.exe from Windows Explorer. 2. File fragmentation. Extensive file activity can lead to thousands of fragment per file, over time. This cannot help performance and could lead to problems. In lieu of a script to periodically verify and (if no errors found) export and re-import all of the files for all version and application or datbase and application combinations or the pain of full backup and restore, some use Executive Software's DiskKeeper product to do this task, say, after every full nightly backup. | |||||||
ASI has not tested and in no way warrants this software.
Comments: |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX/NT Operations and Administration | ||||||||
Line: 46 to 45 | ||||||||
3. How do I start WinAppxD? | ||||||||
Changed: | ||||||||
< < | WinAppxD is normally started automatically by the system when it boots. See this document for detailed Installation and Configuration instructions. | |||||||
> > | WinAppxD is normally started automatically by the system when it boots. See this document for detailed Installation and Configuration instructions. | |||||||
If you don't want WinAppxD to start automatically (for example, if you wish for the system to boot without allowing APPX logins), you can set the Startup Type for the WinAppxD service to "Manual" in the NT "Services" Control Panel applet. Then, you can reboot the system. If you check the NT task list at this point, you should not see WinAppxD in it. To manually start WinAppxD, go to the NT "Services" Control Panel applet again, select WinAppxD, and click "Start". Wait a moment or two, then bring up the task list and verify that it is there. (You must be logged in as Administrator to do this.) | ||||||||
Line: 77 to 76 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
7. My WinAppxD gets stuck regularly. As you say above, sometimes I can restart it without a reboot, and sometimes I can't. I don't have time for reboots in the middle of the day. What can I do?
II. APPX Client/Server session management1. A user has just called me to say that they are hung. What should I do?
2. The user process is hung, and I haven't been able to resolve the problem, so I need to kill that client/server session. How do I do that?
3. How do I manually kill an APPX server process? In many instances, an APPX server process may be killed by doing the following: | |||||||
> > |
7. My WinAppxD gets stuck regularly. As you say above, sometimes I can restart it without a reboot, and sometimes I can't. I don't have time for reboots in the middle of the day. What can I do?
II. APPX Client/Server session management1. A user has just called me to say that they are hung. What should I do?
2. The user process is hung, and I haven't been able to resolve the problem, so I need to kill that client/server session. How do I do that?
3. How do I manually kill an APPX server process? In many instances, an APPX server process may be killed by doing the following: | |||||||
Go to the server on which WinAppxD and the APPX server processes run, and log in as Administrator. |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX/NT Operations and Administration | ||||||||
Changed: | ||||||||
< < | Contents:
| |||||||
> > |
Contents:
| |||||||
| ||||||||
Changed: | ||||||||
< < | I. Care and Feeding of WinAppxD
| |||||||
> > | I. Care and Feeding of WinAppxD
| |||||||
II. APPX Client/Server session management
| ||||||||
Line: 26 to 27 | ||||||||
| ||||||||
Changed: | ||||||||
< < | ______________________________________________________________________
I. Care and Feeding of the WinAppxD Service | |||||||
> > | ______________________________________________________________________
I. Care and Feeding of the WinAppxD Service | |||||||
Changed: | ||||||||
< < | 1. What is WinAppxD, and what is it used for? | |||||||
> > | 1. What is WinAppxD, and what is it used for? | |||||||
Changed: | ||||||||
< < | WinAppxD is the NT implementation of <APPX name for this functionality>. Its purpose is to monitor a user-defined port number for connection requests from clients, such as the APPX Client or AppxNET (used for APPXODBC across the network as well), then validate the client's login and password, and start an APPX Server session connected to that client. | |||||||
> > | WinAppxD is the NT implementation of <APPX name for this functionality>. Its purpose is to monitor a user-defined port number for connection requests from clients, such as the APPX Client or AppxNET (used for APPXODBC across the network as well), then validate the client's login and password, and start an APPX Server session connected to that client. | |||||||
Changed: | ||||||||
< < | After the user authenticates and is connected to a server-side APPX session, WinAppxD has nothing further to do with that client/server session. If WinAppxD is killed, ends with an error, or experiences a hung port, this will not affect users who have already established APPX client/server connections. (A problem with WinAppxD is the most common cause of the error situation in which no new users can login, but users who are already logged in, can continue to work.) | |||||||
> > | After the user authenticates and is connected to a server-side APPX session, WinAppxD has nothing further to do with that client/server session. If WinAppxD is killed, ends with an error, or experiences a hung port, this will not affect users who have already established APPX client/server connections. (A problem with WinAppxD is the most common cause of the error situation in which no new users can login, but users who are already logged in, can continue to work.) | |||||||
Changed: | ||||||||
< < | 2. How can I verify that WinAppxD is running? | |||||||
> > | 2. How can I verify that WinAppxD is running? | |||||||
Changed: | ||||||||
< < | Bring up the NT Task Manager. Look for a process named WinAppxD.exe. If you see it, WinAppxD is running. (Note: this does not necessarily mean that WinAppxD is running properly, as a WinAppxD with a hung port will still appear in the task manager. This is mainly useful to do, to verify that WinAppxD is at least starting successfully.) If this process is not present in your task list, client logins cannot be accepted on your APPX server. | |||||||
> > | Bring up the NT Task Manager. Look for a process named WinAppxD.exe. If you see it, WinAppxD is running. (Note: this does not necessarily mean that WinAppxD is running properly, as a WinAppxD with a hung port will still appear in the task manager. This is mainly useful to do, to verify that WinAppxD is at least starting successfully.) If this process is not present in your task list, client logins cannot be accepted on your APPX server. | |||||||
Changed: | ||||||||
< < | 3. How do I start WinAppxD? | |||||||
> > | 3. How do I start WinAppxD? | |||||||
Changed: | ||||||||
< < | WinAppxD is normally started automatically by the system when it boots. See this document for detailed Installation and Configuration instructions. | |||||||
> > | WinAppxD is normally started automatically by the system when it boots. See this document for detailed Installation and Configuration instructions. | |||||||
Changed: | ||||||||
< < | If you don't want WinAppxD to start automatically (for example, if you wish for the system to boot without allowing APPX logins), you can set the Startup Type for the WinAppxD service to "Manual" in the NT "Services" Control Panel applet. Then, you can reboot the system. If you check the NT task list at this point, you should not see WinAppxD in it. To manually start WinAppxD, go to the NT "Services" Control Panel applet again, select WinAppxD, and click "Start". Wait a moment or two, then bring up the task list and verify that it is there. (You must be logged in as Administrator to do this.) | |||||||
> > | If you don't want WinAppxD to start automatically (for example, if you wish for the system to boot without allowing APPX logins), you can set the Startup Type for the WinAppxD service to "Manual" in the NT "Services" Control Panel applet. Then, you can reboot the system. If you check the NT task list at this point, you should not see WinAppxD in it. To manually start WinAppxD, go to the NT "Services" Control Panel applet again, select WinAppxD, and click "Start". Wait a moment or two, then bring up the task list and verify that it is there. (You must be logged in as Administrator to do this.) | |||||||
Changed: | ||||||||
< < | 4. How do I stop WinAppxD? | |||||||
> > | 4. How do I stop WinAppxD? | |||||||
Changed: | ||||||||
< < | WinAppxD automatically stops when the system is shut down or on its way to a reboot. | |||||||
> > | WinAppxD automatically stops when the system is shut down or on its way to a reboot. | |||||||
Changed: | ||||||||
< < | If you want to manually stop WinAppxD before that point, you MAY be able to stop it through the NT "Services" Control Panel applet, by selecting WinAppxD, and clicking "Stop". Wait a moment or two, then bring up the task list and verify that it is no longer listed. | |||||||
> > | If you want to manually stop WinAppxD before that point, you MAY be able to stop it through the NT "Services" Control Panel applet, by selecting WinAppxD, and clicking "Stop". Wait a moment or two, then bring up the task list and verify that it is no longer listed. | |||||||
Changed: | ||||||||
< < | If after several minutes, you still see WinAppxD in the task list, you can try a more "drastic" measure and try to "End Process" the WinAppxD.exe entry in the task list. | |||||||
> > | If after several minutes, you still see WinAppxD in the task list, you can try a more "drastic" measure and try to "End Process" the WinAppxD.exe entry in the task list. | |||||||
Changed: | ||||||||
< < | It's several minutes after that, and it's still there? The most drastic way of stopping WinAppxD, if you have the NT Resource Kit installed, is to use the kill.exe command provided by the Resource Kit. (Hint: You probably have this installed, since some utilities from it are required to install and run WinAppxD. Do a Find for "kill.exe" if you can't locate it.) (You must be logged in as Administrator to do this.) | |||||||
> > | It's several minutes after that, and it's still there? The most drastic way of stopping WinAppxD, if you have the NT Resource Kit installed, is to use the kill.exe command provided by the Resource Kit. (Hint: You probably have this installed, since some utilities from it are required to install and run WinAppxD. Do a Find for "kill.exe" if you can't locate it.) (You must be logged in as Administrator to do this.) | |||||||
Changed: | ||||||||
< < | 5. Is it safe to stop WinAppxD, if I'm going to need to restart it again without rebooting my server? | |||||||
> > | 5. Is it safe to stop WinAppxD, if I'm going to need to restart it again without rebooting my server? | |||||||
Changed: | ||||||||
< < | MAYBE. Sometimes you can stop WinAppxD, then manually start it again, and everything will work fine. However, sometimes the manual restart process is not successful. This appears to be due to NT not properly releasing the port (usually 8060) when WinAppxD is stopped. If the port is not released, when WinAppxD restarts and attempts to recapture it, it can't, so client logins won't be accepted. | |||||||
> > | MAYBE. Sometimes you can stop WinAppxD, then manually start it again, and everything will work fine. However, sometimes the manual restart process is not successful. This appears to be due to NT not properly releasing the port (usually 8060) when WinAppxD is stopped. If the port is not released, when WinAppxD restarts and attempts to recapture it, it can't, so client logins won't be accepted. (See question #7 below ("My WinAppxD gets stuck regularly ...) for a workaround to this.) It may be a very good idea to set up Multiple WinAppxD servers as per #7 from the get-go, as a fallback position, in case you unexpectedly get a hung port condition.) If the restart fails, you can try stopping WinAppxD again (if one started during the restart process) and restarting it again. If a WinAppxD.exe does not reappear in the task list, or if it appears but client logins are not accepted, at this point, your only option is to reboot. | |||||||
Changed: | ||||||||
< < | (See question #7 below ("My WinAppxD gets stuck regularly ...) for a workaround to this.) It may be a very good idea to set up Multiple WinAppxD servers as per #7 from the get-go, as a fallback position, in case you unexpectedly get a hung port condition.) If the restart fails, you can try stopping WinAppxD again (if one started during the restart process) and restarting it again. If a WinAppxD.exe does not reappear in the task list, or if it appears but client logins are not accepted, at this point, your only option is to reboot. | |||||||
> > | We don't have any figures as to what percentage of the time this is and is not successful. In general, if you stop a WORKING WinAppxD, and expect to be able to restart it without a reboot, YOU ARE TAKING A CHANCE. It may or may not work, due to NT. If you stop a malfunctioning WinAppxD in the hope that restarting it will resolve the error condition without a reboot, you have nothing to lose. In that case, it is definitely worth a try. (You must be logged in as Administrator to do this.)
6. When might I want to stop and restart WinAppxD (either with, or without, a reboot)?
| |||||||
Deleted: | ||||||||
< < | We don't have any figures as to what percentage of the time this is and is not successful. In general, if you stop a WORKING WinAppxD, and expect to be able to restart it without a reboot, YOU ARE TAKING A CHANCE. It may or may not work, due to NT. If you stop a malfunctioning WinAppxD in the hope that restarting it will resolve the error condition without a reboot, you have nothing to lose. In that case, it is definitely worth a try. (You must be logged in as Administrator to do this.)
6. When might I want to stop and restart WinAppxD (either with, or without, a reboot)?
| |||||||
| ||||||||
Changed: | ||||||||
< < |
7. My WinAppxD gets stuck regularly. As you say above, sometimes I can restart it without a reboot, and sometimes I can't. I don't have time for reboots in the middle of the day. What can I do?
II. APPX Client/Server session management1. A user has just called me to say that they are hung. What should I do?
2. The user process is hung, and I haven't been able to resolve the problem, so I need to kill that client/server session. How do I do that?
3. How do I manually kill an APPX server process? In many instances, an APPX server process may be killed by doing the following: | |||||||
> > |
7. My WinAppxD gets stuck regularly. As you say above, sometimes I can restart it without a reboot, and sometimes I can't. I don't have time for reboots in the middle of the day. What can I do?
II. APPX Client/Server session management1. A user has just called me to say that they are hung. What should I do?
2. The user process is hung, and I haven't been able to resolve the problem, so I need to kill that client/server session. How do I do that?
3. How do I manually kill an APPX server process? In many instances, an APPX server process may be killed by doing the following: | |||||||
Changed: | ||||||||
< < | Go to the server on which WinAppxD and the APPX server processes run, and log in as Administrator. | |||||||
> > | Go to the server on which WinAppxD and the APPX server processes run, and log in as Administrator. | |||||||
| ||||||||
Line: 87 to 89 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
4. A user just called me to say that her APPX Client window just disappeared, or there was a power outage or system malfunction, that caused their APPX Client session to end unexpectedly. Do I need to do anything?
5. All of my users except for one have gone home for the night, and I am sure they have turned off their PC's. I still see three (or four, or ten) APPX.EXE processes in the server's task list. Why are they there?
6. How can I determine which APPX.EXE processes on my server are orphans?
7. That command-line "kill" mechanism is too time-consuming and error-prone. Is there a better alternative?
8. I look in my NT task manager and see that an APPX.EXE process is consuming 95% (or more) of the CPU. Why do I get these runaway processes?
III. Other NT Operations and Administration Issues1. Printing to a printer produces blank pages.
2. File fragmentation. Extensive file activity can lead to thousands of fragment per file, over time. This cannot help performance and could lead to problems. In lieu of a script to periodically verify and (if no errors found) export and re-import all of the files for all version and application or datbase and application combinations or the pain of full backup and restore, some use Executive Software's DiskKeeper product to do this task, say, after every full nightly backup. | |||||||
> > |
4. A user just called me to say that her APPX Client window just disappeared, or there was a power outage or system malfunction, that caused their APPX Client session to end unexpectedly. Do I need to do anything?
5. All of my users except for one have gone home for the night, and I am sure they have turned off their PC's. I still see three (or four, or ten) APPX.EXE processes in the server's task list. Why are they there?
6. How can I determine which APPX.EXE processes on my server are orphans?
7. That command-line "kill" mechanism is too time-consuming and error-prone. Is there a better alternative?
8. I look in my NT task manager and see that an APPX.EXE process is consuming 95% (or more) of the CPU. Why do I get these runaway processes?
III. Other NT Operations and Administration Issues1. Printing to a printer produces blank pages.
2. File fragmentation. Extensive file activity can lead to thousands of fragment per file, over time. This cannot help performance and could lead to problems. In lieu of a script to periodically verify and (if no errors found) export and re-import all of the files for all version and application or datbase and application combinations or the pain of full backup and restore, some use Executive Software's DiskKeeper product to do this task, say, after every full nightly backup. | |||||||
ASI has not tested and in no way warrants this software.
Comments: |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Added: | ||||||||
> > |
APPX/NT Operations and AdministrationContents:
I. Care and Feeding of WinAppxD
II. APPX Client/Server session management
III. Other NT Operations and Administration Issues
I. Care and Feeding of the WinAppxD Service1. What is WinAppxD, and what is it used for?WinAppxD is the NT implementation of <APPX name for this functionality>. Its purpose is to monitor a user-defined port number for connection requests from clients, such as the APPX Client or AppxNET (used for APPXODBC across the network as well), then validate the client's login and password, and start an APPX Server session connected to that client. After the user authenticates and is connected to a server-side APPX session, WinAppxD has nothing further to do with that client/server session. If WinAppxD is killed, ends with an error, or experiences a hung port, this will not affect users who have already established APPX client/server connections. (A problem with WinAppxD is the most common cause of the error situation in which no new users can login, but users who are already logged in, can continue to work.)2. How can I verify that WinAppxD is running? Bring up the NT Task Manager. Look for a process named WinAppxD.exe. If you see it, WinAppxD is running. (Note: this does not necessarily mean that WinAppxD is running properly, as a WinAppxD with a hung port will still appear in the task manager. This is mainly useful to do, to verify that WinAppxD is at least starting successfully.) If this process is not present in your task list, client logins cannot be accepted on your APPX server.3. How do I start WinAppxD? WinAppxD is normally started automatically by the system when it boots. See this document for detailed Installation and Configuration instructions. If you don't want WinAppxD to start automatically (for example, if you wish for the system to boot without allowing APPX logins), you can set the Startup Type for the WinAppxD service to "Manual" in the NT "Services" Control Panel applet. Then, you can reboot the system. If you check the NT task list at this point, you should not see WinAppxD in it. To manually start WinAppxD, go to the NT "Services" Control Panel applet again, select WinAppxD, and click "Start". Wait a moment or two, then bring up the task list and verify that it is there. (You must be logged in as Administrator to do this.)4. How do I stop WinAppxD? WinAppxD automatically stops when the system is shut down or on its way to a reboot. If you want to manually stop WinAppxD before that point, you MAY be able to stop it through the NT "Services" Control Panel applet, by selecting WinAppxD, and clicking "Stop". Wait a moment or two, then bring up the task list and verify that it is no longer listed. If after several minutes, you still see WinAppxD in the task list, you can try a more "drastic" measure and try to "End Process" the WinAppxD.exe entry in the task list. It's several minutes after that, and it's still there? The most drastic way of stopping WinAppxD, if you have the NT Resource Kit installed, is to use the kill.exe command provided by the Resource Kit. (Hint: You probably have this installed, since some utilities from it are required to install and run WinAppxD. Do a Find for "kill.exe" if you can't locate it.) (You must be logged in as Administrator to do this.)5. Is it safe to stop WinAppxD, if I'm going to need to restart it again without rebooting my server? MAYBE. Sometimes you can stop WinAppxD, then manually start it again, and everything will work fine. However, sometimes the manual restart process is not successful. This appears to be due to NT not properly releasing the port (usually 8060) when WinAppxD is stopped. If the port is not released, when WinAppxD restarts and attempts to recapture it, it can't, so client logins won't be accepted. (See question #7 below ("My WinAppxD gets stuck regularly ...) for a workaround to this.) It may be a very good idea to set up Multiple WinAppxD servers as per #7 from the get-go, as a fallback position, in case you unexpectedly get a hung port condition.) If the restart fails, you can try stopping WinAppxD again (if one started during the restart process) and restarting it again. If a WinAppxD.exe does not reappear in the task list, or if it appears but client logins are not accepted, at this point, your only option is to reboot. We don't have any figures as to what percentage of the time this is and is not successful. In general, if you stop a WORKING WinAppxD, and expect to be able to restart it without a reboot, YOU ARE TAKING A CHANCE. It may or may not work, due to NT. If you stop a malfunctioning WinAppxD in the hope that restarting it will resolve the error condition without a reboot, you have nothing to lose. In that case, it is definitely worth a try. (You must be logged in as Administrator to do this.) 6. When might I want to stop and restart WinAppxD (either with, or without, a reboot)?
7. My WinAppxD gets stuck regularly. As you say above, sometimes I can restart it without a reboot, and sometimes I can't. I don't have time for reboots in the middle of the day. What can I do?
II. APPX Client/Server session management1. A user has just called me to say that they are hung. What should I do?
2. The user process is hung, and I haven't been able to resolve the problem, so I need to kill that client/server session. How do I do that?
3. How do I manually kill an APPX server process? In many instances, an APPX server process may be killed by doing the following:
4. A user just called me to say that her APPX Client window just disappeared, or there was a power outage or system malfunction, that caused their APPX Client session to end unexpectedly. Do I need to do anything?
5. All of my users except for one have gone home for the night, and I am sure they have turned off their PC's. I still see three (or four, or ten) APPX.EXE processes in the server's task list. Why are they there?
6. How can I determine which APPX.EXE processes on my server are orphans?
7. That command-line "kill" mechanism is too time-consuming and error-prone. Is there a better alternative?
8. I look in my NT task manager and see that an APPX.EXE process is consuming 95% (or more) of the CPU. Why do I get these runaway processes?
III. Other NT Operations and Administration Issues1. Printing to a printer produces blank pages.
2. File fragmentation. Extensive file activity can lead to thousands of fragment per file, over time. This cannot help performance and could lead to problems. In lieu of a script to periodically verify and (if no errors found) export and re-import all of the files for all version and application or datbase and application combinations or the pain of full backup and restore, some use Executive Software's DiskKeeper product to do this task, say, after every full nightly backup. ASI has not tested and in no way warrants this software.Comments:Read what other users have said about this page or add your own comments.-- ChrisBrower - 2011-06-08 |