Help me - slow file server performance and delays occur when you work with files

Squonk

Deity
Joined
Apr 6, 2002
Messages
2,507
Location
Poland
To get internet connection, I had to install some silly program. After I got it, Windows demanded installing 18+ updates, so I did it (I didn't have internet connection in this comp for a year or more).

Now

1) Almost every time I load windows, just at the start explorer crashes, but then it works fine
2) From time to time some other thing pops-up, claiming some strange dos-like thing is located somewhere, blah blah blah, I will write it down.
3) the most annoying - I can not use Word, because after a while it writes that Word can not open blah blah file, I must re-establish internet connection of put a diskette in. And it is the end of this word session.

Thanks to that info, I managed to discover that it's about reduction of efficiency of the files' server or something like that:
http://support.microsoft.com/kb/822219/pl

here is the relevant support page in polish.
and in english
http://support.microsoft.com/kb/822219/br

so I need to do something about ofant.sys and otman.sys

BUT I DUNNO HOW and stuff.

Help me :(
 
I don't fully understand your problem, but that error message seems to indicate that you are saving your files on an external server instead of on your own computer. Make sure you are not doing that.
 
I am not doing that. It's just what it says. Full description of this problem is available on microsoft support page that I posted.
 
http://support.microsoft.com/kb/822219/eng

• When you try to open a Microsoft Word file, you may receive the following error message:
Word failed reading from this file file_name. Please restore the network connection or replace the floppy disk and retry.
Additionally, the following event may be logged in the System log on the client computer:
Type: Warning
Source: MrxSmb
Event ID: 50
Description: {Lost Delayed-Write-Data} The system was attempting to transfer file data from buffers to \Device\LanmanRedirector. The write operation failed, and only some of the data may have been written to the file.

Back to the top

CAUSE
This issue may occur if a non-Microsoft program that is installed on your computer uses an outdated kernel-mode filter driver. The kernel-mode filter driver may be outdated if the following conditions are true: • One of the following programs is installed on the computer: • ARCserve Backup Agent for Open Files or ARCserve Open File Agent from Computer Associates International, Inc. is installed on your computer, and the Ofant.sys driver for the program is outdated.
• Open Transaction Manager is installed on your computer, and the Otman.sys driver for the program is outdated.

Note Open Transaction Manager is included with certain programs from VERITAS Software Corporation, but it can also be installed separately from the VERITAS program. For example, Open Transaction Manager may be included with Open File Option. This program may be included with VERITAS Backup Exec.
• A VERITAS program that uses the Otman4.sys or Otman5.sys driver (such as Open File Option) is installed on your computer, and the Otman4.sys or Otman5.sys driver for the program is outdated.

• The driver for the program is incompatible with the filter driver that is installed on the computer by a non-Microsoft antivirus program. As a result, the filter driver on the server may return an incorrect status code to the Server service. For example, the filter driver may return a STATUS_SUCCESS code instead of a STATUS_OPLOCK_BREAK_IN_PROGRESS code.

Back to the top

RESOLUTION
To resolve this issue, contact the manufacturer of the program to inquire about the availability of a filter driver update. For more information about how to contact Computer Associates to obtain the latest update for the Ofant.sys driver, visit the following Computer Associates Web site:
http://www.ca.com/support/ (http://www.ca.com/support/)
If you installed Open Transaction Manager separately, contact Columbia Data Products, Inc. to inquire about the availability of an update that may resolve this issue. To contact Columbia Data Products, visit the following Columbia Data Products Web site:
http://www.cdp.com/ (http://www.cdp.com/)
For more information about how to contact VERITAS, visit the following VERITAS Web site:
http://support.veritas.com/ (http://support.veritas.com/)
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
Back to the top

MORE INFORMATION
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 (http://support.microsoft.com/kb/322756/) How to back up and restore the registry in Windows


To temporarily work around this issue, restart the Server services on the server. To restart the Server services, follow these steps: 1. Click Start, and then click Run.
2. In the Open box, type cmd, and then click OK.
3. At the command prompt, type the following lines, and press ENTER after each line:
net stop server
net start server
To troubleshoot this issue, use any of the following methods: • Use Performance Logs and Alerts to monitor theAvg. Disk Queue Length counter of the PhysicalDisk performance object. Under ordinary conditions, the number of waiting input/output (I/O) requests is typically no more than 1.5 to 2 times the number of spindles that the physical disk has. Most disks have one spindle, although redundant array of independent disks (RAID) devices typically have more than one spindle. When a program runs small successive I/O operations, you see a spike in the Current Disk Queue Length counter when I/O-bound operations are queued. You may also see an increase in the Context Switches/sec counter of the System performance object.
• Disable opportunistic locking on either the client or on the server. To disable opportunistic locking on the client, set the following registry value to 1:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters\OplocksDisabled
To disable opportunistic locking on the server, set the following registry value to 0:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\EnableOplocks
For more information about how to disable opportunistic locking, click the following article number to view the article in the Microsoft Knowledge Base:
296264 (http://support.microsoft.com/kb/296264/) Configuring opportunistic locking in Windows
• Use the Microsoft Configuration Capture Utility (MPS_REPORTS) to determine the version of the filter driver that is installed on your computer.

For more information about the Microsoft Configuration Capture Utility, click the following article number to view the article in the Microsoft Knowledge Base:
818742 (http://support.microsoft.com/kb/818742/) Overview of the Microsoft Configuration Capture Utility (MPS_REPORTS)
• Edit the registry to temporarily deactivate the filter driver.

For more information about how to temporarily deactivate the kernel-mode filter driver, click the following article number to view the article in the Microsoft Knowledge Base:
816071 (http://support.microsoft.com/kb/816071/) How to temporarily deactivate the kernel mode filter driver in Windows
The registry key that stores information for the Ofant.sys driver is Ofadriver.

Back to the top
 
I'm afraid I still don't really understand your problem. Sorry. You may not be keeping files off of your computer, but from my end it appears that the program thinks that you are. And I don't have an answer for that.
 
uh, I have never did that. It's the same installation from the beginning, some 2 years ago.
 
Back
Top Bottom