验证 MOSS 的 SP2 安装吗？
我在 Central Admin 中显示 12.0.0.6421，这似乎表明已安装 SP2。但是，当我运行 STSADM 命令来备份网站集时，我没有看到通知我它“将网站集设置为仅在备份期间只读”的消息，如下所述：
http://bobfox.securespsite.com/FoxBlog/Lists/Posts/Post.aspx ?ID=121
我只是收到了用于获取 SP2 之前版本的“操作成功完成”消息。这是否意味着 SP2 没有正确安装？
I have 12.0.0.6421 showing in Central Admin, which would seem to indicate that SP2 was installed. However, when I run an STSADM command to backup a site collection, I do not see the message informing me that it's "setting the site collection to be-read only for the duration of the backup" as described here:
http://bobfox.securespsite.com/FoxBlog/Lists/Posts/Post.aspx?ID=121
I simply get the "Operation completed successfully" message I used to get pre-SP2. Does this mean that SP2 wasn't installed correctly?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
Anthony，
显示 6421 版本确实表明 SP2 已就位。为了确保这一点，我检查了自己的场和虚拟机以及可靠的外部源（来自 Todd Klindt 博客的条目：http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=154）。我并不怀疑内部版本号，但确认一下也没什么坏处:-)
起初，我以为我了解问题可能出在哪里，所以我进行了一些测试。首先，我在灾难模式下运行 STSADM 备份来备份整个服务器场。由于这不是网站集备份，因此不应发生锁定：
我的灾难性备份运行没有问题，并且我没有收到任何有关锁定或只读行为的消息。我还查看了 ULS 日志，并确认没有建立锁定（搜索“sitelock”和“lock”）。这正如我所预期的那样，因为我正在进行灾难性备份，而不是网站集备份。
接下来，我尝试了网站集备份：
奇怪的是，我在这里也没有看到锁定消息。我查看了 ULS 日志，没有看到任何迹象表明锁已到位。最后，我执行了一个
...当备份正在运行时，迎接的是：
ARGH！这不是我想要（或期望）看到的！显然，有一个问题......所以，我尝试从不同的角度来解决它。我查看了 STSADM -o backup 命令的 MSDN 文档，它清楚地表明默认情况下应该发生锁定。它还表明 -nositelock 开关应该可以覆盖该行为。因此，我尝试将 -nositelock 添加到我的网站集备份命令行中。
你猜怎么着：它因命令行错误（无效参数）而被 -nositelock 阻塞。
执行STSADM -help 备份表明-nositelock对于我的环境不是有效的开关。我期望的新开关（例如-nositelock和-force）都不存在。就好像我的生产场在备份方面陷入了 SP2 之前的困境。
我决定检查我拥有的开发虚拟机，它也是版本 6421（但映像不同 - 除其他外，Win2K8 而不是 Win2K3 R2），我看到 -nositelock 是 有效的命令行选项。所以我检查了另一个同样是版本 6421 的开发虚拟机（但 Win2K3 R2 就像我的“常规农场”）。 -nositelock 也是一个有效的选项。
升级时，我在所有三个环境中应用了相同的 SP2（WSSv3 SP2 位，然后是 MOSS 2007 SP2 位，然后运行配置向导），所以我不确定发生了什么。
为了好玩，我在每个虚拟机上运行了网站集备份，这些虚拟机正确显示 -nositelock 是网站集备份的有效命令行开关，并且我收到了我没有看到的锁定消息之前看到过（而且你也没有看到）。显然，除了我的主要（生产）农场之外，SP2 更新在所有地方都按照我的预期运行。
我得出结论，在升级我的服务器场的过程中，我一定是做错了什么，所以我尝试在每个机器上重新运行 WSSv3 SP2 更新（第一个）和 MOSS 2007 SP2 更新（第二个）。每个盒子上的每次更新，我都被告知更新已经应用。因此，我退后一步：我重新运行配置向导，看看它是否会执行任何操作。然后我重新启动了场中的两个（虚拟）盒子。
没有变化。
此时此刻，我只能确认你并没有失去理智。我的两个具有 SP2 版本 6421 的一体化开发虚拟机按预期运行，但我的版本 6421 的双服务器/虚拟机场应该锁定网站集备份，但没有。
我想我可能会联系一位 Microsoft TAM 朋友。如果我学到任何东西，我会将其发布在这里，也可能发布在我的博客上。与此同时，您可能还想联系 Microsoft 进行跟进。显然，有些东西没有按预期工作。
为了它的价值！
Anthony,
Showing a build of 6421 does indeed indicate that SP2 is in-place. Just to make sure, I checked my own farm and VMs as well as a reliable external source (an entry from Todd Klindt's blog: http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=154). I didn't doubt the build number, but it never hurts to confirm :-)
At first, I thought I understood where the issue might be, so I ran some tests. First, I ran an STSADM backup in catastrophic mode to backup my entire farm. Since this isn't a site collection backup, no locking should occur:
My catastrophic backup ran without issue, and I didn't receive any message about a lock or read-only behavior. I looked at my ULS logs, as well, and confirmed that no lock was being established (searching for "sitelock" and "lock"). This was as I expected, as I was doing a catastrophic backup -- not a site collection backup.
Next, I tried a site collection backup:
Strangely enough, I didn't see a locking message here, either. I took a look at the ULS logs, and I saw nothing to indicate that a lock was put in place. Finally, I performed an
... while the backup was running and was greeted with this:
ARGH! That's not what I wanted (or expected) to see! Clearly, there was a problem ... so, I tried coming at it from a different angle. I took a look at the MSDN documentation for the STSADM -o backup command, and it clearly indicated that a lock should occur by default. It also indicated that the -nositelock switch should work to override the behavior. So, I tried adding -nositelock to my site collection backup command line.
Guess what: it choked on -nositelock with a command line error (invalid parameter).
Doing an STSADM -help backup indicated that -nositelock was not a valid switch for my environment. None of the new switches I expected (e.g., -nositelock and -force) were present. It's as if my production farm was stuck in pre-SP2 with regard to backups.
I decided to check a development VM I had that was also build 6421 (but different image -- amongst other things, Win2K8 instead of Win2K3 R2), I saw that the -nositelock was a valid command line option. So I checked another development VM that was also build 6421 (but Win2K3 R2 like my "regular farm"). -nositelock was a valid option there, too.
I had applied SP2 the same across all three environments when upgrading (WSSv3 SP2 bits, following by MOSS 2007 SP2 bits, followed by a run of the configuration wizard), so I wasn't sure what was going on.
For fun, I ran a site collection backup on each of the VMs that correctly displayed that -nositelock was a valid command line switch for site collection backups, and I was met with the locking message I didn't see earlier (and that you weren't seeing, either). Clearly, the SP2 updates were operating as I expected them to everywhere except my primary (production) farm.
I concluded I must have somehow done something wrong as part of upgrading my farm, so I tried re-running the WSSv3 SP2 update (first) and MOSS 2007 SP2 update (second) on each box. With each update on each box, I was told the that the update had already been applied. So, I dropped back and punted: I re-ran the configuration wizard to see if it would do anything. I then rebooted the two (virtual) boxes in the farm.
No change.
At this point, I can only confirm that you aren't losing your mind. Two of my all-in-one development VMs with SP2 build 6421 operate as expected, but my two-server/VM farm that is build 6421 that should be locking on site collection backup is not.
I think I'll probably follow up with a friend who is a Microsoft TAM. If I learn anything, I'll post it here and probably on my blog. In the meantime, you might want to follow up with Microsoft, as well. Clearly, something isn't working as expected.
For what it's worth!
这里有一个由 SharePoint 社区维护的 SharePoint 版本列表：
http://www.sharepointdevwiki.com/display/SharePointAdministrationWiki/SharePoint+Versions
There is a list of SharePoint Versions maintained by the SharePoint community here:
http://www.sharepointdevwiki.com/display/SharePointAdministrationWiki/SharePoint+Versions
您的版本对于 SP2 来说是正确的；我不会担心 STSADM 消息的出现；这是一个非常不一致的工具。
Your version is correct for SP2; I wouldn't worry about the STSADM message appearing; it's a pretty inconsistent tool.