SQL Server 2017 Error 1222 State : 55

Question

Hi ,

i got this error after adding a database for VAMT - Volume Activation Management Tool
by running this commands :

sqlcmd -S [server name]\MSSQLSERVER
1> USE [VAMT]
2> GO
1> alter table base.GenuineStatusText alter column GenuineStatusText nvarchar(255) NULL
2> GO

Any ideas

Answer 1

Hi everbody ,

i've uninstall VAMT also delete the database from the sql server , afte checking SMSPro.log , this is what i got , :

-------------------------------------------------------------------------
~
$$<SMS Provider><04-03-2022 11:06:24.207-180><thread=10288 (0x2830)>
~ $$<SMS Provider><04-03-2022 11:06:24.208-180><thread=10288 (0x2830)>
CExtUserContext::EnterThread : User=GUEST Sid= Caching IWbemContextPtr=0000020B41F12350 in Process 0x26e0 (9952)~ $$<SMS Provider><04-03-2022 11:06:24.210-180><thread=10288 (0x2830)>
Context: SMSAppName=Configuration Manager Administrator console~ $$<SMS Provider><04-03-2022 11:06:24.211-180><thread=10288 (0x2830)>
Context: MachineName=s2022.dab.local~ $$<SMS Provider><04-03-2022 11:06:24.212-180><thread=10288 (0x2830)>
Context: UserName=DAB\admin~ $$<SMS Provider><04-03-2022 11:06:24.213-180><thread=10288 (0x2830)>
Context: ObjectLockContext=49c21b30-f74a-416c-824c-1f7c79be9eea~ $$<SMS Provider><04-03-2022 11:06:24.213-180><thread=10288 (0x2830)>
Context: ApplicationName=Microsoft.ConfigurationManagement.exe~ $$<SMS Provider><04-03-2022 11:06:24.214-180><thread=10288 (0x2830)>
Context: ApplicationVersion=5.2111.1056.1000~ $$<SMS Provider><04-03-2022 11:06:24.215-180><thread=10288 (0x2830)>
Context: LocaleID=MS\0x409~ $$<SMS Provider><04-03-2022 11:06:24.215-180><thread=10288 (0x2830)>
Context: __ProviderArchitecture=32 ~ $$<SMS Provider><04-03-2022 11:06:24.216-180><thread=10288 (0x2830)>
Context: __RequiredArchitecture=0 (Bool)~ $$<SMS Provider><04-03-2022 11:06:24.217-180><thread=10288 (0x2830)>
Context: __ClientPreferredLanguages=en-US,en~ $$<SMS Provider><04-03-2022 11:06:24.218-180><thread=10288 (0x2830)>
Context: __CorrelationId={00000000-0000-0000-0000-000000000000}~ $$<SMS Provider><04-03-2022 11:06:24.219-180><thread=10288 (0x2830)>
Context: __GroupOperationId=3725 ~ $$<SMS Provider><04-03-2022 11:06:24.219-180><thread=10288 (0x2830)>
CExtUserContext : Set ThreadLocaleID OK to: 1033~ $$<SMS Provider><04-03-2022 11:06:24.220-180><thread=10288 (0x2830)>
Looking for ExtensionProvider instances...~ $$<SMS Provider><04-03-2022 11:06:24.220-180><thread=10288 (0x2830)>
Loading IClassManager: {3B1F3900-A186-11d0-BDA9-00A0C909FDD7}~ $$<SMS Provider><04-03-2022 11:06:24.220-180><thread=10288 (0x2830)>
**** CSspClassManager CONSTRUCTOR~ $$<SMS Provider><04-03-2022 11:06:24.220-180><thread=10288 (0x2830)>
CSspClassManager::Initialize 0~ $$<SMS Provider><04-03-2022 11:06:24.220-180><thread=10288 (0x2830)>
Correctly got registry root dir~ $$<SMS Provider><04-03-2022 11:06:24.220-180><thread=10288 (0x2830)>
Log level = 1~ $$<SMS Provider><04-03-2022 11:06:24.220-180><thread=10288 (0x2830)>
Log path = C:\Program Files\Microsoft Configuration Manager\Logs~ $$<SMS Provider><04-03-2022 11:06:24.220-180><thread=10288 (0x2830)>
SiteInstallRootDir = C:\Program Files\Microsoft Configuration Manager~ $$<SMS Provider><04-03-2022 11:06:24.220-180><thread=10288 (0x2830)>
Minimal Notification Polling Interval = 30 (seconds) ~ $$<SMS Provider><04-03-2022 11:06:24.220-180><thread=10288 (0x2830)>
UseLegacyCardinality=769649360~ $$<SMS Provider><04-03-2022 11:06:24.220-180><thread=10288 (0x2830)>
CSspClassManager::Initialize, Reading SQL db info from registry for sitecode PR1...~ $$<SMS Provider><04-03-2022 11:06:24.220-180><thread=10288 (0x2830)>
Set SQL Machine s2022.dab.local from registry~ $$<SMS Provider><04-03-2022 11:06:24.236-180><thread=10288 (0x2830)>
[HY000][-2146893048][Microsoft][SQL Server Native Client 11.0]SQL Server Network Interfaces: The token supplied to the function is invalid~~ $$<SMS Provider><04-03-2022 11:06:24.252-180><thread=10288 (0x2830)> [HY000][-2146893048][Microsoft][SQL Server Native Client 11.0]Cannot generate SSPI context $$<SMS Provider><04-03-2022 11:06:24.252-180><thread=10288 (0x2830)>
[HY000][-2146893048][Microsoft][SQL Server Native Client 11.0]SQL Server Network Interfaces: The token supplied to the function is invalid~~ $$<SMS Provider><04-03-2022 11:06:24.252-180><thread=10288 (0x2830)> [HY000][-2146893048][Microsoft][SQL Server Native Client 11.0]Cannot generate SSPI context $$<SMS Provider><04-03-2022 11:06:24.252-180><thread=10288 (0x2830)>
Failed to connect to the SQL Server, connection type: SMS ACCESS. $$<SMS Provider><04-03-2022 11:06:24.252-180><thread=10288 (0x2830)>
Failed to get sql connection $$<SMS Provider><04-03-2022 11:06:24.252-180><thread=10288 (0x2830)>
~ ~~X:\bt\1216594\repo\src\SiteServer\SDK_Provider\SMSProv\sspclassmanager.cpp(689) : Failed to get active site server information.~~~ $$<SMS Provider><04-03-2022 11:06:24.252-180><thread=10288 (0x2830)>
~~~Failed to get active site server information. ~~*~ $$<SMS Provider><04-03-2022 11:06:24.252-180><thread=10288 (0x2830)>
Found IClassManger: Opal SMS CSsp Provider Extension Implementation.~ $$<SMS Provider><04-03-2022 11:06:24.252-180><thread=10288 (0x2830)>
CExtUserContext::LeaveThread : Releasing IWbemContextPtr=1106322256~ $$<SMS Provider><04-03-2022 11:06:24.252-180><thread=10288 (0x2830)>
SMSPROV DllMain - DLL_PROCESS_DETACH...calling AfxTermExtensionModule~ $$<SMS Provider><04-03-2022 11:07:16.458-180><thread=8204 (0x200C)>
EXTNPROV DllMain DLL_PROCESS_DETACH~ $$<SMS Provider><04-03-2022 11:07:16.458-180><thread=8204 (0x200C)>

