I?ve had no luck finding anything about this problem except one in Microsoft?s Knowledgebase which ended up not helping.
OK, the server is a Dell PowerEdge 6400, the server is on a domain (ex. Corporate.com) while the users are within a child domain, child.corporate.com. Here?s the problem, the users are using a program which has two mapped locations where it has data ? a database of options and settings for the program and another for their personal data (still part of the program). After an hour or so a single user will have their station lockup (stall) then one by one as the other users start to go to the same area of the database they will begin to lockup themselves until everyone is like that. It seems that they are waiting for a file to be released by the first computer (like it?s locked by that station), yet, on the server I cannot see either by management or other tools on the server any files that are open. I try to access the database directly on the server and the server stalls just like the workstations do.
Program or database problem, right? Nope, don?t think so because I moved the whole thing to an NT4 server environment and NO problems. This application server is also a print server and we do heavy printing (10,000+ a week) and this server just cut through them like butter (33 printers). The performance logs show the highest server workload in the past 6 weeks was 19% and that was only on one of 4 processors. Total system peak was at only 6% and that was during a very heavy day.
So, I?m only left with three ideas. Perhaps it has something to do with the users being in the child domain and the server residing in the parent. Two, its hardware related. Or three, I have missed something within Windows 2003 security, profiles or permissions.
Things I?ve tried:
Gave users modify (poweruser) permissions, no luck.
Change caching settings giving more memory dedicated to database/users
Lightened restriction on Group Policies.
OK, the server is a Dell PowerEdge 6400, the server is on a domain (ex. Corporate.com) while the users are within a child domain, child.corporate.com. Here?s the problem, the users are using a program which has two mapped locations where it has data ? a database of options and settings for the program and another for their personal data (still part of the program). After an hour or so a single user will have their station lockup (stall) then one by one as the other users start to go to the same area of the database they will begin to lockup themselves until everyone is like that. It seems that they are waiting for a file to be released by the first computer (like it?s locked by that station), yet, on the server I cannot see either by management or other tools on the server any files that are open. I try to access the database directly on the server and the server stalls just like the workstations do.
Program or database problem, right? Nope, don?t think so because I moved the whole thing to an NT4 server environment and NO problems. This application server is also a print server and we do heavy printing (10,000+ a week) and this server just cut through them like butter (33 printers). The performance logs show the highest server workload in the past 6 weeks was 19% and that was only on one of 4 processors. Total system peak was at only 6% and that was during a very heavy day.
So, I?m only left with three ideas. Perhaps it has something to do with the users being in the child domain and the server residing in the parent. Two, its hardware related. Or three, I have missed something within Windows 2003 security, profiles or permissions.
Things I?ve tried:
Gave users modify (poweruser) permissions, no luck.
Change caching settings giving more memory dedicated to database/users
Lightened restriction on Group Policies.
Facebook
Twitter