| Event Id | 670 |
| Source | SnaBase |
| Description | The primary configuration file <filename> was successfully copied to <servername> |
| Event Information | According to Microsoft: CAUSE: This problem occurs in a mixed domain with an SNA Server 3.0 primary configuration file. The SNA Server 4.0 (or 4.0 SP1) Snacfg.dll file is not locating the configuration file time properly in the SNA Server 3.0 configuration file, which causes the 4.0 (or 4.0 SP1) backup server to copy the file even though it has not changed. RESOLUTION: A supported fix that corrects this problem is now available from Microsoft, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Upgrade the primary SNA Server to version 4.0. Microsoft has confirmed this to be a problem in SNA Server versions 4.0 and 4.0 SP1. |
| Reference Links | SNA 4.0 Backup Server Logs Numerous 670 Events With 3.0 Primary |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.