any ideas ? ...

Answer 2

It is still not clear what your issue is. However, this line in the errorlog caught my attention:

022-03-29 12:06:13.01 spid9s The resource database build version is 14.00.1000.

You seem to be running the RTM version of SQL Server. You should apply the most recent Cumulative Update for SQL 2017, which is CU29.

Whether this will resolve issue you are seeing I don't know, but you should absolutely not run with that old build of SQL 2017.

Answer 3

Hi ,
Appreciate your replying
Must mention that the error show up after i add the " VAMT " database

SQL LOG :

2022-03-29 12:06:12.99 spid27s Starting up database 'CM_PR1'.
2022-03-29 12:06:12.99 spid28s Starting up database 'VAMT'.
2022-03-29 12:06:12.99 spid9s Starting up database 'mssqlsystemresource'.
2022-03-29 12:06:13.01 spid9s The resource database build version is 14.00.1000. This is an informational message only. No user action is required.
2022-03-29 12:06:13.16 spid28s Parallel redo is started for database 'VAMT' with worker pool size [8].
2022-03-29 12:06:13.19 spid9s Starting up database 'model'.
2022-03-29 12:06:13.22 spid25s Parallel redo is started for database 'ReportServer' with worker pool size [8].
2022-03-29 12:06:13.35 spid24s Parallel redo is started for database 'SUSDB' with worker pool size [8].
2022-03-29 12:06:13.39 spid26s Parallel redo is started for database 'ReportServerTempDB' with worker pool size [8].
2022-03-29 12:06:13.52 spid5s Parallel redo is shutdown for database 'VAMT' with worker pool size [8].
2022-03-29 12:06:13.60 spid9s Polybase feature disabled.
2022-03-29 12:06:13.60 spid9s Clearing tempdb database.
2022-03-29 12:06:13.63 spid5s Parallel redo is shutdown for database 'ReportServer' with worker pool size [8].
2022-03-29 12:06:13.74 spid5s Parallel redo is shutdown for database 'SUSDB' with worker pool size [8].
2022-03-29 12:06:13.85 spid5s Parallel redo is shutdown for database 'ReportServerTempDB' with worker pool size [8].
2022-03-29 12:06:14.02 spid27s Parallel redo is started for database 'CM_PR1' with worker pool size [8].
2022-03-29 12:06:14.29 spid5s Parallel redo is shutdown for database 'CM_PR1' with worker pool size [8].
2022-03-29 12:06:14.42 spid9s Starting up database 'tempdb'.
2022-03-29 12:06:16.19 spid9s The tempdb database has 8 data file(s).
2022-03-29 12:06:16.20 spid19s Server is listening on [ 'any' <ipv6> 4022].
2022-03-29 12:06:16.20 spid19s Server is listening on [ 'any' <ipv4> 4022].
2022-03-29 12:06:16.20 spid19s The Service Broker endpoint is now listening for connections.
2022-03-29 12:06:16.20 spid19s The Database Mirroring endpoint is in disabled or stopped state.
2022-03-29 12:06:16.21 spid19s Service Broker manager has started.
2022-03-29 12:06:16.72 spid5s Recovery is complete. This is an informational message only. No user action is required.
2022-03-29 12:06:16.90 spid49s An error occurred in Service Broker internal activation while trying to scan the user queue 'CM_PR1.dbo.ConfigMgrDRSMsgBuilderQueue' for its status. Error: 1222, State: 55. Lock request time out period exceeded. This is an informational message only. No user action is required.
2022-03-29 12:06:16.90 spid53s An error occurred in Service Broker internal activation while trying to scan the user queue 'CM_PR1.dbo.AlertVariableChangeInitiatorQueue' for its status. Error: 1222, State: 55. Lock request time out period exceeded. This is an informational message only. No user action is required.
2022-03-29 12:06:16.92 spid53s An error occurred in Service Broker internal activation while trying to scan the user queue 'CM_PR1.dbo.ConfigMgrHMSQueue' for its status. Error: 1222, State: 55. Lock request time out period exceeded. This is an informational message only. No user action is required.
2022-03-29 12:06:16.92 spid55s An error occurred in Service Broker internal activation while trying to scan the user queue 'CM_PR1.dbo.ConfigMgrMDMComplianceQueue' for its status. Error: 1222, State: 55. Lock request time out period exceeded. This is an informational message only. No user action is required.
2022-03-29 12:06:17.01 spid53s An error occurred in Service Broker internal activation while trying to scan the user queue 'CM_PR1.dbo.ConfigMgrGSQueue' for its status. Error: 1222, State: 55. Lock request time out period exceeded. This is an informational message only. No user action is required.
2022-03-29 12:06:17.02 spid55s An error occurred in Service Broker internal activation while trying to scan the user queue 'CM_PR1.dbo.AlertVariableChangeTargetQueue' for its status. Error: 1222, State: 55. Lock request time out period exceeded. This is an informational message only. No user action is required.
2022-03-29 12:08:15.69 spid69 Using 'dbghelp.dll' version '4.0.5'
2022-03-29 12:08:38.30 spid69 Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
2022-03-29 12:08:38.36 spid69 Using 'xplog70.dll' version '2017.140.1000' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
2022-03-29 12:39:40.99 spid58 Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required.
2022-03-29 12:39:41.01 spid58 Using 'xpsqlbot.dll' version '2017.140.1000' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
2022-03-29 12:39:42.00 spid61 Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2022-03-29 12:39:42.10 spid61 Using 'xpstar.dll' version '2017.140.1000' to execute extended stored procedure 'xp_regread'. This is an informational message only; no user action is required.
2022-03-30 00:00:03.82 spid24s This instance of SQL Server has been using a process ID of 8152 since 29/03/2022 12:06:07 (local) 29/03/2022 09:06:07 (UTC). This is an informational message only; no user action is required.

Answer 4

That error is from the error log and has nothing to do with the command you ran.

The error is from Service Broker during server startup. It may be nothing. You must have it configured for something. You should check to see if it is working correctly.