Man On The Way

答题原则：

 

                                  选安全，选礼貌；

                                  遵章守纪最重要，

                                   除了撞车用急刹，

                                   稳住方向看好道。

                                   标志标线不难记，

                                   根据意思辨路标；

                                   方型辅助兰指示，

                                   红色禁止黄警告；

                                   看标线，有诀窍，

                                   颜色虚实要分牢；

                                   中心黄色同向白，

                                   黄线禁止和警告，

                                   实线绝对不能越，

                                   虚线可以适当绕；

                                   ※※※※※※※※※※※※※※※※※※※

答题诀窍：　　

凡是里面有"严禁、禁止、不得、必须、公安机关交通管理部门、车管所、回收企业"的是必选的或者是对的；凡是有"也行、不需要"是不能选或者是错的。

Today, one of my clients reported that, the reporting service cannot started.
They didn't change anything and database service is running fine.

Event Type: Error
Event Source: Report Server Windows Service (MSSQLSERVER)
Event Category: Management
Event ID: 107
Date: 12/10/2009
Time: 11:53:21 PM
User: N/A
Computer: ABC
Description:
Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.

The Reporting Services logs mostly just repeat that "The Report Server Windows service 'ReportServer' is not running." ...

This article is from Dell TechCenter Wiki

This section documents creating multipath connections to iSCSI LUNs on a Dell PowerVault MD3000i using the Microsoft iSCSI Initiator plus Dell's MD3000i iSCSI software. The server connecting to the MD3000i iSCSI LUN was server r3win2950b running 64-bit Windows Server 2003 R2. As shown below each MD3000i controller had two iSCSI ports, with one each in the 10.10.20 and 10.10.22 subnets. The r3win2950b connected to both
network subnets.



The MD3000i uses its own Device Specific Module code and thus required special installation of the Microsoft iSCSI Initiator. Therefore, on the server being connected to MD3000i (r3win2950b in this case), the existing Microsoft iSCSI Initiator instance was uninstalled and the server was rebooted. Then the Microsoft initiator was installed from Initiator-2.04-build3273-amd64fre.exe. All installation options except Microsoft MPIO Multipathing Support for iSCSI were selected:

Things have been busy for me and i haven't had the time to complete this series in a timely fashion. In part #1, we briefly talked about what's in the PlanManager and ResourceManager databases from a very high level. In the next few parts, we will go in a little bit further to discuss how HMC manage the resource allocation in Exchange, SharePoint and also OCS.

Before we get into that, I think it is essential to talk about how HMC database, PlanManager is linked with the Active Directory. It is important to understand that it isn't the purpose of this article to discuss about the database schema but I will discuss briefly how they are linked.

This article was original posted by Kip.Ng onhttp://blogs.technet.com/provtest/archive/2009/07/20/planmanager-and-resourcemanager-part-1.aspx

I believe one of the most mysterious parts of HMC is about the MPS engine and the Resource Management databases. Between last December and January, I blogged about how different products (Exchange, SharePoint and OCS) integrate in a HMC Solution. However, understanding just the integration points without knowing the resource management portion definitely does not paint a complete picture of what HMC is.

Since then, I have received requests to discuss a bit about the resource management in HMC and what those databases that shipped with HMC are storing and being used. So, in my next few entries, I intend to spend some time talking about the following,

1.       PlanManager and ResourceManager - Overall Concept

2.       HMC Resource Management and Active Directory

3.       HMC Resource Management and Exchange

4.       HMC Resource Management and Windows SharePoint Services

5.       HMC Resource Management and Office Communication Servers

1. How to get mailbox size:
Get-Mailbox | Get-MailboxStatistics | select-object  DisplayName, @{Name="Size (MB)"; Expression={ "{0:N2}" -f ($_.TotalItemSize/1.0MB)}}

Security updates are important. And as we're currently an evaluation setup for OCS 2007 R2, i've decided to install todays batch of security updates on these lesser important machines first. And after a reboot, OCS 2007 R2 Front End Service is not running anymore.

Below are error message from event log:

Event source: OCS Server
Event id: 12290
Event text: The evaluation period for Microsoft Office Communications Server 2007 R2 has expired. Please upgrade from the evaluation version to the full released version of the product. 

check this article
Uninstall KB 974571 and OCS works again.

SQLDMO.dll是个好东西，ASP.NET利用它可以实现在线备份、还原数据库等各种功能。近日有客户要求为其在后台添加一个管理数据库的功能。于是就出现了这篇文章。
     由于客户的数据库和WEB服务不再同一台服务器，当我们把网站部署在服务器上以后，运行程序，提示如下错误：

Retrieving the COM class factory for component with CLSID {10020200-E260-11CF-AE68-00AA004A34D5} failed due to the following error: 80040154. 

而客户又不想在这台电脑安装MSSQL，所以我们只需要在没有安装MSSQL的电脑上注册SQLDMO.DLL组件。
第 一步：首先将msvcr71.dll,  SQLDMO.DLL, Resources\2052\sqldmo.rll,Resources\1033\sqldmo.rll 拷贝到C:\Program Files\Microsoft SQL Server\80\Tools\Binn目录。
下载SQLDMO文件   
第二步：打开开始，在运行中输入 regsvr32 "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqldmo.dll" 注册sqldmo.dll。

正常情况下，经过以上两个步骤，网页就应该可以访问了的。 但是我们经过以上两次操作后，访问网页依然提示如下错误：
后 经过一段时间的检查，我们发现C:\Program Files\文件夹仅有Administrator和System的控制权限，而没有其他任何用户的权限，因此我们为Microsoft SQL Server文件夹增加上Network Service 的读取权限。
至此，问题得到解决！

exchange2007,发邮件到qq信箱不正常,在邮件队列中提示如下:
下一跃点域:qq.com  
传递类型:DnsConnectorDelivery ,
状态:重试;
邮件计数:19
重试时间:2009-8-22 10:03:25
上一错误:451 4.4.0 DNS query failed

分析:
此问题的出现和Exchange 2007 是安装在 Windows Server 2008 上面以及IPV6也有关系 (没有AAAA记录)
这是Exchange 2007 的一个Bug, 最快预计会在RU10中修复,Exchange 2010中也没有此问题
还有1个可能是防火墙有没有 DNS 的检查, 默认的 UDP 包的大小是 512 bytes, 可以尝试修改增加此值

暂时的解决方法
1. 在本地的 hosts 文件中添加 qq.com 的 MX 记录的IP (有很多条,最好全部加上)
119.147.10.123  mx0.qq.com
..........
2. 新建个 Send Connector, 在里面 remote 地址指定 qq.com 的MX A记录地址
3. 建立 额外的 SMTP 网关来外发邮件

When running a SSIS package on a 64-bit computer, you may receive below error messages:

Error1: The SSIS Runtime has failed to enlist the OLE DB connection in a distributed transaction with error 0x8004D00E "The transaction has already been implicitly or explicitly committed or aborted".

Error2: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "ora" failed with error code 0xC0202009.

Error3: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x800703E6.
An OLE DB record is available.

Solution:
Make sure you have enable MSDTC network access, and open the exception for DTC in Windows Firewall.