Jump to content


Anmol06

New Members
  • Posts

    7
  • Joined

  • Last visited

Posts posted by Anmol06

  1. are you specifying the sql server instance correctly ? what is it and what are you entering ?---->Where it should be specified?

    on the server in question, logged on with that service account if you open device manager does it tell you you are a standard user ?------->Device Manager shows all the hardware details. what else do I need to check in Device Manager?

  2.  

    SCCM Infrastructure:
    SCCM CB v1910
    Standalone Primary Site

     

    Issue :
    Prerequisite Check for SCCM Upgrade from 1910 to 2010 fails with this error in Prereqcheck.log
     
    ERROR: Failed to retrieve next row. $$<Configuration Manager Prereq><05-21-2021 11:00:09.190+420><thread=2760 (0xAC8)>
    <FQDN OF PRIMARY SITE SERVER>; SQL Server sysadmin rights; Error; Either the user account running Configuration Manager Setup or NT AUTHORITY\SYSTEM does not have sysadmin SQL Server role permissions on the SQL Server instance selected for site database installation, or the SQL Server instance could not be contacted to verify permissions. Setup cannot continue. $$<Configuration Manager Prereq><05-21-2021 11:00:09.191+420><thread=2760 (0xAC8)>
    ERROR: The current user does not have administrative rights on computer: <FQDN OF PRIMARY SITE SERVER>. $$<Configuration Manager Prereq><05-21-2021 11:00:09.198+420><thread=2760 (0xAC8)>
    The service account through which this check is run has sysadmin rights on the SQL Database.
    It will be really helpful if anyone here can point me in the right direction to fix this error.
  3. Can anybody here assist me to fix this issue? I have been struggling to fix this issue.
     
    SCCM Infrastructure:

    SCCM CB v1910

    Standalone Primary Site

    Issue

    SMS Distribution Manager shows error to process package distribution on Primary Site Server - FAILED TO TAKE SNAPSHOT

    I am unable to process any package content for distribution.

    D:\SCCMContentLib Folder is EMPTY.

    DISTMGR.Log details for one Software Update Package are stated below:

    Retrying package FG100***(SourceVersion:2;StoredVersion:2)	SMS_DISTRIBUTION_MANAGER	5/14/2021 6:31:41 AM	9388 (0x24AC)
    Start updating the package FG100F75...	SMS_DISTRIBUTION_MANAGER	5/14/2021 6:31:41 AM	9388 (0x24AC)
    CDistributionSrcSQL::UpdateAvailableVersion PackageID=FG100F75, Version=3, Status=2300	SMS_DISTRIBUTION_MANAGER	5/14/2021 6:31:41 AM	9388 (0x24AC)
    Taking package snapshot for package FG100F75	SMS_DISTRIBUTION_MANAGER	5/14/2021 6:31:41 AM	9388 (0x24AC)
    GetContentLibLocation - ABC.DEF.GHI.com	SMS_DISTRIBUTION_MANAGER	5/14/2021 6:31:41 AM	9388 (0x24AC)
    Finished GetContentLibLocation - ABC.DEF.GHI.com	SMS_DISTRIBUTION_MANAGER	5/14/2021 6:31:41 AM	9388 (0x24AC)
    Snapshot processing content with ID 18155987 ...	SMS_DISTRIBUTION_MANAGER	5/14/2021 6:31:41 AM	9388 (0x24AC)
    Taking snapshot for content 8384e0c7-bee0-4686-ad50-00488870f2bb from source \\ABC.DEF.GHI.com\SoftwareUpdates_Srv\SCDS Windows  Standard MS Patches - April 2021_\8384e0c7-bee0-4686-ad50-00488870f2bb	SMS_DISTRIBUTION_MANAGER	5/14/2021 6:31:41 AM	9388 (0x24AC)
    Sleep 825 seconds...	SMS_DISTRIBUTION_MANAGER	5/14/2021 6:31:42 AM	9356 (0x248C)
    GetTempFileNameA failed; 0x80004005	SMS_DISTRIBUTION_MANAGER	5/14/2021 6:31:42 AM	9388 (0x24AC)
    CContentDefinition::CreateNewContentDefinition failed; 0x80004005	SMS_DISTRIBUTION_MANAGER	5/14/2021 6:31:42 AM	9388 (0x24AC)
     TakeContentSnapshot() failed. Error = 0x80004005	SMS_DISTRIBUTION_MANAGER	5/14/2021 6:31:42 AM	9388 (0x24AC)
    The source directory doesn't exist or the 'Configuration Manager' service cannot access it, Win32 last error = 16389	SMS_DISTRIBUTION_MANAGER	5/14/2021 6:31:42 AM	9388 (0x24AC)
    STATMSG: ID=2361 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=ABC.DEF.GHI.com SITE=FG1 PID=20616 TID=9388 GMTDATE=Fri May 14 13:31:42.701 2021 ISTR0="\\ABC.DEF.GHI.com\SoftwareUpdates_Srv\SCDS Windows  Standard MS Patches - April 2021_\8384e0c7-bee0-4686-ad50-00488870f2bb" ISTR1="8384e0c7-bee0-4686-ad50-00488870f2bb" ISTR2="8384e0c7-bee0-4686-ad50-00488870f2bb" ISTR3="30" ISTR4="62" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="FG100F75"	SMS_DISTRIBUTION_MANAGER	5/14/2021 6:31:42 AM	9388 (0x24AC)
    Failed to take snapshot for Content with ID 18155987	SMS_DISTRIBUTION_MANAGER	5/14/2021 6:31:42 AM	9388 (0x24AC)
    Failed to take snapshot of one or more contents in package FG100F75	SMS_DISTRIBUTION_MANAGER	5/14/2021 6:31:42 AM	9388 (0x24AC)
    CDistributionSrcSQL::UpdateAvailableVersion PackageID=FG100F75, Version=2, Status=2302	SMS_DISTRIBUTION_MANAGER	5/14/2021 6:31:42 AM	9388 (0x24AC)
    STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=ABC.DEF.GHI.com SITE=FG1 PID=20616 TID=9388 GMTDATE=Fri May 14 13:31:42.750 2021 ISTR0="SCDS Windows  Standard MS Patches - April 2021_" ISTR1="FG100F75" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="FG100F75"	SMS_DISTRIBUTION_MANAGER	5/14/2021 6:31:42 AM	9388 (0x24AC)
    Failed to process package FG100***after 38 retries, will retry 62 more times	SMS_DISTRIBUTION_MANAGER	5/14/2021 6:31:42 AM	9388 (0x24AC)
    Exiting package processing thread for package FG100F75.	SMS_DISTRIBUTION_MANAGER	5/14/2021 6:31:42 AM	9388 (0x24AC)
    
    Validations:

    Despool.log has nothing relevant to note.

    I have checked these things already and ANSWER is YES to all of these questions :

    Can you ping the affected SERVERNAME if the path is a UNC path?
    Does the site server computer account have permissions to access the path?
    Can you access the affected path using the FQDN/NetBIOS/IP address when using the SYSTEM account from the site server?
    Can you access the affected path using the FQDN/NetBIOS/IP address when using the logged in user's account from the site server?
    Is there a firewall between the site server and the affected server? Are relevant ports (RPC/SMB) open?
    
×
×
  • 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.