SOLVED Cannot Update SCCM - Update seems to be stuck

[daz5505]

I have been trying to update SCCM for some time now but it seems that all updates are greyed out. I can see that the hotfix update 2303 update was downloaded it seems to have stopped once it extracted the update. Please see screenshots attached. I have previously tried the update cleanup tool but it does not seem to make a difference.

Any help will be appreciated.
Cheers

 

[Prajwal Desai]

Did you run a prerequisite check before installing the update?. I am asking that because I see an exclamation mark for prerequisite check.

Coming to the update 2303 stuck at installation, did you review the cmupdate.log on the site server to see if there are any errors?

 

[daz5505]

Did you run a prerequisite check before installing the update?. I am asking that because I see an exclamation mark for prerequisite check.

Coming to the update 2303 stuck at installation, did you review the cmupdate.log on the site server to see if there are any errors?

Thanks for the quick response and sorry for the delay.

The prerequisite check failed on:
[Failed]:Install the Microsoft ODBC driver 18 for SQL setup from https://go.microsoft.com/fwlink/?linkid=2220989. This was then installed before the update.

With regards to the 2303Hotfix, I have checked the logs but these have been overwritten as this installed has been going on for months now. despite all of our efforts we cannot cancel the install / install any of the new updates.

Cheers

 

[daz5505]

Did you run a prerequisite check before installing the update?. I am asking that because I see an exclamation mark for prerequisite check.

Coming to the update 2303 stuck at installation, did you review the cmupdate.log on the site server to see if there are any errors?

Hello Prajwal

Did you manage to see my latest reply? Our site is now out of support and despite all of my efforts, i cannot seem to resolve the issue.

Any help would be appreciated. As it is quite a large deployment i would not want to start again.

Cheers

 

[williame]

Thanks for the quick response and sorry for the delay.

The prerequisite check failed on:
[Failed]:Install the Microsoft ODBC driver 18 for SQL setup from https://go.microsoft.com/fwlink/?linkid=2220989. This was then installed before the update.

With regards to the 2303Hotfix, I have checked the logs but these have been overwritten as this installed has been going on for months now. despite all of our efforts we cannot cancel the install / install any of the new updates.

Cheers

Hi Daz,

I'm sorry to hear that your upgrade did not go as planned

Which version of the ODBC 18 driver did you install?

 

[daz5505]

Hi Daz,

I'm sorry to hear that your upgrade did not go as planned

Which version of the ODBC 18 driver did you install?

Hi Prajwal
I installed the ODBC Driver 18 for SQL server Version 18.3.3.1. since the last update i have managed to run the SCCMUpdateReset tool on the updates but this does not seem to have helped in this situation. I just cant seem to find a way to reset / stop the current installation as all options are greyed out in update and servicing.

Thank you again

Cheers

 

[daz5505]

Did you run a prerequisite check before installing the update?. I am asking that because I see an exclamation mark for prerequisite check.

Coming to the update 2303 stuck at installation, did you review the cmupdate.log on the site server to see if there are any errors?

Hi Mate.

Would you happen to have any idea on what i can do to resolve this issue?

Cheers

 

[Joh]

Hi Mate.

Would you happen to have any idea on what i can do to resolve this issue?

Cheers

Hi daz,
I had the same issue updating SCCM with the ODBC 18 driver missing.
I had to run the Update reset tool and reset the stuck update.

Update reset tool - Configuration Manager

Use the update reset tool for in-console updates for Configuration Manager.

learn.microsoft.com

With the ODBC driver installed it now worked and I could upgrade to 2403.

Greetings

 

[daz5505]

Hi Joh

Thanks for the suggestions. I have double checked and run the update cleanup tool on all updates but i get the following error on the update that i belive is "Stuck". from what i can see it the update is stuck on extract update package.

[Error]
0xSystem.Data.SqlClient.SqlException (0x80131904): Conversion failed when converting from a character string to uniqueidentifier.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlDataReader.TryHasMoreRows(Boolean& moreRows)
at System.Data.SqlClient.SqlDataReader.TryReadInternal(Boolean setTimeout, Boolean& more)
at System.Data.SqlClient.SqlDataReader.Read()
at System.Data.SqlClient.SqlCommand.CompleteExecuteScalar(SqlDataReader ds, Boolean returnSqlValue)
at System.Data.SqlClient.SqlCommand.ExecuteScalar()
at Microsoft.ConfigurationManagement.ResetTool.DatabaseProxy.GetPackageState(String packageGuid)
ClientConnectionId:95a02b7d-0ba6-48cd-8d0e-1d1837ffed48
Error Number:8169,State:2,Class:16 - Conversion failed when converting from a character string to uniqueidentifier.
Package is in pre-installation state. Attempting to clean up the package.

