Jump to content


edie209

Established Members
 View Profile  See their activity

  • Posts

    57

  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Posts posted by edie209

  9. Site recover fails

    in System Center Configuration Manager (Current Branch)

    Posted

    I am trying to recover my SCCM 1806 site. I have a full site backup but it fails restoring the database.

    I have rebuilt the server to the same version as before and then installed all the prerequisites including SQL and ADM wsus etc.  however it fails when restoring the database.  I have included the portion of the log file that is relevent(changing my site name and username) is there anything I may have got wrong is there another way of recovering?

    Steps I have taken are

    1. selected "recover site"
    2. recovered the site server from my backup location
    3. recovered my database from my backup location
    4. entered serial number
    5. accept terms
    6. downloaded required files
    7. select installation folder
    8. Details of SQL are pre populated
    9. path to SQL server DATA file is prepopulated
    10. path to SQL server LOG file is prepopulated

    At this point I am presented with the install settings, then it presents the prerequisite check and then begins the install where it fails with the errors seen on the log file attached

    sccmlog.txt

  12. 2012R2 SP1 not completing the Task Sequence

    in Configuration Manager 2012

    Posted

    I have noticed that since upgrading to 2012R2 SP1, Task Sequences will go no further than "Setup Windows and Configuration Manager" going to the login prompt after a reboot at that point.

     

    I have searched around and have noticed people talking about "microsoft configuration manager client upgrade 6.0 all" yet on inspection I still have "microsoft configuration manager client upgrade 5.0 all"

     

    I suspect that this is probably my problem but I can't find and information on how to upgrade microsoft configuration manager client.

     

    Thanks in advance for any help

     

    Edit I have just seen that I have to manually create the microsoft configuration manager client upgrade 6.0 all package

  15. Assignment Schedule not working

    in Configuration Manager 2012

    Posted

    I would like to have my client PC's re imaged on a schedule (as I work in a school), lets say every 6 weeks.

     

    I have created a collection to test my idea and I can get the PC's to re-image, but they continue to image again and again. I have obviously got the settings wrong in the scheduling tab.

     

    At present I have the "Assignment Schedule" set to run daily at 14:00 and the "Run Behaviour" set to Never rerun deployed program (I will change this once I know it works)

     

    I have set the Maintenance window for the collection to 12:00 - 15:00 to occur every 1 day during testing

  16. PXE-T04: Access Violation after SP1

    in Configuration Manager 2012

    Posted

    Well after trying every possible answer I have found on the web I have given up and taken my server back to an earlier checkpointed dated and now everything is working as it was.

     

    I have come to the conclusion that my Management Point was the issue but I was not able to find out for sure.

     

    I will upgrade again but not immediately as I have a bit od a backlog SCCM wise.

  17. PXE-T04: Access Violation after SP1

    in Configuration Manager 2012

    Posted

    After much reading of many similar problems I have got to this screen

     

    win8-repair-efi-bootloader.jpg

     

    I have also managed to get smspxe.log working and this is the errors I am getting

     

    Prioritizing local MP SCCM Server SMSPXE 01/10/2015 12:40:16 4216 (0x1078)
    RequestMPKeyInformation: Send() failed. SMSPXE 01/10/2015 12:40:16 4216 (0x1078)
    Failed to get information for MP: SCCM Server 80004005. SMSPXE 01/10/2015 12:40:16 4216 (0x1078)
    reply has no message header marker SMSPXE 01/10/2015 12:40:16 4216 (0x1078)
    PXE::MP_LookupDevice failed; 0x80004005 SMSPXE 01/10/2015 12:40:16 4216 (0x1078)
    Prioritizing local MP SCCM Server SMSPXE 01/10/2015 12:40:16 4216 (0x1078)
    RequestMPKeyInformation: Send() failed. SMSPXE 01/10/2015 12:40:16 4216 (0x1078)
    Failed to get information for MP: SCCM Server 80004005. SMSPXE 01/10/2015 12:40:16 4216 (0x1078)
    reply has no message header marker SMSPXE 01/10/2015 12:40:16 4216 (0x1078)
    Failed to send status message (80004005) SMSPXE 01/10/2015 12:40:16 4216 (0x1078)
    Failed to send the status message SMSPXE 01/10/2015 12:40:16 4216 (0x1078)
    PXE::MP_ReportStatus failed; 0x80004005 SMSPXE 01/10/2015 12:40:16 4216 (0x1078)
    PXE Provider failed to process message.
    Unspecified error (Error: 80004005; Source: Windows) SMSPXE 01/10/2015 12:40:16 4216 (0x1078)
    00:1A:4B:8C:08:24, 9006B0DA-15AA-11E0-7884-6D990E5F6D29: Not serviced. SMSPXE 01/10/2015 12:40:16 4216 (0x1078)
    Can anyone help?

     

     

  19. PXE-T04: Access Violation after SP1

    in Configuration Manager 2012

    Posted

    I have just upgraded my sccm 2012R2 to SP1 and now I am having the following error

     

    PXE-T04: Access Violation

     

    PXE-E36: Error Received from TFTP Server
    PXE-M-F Exiting PXE Rom
    Before the upgrade everything was working properly
    I have done this as RocketMan has explained in another post

    I have never had to reinstall PXE/WDS so correct me if I am wrong when doing this procedure.

    • If you uncheck all from the PXE tab on the DP properties and apply.
    • Wait for some time.....open up the wds console(If it still exists after the last step) and make sure that there is a yellow exclamation mark on the server node of the console. If this is correct then manually remove the wds role via server management.
    • Restart your server.......check the drive and if Remote Install folder exists then manually delete it.

    Now this is the way I always set up PXE and have never had any problems.

    I manually add the WDS role from server manager first on the site system DP. Do not configure it or do anything in relation to manually configuring it in any way. Restart the server. Now enable the PXE options again on the DP. This will configure WDS for you and should pre-populate the extra directories and extra files automatically as you already have the boot images configured to deploy from PXE server.

     

     

    Does anyone have any suggestions?

  21. error code 0x8007000 and 0x80004005

    in Configuration Manager 2012

    Posted

    I have fixed this issue and here is what I did.

     

    I think that when sccm came back online after the cluster upgrade it didn't see the D:\ drive and because of this referenced the c:\ drive because of this. First of all I was getting x86 boot disk was not available at my distribution point, I sorted this by deleting it and recreating and distributing it. But this was still looking at C:\ and when I came to the "applying OS stage" of the task sequence the error was 0x8007000. I went down the route of thinking it was a permission issue when it was actually unable to find the files.

     

    I realised that the references were all a bit messed up after quite alot of head scratching I read about creating blank txt file called NO_SMS_ON_DRIVE.SMS on the root of the drive on which you don't want any packages created so I did this and renamed the folders SMSSIG$ to SMSSIG$-old, SMSPKGSIG to SMSPKGSIG-old, SCCMContentLib to SCCMContentLib-old, SMSPKGC$ to SMSPKGC$-old, all of which had been created on the C:\ drive, and rebooted the server thinking all would now be ok.

     

    On reboot nothing worked again I was getting x86 boot disk was not available at my distribution point, I sorted this again by deleting it and recreating and distributing it. But no matter what I tried I could not get past the "applying OS stage" of the task sequence the error was still 0x8007000.

     

    Then it came to me in IIS my site was still looking to C:\ I changed this and now all is working again.

     

    I hope this might help someone else if you find yourself in a similar situation :)

  23. error code 0x8007000 and 0x80004005

    in Configuration Manager 2012

    Posted

    I think I may have made some progress. I figured that the issue was the OS installer that it was failing on so I removed it from my distribution point and then redistributed it and I have got further but failing on a driver package.

     

    My thoughts and I am not sure yet as I have to investigate further is that the cluster crash has caused some corruption to my distribution point. Is there a way I can remove everything that has been distributed and re distribute them or do I have to do every one individually?

  24. error code 0x8007000 and 0x80004005

    in Configuration Manager 2012

    Posted

    I have had SCCM2012 up and running great for about 2 years now. It is a VM running on Microsoft Hyper-V

     

    This summer I upgraded our Hyper V cluster and things went a little pear shaped I have everything back and working as it was, except SCCM.

     

    First of all the x86 boot disk was not available at my distribution point, I sorted this by deleting it and recreating and distributing it. However I am now getting an error at the applying OS stage of the task sequence the error is 0x8007000. With lots of reading I have been pointed to the Network Access Account, but no luck here I have tried a new account, and also a domain admin account and both fail, I have tried the "Allow clients to connect anonymously" in Distribution Point Properties with no luck.

     

     

    looking at smsts log files I see these errors

     

    RegQueryValueExW failed for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram TSManager 12/08/2014 10:20:03 1468 (0x05BC)
    GetTsRegValue() failed. 0x80070002. TSManager 12/08/2014 10:20:03 1468 (0x05BC)
    Error Task Sequence Manager failed to execute task sequence. Code 0x80004005 TSManager 12/08/2014 10:20:03 1468 (0x05BC)
    I have include the files hoping that someone can point me in the right direction

    smsts.log

    smsts-1.log

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.