Performance problems over network.

  • Thread starter Thread starter Charles
  • Start date Start date
C

Charles

Hello,

Something is going drastically wrong on my server and I don't know where to
look. I have a Windows 2000 Server (Proliant ML530 G1) used as a file
server. It has on it:

1. Users' home folders (containing Outlook.pst) and departmental shares.
2. Payroll software (Earnie payroll)
3. Time Management System software
3. Personnel software
4. Shipping software
5. Online banking software
6. Arcserve 2000 backup software
7. Exchange 2000 (not being used at present)
8. RAS
9. Syamantec Anti-virus 8.6

2-5 all use different databases like Interbase, Centura, etc.

For some reason the performance on this server is increasingly poor. At
forst glance it would appear that it dergrades gradually after system
startup. The main victims are the Time Management System and Earnie Payroll
users. These just freeze up and users either can't gain access at all or
they get locked out whilst connected to the system. I have moved the
Payroll software
to another server and now it is working fine. The other major
head-ache is Outlook. I get delayed write failure errors and outlook has to
be restarted. Sometimes desktops have to be restarted, and other times it
is so bad that the server has to be restarted as well.

Does anyone know where I can start looking. I have already run the HP Server
diagnostics off a bootable floppy and the system passed every test. I have
run some rudimentary performance monitoring for a few hours but nothing was
screaming at me. It all looked OK. What counters should be using for this
type of performance problem anyway? I have a feeling it might be software
related; are there file system counters or some other king of system
software monitoring that can be done?

Thanks in advance,

C
 
The first place you should start to look is in the Event log. Find all
events that are errors and warnings. Next, you may want to run performance
monitor. If you want to call into us for support, we are going to get you
to do a perfmon log.

How to setup a Performance Monitor log on Window 2000.
******************************************************
IMPORTANT:
Before creating a log, please go to 'Start', 'Run' and type cmd and press
enter. At the command prompt type
"diskperf -y" (without the quotation marks). It will return a message
pertaining to physical and logical counters. (This is not necessary on
Server or Adv. Server)
Type exit and reboot the system.
******************************************************

1. Go to 'Start', then 'Settings' and click on 'Control Panel'

2. Double-click the 'Administrative Tools' folder.

3. Double-click the 'Performance' icon.

4. You will be presented with the 'Performance Monitor' window.

5. In the left-hand pane, expand the 'Performance Logs and Alerts' section.

6. Right-click on 'Counter Logs' and select 'New Log Settings...'

7. Give the log a name (ie. Danzer) and click Okay.

8. You will be presented with the log properties window.

9. In the 'General' tab, click 'Add'.

10. In the 'Select Counters' dialog box, select the 'Use local computer
counters' radial button.

11. Click the radial buttons for 'All counters' and 'All instances'.

12. In the 'Performance objects' pull down box, go up to the very first
listing and click 'Add'.

13. Go back to the 'Performance objects' pull down box and select the next
object and click 'Add'.

14. Go back to the 'Performance objects' pull down box and select the next
object and click 'Add'.

15. Do the above for all 'Performance objects' in the list.

16. Once you have selected and added all of the objects in the 'Performance
objects' list click 'Close'.

17. This will take you back to the 'General' tab of the log properties
dialog box.

18. In the 'Sample data every:' section, change the 'Interval' to 10 and the
'Units' to seconds.

19. Once you have set the Interval to 10 seconds, click the 'Apply' button.

20. Select the 'Log Files' tab.

21. Note the location and name of the log file being created. In the window
you will see an 'Example:'. This example is
the location and name of the log file you created. Write it down you
will need it later.

22. click on the 'Schedule' tab.

23. Make sure both of the radial buttons are set to 'Manually (using the
shortcut menu)'.

24. Click 'Apply' then 'OK'.

25. After you click 'OK' you will see your newly created log on the
right-hand side of the Performance Monitor window.

26. Note the 'Log File Name'. This should be same as the information from
the 'Log Files' tab.

27. Right-click on your log name and select 'Start'. This will start the
performance monitor running in the background.

28. Minimize the Performance Monitor window and attempt to reproduce the
problem until failure.

29. Once you have reproduced the condition, maximize the Performance Monitor
and right-click your log name again and click
'Stop'.

30. At this point the Performance Monitor is stopped and the log is saved.
Close the performance monitor.

31. Locate the .blg file, ZIP it up and send it to me.

