Welcome to MicrosoftTechEd

SYMPTOMS

Users may be unable to view and execute the System Center Configuration Manager 2007 reports hosted on SQL Reporting Services.
Problem 1: Trying to access http://<SQLServerName>/reports returns blank window. 
Problem 2: When trying to execute one of the reports you get the following error: 

An error has occurred during report processing. (rsProcessingAborted)

Cannot create a connection to data source ‘{5C6358F2-4BB6-4a1b-A16E-8D96795D8602}’. (rsErrorOpeningConnection)

For more information about this error navigate to the report server on the local server machine, or enable remote errors.

CAUSE

This can occur due to a lack of permissions on the Reporting Server and the Database.

RESOLUTION

The basic configuration to allow an end user to view and execute the Configuration Manager Reports hosted via Reporting Services Point are as follows: 
1. Create a Global Security Group for users with Read access to the Reports.
2. Add all of the users to this group who need to access to the Reports. 
3. Open the Reports website with admin privileges (e.g. http://<SQLServerName>/reports).
4. Click on the Properties Tab > Click on New Role Assignment.
5. In the Group or User name box type in the domain\<GlobalSecurityGroup> you created in step 1.
This will allow those users to view the reports but will fail to execute them. They will get the error described in Problem 2.
To resolve Problem 2 follow the below steps: 
1. Add the Global Security Group in SQL using the SQL Server Management Studio Security > Logins > New Login > User Mapping.
2. Check the box for the SCCM DB and Check “db_datareader” role.

Source :-http://support.microsoft.com/default.aspx?scid=kb;EN-US;2428400

Symptoms

When using System Center Configuration Manager 2007, some clients may be assigned to the incorrect sitecode.  You may also see entries similar to those below in the locationservices.log file:

DhcpGetOriginalSubnetMask entry point not supported.

Current AD site of machine is ADSite1

This client might be within the boundaries of more than one site – AD SiteCode search matched 2 entries

The client will be assigned to the first valid site

LSGetAssignedSiteFromAD : Trying to Assign to the Site <P04>

LSVerifySiteVersion : Verifying Site Version for <P04>

LSGetSiteVersionFromAD : Successfully retrieved version ’4.00.6221.0000′ for site ‘P04‘

LSVerifySiteVersion : Verified Client Version ’4.00.6221.1000′ is not greater than Site Version ’4.00.6221.0000′. Client can be assigned to site <P04>.

Executing Task LSRefreshLocationsTask

Note that in the example above, the client should have been assigned to site P01 but was instead assigned to site P04.

Cause

This can occur if Active Directory references more than one site with the same site boundary.

Resolution

Remove or correct the site that contains objects using the same boundaries.  To identify sites using the same boundaries, run ldifde -f output.txt from a command prompt and search the text file for the related boundary (ADSite1 in the example above).

APPLIES TO

• Microsoft System Center Configuration Manager 2007

Directly copied from http://support.microsoft.com/kb/2002059

Thanks And Regards | Abhishek Joshi

SYMPTOMS

Assume that you frequently open and then close the System Center Configuration Manager console window on a computer that has System Center Configuration Manager 2007 Service Pack 2 (SP2) installed. In this situation, the memory usage of a Wmiprvse.exe process keeps increasing.

CAUSE

This issue occurs because the session to the Windows Management Instrumentation (WMI) provider is not closed when the Configuration Manager console window is closed. Therefore, the session state leaks memory.

RESOLUTION

To resolve this issue, install the following hotfix on all computers that have the Configuration Manager console installed. 

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

Note:- The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have System Center Configuration Manager 2007 Service Pack 2 (SP2) installed. 

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

File name	File version	File size	Date	Time	Platform
Adminui.wqlqueryengine.dll	4.0.6487.2141	96,104	01-Feb-2010	12:20	x86

APPLIES TO

• Microsoft System Center Configuration Manager 2007 Service Pack 2

Directly copied from http://support.microsoft.com/kb/2176220

Thanks and Regards | Abhishek Joshi

Incoming search terms:

• this does not appear to be system centre configuration manger (1)

SYMPTOMS

Consider the following scenario:

• You have a computer that is running a Microsoft System Center Configuration Manager 2007 Service Pack 2 (SP2) site server.
• You click the following item in the Configuration Manager console:

  Computer Management\Operating System Deployment\Computer Association

• You run the Import Computer information Wizard to import new computer information.

In this scenario, the computer associations are not created when the new computer information is imported. Therefore, there is no new node in the computer association list.
Note When you import the new computer information, you expect to see a new node in the computer association list.

RESOLUTION

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, your computer must be running a System Center Configuration Manager 2007 Service Pack 2 (SP2) site server.

Installation instructions

Note The following hotfix package can be installed on a System Center Configuration Manager 2007 SP2 site server and a client running System Center Configuration Manager Client SP2. Both systems can be running an x86-based or x64-based version of the Windows operating system:

SCCM2007-SP2-KB980270-X86-ENU.msi

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

For all supported x86-based and x64-based versions of System Center Configuration Manager SP2

APPLIES TO

• Microsoft System Center Configuration Manager 2007 Service Pack 2

Directly copied from http://support.microsoft.com/kb/980270

Thanks and regards | Abhishek Joshi

Incoming search terms:

• sccm 2007 find computer (1)
• sccm import computer not working (1)

Symptoms

Microsoft System Center Configuration Manager 2007 backups may fail if other VSS-aware backup software is scheduled to run concurrently.  In this scenario, the Smsbkup.log will show entries similar to the following:

Deleting E:\SMSbackup\SiteServer\SMSServer\inboxes\auth\statesys.box\incoming, FAILED, Win32 Error = 145
Deleting E:\SMSBackup\SiteServer\SMSServer\inboxes\auth\ddm.box, FAILED, Win32 Error = 145

Deleting E:\SCCMBackup\Backup, FAILED, Win32 Error = 145

Failed to delete the contents of the backup folder. Error Code = 0×0 SMS_SITE_BACKUP 
Error: Deleting the existing files in the backup location failed… SMS_SITE_BACKUP

SMS site backup failed. Please see previous errors. SMS_SITE_BACKUP

SMS site backup service is stopping. SMS_SITE_BACKUP

Cause

These errors can occur if the Volume Shadow Copy Service (VSS) provider is in use by another process.  Configuration Manager Backup expects to have exclusive access to these resources when performing a backup.

Resolution

To prevent these errors, configure Configuration Manager Backup to start at a time outside the window for other backup jobs on the server.  The schedule for this can be found in the Configuration Manager Console under Site Management -> Site Code -> Site Settings -> Site Maintenance -> Tasks -> Backup ConfigMgr Site Server.

APPLIES TO

• Microsoft System Center Configuration Manager 2007 Service Pack 1
• Microsoft System Center Configuration Manager 2007 R2

Directly copied from http://support.microsoft.com/kb/2387913 

Thanks and regards | Abhishek Joshi

Incoming search terms:

• sccm 2007 an error has occurred during report processing (rsprocessingaborted) (1)
• sccm2007-sp2-kb2176220-enu msi problem install (1)
• siteserver\smsserver\inboxes\auth\ddm box failed win32 error = 5 (1)