Tuesday, December 27, 2011

ENOW Mailscape

We have deployed Exchange 2010 and wanted to use a tool that monitors our Exchange environment. We did deploy ENOW Mailscape and are happy with this tool for the following reasons:

1.       Ease of deployment.
2.       Simple and intuitive user interface.
3.       Proactive monitoring.

Friday, July 1, 2011

CRM 2011 two warnings messages when launching Deployment Manager

We did a new install for CRM 2011 RTM on a machine that has Windows 2008 R2 Ent. and SQL 2008 R2 Ent. The installation went fine and we did not encounter any issues.However, when we launched Microsoft CRM Deployment Manager we got the two warning messages:

"Reporting is not enabled"
"One or more server roles are missing from this deployment"
















We have tried to re-install the Reporting Extensions for SQL and rebooted the machine several times to no avail.

So, I called MS support and the support engineer sent me  CRM 2011 diagnostic tool (do search and you can download it from the net). After we had run the tool we found the following:


================================================================================
                  SQL: Server Table Information [MSCRM_CONFIG]
================================================================================
>>           CRM
[Id......................................]: a29ccb04-21a3-e011-af81-005056a10003
[Name....................................]: CRM
[PodId...................................]: 00000000-0000-0000-0000-000000000000
[Roles...................................]: 86278415
[ScaleGroupId............................]: 00000000-0000-0000-0000-000000000000
[State...................................]: 1
[UniqueifierId...........................]:
[Version.................................]: 5.0.9688.583
[IsDeleted...............................]: False


HKEY_LOCAL_MACHINE\Software\Microsoft\MSCRM[CRM_Server_Serviceability_Version]: 5.0.9688.596

HKEY_LOCAL_MACHINE\Software\Microsoft\MSCRM[CRM_SrsDataConnector_Serviceability_Version]: 5.0.9688.583

So, to resolve the issue is a simple as check for Widows Updates and you might see the following updates:













Go ahead and install the updates, then reboot the machine and that should fix the issue.

Wednesday, April 6, 2011

DCOM 10016 errors on SharePoint 2010 Servers

We used to get DCOM error 10016 on all SharePoint 2010 servers:
Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          4/2/2011 12:51:29 AM
Event ID:      10016
Task Category: None
Level:         Error
Keywords:      Classic
User:          MyDomain\sp_farm_svc
Computer:      spapp.MyDomain.org
Description:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{61738644-F196-11D0-9953-00C04FD919C1}
to the user MyDomain\sp_farm_svc SID (S-1-5-21-1055929112-3131468103-4168165710-1893) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
After searching for a solution, I found this Blog and we did implement the suggested method instead of using the account that shows in the error message (in my case sp_farm_svc ) we have added WSS_WPG and WSS_ADMIN_WPG as shown below:
4-6-2011 8-06-51 AM
Our issued was resolved, but we still get DCOM error 10016 for a different class:
Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          4/6/2011 12:51:31 AM
Event ID:      10016
Task Category: None
Level:         Error
Keywords:      Classic
User:          MyDomain\SP_Farm_svc
Computer:      spapp.MyDomain.org
Description:
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{000C101C-0000-0000-C000-000000000046}
to the user MyDomain\SP_Farm_svc SID (S-1-5-21-1055929112-3131468103-4168165710-1893) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
At this point we are still working on the issue, and will post an update once we resolve it.