Per checking the \Opalis Software\Opalis Integration Server\Management Service\Console\Logs, we have the following information.

2011\02\23 06:37:55.850 [0x00000000] <E> Exception caught in CRemoteEscortUtils::Connect: <Exception>
<Type>Opalis::Exception</Type>
<Location>
long __thiscall CRemoteEscortUtils::_DeployService(void)
C:\AutomatedBuild\IS5.Platform\Branches\6.2_Sanitized\Platform\ManagementUtilities\RemoteEscortUtils.cpp(165)
</Location>
<MsgCode>Deploy of upgrade Service failed</MsgCode>
<Prev><Exception>
<Type>Opalis::Exception</Type>
<Location>
long __thiscall OISManagementLibrary::WMIRunner::RunCommand(unsigned short *,int)
C:\AutomatedBuild\IS5.Platform\Branches\6.2_Sanitized\Platform\ManagementLibrary\WMIRunner.cpp(164)
</Location>
<MsgCode>WMI error</MsgCode>
<Prev><Exception>
<Type>Opalis::Exception</Type>
<Location>
long __thiscall OISManagementLibrary::WMIRunner::RunCommand(unsigned short *,int)
C:\AutomatedBuild\IS5.Platform\Branches\6.2_Sanitized\Platform\ManagementLibrary\WMIRunner.cpp(119)
</Location>
<MsgCode>WMI command call failed</MsgCode>
<Params>
<Param>9</Param>
</Params>
</Exception></Prev>
</Exception></Prev>
</Exception>

 - Unable to connect to the remote machine with the OpalisRemotingService
 - Cannot connect to the Escorter service on the remote machine
 - Deploy of upgrade Service failed
 - WMI error
 - WMI command call failed "9"

This problem is caused by the Opalis 6.2.2 doesn't support the Windows Server 2008 R2 platform as the Action Server, we can upgrade the Management Service to version 6.3 to fix this issue.

Client: YES/NO

This flag is used to flag whether the ConfigMgr client registered on the site server. In ConfigMgr 2007,  the RDR or UDR files can mark this flag.

RDR and UDR files are sent to the assigned MP, it means if the client belongs to the second site boundaries,  the RDR and UDR files would still send to its parent site MP directly.

Assigned: YES/NO

This flag is marked based on the boundaries setting.  The DDR file is used to update this flag.

Site Code: Primary site code/Secondary site code

DDR would update this flag. For the client belongs secondary site boundaries, before the 1^st heartbeat DDR inserts into the database, other discovery method can mark the site code as the secondary site code. Once the heartbeat DDR file comes, it would mark as its assigned site(it is always Primary Site).

Obsolete: Yes/No

A record that is marked obsolete typically was superseded by a newer record for the same client. The newer record becomes the client's current record, and the older record becomes obsolete.

Normally, it happens when the same machine reinstalled the OS or the same machine’s hardware ID changes.

Active: Yes/No

If a client computer is marked as obsolete, this state is set to No.

Blocked:Yes/No

This flag is set manually, used to block the client to server data, not block the client downloads the policy from the server.

Approval: Yes/No

Only the clients that are approved can receive policies containing sensitive data.

Here comes more information.

https://blogs.technet.com/b/configurationmgr/archive/2010/01/20/how-it-works-automatic-client-approval-in-configuration-manager-2007.aspx

The CCMEXEC.exe occupies high memory usage on the problematic machines, which can reach 200 MB or more.

This problem may happen after you assign a configuration baseline rule that includes more than many software updates in Microsoft System Center Configuration Manager 2007.

Cause

Each time you restart the CCMEXEC.exe service, you may see the following information from the SDMAgent.log, which contain many pending Package Loader Jobs.

SDM Agent starting up...      SdmAgent      1/5/2011 4:26:57 PM 2472 (0x09A8)

CTypeStore::RemoveStalePackages - 0 stale package(s) removed.       SdmAgent      1/5/2011 4:26:57 PM      2472 (0x09A8)

CTypeStore::Initialize succeeded.    SdmAgent      1/5/2011 4:26:57 PM 2472 (0x09A8)

CPackageLoader::InitializeJobState deserilalized X jobs.  SdmAgent      1/5/2011 4:27:14 PM          2472 (0x09A8)

CPackageLoader::DeleteAgedOutJobs deleted 0 old jobs.  SdmAgent      1/5/2011 4:27:14 PM 2472 (0x09A8)

Per using the following WQL query through the WMI namespace (root\ccm\xmlstore), you may find there are many obsolete package loader jobs exists

select * from xmldocument where storeid='Sdm Package Loader State Store'

Within the package loader job content, you can see it relates to the DCM baseline.  

While in the SDMAgent.log, we can see the following error reported repeatly.

CPackageLoader::ParseDtsMessage error (0x80004005).      SdmAgent      12/21/2010 7:25:08 PM     4736 (0x1280)

Error during SdmPackageLoader::HandleMessage (0x80004005).     SdmAgent      12/21/2010 7:25:08 PM     4736 (0x1280)

CPackageLoader::ParseDtsMessage error (0x80004005).      SdmAgent      12/21/2010 7:29:25 PM     4648 (0x1228)

Error during SdmPackageLoader::HandleMessage (0x80004005).     SdmAgent      12/21/2010 7:29:25 PM     4648 (0x1228)

CPackageLoader::ParseDtsMessage error (0x80004005).      SdmAgent      12/21/2010 7:33:53 PM     3648 (0x0E40)

