![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Greetings all. One of my clients that uses Terminal Services, with 15 or more users logged in at a time, is having a serious problem. After working normally for days or weeks, no new users can open the application. They say that the users aren't being dropped from TS, and that they don't cancel the TS sessions. The workaround is to get everyone out, and run the Clear Lock Files utility. But, I need to fix the problem instead. I'm at a loss to explain how the lock/net files are getting corrupted (or filled?), so that they have to be purged before they can be used again. Can the application be causing this issue, or is it solely a Runtime (or connection) issue? Does anyone have any insight, or even a good guess? ![]() Pdox 9 Runtime sp3. Thanks, Jim Moseley |
#3
| |||
| |||
|
|
Greetings all. One of my clients that uses Terminal Services, with 15 or more users logged in at a time, is having a serious problem. After working normally for days or weeks, no new users can open the application. They say that the users aren't being dropped from TS, and that they don't cancel the TS sessions. The workaround is to get everyone out, and run the Clear Lock Files utility. But, I need to fix the problem instead. I'm at a loss to explain how the lock/net files are getting corrupted (or filled?), so that they have to be purged before they can be used again. Can the application be causing this issue, or is it solely a Runtime (or connection) issue? Does anyone have any insight, or even a good guess? ![]() Pdox 9 Runtime sp3. Thanks, Jim Moseley |
#4
| |||
| |||
|
|
Greetings all. One of my clients that uses Terminal Services, with 15 or more users logged in at a time, is having a serious problem. After working normally for days or weeks, no new users can open the application. They say that the users aren't being dropped from TS, and that they don't cancel the TS sessions. The workaround is to get everyone out, and run the Clear Lock Files utility. But, I need to fix the problem instead. I'm at a loss to explain how the lock/net files are getting corrupted (or filled?), so that they have to be purged before they can be used again. Can the application be causing this issue, or is it solely a Runtime (or connection) issue? Does anyone have any insight, or even a good guess? ![]() Pdox 9 Runtime sp3. Thanks, Jim Moseley |
#5
| |||
| |||
|
|
Greetings all. One of my clients that uses Terminal Services, with 15 or more users logged in at a time, is having a serious problem. After working normally for days or weeks, no new users can open the application. They say that the users aren't being dropped from TS, and that they don't cancel the TS sessions. The workaround is to get everyone out, and run the Clear Lock Files utility. But, I need to fix the problem instead. I'm at a loss to explain how the lock/net files are getting corrupted (or filled?), so that they have to be purged before they can be used again. Can the application be causing this issue, or is it solely a Runtime (or connection) issue? Does anyone have any insight, or even a good guess? ![]() Pdox 9 Runtime sp3. Thanks, Jim Moseley |
#6
| |||
| |||
|
|
Greetings all. One of my clients that uses Terminal Services, with 15 or more users logged in at a time, is having a serious problem. After working normally for days or weeks, no new users can open the application. They say that the users aren't being dropped from TS, and that they don't cancel the TS sessions. The workaround is to get everyone out, and run the Clear Lock Files utility. But, I need to fix the problem instead. I'm at a loss to explain how the lock/net files are getting corrupted (or filled?), so that they have to be purged before they can be used again. Can the application be causing this issue, or is it solely a Runtime (or connection) issue? Does anyone have any insight, or even a good guess? ![]() Pdox 9 Runtime sp3. Thanks, Jim Moseley |
#7
| |||
| |||
|
|
Greetings all. One of my clients that uses Terminal Services, with 15 or more users logged in at a time, is having a serious problem. After working normally for days or weeks, no new users can open the application. They say that the users aren't being dropped from TS, and that they don't cancel the TS sessions. The workaround is to get everyone out, and run the Clear Lock Files utility. But, I need to fix the problem instead. I'm at a loss to explain how the lock/net files are getting corrupted (or filled?), so that they have to be purged before they can be used again. Can the application be causing this issue, or is it solely a Runtime (or connection) issue? Does anyone have any insight, or even a good guess? ![]() Pdox 9 Runtime sp3. Thanks, Jim Moseley |
#8
| |||
| |||
|
|
Greetings all. One of my clients that uses Terminal Services, with 15 or more users logged in at a time, is having a serious problem. After working normally for days or weeks, no new users can open the application. They say that the users aren't being dropped from TS, and that they don't cancel the TS sessions. The workaround is to get everyone out, and run the Clear Lock Files utility. But, I need to fix the problem instead. I'm at a loss to explain how the lock/net files are getting corrupted (or filled?), so that they have to be purged before they can be used again. Can the application be causing this issue, or is it solely a Runtime (or connection) issue? Does anyone have any insight, or even a good guess? ![]() Pdox 9 Runtime sp3. Thanks, Jim Moseley |
#9
| |||
| |||
|
|
Greetings all. One of my clients that uses Terminal Services, with 15 or more users logged in at a time, is having a serious problem. After working normally for days or weeks, no new users can open the application. They say that the users aren't being dropped from TS, and that they don't cancel the TS sessions. The workaround is to get everyone out, and run the Clear Lock Files utility. But, I need to fix the problem instead. I'm at a loss to explain how the lock/net files are getting corrupted (or filled?), so that they have to be purged before they can be used again. Can the application be causing this issue, or is it solely a Runtime (or connection) issue? Does anyone have any insight, or even a good guess? ![]() Pdox 9 Runtime sp3. Thanks, Jim Moseley |
#10
| |||
| |||
|
|
Greetings all. One of my clients that uses Terminal Services, with 15 or more users logged in at a time, is having a serious problem. After working normally for days or weeks, no new users can open the application. They say that the users aren't being dropped from TS, and that they don't cancel the TS sessions. The workaround is to get everyone out, and run the Clear Lock Files utility. But, I need to fix the problem instead. I'm at a loss to explain how the lock/net files are getting corrupted (or filled?), so that they have to be purged before they can be used again. Can the application be causing this issue, or is it solely a Runtime (or connection) issue? Does anyone have any insight, or even a good guess? ![]() Pdox 9 Runtime sp3. Thanks, Jim Moseley |
![]() |
| Thread Tools | |
| Display Modes | |
| |