none
Major SQL Issues after upgrading to latest 1903 Branch and Updating SQL Native Client RRS feed

  • Question

  • Good afternoon, I need some help please

    I ran all the pre-requisite tests for the new CM1902, and everything passed except the SQL native client version.  I upgraded it to the latest, ran pre-requisite test again, everything passed and we proceeded.  It is stuck on "Installing" state and when I go to Monitoring\Updates and Servicing Status and look at the state of Configuration Manager 1902, it's still in the sate of "Installing" here too, but it's blank when I go to status:

    

    I go to component status, and I have a lot of failures now:

    When I look at SMS_STATE_SYSTEM Status Messages i get a ton of SQL errors:

    I am at a loss as to where to start.  Any guidance would be greatly appreciated!  I have never had any issue with any upgrades prior to this, so I have a feeling it has to do with the SQL Native Client upgrade.  

    Tuesday, June 18, 2019 9:00 PM

Answers

  • So most of this was fixed and all the errors were resolved by restarting the following services:
    SMS_EXECUTIVE, SMS_SITE_COMPONENT_MANAGER, CONFIGURATION_MANAGER_UPDATE.

    A few hours later, the update/upgrade finished and it's all working ok now.  I'm having issues with distribution points but will figure it...baby steps.  :)

    Thanks so much!

    Wednesday, June 19, 2019 6:17 PM