Error during SdmPackageLoader::HandleMessage (0x80004005).     SdmAgent      12/21/2010 7:33:53 PM     3648 (0x0E40)

The cause can be found in the KB 937532.

 https://support.microsoft.com/kb/937532

When you create a configuration baseline rule that includes more than 300 software updates in System Center Configuration Manager 2007, the configuration baseline is not evaluated correctly

Resolution

1. Remove the problematic DCM baseline.

2. Remove the existing obsolete package loader jobs(all existing instances) in WMI namespace root\ccm\xmlstore returned from the following WQL query.

select * from xmldocument where storeid='Sdm Package Loader State Store'

The Service Manager Dashboard Solution Accelerator Portal can't display correctly.

It displays the following error.

Required permissions cannot be acquired.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Security.Policy.PolicyException: Required permissions cannot be acquired.

Source Error:

Stack Trace:

Version Information: Microsoft .NET Framework Version:2.0.50727.4952; ASP.NET Version:2.0.50727.4927

Resolution

We fixed with the following steps. 

a. Backup the web.config under the SLA website(the default port is 12345)

b. Open the web.config using notepad.exe, search the “trust level”, change the value to Full

<trust level="Full" />

c. Do a iisreset.

Problem Description

After upgrading the System Center Service Manager 2010 from RTM to SP1, we failed to add the web part through SharePoint website(integrated with Service Manager Web Portal).

It reported the following error.

Unable to add selected web part(s).

Top Announcements: Object reference not set to an instance of an object.

We also have the following error information after enabling the verbose log in SharePoint website.

01/31/2011 16:14:50.72 w3wp.exe (0x3DDC) 0x43AC Windows SharePoint Services Web Parts 89ku High Failed to add webpart http%253A%252F%252Fca%252Dsyd%252Dsms%252D101%253A16096%252Fsites%252FPortal%252F%255Fcatalogs%252Fwp%252FAnnouncements%252EWebPart;Top%2520Announcements. Exception Microsoft.SharePoint.WebPartPages.WebPartPageUserException: Object reference not set to an instance of an object . ---> System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.EnterpriseManagement.ServiceManager.Portal.Common.SdkQueryUtility.GetClass(Guid classId) at Microsoft.EnterpriseManagement.ServiceManager.WebParts.Announcements.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.AddedControl(Control control, Int32 index) at System.Web.UI.WebControls.WebParts.WebPartManager.WebPartManagerControlCollection.AddWebPartHelper(WebPart webPart) at System.Web.UI.WebControls.WebParts.WebPartManager.WebPartManagerControlCollection.AddWebPart(WebPart webPart) at System.Web.UI.WebControls.WebParts.WebPartManagerInternals.AddWebPart(WebPart webPart) at Microsoft.SharePoint.WebPartPages.SPWebPartManager.AddWebPartWithRetry(WebPart webPart) at Microsoft.SharePoint.WebPartPages.SPWebPartManager.AddDynamicWebPart(WebPart webPart) at Microsoft.SharePoint.WebPartPages.SPWebPartManager.LoadWebPart(WebPart aspWebPart, String zoneId, Int32 zoneIndex, Boolean isClosed) at Microsoft.SharePoint.WebPartPages.SPWebPartManager.AddWebPartInternalShared(WebPart webPart) at Microsoft.SharePoint.WebPartPages.SPWebPartManager.AddWebPartInternal(SPSupersetWebPart superset, Boolean throwIfLocked) --- End of inner exception stack trace --- at Microsoft.SharePoint.WebPartPages.SPWebPartManager.AddWebPartInternal(SPSupersetWebPart superset, Boolean throwIfLocked) at Microsoft.SharePoint.WebPartPages.SPWebPartManager.AddWebPartInternal(SPSupersetWebPart superset) at Microsoft.SharePoint.WebPartPages.WebPartQuickAdd.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)

Cause

This problem is caused by the .dll files used by the SharePoint integrated website is still RTM version. We need to replace them manually with the SP1 verion files.

Resolution

1. Check the dll file version under the SharePoint website, which is integrated with Service Manager Portal

   C:\inetpub\wwwroot\wss\VirtualDirectories\ bin

For example, C:\inetpub\wwwroot\wss\VirtualDirectories\16096\bin

Make sure most of the files version is 7.0.6555.0

2. If the file version in the above folder is less than 7.0.6555.0, please do the following actions.

a. Backup the folder “C:\inetpub\wwwroot\wss\VirtualDirectories \bin”

b. Go to the System Center Service Manager Portal installation folder, by default it is as following

   C:\inetpub\wwwroot\System Center Service Manager Portal\Analyst\Bin

There should be 18 .dll files under the folder and most of them are version 7.0.6555.0. Copy these 18 .dll files to replace the files mentioned in step 1.

c. Go to the C:\inetpub\wwwroot\System Center Service Manager Portal\Analyst\Bin\en, copy the 5 .dll files, and replace the files in the following path "C:\inetpub\wwwroot\wss\VirtualDirectories \bin\en"

d. Search the following two files on the Service Manager Management Server.

   C:\inetpub\wwwroot\wss\VirtualDirectories \bin

   Microsoft.EnterpriseManagement.ServiceManager.WebParts.dll

   C:\inetpub\wwwroot\wss\VirtualDirectories \bin\en

   Microsoft.EnterpriseManagement.ServiceManager.WebParts.resources.dll

In case either of them is less than 7.0.6555.0, please search the files to find out the latest version and replace in the above folder as well.

e. Open a DOS command line with the administrative right, then input “iisreset” to restart the IIS services.