Hi, I need to install Microsoft Forefront Endpoint Protection 2010 on a Server. I created a test lab that works. I installed SQL Server 2008 R2, then SCCM 2007 SP2, then SCCM 2007 R2, then Forefront Endpoint Protection 2010. The problem I have it on a client in which I install the same. I get an error in the installation of SCCM 2007 SP2 during step "create and initialize site database". After this error came back to start the installation process from scratch, installing the first Windows Server 2008 R2, update all windows patches and then reinstalling SQL Server 2008 R2 and the following next steps and re-express exactly the same error. All components are on the same server. The user is Domain Admin in the two scenarios. Assistant which gives the error in ConfigMgrSetup.log <03-26-2012 17:15:22> SQL Script: Create SQL object v_LocalizedSettingType <03-26-2012 17:15:22> SQL Script: Create SQL object fnBuildCICategories <03-26-2012 17:15:22> SQL Script: Create SQL object v_LocalizedNameValue <03-26-2012 17:15:27> ***SqlError: [42000][601][Microsoft][ODBC SQL Server Driver][SQL Server]Could not continue scan with NOLOCK due to data movement. <03-26-2012 17:15:27> SqlExecute < exec sp_bindefault SMSDefaultToday, 'Collections.BeginDate' exec sp_bindefault SMSDefaultToday, 'Collections.LastChangeTime' exec sp_bindefault SMSDefaultToday, 'Collections.LastMemberChangeTime' exec sp_bindefault SMSDefaultToday, 'Collections.CurrentStatusTime' exec sp_bindefault SMSDefaultToday, 'Collection_Copies.TimeSaved' exec sp_bindefault SMSDefaultToday, 'Collection_MemberChg_Notif.TimeUpdated' exec sp_bindefault SMSDefaultToday, 'UpdatesSummary.DateCreated' exec sp_bindefault SMSDefaultToday, 'PatchStatusSummary.LastModifiedDate' > <03-26-2012 17:15:27> Cannot execute sql command exec sp_bindefault SMSDefaultToday, 'Collections.BeginDate' exec sp_bindefault SMSDefaultToday, 'Collections.LastChangeTime' exec sp_bindefault SMSDefaultToday, 'Collections.LastMemberChangeTime' exec sp_bindefault SMSDefaultToday, 'Collections.CurrentStatusTime' exec sp_bindefault SMSDefaultToday, 'Collection_Copies.TimeSaved' exec sp_bindefault SMSDefaultToday, 'Collection_MemberChg_Notif.TimeUpdated' exec sp_bindefault SMSDefaultToday, 'UpdatesSummary.DateCreated' exec sp_bindefault SMSDefaultToday, 'PatchStatusSummary.LastModifiedDate' <03-26-2012 17:15:27> Setup cannot create the required database tables. Contact your SQL administrator. I tried to duplicate the error in my laboratory but still works well, I've uninstalled and installed again and the installation is successful. In my laboratory the next step in the log where I have the error is: <03-30-2012 11:17:02> SQL Script: Create SQL object v_LocalizedSettingType <03-30-2012 11:17:02> SQL Script: Create SQL object fnBuildCICategories <03-30-2012 11:17:02> SQL Script: Create SQL object v_LocalizedNameValue <03-30-2012 11:17:07> Executing AssetIntelligence WMI scripts <03-30-2012 11:17:07> Creating AssetIntelligence GroupMap entries <03-30-2012 11:17:08> Creating AssetIntelligence KB WMI tables' primary keys <03-30-2012 11:17:08> SQL Script: Installing key on table AIHinvClass <03-30-2012 11:17:08> SQL Script: Installing key on table INSTALLED_SOFTWARE_DATA I appreciate the help I can give. thanks Maximiliano

<03-26-2012 17:15:27> ***SqlError: [42000][601][Microsoft][ODBC SQL Server Driver][SQL Server]Could not continue scan with NOLOCK due to data movement. Is SQL Server running on VMware ?? Because I've seen the same problem on VMware but never with a physical server or Hyper-v and I was forced to move away from VMware because there was no alternative.Bechir Gharbi | http://myitforum.com/myitforumwp/community/members/bgharbi/ | Time zone : GMT+1

<03-26-2012 17:15:27> ***SqlError: [42000][601][Microsoft][ODBC SQL Server Driver][SQL Server]Could not continue scan with NOLOCK due to data movement. Is SQL Server running on VMware ?? Because I've seen the same problem on VMware but never with a physical server or Hyper-v and I was forced to move away from VMware because there was no alternative.Bechir Gharbi | http://myitforum.com/myitforumwp/community/members/bgharbi/ | Time zone : GMT+1

Yes, SQL is running on Vmware. I have a virtual Server with all roles, SQL, SCCM and Forefront in my test Lab and the same in my client. The only differenceis that in mylaboratory isinhyper-v. The problemis that I haventaphysicalcomputerto solvethis problemifthatthe onlyalternative. I'll tryto do the sameinVMwareto seeif I canduplicate the error. Many Thanks

Yes, SQL is running on Vmware. I have a virtual Server with all roles, SQL, SCCM and Forefront in my test Lab and the same in my client. The only differenceis that in mylaboratory isinhyper-v. The problemis that I haventaphysicalcomputerto solvethis problemifthatthe onlyalternative. I'll tryto do the sameinVMwareto seeif I canduplicate the error. Many Thanks

Perform the test installation of System Center Configuration Manager 2007 in a VMware environment and it worked correctly. I could not duplicate the error and I still find a path to the solution of this problem. Any help is appreciated that they can provide. regards

Perform the test installation of System Center Configuration Manager 2007 in a VMware environment and it worked correctly. I could not duplicate the error and I still find a path to the solution of this problem. Any help is appreciated that they can provide. regards

Your test is not a final confirmation. That problem is random and may not appear. Personally, I've only seen it with VMWare. If you want a quick answer then it's better contact to Microsoft support.Bechir Gharbi | My blog: @myITforum.com | Twitter: @Bechir_Gharbi | Linkedin: Bechir Gharbi | Time zone: GMT + 1

Your test is not a final confirmation. That problem is random and may not appear. Personally, I've only seen it with VMWare. If you want a quick answer then it's better contact to Microsoft support.Bechir Gharbi | My blog: @myITforum.com | Twitter: @Bechir_Gharbi | Linkedin: Bechir Gharbi | Time zone: GMT + 1

The problem has been resolved. Applying the Service Pack 1 for SQL Server 2008 R2. It was not necessary in laboratory environment install Service Pack 1, but something in the production environment was different and it was resolved that way.