Shulou(Shulou.com)06/02 Report--

Background information, using the file service on windows server 2012, the file server is cluster (two nodes), and the windows sync share service is enabled. However, the windows sync share service on node 2 has been unable to start, and a 2276 and 2269 error has been reported in the log.

For the first time, I uninstalled all the iis components on node2 and installed them according to the components on node1. After solving the problem, I also configured the cluster settings for the workspace service.

On the last two occasions, it was found that the windows sync share service could not be started when switching services to node2. I found a lot of articles and links, which were useless and could only be solved by reinstalling them above, and encountered this problem again on May 8.

When reporting an error, it is found that it is still a log that the workgroup process failed to initialize, and the following phenomena and information are summarized:

Workspace uses hostablecore, the underlying functionality of http.sys, and does not rely on iis, but uses the IIS manager to discover that the www service is started. Manually start the windows sync share service report-2147024713 on node2, which is similar to but different from the phenomenon in this article. There are IIS sites in this article, but not in our environment, and node1 is normal even if the www service is enabled, and it is not normal for node2 to open www.

The windows sync share service on node2 cannot be started. After the www service is stopped, the windows sync share service on node2 can be started. Stopping the www service on node1 has no effect on workspace. So the conclusion is that www services do not seem to have an impact on workspace services, but may cause conflicts on windows sysnc share services. But the inconsistent performance on fsnode1,fsnode2 is very confusing.

The final solution:

1. Disable the www service on each of the file server clusters. After the www service is disabled, the windows sync share can be started on node2 and has no effect on node1.

Last question:

Node1,node2 configuration is the same, why there is no conflict between www service and windows sync share service on node1, but conflict on node2. .

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.