============================================================================
===============================How to setup a Performance Monitor log on
Windows NT 4.0:
*********************************************************
1. Turn off screen saver permanently.

2. From a command prompt enter "diskperf -y" (DO NOT use diskperf -YE
unless instructed) to enable counters for all possible disk issues, this can
be turned off later with "diskperf -n"

3. Set the virtual memory paging file to a minimum of physical memory plus
100 MB initial and final sizes. We do not care where the actual file is
located, do not restart yet.

4. From within the registry editor (regedt32), go to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SessionManager\Memory
Management and
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

write down ALL values on the right-hand side that is NOT zero.
The best way save the values is to export the entire key using REGEDIT to a
*.TXT file (DO NOT NAME IT a *.REG file).

5. Install the SNMP service and Network Monitor Agent. This will require
the NT CD or appropriate share and the last applied service pack.

To install this:
In Windows NT 3.51
Main, Control Panel, Network
Add Software...
Select SNMP and Network Monitor Agent from the list of Network Software

In Windows NT 4.0
Start, Settings, Control Panel, Network, Services, Add
Select SNMP from the list of Network Software
When it asks for the path of the software, point it at the I386 directory
on the CD
Do not reboot yet. Instead install Network Monitor Agent and Tools, then
reboot.
These services install Network Interface, Network Segment, and all tcpip
counters in Performance Monitor.

Reapply last applied Service pack and restart.

6. Set all NON RELEVANT services to DISABLED and reboot.

Creating the Performance Monitor log:

Go to 'Start', 'Programs', 'Administrative Tools (Common), and click on
'Performance Monitor'.

7. On the View menu, select Log.

8. On the Edit menu, select Add To Log

9. In the "Computer" box use the local computer name.

10. In the Add To Log dialog box you will see Computer and Objects. In
Computer, specify the name of the local computer or a remote computer
you want to get a log of. In Objects, add the counters that you want
Performance Monitor to log.
Add the following counters,
Cache
IP
Logical Disk
Memory
Network Interface
Network Segment
Objects
Paging File
Process
Processor
Redirector
Server
Server Work Queues
System
TCP
Thread

11. Highlight the above objects and click 'Add' then click 'Done'.

12. Under Options select Log.

13. Under File Name, name the log.

14. At the bottom of this window you will see Update Time. It is important
to set this update time. If you are going to be running the Performance
Monitor log more that 12 hours set Periodic Update Interval to 300
seconds
and to 10 seconds if running the log less than 4 hours

15. Now you are ready to start the log. Press the Start Log button
located in the same window as the above. This will start the log and
this icon will change to a Stop Log icon once the log is started.
(Note: Do Not log off of the machine where you are running performance
monitor
as this will close out performance monitor. Minimize Performance
monitor and if needed lock
the screen on this machine.)

16. Allow the Performance Monitor to run until the failure or process
completion. Once you are ready to stop the
log, click on 'Options' then 'Log' and click 'Stop Log'. Then close the
Performance Monitor.

17. At the end of the Performance Monitor, on the machine being monitored
run Windows NT Diagnostics in Administrative Tools, click File then Save
Report with detail level set to "Complete" and Scope set to "all tabs" and
Destination to "File", then select OK.
This will save the system information to msdrpt.txt.

18. Save the System and Application Event Logs to files using the Event
Viewer in Administrative Tools.





--
Thank you,

Brennan Crowe
Microsoft corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Charles,

If performance improves on boot and then degrades this will be the best way to proceed.
To start with check system resources
1. How much available free space do you have on the C: drive?
2. Where is the page file located and is there enough free space so that the max page file setting does not exceed available space?
3. Defragment the hard drives.

Unfortunately delayed write failed errors are not often easy to track down, this is because the can be caused by a combination of things.
For this I would do the following
1. Update NIC drivers.
2. Do not use aute detect or hardware default for the nic, change it to full or half duplex to match your switch or router.
3. Check for updates to any software that loads a filter driver, such as anti virus and backup software.
4. Update the service pack to SP4 if you have not already.
5. Update system bios and disk controller drivers.

330174 "Delayed Write Failed" Error Message When You Manage Files in Windows XP
http://support.microsoft.com/?id=330174

Hope that helps


Regards,
Clark Satter
MCSA MCSE A+
Microsoft Networking Support

--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.




--------------------
 
Back
Top