[Error]
0x80131509 - The connection was not closed. The connection's current state is open.


The update in Question 2303 Hotfix i believe is the issue.
.\CMUpdateReset.exe -S "Blankedforsecurity" -D CM_LD1 -P DOOBEC76-353F-485E-8FD7-4DB70020D01A


Any help would be appreciated as i am out of idea's now.

Cheers

 

[Joh]

Hi Joh

Thanks for the suggestions. I have double checked and run the update cleanup tool on all updates but i get the following error on the update that i belive is "Stuck". from what i can see it the update is stuck on extract update package.

[Error]
0xSystem.Data.SqlClient.SqlException (0x80131904): Conversion failed when converting from a character string to uniqueidentifier.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlDataReader.TryHasMoreRows(Boolean& moreRows)
at System.Data.SqlClient.SqlDataReader.TryReadInternal(Boolean setTimeout, Boolean& more)
at System.Data.SqlClient.SqlDataReader.Read()
at System.Data.SqlClient.SqlCommand.CompleteExecuteScalar(SqlDataReader ds, Boolean returnSqlValue)
at System.Data.SqlClient.SqlCommand.ExecuteScalar()
at Microsoft.ConfigurationManagement.ResetTool.DatabaseProxy.GetPackageState(String packageGuid)
ClientConnectionId:95a02b7d-0ba6-48cd-8d0e-1d1837ffed48
Error Number:8169,State:2,Class:16 - Conversion failed when converting from a character string to uniqueidentifier.
Package is in pre-installation state. Attempting to clean up the package.

[Error]
0x80131509 - The connection was not closed. The connection's current state is open.


The update in Question 2303 Hotfix i believe is the issue.
.\CMUpdateReset.exe -S "Blankedforsecurity" -D CM_LD1 -P DOOBEC76-353F-485E-8FD7-4DB70020D01A


Any help would be appreciated as i am out of idea's now.

Cheers

I was also running out of ideas, so I just made a snapshot of the server and then ran it with "-FDELETE" to force it, then I was able to click "try installation again".
I also update in two steps, first to 2309 and then to 2409, maybe that might work for you.
Greetings

 

[daz5505]

Thanks for the advice. I have tried a -FDELETE but i still seem to have the same issue where all of the options are greyed out when you right click any update that is available. Please see error below. I upgraded the version of SQL to 2022 today hoping that would resolve the issue but unfortunately not.

Running out of idea's now?

Cheers

.\CMUpdateReset.exe -FDELETE -S "blankedforsecurity: -D CM_LD1 -P DOOBEC76-353F-485E-8FD7-4DB70020D01A
[Warning]
You can use this tool when an in-console update has not yet installed and is in a failed state. A failed state can mean the update download remains in progress but is stuck and taking an excessively long time, perhaps hours longer than your historical expectations for update packages of similar size. It can also be a failure to replicate the update to child primary sites. When you run the tool, it runs against the update that you specify. If the package is in pre-installation state, it will delete it. If package is in replicating state, it will reinitiate replication. Are you sure you want to run the tool? Enter Y for Yes and N for No.
y
Running CMUpdateReset.exe tool ...
Verified that the SQL server FQDN belongs to the top level site.
Verified that the site servers run version 1606 or later.

Verified that replication is active.

[Error]
0xSystem.Data.SqlClient.SqlException (0x80131904): Conversion failed when converting from a character string to uniqueidentifier.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlDataReader.TryHasMoreRows(Boolean& moreRows)
at System.Data.SqlClient.SqlDataReader.TryReadInternal(Boolean setTimeout, Boolean& more)
at System.Data.SqlClient.SqlDataReader.Read()
at System.Data.SqlClient.SqlCommand.CompleteExecuteScalar(SqlDataReader ds, Boolean returnSqlValue)
at System.Data.SqlClient.SqlCommand.ExecuteScalar()
at Microsoft.ConfigurationManagement.ResetTool.DatabaseProxy.GetPackageState(String packageGuid)
ClientConnectionId:b6e5cd81-a963-436c-809d-8dd72e2ac130
Error Number:8169,State:2,Class:16 - Conversion failed when converting from a character string to uniqueidentifier.
Package is in pre-installation state. Attempting to clean up the package.

[Error]
0x80131509 - The connection was not closed. The connection's current state is open.

 

[Joh]

