Site Maintenance (CM12 TR) Archives - FAQShop

Why is the Delete Aged Enrolled Devices Site Maintenance Task removing Devices it shouldn’t?

Cliff Hobbs — Tue, 04 Aug 2015 18:03:58 +0000

FAQShop.com -

Why is the Delete Aged Enrolled Devices Site Maintenance Task removing Devices it shouldn’t?

I’ve noticed that for some reason the Delete Aged Enrolled Devices Site Maintenance Task is removing devices it shouldn’t.

You need a subscription to access the answer.

This content is restricted to subscribers

The post Why is the Delete Aged Enrolled Devices Site Maintenance Task removing Devices it shouldn’t? appeared first on FAQShop.

Why are my Clients reporting their “Obsolete” status incorrectly?

Cliff Hobbs — Tue, 10 Feb 2015 16:53:43 +0000

FAQShop.com -

Why are my Clients reporting their “Obsolete” status incorrectly?

I’ve noticed that my Clients are misreporting their obsolete status.

You need a subscription to access the answer.

This content is restricted to subscribers

The post Why are my Clients reporting their “Obsolete” status incorrectly? appeared first on FAQShop.

Why are my Clients “disappearing” from the Site Database?

Cliff Hobbs — Tue, 10 Feb 2015 08:06:22 +0000

FAQShop.com -

Why are my Clients “disappearing” from the Site Database?

I’ve noticed that active, healthy Clients seems to be being deleted from Site Database but I don’t understand why.

You need a subscription to access the answer.

This content is restricted to subscribers

The post Why are my Clients “disappearing” from the Site Database? appeared first on FAQShop.

“ERROR: Received unhandled SQL exception, printing info and throwing it again. This will be retried in next cycle” after Recovering a ConfigMgr 2012 SP1 Site

Cliff Hobbs — Wed, 02 Oct 2013 07:07:24 +0000

FAQShop.com -

“ERROR: Received unhandled SQL exception, printing info and throwing it again. This will be retried in next cycle” after Recovering a ConfigMgr 2012 SP1 Site

I had to recover a ConfigMgr 2012 Service Pack 1 (SP1) Site Server from a database backup that has a Cumulative Update installed.

The Site Server seems stuck in read-only mode and if I look Rcmctrl.log I see the following:

ERROR: Received unhandled SQL exception, printing info and throwing it again. This will be retried in next cycle.

ERROR: Exception message: [Procedure or function ‘spGetChangeTrackingMinValidVersion’ expects parameter ‘@PublicationMinValidVer’, which was not supplied.]

STATMSG: ID=7832 SEV=E LEV=M SOURCE=”SMS Server” COMP=”SMS_REPLICATION_CONFIGURATION_MONITOR”… ISTR0=”System.Data.SqlClient.SqlException: Procedure or function ‘spGetChangeTrackingMinValidVersion’ expects parameter ‘@PublicationMinValidVer’, which was not supplied.~~ at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakCon” …
Failed to call Configure of RCM. error = Unknown error 0x80131904

You need a subscription to access the answer.

This content is restricted to subscribers

The post “ERROR: Received unhandled SQL exception, printing info and throwing it again. This will be retried in next cycle” after Recovering a ConfigMgr 2012 SP1 Site appeared first on FAQShop.

“ERROR: Failed to execute dbo.spConfigureReplication” when trying to install a new Secondary Site or Recover an Existing one

Cliff Hobbs — Wed, 10 Jul 2013 18:08:24 +0000

FAQShop.com -

“ERROR: Failed to execute dbo.spConfigureReplication” when trying to install a new Secondary Site or Recover an Existing one

Ever since I installed Cumulative Update 2 (CU2), for ConfigMgr 2012 Service Pack 1 (SP1), whenever I try to install a new Secondary Site or recover an old Secondary Site using the Copy installation source files over the network from the parent site server Installation Source Files option it fails and I see the following errors in ConfigMgrSetup.log:

INFO: SQL Server Script: Creating object spupdatemessageactivity~
INFO: Configuring database replication tables.
*** [42000][50000][Microsoft][SQL Server Native Client 11.0][SQL Server]Object ‘PullDPResponse’ does not exist : spConfigureReplication
ERROR: Failed to execute dbo.spConfigureReplication.
ERROR: Failed to configure SQL Server replication tables.

You need a subscription to access the answer.

This content is restricted to subscribers

The post “ERROR: Failed to execute dbo.spConfigureReplication” when trying to install a new Secondary Site or Recover an Existing one appeared first on FAQShop.

“The SQL Server MYSQLSERVER..com is not accessible or its version not supported.”

Cliff Hobbs — Tue, 12 Feb 2013 18:53:19 +0000

FAQShop.com -

“The SQL Server MYSQLSERVER..com is not accessible or its version not supported.”

I am trying to restore a backup of the Site Database to a server running SQL 2014.

However, the ConfigMgr Setup Wizard is failing with the following error which I’m also seeing in the ConfigMgr Setup log:

The SQL Server MYSQLSERVER..com is not accessible or its version not supported.”

You need a subscription to access the answer.

This content is restricted to subscribers

The post “The SQL Server MYSQLSERVER..com is not accessible or its version not supported.” appeared first on FAQShop.

Why is my Site stuck in “Maintenance Mode” despite the Recovery completing successfully?

Cliff Hobbs — Mon, 09 Jul 2012 17:54:58 +0000

FAQShop.com -

Why is my Site stuck in “Maintenance Mode” despite the Recovery completing successfully?

I am trying to recover a ConfigMgr 2012 Site that is using remote instance of SQL.

The Recovery process has completed successfully but for some reason the Site is stuck in Maintenance Mode.

You need a subscription to access the answer.

This content is restricted to subscribers

The post Why is my Site stuck in “Maintenance Mode” despite the Recovery completing successfully? appeared first on FAQShop.