All replies

  • Check CMUpdate.log and sitecomp.log
    Tuesday, June 18, 2019 10:25 PM
  • Hi,

    I do not think it has to do with SQL Native Client, as mentioned, please check CMUpdate.log firstly to check where the upgrade stuck.

    Regards,
    Allen

    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, June 19, 2019 8:35 AM
  • Thanks so much for your reply Michael-CM and Allen Lio

    Here's the logs for the install...it's a bunch, but you'll see where it all starts:

    Waiting for changes to the "F:\Microsoft Configuration Manager\inboxes\cmupdate.box" directories, updates will be polled in 600 seconds...	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:46:37 AM	3724 (0x0E8C)
    Detected a change to the "F:\Microsoft Configuration Manager\inboxes\cmupdate.box" directory.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:47:48 AM	3724 (0x0E8C)
    INFO: setup type: 1, top level: 1.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:47:53 AM	3724 (0x0E8C)
    Content replication succeeded. Start extracting the package to run prereq check...	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:47:53 AM	3724 (0x0E8C)
    Successfully reported ConfigMgr update status (SiteCode=MPS, SubStageID=0xd0005, IsComplete=1, Progress=1, Applicable=1)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:47:53 AM	3724 (0x0E8C)
    Successfully reported ConfigMgr update status (SiteCode=MPS, SubStageID=0xd0005, IsComplete=1, Progress=25, Applicable=1)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:47:53 AM	3724 (0x0E8C)
    Checking if the CMU Staging folder already has the content extracted.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:47:53 AM	3724 (0x0E8C)
    Creating hash for algorithm 32780	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:47:54 AM	3724 (0x0E8C)
    Staging folder has hash = 648405A1DE41056E59736081699AA11BFC349FD1211C619D47D423A6CF0135EC	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:47:55 AM	3724 (0x0E8C)
    Staging folder (\\?\F:\Microsoft Configuration Manager\CMUStaging\936C9D3E-5065-4C95-BAB6-7DB24F64083A) has hash 648405A1DE41056E59736081699AA11BFC349FD1211C619D47D423A6CF0135EC which does not match hash from content library AF4BD13FC591BF63105C413CFB209FD849406996C49378B9742C0A9721C841EE	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:47:55 AM	3724 (0x0E8C)
    Delete folder \\?\F:\Microsoft Configuration Manager\CMUStaging\936C9D3E-5065-4C95-BAB6-7DB24F64083A\ returned 0. Extractring the content from content library...	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:47:55 AM	3724 (0x0E8C)
    update package content 936C9D3E-5065-4C95-BAB6-7DB24F64083A has been expanded to foler \\?\F:\Microsoft Configuration Manager\CMUStaging\936C9D3E-5065-4C95-BAB6-7DB24F64083A\	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:54:29 AM	3724 (0x0E8C)
    Successfully reported ConfigMgr update status (SiteCode=MPS, SubStageID=0xd0005, IsComplete=1, Progress=50, Applicable=1)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:54:35 AM	3724 (0x0E8C)
    File '\\?\F:\Microsoft Configuration Manager\CMUStaging\936C9D3E-5065-4C95-BAB6-7DB24F64083A\SMSSetup\update.map.cab' is signed and trusted.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:54:35 AM	3724 (0x0E8C)
    Signing root cert's thumbprint: cdd4eeae6000ac7f40c3802c171e30148030c072	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:54:35 AM	3724 (0x0E8C)
    Extracting file \\?\F:\Microsoft Configuration Manager\CMUStaging\936C9D3E-5065-4C95-BAB6-7DB24F64083A\SMSSetup\update.map.cab to \\?\F:\Microsoft Configuration Manager\CMUStaging\936C9D3E-5065-4C95-BAB6-7DB24F64083A\SMSSetup\	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:54:36 AM	3724 (0x0E8C)
    Extracted \\?\F:\Microsoft Configuration Manager\CMUStaging\936C9D3E-5065-4C95-BAB6-7DB24F64083A\SMSSetup\update.map	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:54:36 AM	3724 (0x0E8C)
    Successfully reported ConfigMgr update status (SiteCode=MPS, SubStageID=0xd0005, IsComplete=1, Progress=75, Applicable=1)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:54:36 AM	3724 (0x0E8C)
    Successfully read file \\?\F:\Microsoft Configuration Manager\CMUStaging\936C9D3E-5065-4C95-BAB6-7DB24F64083A\SMSSetup\update.map	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:54:36 AM	3724 (0x0E8C)
    Successfully reported ConfigMgr update status (SiteCode=MPS, SubStageID=0xd0005, IsComplete=2, Progress=100, Applicable=1)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:54:36 AM	3724 (0x0E8C)
    FQDN for server MPS-SCCM is MPS-SCCM.magnoliaschools.net	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:54:36 AM	3724 (0x0E8C)
    INFO: Target computer is a 64 bit operating system.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:54:36 AM	3724 (0x0E8C)
    INFO: Checking for existing setup information.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:54:37 AM	3724 (0x0E8C)
    INFO: Setting setup type to  1.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:54:37 AM	3724 (0x0E8C)
    INFO: Checking for existing SQL information.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:54:37 AM	3724 (0x0E8C)
    INFO: 'MPS-SCCM.magnoliaschools.net' is a valid FQDN.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:54:37 AM	3724 (0x0E8C)
    INFO: Verifying the registry entry for Asset Intelligence installation	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:54:37 AM	3724 (0x0E8C)
    INFO: Found registry key for installation of Asset Intelligence full version	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:54:37 AM	3724 (0x0E8C)
    INFO: Setup detected an existing Configuration Manager installation. Currently installed version is 8692	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:54:37 AM	3724 (0x0E8C)
    INFO: Phase is 1C7	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:54:37 AM	3724 (0x0E8C)
    INFO: SDK Provider is on MPS-SCCM.magnoliaschools.net.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:54:38 AM	3724 (0x0E8C)
    Set working directory to the staging folder F:\Microsoft Configuration Manager\CMUStaging\936C9D3E-5065-4C95-BAB6-7DB24F64083A\SMSSetup	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:54:38 AM	3724 (0x0E8C)
    INFO: Setting the default CSV folder path	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:54:38 AM	3724 (0x0E8C)
    INFO: Language: Mobile Device (INTL), LangPack: 0.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:54:38 AM	3724 (0x0E8C)
    INFO: Configuration Manager Build Number = 8790	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:54:38 AM	3724 (0x0E8C)
    INFO: Configuration Manager Version = 5.0	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:54:38 AM	3724 (0x0E8C)
    INFO: Configuration Manager Minimum Build Number = 800	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:54:38 AM	3724 (0x0E8C)
    Preparing prereq check for site server [MPS-SCCM.MAGNOLIASCHOOLS.NET]...	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:54:38 AM	3724 (0x0E8C)
    prereqcore has hash value SHA256:60B047E34F125393F6AC111652D10ECFFE2A24CDD933C8C21F3CA0C2B009145C	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:54:39 AM	3724 (0x0E8C)
    Running prereq checking against Server [MPS-SCCM.MAGNOLIASCHOOLS.NET] ...	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:54:39 AM	3724 (0x0E8C)
    INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Secure	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:55:08 AM	3724 (0x0E8C)
    Error information persisted in the database.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:55:09 AM	3724 (0x0E8C)
    Waiting for changes to the "F:\Microsoft Configuration Manager\inboxes\cmupdate.box" directories, updates will be polled in 88 seconds...	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:55:09 AM	3724 (0x0E8C)
    Detected a change to the "F:\Microsoft Configuration Manager\inboxes\cmupdate.box" directory.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:55:09 AM	3724 (0x0E8C)
    Waiting for changes to the "F:\Microsoft Configuration Manager\inboxes\cmupdate.box" directories, updates will be polled in 88 seconds...	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:55:09 AM	3724 (0x0E8C)
    Detected a change to the "F:\Microsoft Configuration Manager\inboxes\cmupdate.box" directory.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:55:09 AM	3724 (0x0E8C)
    Waiting for changes to the "F:\Microsoft Configuration Manager\inboxes\cmupdate.box" directories, updates will be polled in 88 seconds...	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:55:09 AM	3724 (0x0E8C)
    There is no pending update package to be processed.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:56:37 AM	3724 (0x0E8C)
    INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Secure	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:56:37 AM	3724 (0x0E8C)
    Waiting for changes to the "F:\Microsoft Configuration Manager\inboxes\cmupdate.box" directories, updates will be polled in 600 seconds...	CONFIGURATION_MANAGER_UPDATE	6/17/2019 8:56:38 AM	3724 (0x0E8C)
    There is no pending update package to be processed.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:06:38 AM	3724 (0x0E8C)
    INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Secure	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:06:38 AM	3724 (0x0E8C)
    Waiting for changes to the "F:\Microsoft Configuration Manager\inboxes\cmupdate.box" directories, updates will be polled in 600 seconds...	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:06:38 AM	3724 (0x0E8C)
    There is no pending update package to be processed.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:16:38 AM	3724 (0x0E8C)
    INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Secure	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:16:38 AM	3724 (0x0E8C)
    Waiting for changes to the "F:\Microsoft Configuration Manager\inboxes\cmupdate.box" directories, updates will be polled in 600 seconds...	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:16:38 AM	3724 (0x0E8C)
    There is no pending update package to be processed.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:26:39 AM	3724 (0x0E8C)
    INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Secure	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:26:39 AM	3724 (0x0E8C)
    Waiting for changes to the "F:\Microsoft Configuration Manager\inboxes\cmupdate.box" directories, updates will be polled in 600 seconds...	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:26:39 AM	3724 (0x0E8C)
    There is no pending update package to be processed.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:36:39 AM	3724 (0x0E8C)
    INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Secure	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:36:39 AM	3724 (0x0E8C)
    Waiting for changes to the "F:\Microsoft Configuration Manager\inboxes\cmupdate.box" directories, updates will be polled in 600 seconds...	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:36:39 AM	3724 (0x0E8C)
    There is no pending update package to be processed.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:46:40 AM	3724 (0x0E8C)
    INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Secure	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:46:40 AM	3724 (0x0E8C)
    Waiting for changes to the "F:\Microsoft Configuration Manager\inboxes\cmupdate.box" directories, updates will be polled in 600 seconds...	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:46:40 AM	3724 (0x0E8C)
    CONFIGURATION_MANAGER_UPDATE service is stopping...	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:55:47 AM	6288 (0x1890)
    *** [08001][-2146893051][Microsoft][SQL Server Native Client 11.0]SQL Server Network Interfaces: The requested security package does not exist	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:55:47 AM	6288 (0x1890)
    *** [08001][-2146893051][Microsoft][SQL Server Native Client 11.0]SQL Server Network Interfaces: The requested security package does not exist	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:55:47 AM	6288 (0x1890)
    *** [08001][-2146893051][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:55:47 AM	6288 (0x1890)
    *** [08001][-2146893051][Microsoft][SQL Server Native Client 11.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:55:47 AM	6288 (0x1890)
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:55:47 AM	6288 (0x1890)
    *** [08001][-2146893051][Microsoft][SQL Server Native Client 11.0]SQL Server Network Interfaces: The requested security package does not exist	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:55:47 AM	6288 (0x1890)
    *** [08001][-2146893051][Microsoft][SQL Server Native Client 11.0]SQL Server Network Interfaces: The requested security package does not exist	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:55:47 AM	6288 (0x1890)
    *** [08001][-2146893051][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:55:47 AM	6288 (0x1890)
    *** [08001][-2146893051][Microsoft][SQL Server Native Client 11.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:55:47 AM	6288 (0x1890)
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:55:47 AM	6288 (0x1890)
    Info: Currently Site MPS is initializing Site Control Data. Can't get Master SCF from database at this time. Will try later.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:55:47 AM	6288 (0x1890)
    STATMSG: ID=501 SEV=I LEV=M SOURCE="SMS Server" COMP="CONFIGURATION_MANAGER_UPDATE" SYS=MPS-SCCM.MAGNOLIASCHOOLS.NET SITE=MPS PID=1676 TID=6288 GMTDATE=Mon Jun 17 14:55:47.037 2019 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:55:47 AM	6288 (0x1890)
     RETURN CODE -2	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:55:47 AM	3724 (0x0E8C)
    CONFIGURATION_MANAGER_UPDATE service is signalled to stop...	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:55:47 AM	3724 (0x0E8C)
    STATMSG: ID=502 SEV=I LEV=M SOURCE="SMS Server" COMP="CONFIGURATION_MANAGER_UPDATE" SYS=MPS-SCCM.MAGNOLIASCHOOLS.NET SITE=MPS PID=1676 TID=3724 GMTDATE=Mon Jun 17 14:55:47.896 2019 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:55:47 AM	3724 (0x0E8C)
    *******************************************************************************	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:56:51 AM	3488 (0x0DA0)
    CONFIGURATION_MANAGER_UPDATE service is starting...	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:56:51 AM	3488 (0x0DA0)
    Microsoft System Center Configuration Manager v5.00 (Build 8692)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:56:51 AM	3488 (0x0DA0)
    Process ID: 1688	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:56:51 AM	3488 (0x0DA0)
    Worker thread ID: 3488	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:56:51 AM	3488 (0x0DA0)
    Inbox source is local on MPS-SCCM.MAGNOLIASCHOOLS.NET	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:56:51 AM	3488 (0x0DA0)
    Set inbox to F:\Microsoft Configuration Manager\inboxes\cmupdate.box	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:56:51 AM	3488 (0x0DA0)
    This running on active site server MPS-SCCM.MAGNOLIASCHOOLS.NET.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:56:51 AM	3488 (0x0DA0)
    Inbox source is local on MPS-SCCM.MAGNOLIASCHOOLS.NET	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:56:51 AM	3488 (0x0DA0)
    *** [08001][2][Microsoft][SQL Server Native Client 11.0]Named Pipes Provider: Could not open a connection to SQL Server [2].	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:58:17 AM	3488 (0x0DA0)
    *** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'MAGNOLIASCHOOLS\MPS-SCCM$'.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:58:55 AM	3488 (0x0DA0)
    *** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_MPS" requested by the login. The login failed.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:58:55 AM	3488 (0x0DA0)
    *** [08001][2][Microsoft][SQL Server Native Client 11.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:58:55 AM	3488 (0x0DA0)
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:58:56 AM	3488 (0x0DA0)
    ExecuteSqlCMUpdateInitScripts: Can't get SQL connection	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:58:57 AM	3488 (0x0DA0)
    Getting SYSCENTERID & iLicenseType	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:58:58 AM	3488 (0x0DA0)
    Initializing the status message reporting system...	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:58:58 AM	3488 (0x0DA0)
    Inbox source is local on MPS-SCCM.MAGNOLIASCHOOLS.NET	CONFIGURATION_MANAGER_UPDATE	6/17/2019 9:58:58 AM	3488 (0x0DA0)
        The path to the "Status Manager" i

    This is where the crap starts hitting the fan, and seems to be the same error over and over again:

    CONFIGURATION_MANAGER_UPDATE service is starting...	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:40:34 PM	3564 (0x0DEC)
    Microsoft System Center Configuration Manager v5.00 (Build 8790)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:40:34 PM	3564 (0x0DEC)
    Process ID: 2104	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:40:34 PM	3564 (0x0DEC)
    Worker thread ID: 3564	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:40:34 PM	3564 (0x0DEC)
    Inbox source is local on MPS-SCCM.MAGNOLIASCHOOLS.NET	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:40:34 PM	3564 (0x0DEC)
    Set inbox to F:\Microsoft Configuration Manager\inboxes\cmupdate.box	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:40:34 PM	3564 (0x0DEC)
    This running on active site server MPS-SCCM.MAGNOLIASCHOOLS.NET.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:40:34 PM	3564 (0x0DEC)
    Inbox source is local on MPS-SCCM.MAGNOLIASCHOOLS.NET	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:40:34 PM	3564 (0x0DEC)
    *** [08001][2][Microsoft][SQL Server Native Client 11.0]Named Pipes Provider: Could not open a connection to SQL Server [2].	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:41:31 PM	3564 (0x0DEC)
    *** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'MAGNOLIASCHOOLS\MPS-SCCM$'.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:42:04 PM	3564 (0x0DEC)
    *** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_MPS" requested by the login. The login failed.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:42:20 PM	3564 (0x0DEC)
    *** [08001][2][Microsoft][SQL Server Native Client 11.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:42:24 PM	3564 (0x0DEC)
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:42:24 PM	3564 (0x0DEC)
    ExecuteSqlCMUpdateInitScripts: Can't get SQL connection	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:42:24 PM	3564 (0x0DEC)
    Getting SYSCENTERID & iLicenseType	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:42:26 PM	3564 (0x0DEC)
    Initializing the status message reporting system...	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:42:26 PM	3564 (0x0DEC)
    Inbox source is local on MPS-SCCM.MAGNOLIASCHOOLS.NET	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:42:26 PM	3564 (0x0DEC)
        The path to the "Status Manager" inbox is "F:\Microsoft Configuration Manager\inboxes\statmgr.box\statmsgs".	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:42:26 PM	3564 (0x0DEC)
        SMS_STATUS_MANAGER is not running as part of this process, the SMS_EXECUTIVE to SMS_STATUS_MANAGER in-memory status message queue will not be used.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:42:26 PM	3564 (0x0DEC)
    Registered this process as a source of "SMS Server" events.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:48:56 PM	3564 (0x0DEC)
    Registered this process as a source of "SMS Client" events.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:49:03 PM	3564 (0x0DEC)
    Registered this process as a source of "SMS Provider" events.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:49:03 PM	3564 (0x0DEC)
    Status message reporting system initialized successfully.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:49:04 PM	3564 (0x0DEC)
    There is no need to start monitoring thread.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:49:18 PM	3564 (0x0DEC)
    Waiting for changes to the "F:\Microsoft Configuration Manager\inboxes\cmupdate.box" directories, updates will be polled in 600 seconds...	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:49:18 PM	3564 (0x0DEC)
    INFO: setup type: 1, top level: 1.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:59:19 PM	3564 (0x0DEC)
    Successfully reported ConfigMgr update status (SiteCode=MPS, SubStageID=0xd0007, IsComplete=1, Progress=1, Applicable=1)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:59:19 PM	3564 (0x0DEC)
    Successfully reported ConfigMgr update status (SiteCode=MPS, SubStageID=0xd0007, IsComplete=2, Progress=100, Applicable=1)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:59:20 PM	3564 (0x0DEC)
    Successfully reported ConfigMgr update status (SiteCode=MPS, SubStageID=0xd0008, IsComplete=1, Progress=1, Applicable=1)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:59:20 PM	3564 (0x0DEC)
    There is no service window defined for the site server to apply the CM server updates.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:59:20 PM	3564 (0x0DEC)
    Successfully reported ConfigMgr update status (SiteCode=MPS, SubStageID=0xd0008, IsComplete=2, Progress=100, Applicable=1)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:59:20 PM	3564 (0x0DEC)
    *** spCMUAddMonitorMessage N'MPS', 0, 3, 1	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:59:21 PM	3564 (0x0DEC)
    *** [23000][515][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot insert the value NULL into column 'LogTime', table 'CM_MPS.dbo.Logs'; column does not allow nulls. INSERT fails. : spLogEntry	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:59:21 PM	3564 (0x0DEC)
    ERROR: Failed to executive [spCMUAddMonitorMessage N'MPS', 0, 3, 1] to save site status.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:59:21 PM	3564 (0x0DEC)
    Failed to report status 30001	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:59:21 PM	3564 (0x0DEC)
    INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Secure	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:59:21 PM	3564 (0x0DEC)
    Error information persisted in the database.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:59:22 PM	3564 (0x0DEC)
    Waiting for changes to the "F:\Microsoft Configuration Manager\inboxes\cmupdate.box" directories, updates will be polled in 600 seconds...	CONFIGURATION_MANAGER_UPDATE	6/17/2019 2:59:22 PM	3564 (0x0DEC)
    INFO: setup type: 1, top level: 1.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:09:23 PM	3564 (0x0DEC)
    Successfully reported ConfigMgr update status (SiteCode=MPS, SubStageID=0xd0007, IsComplete=1, Progress=1, Applicable=1)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:09:24 PM	3564 (0x0DEC)
    Successfully reported ConfigMgr update status (SiteCode=MPS, SubStageID=0xd0007, IsComplete=2, Progress=100, Applicable=1)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:09:24 PM	3564 (0x0DEC)
    Successfully reported ConfigMgr update status (SiteCode=MPS, SubStageID=0xd0008, IsComplete=1, Progress=1, Applicable=1)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:09:25 PM	3564 (0x0DEC)
    There is no service window defined for the site server to apply the CM server updates.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:09:25 PM	3564 (0x0DEC)
    Successfully reported ConfigMgr update status (SiteCode=MPS, SubStageID=0xd0008, IsComplete=2, Progress=100, Applicable=1)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:09:25 PM	3564 (0x0DEC)
    *** spCMUAddMonitorMessage N'MPS', 0, 3, 1	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:09:25 PM	3564 (0x0DEC)
    *** [23000][515][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot insert the value NULL into column 'LogTime', table 'CM_MPS.dbo.Logs'; column does not allow nulls. INSERT fails. : spLogEntry	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:09:25 PM	3564 (0x0DEC)
    ERROR: Failed to executive [spCMUAddMonitorMessage N'MPS', 0, 3, 1] to save site status.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:09:26 PM	3564 (0x0DEC)
    Failed to report status 30001	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:09:26 PM	3564 (0x0DEC)
    INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Secure	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:09:26 PM	3564 (0x0DEC)
    Error information persisted in the database.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:09:26 PM	3564 (0x0DEC)
    Waiting for changes to the "F:\Microsoft Configuration Manager\inboxes\cmupdate.box" directories, updates will be polled in 600 seconds...	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:09:26 PM	3564 (0x0DEC)
    INFO: setup type: 1, top level: 1.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:19:27 PM	3564 (0x0DEC)
    Successfully reported ConfigMgr update status (SiteCode=MPS, SubStageID=0xd0007, IsComplete=1, Progress=1, Applicable=1)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:19:34 PM	3564 (0x0DEC)
    Successfully reported ConfigMgr update status (SiteCode=MPS, SubStageID=0xd0007, IsComplete=2, Progress=100, Applicable=1)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:19:34 PM	3564 (0x0DEC)
    Successfully reported ConfigMgr update status (SiteCode=MPS, SubStageID=0xd0008, IsComplete=1, Progress=1, Applicable=1)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:19:35 PM	3564 (0x0DEC)
    There is no service window defined for the site server to apply the CM server updates.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:20:15 PM	3564 (0x0DEC)
    Successfully reported ConfigMgr update status (SiteCode=MPS, SubStageID=0xd0008, IsComplete=2, Progress=100, Applicable=1)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:20:29 PM	3564 (0x0DEC)
    *** spCMUAddMonitorMessage N'MPS', 0, 3, 1	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:20:34 PM	3564 (0x0DEC)
    *** [23000][515][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot insert the value NULL into column 'LogTime', table 'CM_MPS.dbo.Logs'; column does not allow nulls. INSERT fails. : spLogEntry	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:20:34 PM	3564 (0x0DEC)
    ERROR: Failed to executive [spCMUAddMonitorMessage N'MPS', 0, 3, 1] to save site status.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:20:34 PM	3564 (0x0DEC)
    Failed to report status 30001	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:20:34 PM	3564 (0x0DEC)
    INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Secure	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:20:34 PM	3564 (0x0DEC)
    Error information persisted in the database.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:20:35 PM	3564 (0x0DEC)
    Waiting for changes to the "F:\Microsoft Configuration Manager\inboxes\cmupdate.box" directories, updates will be polled in 600 seconds...	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:20:35 PM	3564 (0x0DEC)
    INFO: setup type: 1, top level: 1.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:30:36 PM	3564 (0x0DEC)
    Successfully reported ConfigMgr update status (SiteCode=MPS, SubStageID=0xd0007, IsComplete=1, Progress=1, Applicable=1)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:30:42 PM	3564 (0x0DEC)
    Successfully reported ConfigMgr update status (SiteCode=MPS, SubStageID=0xd0007, IsComplete=2, Progress=100, Applicable=1)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:30:42 PM	3564 (0x0DEC)
    Successfully reported ConfigMgr update status (SiteCode=MPS, SubStageID=0xd0008, IsComplete=1, Progress=1, Applicable=1)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:30:42 PM	3564 (0x0DEC)
    There is no service window defined for the site server to apply the CM server updates.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:30:42 PM	3564 (0x0DEC)
    Successfully reported ConfigMgr update status (SiteCode=MPS, SubStageID=0xd0008, IsComplete=2, Progress=100, Applicable=1)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:30:43 PM	3564 (0x0DEC)
    *** spCMUAddMonitorMessage N'MPS', 0, 3, 1	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:30:43 PM	3564 (0x0DEC)
    *** [23000][515][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot insert the value NULL into column 'LogTime', table 'CM_MPS.dbo.Logs'; column does not allow nulls. INSERT fails. : spLogEntry	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:30:43 PM	3564 (0x0DEC)
    ERROR: Failed to executive [spCMUAddMonitorMessage N'MPS', 0, 3, 1] to save site status.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:30:43 PM	3564 (0x0DEC)
    Failed to report status 30001	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:30:43 PM	3564 (0x0DEC)
    INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Secure	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:30:43 PM	3564 (0x0DEC)
    Error information persisted in the database.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:30:44 PM	3564 (0x0DEC)
    Waiting for changes to the "F:\Microsoft Configuration Manager\inboxes\cmupdate.box" directories, updates will be polled in 600 seconds...	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:30:44 PM	3564 (0x0DEC)
    INFO: setup type: 1, top level: 1.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:40:47 PM	3564 (0x0DEC)
    Successfully reported ConfigMgr update status (SiteCode=MPS, SubStageID=0xd0007, IsComplete=1, Progress=1, Applicable=1)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:40:54 PM	3564 (0x0DEC)
    Successfully reported ConfigMgr update status (SiteCode=MPS, SubStageID=0xd0007, IsComplete=2, Progress=100, Applicable=1)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:40:56 PM	3564 (0x0DEC)
    Successfully reported ConfigMgr update status (SiteCode=MPS, SubStageID=0xd0008, IsComplete=1, Progress=1, Applicable=1)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:40:56 PM	3564 (0x0DEC)
    There is no service window defined for the site server to apply the CM server updates.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:40:59 PM	3564 (0x0DEC)
    Successfully reported ConfigMgr update status (SiteCode=MPS, SubStageID=0xd0008, IsComplete=2, Progress=100, Applicable=1)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:41:05 PM	3564 (0x0DEC)
    *** spCMUAddMonitorMessage N'MPS', 0, 3, 1	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:41:05 PM	3564 (0x0DEC)
    *** [23000][515][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot insert the value NULL into column 'LogTime', table 'CM_MPS.dbo.Logs'; column does not allow nulls. INSERT fails. : spLogEntry	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:41:05 PM	3564 (0x0DEC)
    ERROR: Failed to executive [spCMUAddMonitorMessage N'MPS', 0, 3, 1] to save site status.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:41:06 PM	3564 (0x0DEC)
    Failed to report status 30001	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:41:06 PM	3564 (0x0DEC)
    INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Secure	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:41:06 PM	3564 (0x0DEC)
    Error information persisted in the database.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:41:06 PM	3564 (0x0DEC)
    Waiting for changes to the "F:\Microsoft Configuration Manager\inboxes\cmupdate.box" directories, updates will be polled in 600 seconds...	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:41:06 PM	3564 (0x0DEC)
    INFO: setup type: 1, top level: 1.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:51:08 PM	3564 (0x0DEC)
    Successfully reported ConfigMgr update status (SiteCode=MPS, SubStageID=0xd0007, IsComplete=1, Progress=1, Applicable=1)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:51:15 PM	3564 (0x0DEC)
    Successfully reported ConfigMgr update status (SiteCode=MPS, SubStageID=0xd0007, IsComplete=2, Progress=100, Applicable=1)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:51:16 PM	3564 (0x0DEC)
    Successfully reported ConfigMgr update status (SiteCode=MPS, SubStageID=0xd0008, IsComplete=1, Progress=1, Applicable=1)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:51:16 PM	3564 (0x0DEC)
    There is no service window defined for the site server to apply the CM server updates.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:52:55 PM	3564 (0x0DEC)
    Successfully reported ConfigMgr update status (SiteCode=MPS, SubStageID=0xd0008, IsComplete=2, Progress=100, Applicable=1)	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:53:05 PM	3564 (0x0DEC)
    *** spCMUAddMonitorMessage N'MPS', 0, 3, 1	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:53:07 PM	3564 (0x0DEC)
    *** [23000][515][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot insert the value NULL into column 'LogTime', table 'CM_MPS.dbo.Logs'; column does not allow nulls. INSERT fails. : spLogEntry	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:53:07 PM	3564 (0x0DEC)
    ERROR: Failed to executive [spCMUAddMonitorMessage N'MPS', 0, 3, 1] to save site status.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:53:07 PM	3564 (0x0DEC)
    Failed to report status 30001	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:53:07 PM	3564 (0x0DEC)
    INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Secure	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:53:07 PM	3564 (0x0DEC)
    Error information persisted in the database.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:53:08 PM	3564 (0x0DEC)
    Waiting for changes to the "F:\Microsoft Configuration Manager\inboxes\cmupdate.box" directories, updates will be polled in 600 seconds...	CONFIGURATION_MANAGER_UPDATE	6/17/2019 3:53:08 PM	3564 (0x0DEC)
    INFO: setup type: 1, top level: 1.	CONFIGURATION_MANAGER_UPDATE	6/17/2019 4:03:09 PM	3564 (0x0DEC)
    Successfully reported ConfigMgr update status (SiteCode=MPS, SubStageID=0xd0007, IsComplete=1, Progress=1, Applicable=1)	CONFIGUR

    The errors that keep showing up over and over are this:

    *** [23000][515][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot insert the value NULL into column 'LogTime', table 'CM_MPS.dbo.Logs'; column does not allow nulls. INSERT fails. : spLogEntry CONFIGURATION_MANAGER_UPDATE 6/18/2019 1:16:14 AM 3564 (0x0DEC)
    ERROR: Failed to executive [spCMUAddMonitorMessage N'MPS', 0, 3, 1] to save site status. CONFIGURATION_MANAGER_UPDATE 6/18/2019 1:16:14 AM 3564 (0x0DEC)
    Failed to report status 30001 CONFIGURATION_MANAGER_UPDATE 6/18/2019 1:16:14 AM 3564 (0x0DEC)
    INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Secure CONFIGURATION_MANAGER_UPDATE 6/18/2019 1:16:15 AM 3564 (0x0DEC)
    Error information persisted in the database. CONFIGURATION_MANAGER_UPDATE 6/18/2019 1:16:15 AM 3564 (0x0DEC)

    I'm going to continue researching this, but does this stick anything in particular out to any of you?

    Thanks SO much!

    Wednesday, June 19, 2019 1:08 PM
  • So most of this was fixed and all the errors were resolved by restarting the following services:
    SMS_EXECUTIVE, SMS_SITE_COMPONENT_MANAGER, CONFIGURATION_MANAGER_UPDATE.

    A few hours later, the update/upgrade finished and it's all working ok now.  I'm having issues with distribution points but will figure it...baby steps.  :)

    Thanks so much!

    Wednesday, June 19, 2019 6:17 PM