Receiving message "Operation Failed"
Moderator: SourceGear
Receiving message "Operation Failed"
Environment: Windows 2003 Server
SOS Server: 4.0.2 (standard)
SOS Client: 4.0.2 (standard)
When we try to view a tree with many files (1013 files), we get the message:
"Operation Failed". We have no problems viewing trees with small number of files.
Please let me know how we can resolve this.
SOS Server: 4.0.2 (standard)
SOS Client: 4.0.2 (standard)
When we try to view a tree with many files (1013 files), we get the message:
"Operation Failed". We have no problems viewing trees with small number of files.
Please let me know how we can resolve this.
Is it possible that a firewall or other device on the network is closing the connection between the SOS Client and Server? Firewalls can be configured to close a connection after a certain amount of data or time has passed.
Check the log.txt file in the SOS Servers directory. Are there any error messages that coincide with the failed operation?
Check the log.txt file in the SOS Servers directory. Are there any error messages that coincide with the failed operation?
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
PLEASE READ THE ENTIRE POST!!!!!
I posted the log file for you to review!!! There is an exception in the log file.
The error: "Error processing client request" could be a network issue.
Is it possible that a firewall or other device on the network is closing the connection between the SOS Client and Server? Firewalls can be configured to close a connection after a certain amount of data or time has passed. A firewall might also close a connection if no data is being passed. This often happens in SOS, where a great deal of processing is done on the SOS Server side, during which time there is little communication with the Client.
Another possibility might be minor database corruption. Do you run Analyze regularly on your database?
http://support.sourcegear.com/viewtopic.php?t=50
Is it possible that a firewall or other device on the network is closing the connection between the SOS Client and Server? Firewalls can be configured to close a connection after a certain amount of data or time has passed. A firewall might also close a connection if no data is being passed. This often happens in SOS, where a great deal of processing is done on the SOS Server side, during which time there is little communication with the Client.
Another possibility might be minor database corruption. Do you run Analyze regularly on your database?
http://support.sourcegear.com/viewtopic.php?t=50
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
PLEASE READ THE ENTIRE POST!!!!!
I posted the log file for you to review!!! There is an exception in the log file.
I did look at the log and also consulted with some of my SourceGear colleagues.
While there are a number of exceptions, they don't show anything specifically wrong with the SOS Server. For instance, you can see smaller file lists in other directories.
The exceptions point to unexpected data being received by the SOS Server.
When you have a very large file list (of over 1000 files, for instance), it can take a while for the SOS Server to gather up the data to send to the client since it must communicate through the SourceSafe automation component, which is not terribly efficient.
In the meantime, a proxy, firewall, router, or other device might close the connection, since no data is passing -- or perhaps if too much data has passed.
If the connection has closed when the SOS Server is trying to send data to the client, it might be getting a bounce back from the firewall or other device and then the log shows an exception.
Your log also shows there's a problem with DNS on your network:
"Unable to get hostname from address. This *should* be non-fatal."
This also slows down operations.
Is it possible that a firewall or other device on the network is closing the connection between the SOS Client and Server? Firewalls can be configured to close a connection after a certain amount of data or time has passed.
Is there a firewall on the SOS Client side? On the SOS Server side?
Are you using NAT?
Are you using a cable modem or DSL modem? These have been known to pass unrecognized data to the SOS Server.
When you try to get the file list from the large directory, how long does it take before you get the error: "Operation failed?"
While there are a number of exceptions, they don't show anything specifically wrong with the SOS Server. For instance, you can see smaller file lists in other directories.
The exceptions point to unexpected data being received by the SOS Server.
When you have a very large file list (of over 1000 files, for instance), it can take a while for the SOS Server to gather up the data to send to the client since it must communicate through the SourceSafe automation component, which is not terribly efficient.
In the meantime, a proxy, firewall, router, or other device might close the connection, since no data is passing -- or perhaps if too much data has passed.
If the connection has closed when the SOS Server is trying to send data to the client, it might be getting a bounce back from the firewall or other device and then the log shows an exception.
Your log also shows there's a problem with DNS on your network:
"Unable to get hostname from address. This *should* be non-fatal."
This also slows down operations.
Is it possible that a firewall or other device on the network is closing the connection between the SOS Client and Server? Firewalls can be configured to close a connection after a certain amount of data or time has passed.
Is there a firewall on the SOS Client side? On the SOS Server side?
Are you using NAT?
Are you using a cable modem or DSL modem? These have been known to pass unrecognized data to the SOS Server.
When you try to get the file list from the large directory, how long does it take before you get the error: "Operation failed?"
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager