博客园_中道学友

如何通过Performance Log确定SQL的磁盘有性能问题?

2012-04-18T08:36:00Z

1. 查看Disk Bytes/sec. 举个例子, 这个counter的最大值如果是11M, 那么说明work load并不高.

2. 查看Avg. Disk sec/Transfer. 举例, 这个counter的推荐值是<0.015.

3. 查看Avg. Disk Queue Length, 这个推荐值是<2.

本文链接

IIS URL Rewriter

2012-03-20T07:16:00Z

今天一个朋友打电话过来, 问了这么一个问题:

假设有个用户的SharePoint网站的网址是http://company/defaut.aspx , 该用户希望浏览器上显示的URL是http://company/ , 不带后面的default.aspx.

怎么办?

解决方案

=======================

SharePoint返回的页面是什么URL, 就会返回什么URL.

SharePoint没有为这种需求做什么配置.

但是这还是可以做到的, 需要使用一个叫做URL Rewriter的IIS扩展.

可以在这里下载这个扩展.

页面上还有一个视频介绍, 挺给力的.

感谢Shuo Yang提供的信息.

本文链接

User的Delegation选项卡在Active Directory Users and Computers找不到?

2012-03-16T02:03:00Z

排查一个问题的时候需要检查某个用户的Delegation配置, 在自己的测试环境上除了域管理员外居然找不到普通用户的Delegation选项卡.

截图:

原因

====================

Delegation tab is only displayed when there is at least one value set in the servicePrincipalName attribute.

Delegation选项卡仅在Object的servicePrincipalName属性包含至少一个值的时候才会出现.

解决方案

===================

使用setspn.exe为该属性设置一个值.

还可以使用Attribute Editor选项卡, 给servicePrincipalName赋值. 之后该选项卡就出来了.

参考资料

====================

Delegation tab in ADUC not available until a SPN is set

http://blogs.msdn.com/b/mattlind/archive/2010/01/14/delegation-tab-in-aduc-not-available-until-a-spn-is-set.aspx

本文链接

SharePoint Workflow的code运行在哪个进程? w3wp.exe 还是OWSTimer.exe?

2012-03-15T08:59:00Z

之前做Workflow的问题, 代码一般都会运行在OWSTimer中. 于是便天真的认为所有的workflow都运行在OWSTimer进程中.

周二, 在客户的Win7上安装的SharePoint 2010里分析一个workflow的问题, 直接就抓了OWSTimer的TTT dump回来.

拿到之后一看, 客户的代码里的方法根本没有被执行过.

于是怀疑workflow是不是会在w3wp.exe里执行的. 在客户的环境上, 使用VS2010定下断点, 然后启动workflow. 注意, SPS2010里的workflow开发进程的attach是自动的.

断点进入了, 检查VS2010所Attach的进程, 果然是w3wp.exe.

额... 枉我自认为SharePoint基础扎实. 居然在这个问题上栽了. 汗呀~

那么究竟是什么因素决定workflow究竟是在w3wp.exe还是OWSTimer.exe里运行呢?

微软产品组的Paul Andrew给出答案如下:

Workflow instances in SharePoint run in either the sptimerv3.exe process or the w3wp.exe process. Which one an instance runs in at any particular time depends on what the most recent waiting activity. If the workflow starts as a result of a user interactive operation or if it restarts after waiting for a user activity which is web oriented, then the workflow instance will be executing on the w3wp.exe process. If the workflow instance restarts as a result of a Delay activity (some timeout) then it will be running on the v3timer.exe process.

I recommend you use the Visual Studio 2008 built in SharePoint workflow template and have Visual Studio 2008 and SharePoint 2007 on your development machine. This avoids most of the complexities with debugging workflow in SharePoint as Visual Studio 2008 will take care of it.

Alternatively, you can use Visual Studio to attach to both processes to do your debugging and it will work just fine.

Workflow instances running on your site lists do not run on your Central Admin process.

翻译:

SharePoint里的Workflow实例要么运行会运行在OWSTimer.exe里, 要么运行在w3wp.exe里. 某个特定的时间点上, 一个workflow的实例究竟运行在哪个进程里取决于最近的一次等待动作(activity). 如果workflow由于一次用户交互而启动, 或者它等待用户的某个动作之后重启的话(基本上都是web交互式的), 那么workflow实例会运行在w3wp.exe进程里. 如果workflow实例由于一个延迟动作(delay activity)(比如超时)而重启的话, 那么它会在OWSTimer.exe中运行.

另外, 注意STSADM的Workflow-eventdelivery-throttle属性的propertyvalue的说明:

A valid integer. For example, if the value is set to 15, 15 workflows are active in memory, and the sixteenth workflow automatically starts. The auto-start will be sent to the timer service to be processed later.

The default value is 15.

即, 即使是web交互式启动的workflow如果同时有超过throttle数值个同时启动的话, 那么超出的部分也会在OWSTimer里运行.

唉, 一个小小的问题竟如此纠结. 不过, 研究到这里也算告一段落了.

Reference

===================

In which process to Sharepoint 2007 Workflows run?

http://stackoverflow.com/questions/371657/in-which-process-to-sharepoint-2007-workflows-run

Workflow-eventdelivery-throttle: Stsadm property (Windows SharePoint Services)

http://technet.microsoft.com/en-us/library/cc287939%28v=office.12%29.aspx

本文链接

WinDBG脚本入门

2012-03-15T03:09:00Z

最近开始看一些针对非托管进程的WinDBG的使用了, Tess推荐去看Debugging Toolbox. 其第一篇就把我难住了, 脚本看不懂.

动手实践了一下, 发现下面的文章所讲的内容特别有帮助, 于是转载在这里.

原文地址

First steps with WinDBG scripting… (Memento)

http://www.msuiche.net/2007/08/03/first-steps-with-windbg-scripting-memento/

Here is a sample of script for Windbg for people who doesn’t want to waste time because they don’t find any document.

Firstly, to declare a variable you must use the prefix “r”. Moreover, the name must be $t[0..n]

Secondly, if you use the flag “/D” after “.printf” you can use pseudo-html code inside.

Thirdly, to read the value of an address you have to use “poi()” with the prefix “@” like : poi(@$t0)

To write byte or dword, you should use “eb” or “ed”.

And… the most fun is that you can create links like the following scheme :
.printf /D “<link cmd=\”COMMAND_TO_EXECUTE\”>DISPLAY_TEXT</link>\\n”;

To execute a script use
kd> $$>< "FULL_SCRIPT_PATH"

References:
http://blogs.msdn.com/debuggingtoolbox/archive/tags/Windbg+Scripts/default.aspx
http://www.dumpanalysis.org/blog/index.php/category/windbg-scripts/

本文链接

修改SPS2010的Search Core Results webpart, 令其显示文档被索引了的所有属性

2012-03-14T02:07:00Z

详细步骤在这里.

See what actually gets indexed in FAST

http://blogs.msdn.com/b/thomsven/archive/2011/01/26/seeing-what-actual-gets-indexed.aspx

本文链接

SharePoint中自定义代码普通用户执行报Access Denied, 管理员执行就OK, 咋办?

2012-03-13T10:04:00Z

正解如下:

把出错的代码调用放在SPSecurity.RunWithElevatedPrivileges中, 即可.

举例

SPSecurity.RunWithElevatedPrivileges(delegate()
{
// implementation details omitted
});

MSDN解释该方法的功能如下:

Executes the specified method with Full Control rights even if the user does not otherwise have Full Control.

参考资料

==============

SPSecurity.RunWithElevatedPrivileges Method

http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spsecurity.runwithelevatedprivileges.aspx

本文链接

记录一个SPS2010中RSS Web Part报错的问题

2012-03-13T07:08:00Z

SharePoint中的RSS WebPart只要访问需要认证的RSS Feed的时候就会失败.

错误信息

================

“The RSS webpart does not support authenticated feeds”

当RSS Web Part试图展示SharePoint站点自身上的列表内容的时候, 如果SharePoint站点不支持匿名访问, 那么上面的错误就会报出来了.

那么有没有办法既让RSS web part可以显示站点自身的数据, 同时又需要用户通过认证才能访问站点呢?

答案是可以的. 那就是让站点使用Kerberos认证. RSS Web Part只支持一种认证模式, 那就是Kerberos.

然而有一个客户她的环境里就配了Kerberos, 但是她的RSS web part还是会报上面的错误.

她的场里有两台WFE, 使用一个Host Header作为Network Load Balancer的名字.

1. 用户请求带有RSS web part的页面 –> WFE1

2. WFE1试图展示页面上所有的web part, 发现有个RSS web part, 于是再发一个http请求给Rss web part里配置的RSS Feed URL. 即再发一个请求给站点自己.

3. 由于有两个WFE, 那么这个请求有可能被另一个WFE处理, 也有可能自己处理.

4. 两个WFE之间通信的时候使用NTLM认证, 于是RSS Web Part显示失败.

尝试过的步骤

=================

通过下面的方式禁止任何的NTLM认证.

1. 修改每台WFE上的host文件, 让Host Header指向127.0.0.1. 防止请求发给另一个WFE.

2. 删除下面的注册表键值

"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\BackConnectionHostNames"

3. 执行下面的步骤, 禁止LoopBackCheck.

locate and then click the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

Right-click Lsa, point to New, and then click DWORD Value.
Type DisableLoopbackCheck, and then press ENTER.
Right-click DisableLoopbackCheck, and then click Modify.
In the Value data box, type 1, and then click OK.
Quit Registry Editor, and then restart your computer.

经过上面的步骤, 我们发现该问题依然存在. SharePoint服务器在修改了host文件的情况下依然会发出Internal RSS request.

经过进一步的研究, 我们发现该客户的内外网络间配置了防火墙, 该防火墙还扮演着Proxy的角色.

因为SharePoint两台前端上都配置了代理, 因为这个原因, 请求在修改了host文件的情况下还是会发到网络上, 从而被另一台WFE接收.

防火墙在转发请求的时候却使用了不该使用的NTLM认证方式, SharePoint于是向用户发出认证要求, 方式正是NTLM. 由于NTLM认证不会被RSS web part所接受, 于是错误发生了.

解决方案

=============

为"Use any authentication protocol"配置constrained delegation.

将SharePoint所使用的apppool帐号, farm admin帐号都添加到该配置中.

这里的配置(即"Use any authentication protocol")可以让用户使用NTLM认证协议访问WFE服务器, 然后WFE服务器可以impersonate该用户并使用Kerberos认证协议来访问其他服务器.

问题解决.

本文链接

利用PsExec提升命令行的安全级别, 绕过组策略执行命令

2012-03-12T02:16:00Z

有一次, 我需要在客户的环境上抓取Time Travel Tracing, 简称TTT(dump的一种). 但是就是不能成功抓取. 报错如下:

具体错误信息如下:

c:\Debuggers\ttt>tttracer -dumpfull -out e:\tttoutput -attach 3384

Microsoft (R) TTTracer 2.010.40929 (Sep 29 2009 21:13:03)

Copyright (C) Microsoft Corporation. All rights reserved.

Warning: Please upgrade to a newer version of TT Tracing.

Error: Trace of "w3wp.exe" PID:3384 did not complete successfully: status:20

Error: Communication between the guest process and this client

could not be established, which may be an indication of

permissions or privileges problem (see e:\tttoutput\w3wp01.out

for more details).

Error: Corrupted trace dumped to e:\tttoutput\w3wp01.run.err.

SEE ERROR OUTPUT FILE e:\tttoutput\w3wp01.out FOR MORE DETAILS.

w3wp01.run.err 的内容

------------

Microsoft (R) TTTClient 2.010.40929 (Sep 29 2009 21:12:58)

Microsoft (R) Time Travel Tracing 2.010.40929 (Sep 29 2009 21:12:58)

Copyright (C) Microsoft Corporation. All rights reserved.

Microsoft Confidential - Strictly For Internal Use Only

Initializing Time Travel Tracing for Attach to 3384

Time: 03/02/2012 15:40:36

OS:6.1.7601 EDITION:x64

Group tracing GUID: d2c17755-0428-4e74-8709-b2f3bdfe0fa1

Running "w3wp.exe"

Running "c:\Debuggers\ttt\nirvexec.exe" /duration 1 /ClientName "c:\Debuggers\ttt\TTTraceWriter.dll" /ClientParams "23 e:\tttoutput\w3wp01.run 0 0 0 100000 0 1 0 0 6001" /attach 3384

客户说他们有一些组策略对他们的计算机进行安全限制, 然而当我们打开secpol.msc进行查看的时候, 他们也不记得究竟修改了那些组策略了. -_-||

解决方案

===================

使用系统Command Prompt, 而不是提升了权限的Command Prompt.

如何才能使用System的Command Prompt呢? 答案是使用Sysinternals(已被微软收购)的一个叫做PsExec的命令行工具.

首先运行命令:

PsExec.exe -s -i -d cmd.exe

稍等, 在新弹出的CMD窗口中输入原本被系统拒绝的命令.

关于该工具的更多信息

==================

PsExec, User Account Control and Security Boundaries

http://blogs.technet.com/b/markrussinovich/archive/2007/02/12/638372.aspx

Execute processes on a remote system and redirect output to the local system

http://www.windowsitpro.com/article/remote-computing/psexec

下载地址

==================

PsExec v1.98

http://technet.microsoft.com/en-us/sysinternals/bb897553

本文链接

无法抓DUMP, 报错"Could not attach to process XXXX, NTSTATUS 0xC0000048"

2012-03-09T07:23:00Z

Problem Description

=================

We tried to use ADPlus to capture dump file. But the size of dump files are all under 20K.

We tried it many times.

Trouble Shoot

=================

I tried to use the “PsExec.exe –s –i –d cmd.exe” to initialize ADPLUS. No luck.

I tried to use WinDBG attach to the process, I failed with information below.

Detail Message is as below.

---------------------------

Could not attach to process 1272, NTSTATUS 0xC0000048

已试图设置进程的 DebugPort 或 ExceptionPort，但该进程中已存在端口，或试图设置文件的 CompletionPort，但文件中已设置端口，或已试图设置 ALPC 端口的相关完成端口，但该端口已设置。

Did more research, we found the root cause and solution.

We saw DebugDiag, and we asked customer to open that. We see the dialog below.

There it is! 1272 is our SharePoint w3wp.exe process.

Root Cause

========================

Debug Diag already attached to the process.

Debug Diag has rules, which can attach to target process. Even if the rule is completed, it won’t let go of the process.

Another word to say is the debug port is still occurpied by DebugDiag, so other debuggers such as WinDBG or CDB.exe cannot attach and write dump file.

Solution

========================

1. Clear the Rules in DebugDiag.

2. Kill the following processes in task manager.

· DbgSvc.exe

· Dbghost.exe

Problem Resolved.

Dump can now be successfully written.

Lesson Learned

========================

Be careful with DebugDiag. When its rules are finished, it won’t let go of the process.

Reference

========================

How to resolve "Cannot debug pid <pid>, NTSTATUS 0xC0000048" - "An attempt to set a process's DebugPort or ExceptionPort was made ..."

http://blogs.msdn.com/b/spike/archive/2011/10/21/how-to-resolve-quot-cannot-debug-pid-lt-pid-gt-ntstatus-0xc0000048-quot-quot-an-attempt-to-set-a-process-s-debugport-or-exceptionport-was-made-quot.aspx?CommentPosted=true#commentmessage

本文链接