Thanks for the advice. I have tried a -FDELETE but i still seem to have the same issue where all of the options are greyed out when you right click any update that is available. Please see error below. I upgraded the version of SQL to 2022 today hoping that would resolve the issue but unfortunately not.

Running out of idea's now?

Cheers

.\CMUpdateReset.exe -FDELETE -S "blankedforsecurity: -D CM_LD1 -P DOOBEC76-353F-485E-8FD7-4DB70020D01A
[Warning]
You can use this tool when an in-console update has not yet installed and is in a failed state. A failed state can mean the update download remains in progress but is stuck and taking an excessively long time, perhaps hours longer than your historical expectations for update packages of similar size. It can also be a failure to replicate the update to child primary sites. When you run the tool, it runs against the update that you specify. If the package is in pre-installation state, it will delete it. If package is in replicating state, it will reinitiate replication. Are you sure you want to run the tool? Enter Y for Yes and N for No.
y
Running CMUpdateReset.exe tool ...
Verified that the SQL server FQDN belongs to the top level site.
Verified that the site servers run version 1606 or later.

Verified that replication is active.

[Error]
0xSystem.Data.SqlClient.SqlException (0x80131904): Conversion failed when converting from a character string to uniqueidentifier.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlDataReader.TryHasMoreRows(Boolean& moreRows)
at System.Data.SqlClient.SqlDataReader.TryReadInternal(Boolean setTimeout, Boolean& more)
at System.Data.SqlClient.SqlDataReader.Read()
at System.Data.SqlClient.SqlCommand.CompleteExecuteScalar(SqlDataReader ds, Boolean returnSqlValue)
at System.Data.SqlClient.SqlCommand.ExecuteScalar()
at Microsoft.ConfigurationManagement.ResetTool.DatabaseProxy.GetPackageState(String packageGuid)
ClientConnectionId:b6e5cd81-a963-436c-809d-8dd72e2ac130
Error Number:8169,State:2,Class:16 - Conversion failed when converting from a character string to uniqueidentifier.
Package is in pre-installation state. Attempting to clean up the package.

[Error]
0x80131509 - The connection was not closed. The connection's current state is open.

sadly I'm also running out of ideas then

did you try the resetting on all the updates? for me the Hotfixes also didn't work like that, but the direkt update did and then after running one update successfully I could update again

 

[Garth]

Thanks for the advice. I have tried a -FDELETE but i still seem to have the same issue where all of the options are greyed out when you right click any update that is available. Please see error below. I upgraded the version of SQL to 2022 today hoping that would resolve the issue but unfortunately not.

Running out of idea's now?

Cheers

.\CMUpdateReset.exe -FDELETE -S "blankedforsecurity: -D CM_LD1 -P DOOBEC76-353F-485E-8FD7-4DB70020D01A
[Warning]
You can use this tool when an in-console update has not yet installed and is in a failed state. A failed state can mean the update download remains in progress but is stuck and taking an excessively long time, perhaps hours longer than your historical expectations for update packages of similar size. It can also be a failure to replicate the update to child primary sites. When you run the tool, it runs against the update that you specify. If the package is in pre-installation state, it will delete it. If package is in replicating state, it will reinitiate replication. Are you sure you want to run the tool? Enter Y for Yes and N for No.
y
Running CMUpdateReset.exe tool ...
Verified that the SQL server FQDN belongs to the top level site.
Verified that the site servers run version 1606 or later.

Verified that replication is active.

[Error]
0xSystem.Data.SqlClient.SqlException (0x80131904): Conversion failed when converting from a character string to uniqueidentifier.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlDataReader.TryHasMoreRows(Boolean& moreRows)
at System.Data.SqlClient.SqlDataReader.TryReadInternal(Boolean setTimeout, Boolean& more)
at System.Data.SqlClient.SqlDataReader.Read()
at System.Data.SqlClient.SqlCommand.CompleteExecuteScalar(SqlDataReader ds, Boolean returnSqlValue)
at System.Data.SqlClient.SqlCommand.ExecuteScalar()
at Microsoft.ConfigurationManagement.ResetTool.DatabaseProxy.GetPackageState(String packageGuid)
ClientConnectionId:b6e5cd81-a963-436c-809d-8dd72e2ac130
Error Number:8169,State:2,Class:16 - Conversion failed when converting from a character string to uniqueidentifier.
Package is in pre-installation state. Attempting to clean up the package.

[Error]
0x80131509 - The connection was not closed. The connection's current state is open.

There is a problem with your database, you need to contact Microsoft for support.