Jump to content


vks1

Established Members
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About vks1

  • Rank
    Newbie
  1. Sorted.. I was using an aliast.. changed to the FQDN of the CAS server and it worked straight away.
  2. Hi - did you ever get this fixed? I am having the exact same error?!!?
  3. Got it working in the end, I had installed SQL in Single mode and needed to have it running in Mixed mode, enabled and then enabled the SA account and then run again and it all worked fine following the instructions below: http://support.microsoft.com/kb/2709082/de To resolve this issue complete the following steps: 1. Manually set the property back to ON by running the following command against your CM database: ALTER DATABASE <ConfigMgr DB> SET TRUSTWORTHY ON 2. Ensure that the database that was moved is owned by SA. 3. Ensure that Isolation Level is set to 'READ_COMMITTED_SNAPSHOT' - To check the Isolation Level run 'DBCC USEROPTIONS' - If it is set to anything else then 'READ COMMITTED SNAPSHOT', please run following commands: ALTER DATABASE <ConfigMgr DB> SET ALLOW_SNAPSHOT_ISOLATION ON ALTER DATABASE <ConfigMgr DB> SET READ_COMMITTED_SNAPSHOT ON Note: You might have to switch the SQL DB to Single User mode before running the two commands in previous step. Once done, please change it back to Multi User mode. Also make sure that all properties are set correctly under Database Properties - Options
  4. Hi, I am getting "SMS Provider reported an Error" message when trying to import an application into Config Manager. 03-09-2012 14-16-44.bmp I have looked at the SMSProv.log and its showing the following 'red' items *~*~[24000][0][Microsoft] Invalid cursor state [24000][0][Microsoft][sql Server Native Client 10.0]Invalid cursor state ThreadID : 6088 , DbError: 0 , Sev: 0~*~* *~*~e:\nts_sccm_release\sms\siteserver\sdk_provider\smsprov\ssputility.cpp(2105) : SQL command failed: if (object_id('tempdb..#sp_setupci_resultstr') IS NOT NULL) drop table #sp_setupci_resultstr;~ SQL Error: [24000][0][Microsoft][sql Server Native Client 10.0]Invalid cursor state~*~* ERROR: SQL command failed: if (object_id('tempdb..#sp_setupci_resultstr') IS NOT NULL) drop table #sp_setupci_resultstr; I have gone through and checked the DB and locations and all looks ok, even done the ALTER DATABASE commands but I am still getting this error message. Urgently need to get this up and running and this is a massive stumbling block and cant find what to do on the net anywhere
  5. I had a problem when deploying an OS and was pulling my hair out with the error message Task Sequence: <Task_Sequence_Name> has failed with the error code (0x8000FFFF). For more information, please contact your system administrator or helpdesk operator. And the image below: 07-08-2012 15-13-34.bmp Checking the Software Library the 'Operating System Images' was still Yellow.. deleted and readded and pushed to the DP's, took a few hours but was green after that. Deleted all unknown machines in the Assets and Compliance - All Systems window.. then went about and Deleted the Task Sequence and recreated in the following format (link below from technet is for 2007 but followed it and it worked for me in SCCM 2012) The following info albeit for SCCM 2007 worked for me as its essentially the same thing.. click here (method 2 worked for me) Cause The issue may occur because of two reasons: The "Create New Task Sequence Wizard" may create the Task Sequence with the "Apply Operating System" task and "Apply Data Image 1" task in the incorrect order. The "Create New Task Sequence Wizard" may create a partition the size of the hard drive where the Task Sequence was created, which usually will not match up with the size of the hard drive where the Task Sequence is deployed to. Resolution Use one of the below methods to resolve the issue. If the 100MB partition for BitLocker is desired, Method 1 is preferred because it is cleaner and less complex. If no 100MB partition is desired for BitLocker, use Method 3. Method 1 1. Right click the affected Task Sequence and choose “Edit”. 2. In the left pane of the Task Sequence select “Partition Disk”. 3. Double click on the first item under “Volume” to bring up the “Partition Properties”. 4. Under “Formatting options”, select “Quick Format”. Make sure that the option "Make this the boot partition" is set. Click on the “OK” button. 5. Double click on the second item under “Volume:” to bring up the “Partition Properties”. 6. Under “Partition options”, select “Use a percentage of remaining free space”. Set the “Size(%)” field to “100”. Under “Formatting options”, select “Quick Format”. 7. Select the “Apply Operating System” task. 8. Under the “Apply operating system from a captured image” option, make sure that the “Image:” drop down menu is set to “2-2”. 9. Select the “Apply Data Image 1” task. 10. Under the “Select the image from this package that you want to apply. This image can not contain any operating system. ” option, make sure the “Image:” drop down menu is set to “1-1”. 11. Move the “Apply Data Image 1” task immediately BEFORE the “Apply Operating System” task, but AFTERthe “Partition Disk” task. In Method 1, we apply the Data Image first via the "Apply Data Image 1" task, although the data image really doesn't contain anything we need. The reason we take this step is so that the "Apply Operating System" task that follows it moves on to the second partition via the option "Next available formatted partition". If we did not include the "Apply Data Image 1" task, the Task Sequence would try to apply the OS image on the first partition instead of the second partition. Method 2 1. Right click the affected Task Sequence and choose “Edit”. 2. In the left pane of the Task Sequence select “Partition Disk”. 3. Double click on the first item under “Volume” to bring up the “Partition Properties”. 4. Under “Formatting options”, select “Quick Format”. In the “Variable: ” field under “Advance options”, type BOOTPART Make sure that the option "Make this the boot partition" is set. Click on the “OK” button. 5. Double click on the second item under “Volume:” to bring up the “Partition Properties”. 6. Under “Partition options”, select “Use a percentage of remaining free space”. Set the “Size(%)” field to “100”. Under “Formatting options”, select “Quick Format”. In the “Variable:” field under “Advance options”, type OSPART Click on the “OK” button. 7. Select the “Apply Operating System” task. 8. Under the “Apply operating system from a captured image” option, make sure that the “Image:” drop down menu is set to “2-2”. 9. Under the “Select the location where you want to apply this operating system”, select from the “Destination:” drop-down menu “Logical drive letter stored in a variable”. In the “Variable name:” field, type OSPART 10. Select the “Apply Data Image 1” task. 11. In the right pane of the Task Sequence, click on the “Options” tab. Select “Disable this step”. As an alternative, you can also completely remove the “Apply Data Image 1” task instead of just simply disabling it. 12. Click on the “OK” button to save the changes to the Task Sequence. In Method 2, we have specified specifically what partition the OS image should be installed onto and not allowed it "guess" via the option "Next available formatted partition". Via Steps 10 and 11, we also have chosen not to apply the 100MB partition data image because it does not contain anything we need so it is not necessary (the "Setup windows and ConfigMgr" task will take care of setting up the Boot Manager on this partition). These steps are actually necessary because if these steps are not taken, it can cause issues 4 & 5 listed in the More Information section. Assigning the variable “BOOTPART” in Step 4 above is actually also not necessary because the variable is never used, but is included to make a clear distinction between the Boot and Windows partitions. Method 3 Method 3 should only be used to create only one partition that fills the entire hard drive in cases where 100MB partition is not desired for either immediate or future use of BitLocker: 1. Right click the affected Task Sequence and choose “Edit”. 2. In the left pane of the Task Sequence select “Partition Disk”. 3. Double click on the first item under “Volume” to bring up the “Partition Properties”. 4. Under “Partition options”, select “Use a percentage of remaining free space”. Set the “Size(%)” field to “100”. Under “Formatting options”, select “Quick Format”. Make sure that the option "Make this the boot partition" is set. Click on the “OK” button. 5. Single click on the second item under “Volume:” to highlight it, and then click on the red “X” button to delete it. 6. Select the “Apply Operating System” task. 7. Under the “Apply operating system from a captured image” option, make sure that the “Image:” drop down menu is set to “2-2”. 8. Select the “Apply Data Image 1” task. 9. In the right pane of the Task Sequence, click on the “Options” tab. Select “Disable this step”. As an alternative, you can also completely remove the “Apply Data Image 1” task instead of just simply disabling it. Note: Method 3 is actually the exact way that Task Sequences are created by the "New Task Sequence Wizard" when deploying non-Windows 7 OSes.
×
×
  • Create New...