Sql error 1355

sql error 1355

Microsoft states that this is not an error message, but a warning that SQL Server is using NTLM authentication instead of Kerberos. For more detailed. information: (SpnRegister): error 1355 message is displayed. bytes.com › topic › sql-server › answers › 530172-supersocket-info-spnreg.

Sql error 1355 - opinion you

SuperSocket info: (SpnRegister) : Error 1355.

(go**********@gmail.com) writes:

For hardware upgratdation we have to move our database server(MSSQL
2000) from a P3(Window 2003) machine to a p4(Windows 2003) machine. We
have replicated the data from P3 machine to P4 machine.

the replication was success full.

After this we have changed the name of the p4 machine to tha of p3
machine.

now when we try to connect to the new p4 machine using the windows
authentication we are not getting errror "Cannot generate SSPI
Context."
You are not getting error? Or should that "not" not be there?
for solving it we have tried to change the name of the sqlserver.
Your posting is a bit unclear, but to comlete an operation as the one
you described, you need to do

EXEC sp_dropserver P4
EXEC sp_addserver P3, 'local'

and then restart SQL Server. Once you are done, verify that @@servername
has the correct value.


--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

Aug 31 '06

sp_blitzLock execution error #1355

Do you want to request a feature or report a bug?
BUG
If you're reporting a bug, include the version number of the script you're using. If it's not the current version, upgrade to the current version and test that before reporting a bug - we fix a lot of stuff in each new build.

What is the current behavior?
The procedure throws an error when run complaining "illegal qualified name character".

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via http://sqlfiddle.com
Just executing the sp_blitzlock throws the error after running for few seconds.

What is the expected behavior?
Results without errors.

Which versions of SQL Server and which OS are affected by this issue? Did this work in previous versions of our procedures?
SQL Server 2016. I am a first time user of the FirstResponderKit and so I cannot comment on its past version behavior.

sp_blitzlock error

Error and warning in Event log -- SuperSocket info

Hey folks,

I wasn't sure where to post this but here goes...

We have 3 database servers running Win 2K Advanced with SP3 with SQL Server 2K SP3

(All recent installs -- within the last month)

2 of the database servers use a domain account at startup as the service account.

When the SP3 was applied I was logged in using my account (domain admin) instead of the service account.

We are getting an error message:

"SuperSocket info: Failed to get Exclusive port use(MSAFD Tcpip [TCP/IP]) : Error 10013."

and a warning message:

"SuperSocket info: (SpnRegister) : Error 8344."

I found a solution to the error message -- reapply SP3 while logged in as service account.

However I'm still getting the warning message.

I can't find any information anywhere about it.

I've searched here, Microsoft, Google, Technet

and can find absolutely nothing on it.

Does anyone have any ideas as to the cause/possible resolutions?

Thanks

Mark

-- Edit --

I just went back and checked the event log again -- the error was occurring before the SP3 install.

So does anyone have any suggestions still

-- End Edit --

Edited by - mark.fleming on 01/29/2003 08:52:32 AM

Read these next...

7-10-2013 15:42:23 MSSQLSERVER Fout (2) 17055 n.v.t. VIRTUALXP-22623 17120 :
SQL Server could not spawn FRunCM thread.

7-10-2013 15:42:23 MSSQLSERVER Fout (2) 17052 n.v.t. VIRTUALXP-22623 Error: 17826, Severity: 18, State: 1
Could not set up Net-Library 'SSNETLIB'.
7-10-2013 15:42:23 MSSQLSERVER Informatie (2) 17055 n.v.t. VIRTUALXP-22623 19013 :
SQL server listening on .

7-10-2013 15:42:23 MSSQLServer Waarschuwing (8) 19011 n.v.t. VIRTUALXP-22623 SuperSocket info: (SpnRegister) : Error 1355.
7-10-2013 15:42:23 MSSQLServer Fout (8) 19011 n.v.t. VIRTUALXP-22623 SuperSocket info: ConnectionListen(Shared-Memory (LPC)) : Error 5.
7-10-2013 15:42:23 MSSQLSERVER Informatie (2) 17055 n.v.t. VIRTUALXP-22623 17834 :
Using 'SSNETLIB.DLL' version '8.0.766'.

7-10-2013 15:42:22 MSSQLSERVER Informatie (2) 17055 n.v.t. VIRTUALXP-22623 17125 :
Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.

7-10-2013 15:42:22 MSSQLSERVER Informatie (2) 17055 n.v.t. VIRTUALXP-22623 17124 :
SQL Server configured for thread mode processing.

7-10-2013 15:42:22 MSSQLSERVER Informatie (2) 17055 n.v.t. VIRTUALXP-22623 17162 :
SQL Server is starting at priority class 'normal'(1 CPU detected).

7-10-2013 15:42:22 MSSQLSERVER Informatie (2) 17176 n.v.t. VIRTUALXP-22623 This instance of SQL Server last reported using a process id of 2332 at 6-10-2013 22:19:42 (local) 6-10-2013 20:19:42 (UTC).
7-10-2013 15:42:22 MSSQLSERVER Informatie (2) 17055 n.v.t. VIRTUALXP-22623 17104 :
Server Process ID is 3656.

7-10-2013 15:42:22 MSSQLSERVER Informatie (2) 17055 n.v.t. VIRTUALXP-22623 "17052 :
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 3)

"

Workstation update fails trying to join computer to domain: "Error 1355" (4329458)

This is almost always a network resolution issue between the computer to be moved and the target domain. In short, a WINS or DNS issue. To troubleshoot use the following commands:

1- NSLOOKUP of the  FQDN (fully qualified domain name) of the target domain (domain.com) <- verify the IP address returned is correct (from the computer to be moved)

2- NSLOOKUP of the target Domain Controller <- verify the IP address returned is correct (from the computer to be moved)

3- PING the NETBIOS domain name (domain) <- verify the IP address returned is correct (from the computer to be moved)

4- PING the Domain Controller name <- verify the IP address returned is correct (from the computer to be moved)

5- Try adding the computer to the domain manually or via the NETDOM command. For example: "Netdom join TestComputerName /domain:TestDomain /OU:CN=Computers,DC=Testdomain /userd:MyuserID /pd:MyPassword /reboot"

In short confirm WINS and DNS are correctly configured at the server and client level.

Join: Sql error 1355

Sql error 1355
Sql error 1355
Run time error 217 windows 7

watch the thematic video

The EASIEST Way To Find SQL Query Errors

SuperSocket info: (SpnRegister) : Error 1355.

(go**********@gmail.com) writes:

For hardware upgratdation we have to move our database server(MSSQL
2000) from a P3(Window 2003) machine to a p4(Windows 2003) machine. We
have replicated the data from P3 machine to P4 machine.

the replication was success full.

After this we have changed the name of the p4 machine to tha of p3
machine.

now when we try to connect to the new p4 machine using the windows
authentication we win7 a disk read error occurred not getting errror "Cannot generate SSPI
Context."
You are not getting error? Or should that "not" not be there?
for solving it we have tried to change the name of the sqlserver.
Your posting is a bit unclear, but to comlete an operation as the sql error 1355 you described, sql error 1355, you need to do

EXEC sp_dropserver P4
EXEC sp_addserver P3, sql error 1355, 'local'

and then restart SQL Server. Once you are done, verify that @@servername
has the correct value.


--
Erland Sommarskog, sql error 1355, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro.ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf.ons/books.mspx

Aug 31 '06

Error and warning in Event log -- SuperSocket info

Hey folks,

I wasn't sure where to post this but here goes.

We have 3 database servers running Win 2K Advanced with SP3 with SQL Server 2K Stunnel verify error depth=0 error=self signed certificate recent installs -- within the rx packets 56 errors month)

2 of the database servers use a domain account at startup as the service account.

When the SP3 was applied I was logged in using my account (domain admin) instead of the service account.

We are getting an error message:

"SuperSocket info: Failed to get Exclusive port use(MSAFD Tcpip [TCP/IP]) : Error 10013."

and a warning message:

"SuperSocket info: (SpnRegister) : Error 8344."

I 0x00000be error windows 7 a solution to the error message -- reapply SP3 while logged in as service account.

However I'm still getting the warning message.

I can't find any information anywhere about it.

I've searched here, Microsoft, Google, Technet

and can find absolutely nothing on it.

Does anyone have any ideas as to the cause/possible resolutions?

Thanks

Mark

-- Edit --

I just went back and checked the event log again -- the error was occurring before the SP3 install.

So does anyone have any suggestions still

-- End Edit --

Edited by - mark.fleming on 01/29/2003 08:52:32 AM

  • Error: 1350 SQLSTATE: HY000 (ER_VIEW_SELECT_CLAUSE)

    Message: View's SELECT contains a '%s' clause

  • Error: 1351 SQLSTATE: HY000 (ER_VIEW_SELECT_VARIABLE)

    Message: View's SELECT contains a variable or parameter

  • Error: 1352 SQLSTATE: HY000 (ER_VIEW_SELECT_TMPTABLE)

    Message: View's SELECT refers to a temporary table '%s'

  • Error: 1353 SQLSTATE: HY000 (ER_VIEW_WRONG_LIST)

    Message: View's SELECT and view's field list have different column counts

  • Error: 1354 SQLSTATE: HY000 (ER_WARN_VIEW_MERGE)

    Message: View merge algorithm can't be used here for now (assumed undefined algorithm)

  • Error: 1355 SQLSTATE: HY000 (ER_WARN_VIEW_WITHOUT_KEY)

    Message: View being updated does not have complete key of underlying table in it

  • Error: 1356 SQLSTATE: HY000 (ER_VIEW_INVALID)

    Message: View '%s.%s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them

  • Error: 1357 SQLSTATE: HY000 (ER_SP_NO_DROP_SP)

    Message: Can't drop or alter a %s from within another stored routine

  • Error: 1358 SQLSTATE: HY000 (ER_SP_GOTO_IN_HNDLR)

    Message: GOTO is not allowed in a stored procedure handler

  • sql error 1355 Error: 1359 SQLSTATE: HY000 (ER_TRG_ALREADY_EXISTS)

    Message: Trigger already exists

  • Error: 1360 Sql error 1355 HY000 (ER_TRG_DOES_NOT_EXIST)

    Message: Trigger does not exist

  • Error: 1361 SQLSTATE: HY000 (ER_TRG_ON_VIEW_OR_TEMP_TABLE)

    Message: Trigger's '%s' is view or temporary table

  • Error: 1362 SQLSTATE: HY000 (ER_TRG_CANT_CHANGE_ROW)

    Message: Updating sql error 1355 %s row is not allowed in %strigger

  • Error: 1363 SQLSTATE: HY000 (ER_TRG_NO_SUCH_ROW_IN_TRG) sharepoint 7043 error

    Message: There is no %s row in %s trigger

  • Error: 1364 SQLSTATE: HY000 (ER_NO_DEFAULT_FOR_FIELD)

    Message: Field '%s' doesn't have a default value

  • Error: 1365 SQLSTATE: 22012 (ER_DIVISION_BY_ZERO)

    sql error 1355 Message: Division by 0

  • Error: 1366 SQLSTATE: HY000 (ER_TRUNCATED_WRONG_VALUE_FOR_FIELD)

    runtime error at cannot import Message: Incorrect %s value: '%s' for column '%s' at row %ld

  • sql error 1355 Error: 1367 SQLSTATE: 22007 (ER_ILLEGAL_VALUE_FOR_TYPE)

    input command error Message: Illegal %s '%s' value found during parsing

  • Error: 1368 SQLSTATE: HY000 (ER_VIEW_NONUPD_CHECK)

    Message: CHECK OPTION on non-updatable view '%s.%s'

  • Error: 1369 SQLSTATE: HY000 (ER_VIEW_CHECK_FAILED)

    Message: CHECK OPTION failed '%s.%s'

  • Error: 1370 SQLSTATE: 42000 (ER_PROCACCESS_DENIED_ERROR)

    Message: %s command denied to user '%s'@'%s' for routine '%s'

  • Error: 1371 SQLSTATE: HY000 (ER_RELAY_LOG_FAIL)

    Message: Failed purging old relay logs: %s sql error 1355

  • Error: 1372 SQLSTATE: HY000 (ER_PASSWD_LENGTH)

    Message: Password hash should be a %d-digit hexadecimal number

  • Error: 1373 SQLSTATE: HY000 (ER_UNKNOWN_TARGET_BINLOG)

    Message: Target log not found in binlog index

  • Error: 1374 SQLSTATE: HY000 (ER_IO_ERR_LOG_INDEX_READ)

    Message: I/O error reading log index file

  • Error: 1375 SQLSTATE: HY000 (ER_BINLOG_PURGE_PROHIBITED)

    Message: Server configuration does not permit binlog purge

  • Error: 1376 SQLSTATE: HY000 (ER_FSEEK_FAIL)

    Message: Failed on fseek() sql error 1355

  • Error: 1377 SQLSTATE: HY000 (ER_BINLOG_PURGE_FATAL_ERR)

    Message: Fatal error during log purge

  • Error: 1378 SQLSTATE: HY000 (ER_LOG_IN_USE)

    Message: A purgeable log is in use, will not purge

  • Error: 1379 SQLSTATE: HY000 (ER_LOG_PURGE_UNKNOWN_ERR)

    Message: Unknown error during log purge

  • Error: 1380 SQLSTATE: HY000 (ER_RELAY_LOG_INIT)

    Message: Failed initializing relay log position: %s

  • Error: 1381 SQLSTATE: HY000 (ER_NO_BINARY_LOGGING)

    Message: You are not using binary logging

  • Error: 1382 SQLSTATE: HY000 (ER_RESERVED_SYNTAX)

    Message: The '%s' syntax is reserved for purposes internal to the MySQL server

  • Error: 1383 SQLSTATE: HY000 (ER_WSAS_FAILED)

    Message: WSAStartup Failed

  • Error: 1384 SQLSTATE: HY000 (ER_DIFF_GROUPS_PROC)

    Message: Can't handle procedures with different groups yet

  • Error: 1385 SQLSTATE: HY000 (ER_NO_GROUP_FOR_PROC)

    Message: Select must have a group with this procedure

  • Error: 1386 SQLSTATE: HY000 (ER_ORDER_WITH_PROC)

    Message: Hp lj 4515 error 41.08 use ORDER clause with this procedure

  • Error: 1387 SQLSTATE: HY000 (ER_LOGGING_PROHIBIT_CHANGING_OF)

    Message: Binary logging and replication forbid changing the global server %s

  • Error: 1388 SQLSTATE: HY000 (ER_NO_FILE_MAPPING)

    Message: Can't map file: %s, errno: %d

  • Error: 1389 SQLSTATE: HY000 (ER_WRONG_MAGIC)

    Message: Wrong magic in %s

  • Error: 1390 SQLSTATE: HY000 (ER_PS_MANY_PARAM)

    Message: Prepared statement contains too many placeholders

  • error invoking configure data adapter Error: 1391 SQLSTATE: HY000 (ER_KEY_PART_0)

    Message: Key part '%s' length cannot be 0

  • Error: 1392 SQLSTATE: HY000 (ER_VIEW_CHECKSUM)

    Message: View text checksum failed bad rtc chip error

  • Error: 1393 SQLSTATE: HY000 (ER_VIEW_MULTIUPDATE)

    Message: Can not modify more than one base table through a join view '%s.%s'

  • Error: 1394 SQLSTATE: HY000 (ER_VIEW_NO_INSERT_FIELD_LIST)

    Message: Can not insert into join view '%s.%s' without fields list

  • Error: 1395 SQLSTATE: HY000 (ER_VIEW_DELETE_MERGE_VIEW)

    Message: Can not delete from join view '%s.%s'


  • Error: 1396 SQLSTATE: HY000 (ER_CANNOT_USER) Message: Operation %s failed for %s

    How does the MySQL error sql error 1355 look like?

    ERROR 1396 (HY000): Operation CREATE USER failed for 'dummy'@'%'

    What does the MySQL error message mean?

    MySQL bit error rate tester bert a problem creating or dropping this user.

    When does this MySQL error message happen?

    Most probably the user exists already (during creation) or does not exist any more (during deletion).

    mysql> create user 'dummy'@'%' identified by 'Abcdrs!12'; Query OK, 0 rows affected (0.00 sec) mysql> -- minutes later mysql> CREATE USER 'dummy'@'%' identified by 'Abcdrs!12'; ERROR 1396 (HY000): Operation CREATE USER failed for 'dummy'@'%' mysql> DROP USER dummy; ERROR 1396 (HY000): Operation DROP USER failed for 'dummy'@'%'

    How to fix this MySQL error?

    Drop the user before creating it or omit creation. Create user before dropping it or omit dropping.


  • Error: 1397 SQLSTATE: XAE04 (ER_XAER_NOTA)

    Message: XAER_NOTA: Unknown XID

  • Error: 1398 SQLSTATE: XAE05 (ER_XAER_INVAL)

    Message: XAER_INVAL: Invalid sql error 1355 (or unsupported command)

  • Error: 1399 SQLSTATE: XAE07 (ER_XAER_RMFAIL)

    Message: XAER_RMFAIL: The command cannot be executed when global transaction is in the %s state

  • Event Log error 19011 with MSSQL$WHATSUP

    The following is from Microsoft KB article Q303411 ( http://support.microsoft.com/default.aspx?scid=kb;en-us;Q303411):

    SYMPTOMS

    When SQL Server starts on a computer that is running Microsoft SQL Server 2000/2005, the SQL Server program always attempts to register the virtual server in the Active Directory. You may see the following warning in the Microsoft Windows NT Event Log:

    Warning SuperSocket Info: (SPNRegister) : Error 1355

    Event Category 8

    Event ID 19011

    This message is not an error message. This text is only a warning that SQL Server was not able to register a Service Principal Name (SPN), which indicates that the security mechanism that will be used is Microsoft Windows NT Challenge\Response (NTLM) authentication instead of Kerberos, sql error 1355.

    CAUSE

    The message usually appears because the SQL Server service account is running as a domain user who does not have requisite permissions to register SPNs. With Microsoft Windows 2000 Service Pack 3 (SP3), you can enable Kerberos authentication on server clusters. For instructions on how to do this, see the following article in the Microsoft Knowledge Base:   319723 ( http://support.microsoft.com/kb/319723/) INF: SQL Server 2000 Kerberos Support Including SQL Server Virtual Servers on Server Clusters


    Microsoft has confirmed sql error 1355 to be a problem in SQL Server 2000 and 2005.

    Read these next.

    7-10-2013 15:42:23 MSSQLSERVER Fout (2) 17055 n.v.t. VIRTUALXP-22623 17120 :
    SQL Server could not spawn FRunCM thread.

    7-10-2013 15:42:23 MSSQLSERVER Fout (2) 17052 n.v.t, sql error 1355. VIRTUALXP-22623 Error: 17826, sql error 1355, Severity: 18, State: 1
    Could not set up Net-Library 'SSNETLIB'.
    7-10-2013 15:42:23 MSSQLSERVER Informatie (2) 17055 n.v.t. VIRTUALXP-22623 19013 :
    SQL server listening on .

    7-10-2013 15:42:23 MSSQLServer Waarschuwing (8) 19011 n.v.t. VIRTUALXP-22623 SuperSocket info: (SpnRegister) : Error 1355.
    7-10-2013 15:42:23 MSSQLServer Fout (8) 19011 n.v.t, sql error 1355. VIRTUALXP-22623 SuperSocket info: ConnectionListen(Shared-Memory (LPC)) : Error 5.
    7-10-2013 15:42:23 MSSQLSERVER Informatie (2) 17055 n.v.t. VIRTUALXP-22623 17834 :
    Using 'SSNETLIB.DLL' version '8.0.766'.

    7-10-2013 15:42:22 MSSQLSERVER Informatie (2) 17055 n.v.t, sql error 1355. VIRTUALXP-22623 17125 :
    Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.

    7-10-2013 15:42:22 MSSQLSERVER Informatie (2) 17055 n.v.t. VIRTUALXP-22623 17124 :
    SQL Server configured for thread mode processing.

    7-10-2013 15:42:22 MSSQLSERVER Informatie (2) 17055 n.v.t. VIRTUALXP-22623 17162 :
    SQL Server is starting at priority class 'normal'(1 CPU detected).

    7-10-2013 15:42:22 MSSQLSERVER Informatie (2) 17176 n.v.t, sql error 1355. VIRTUALXP-22623 This instance of SQL Server last reported using a process id of 2332 at 6-10-2013 22:19:42 (local) 6-10-2013 20:19:42 (UTC).
    7-10-2013 15:42:22 MSSQLSERVER Informatie (2) 17055 n.v.t, sql error 1355. VIRTUALXP-22623 17104 :
    Server Process ID is 3656.

    7-10-2013 15:42:22 MSSQLSERVER Informatie (2) 17055 n.v.t. VIRTUALXP-22623 "17052 :
    Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
    Dec 17 2002 14:22:05
    Copyright (c) 1988-2003 Microsoft Corporation
    Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 3)

    "

    samsung tool error card not found sp_blitzLock execution error #1355

    Do you want to request a feature or report a bug?
    BUG
    If you're reporting a bug, include the version number of the script you're using, sql error 1355. If it's not the current version, upgrade to the current version and test that before reporting a bug - we fix a lot of stuff in each new build.

    What is the current behavior?
    The procedure throws an error when run complaining "illegal qualified name character".

    If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via http://sqlfiddle.com
    Just executing the sp_blitzlock throws the error after running for few seconds.

    What is the expected behavior?
    Results without errors.

    Which versions of SQL Server and which OS are affected by this issue? Did this work in previous versions of our procedures?
    SQL Server 2016. I am a first time user of the FirstResponderKit and so I cannot comment on its past version behavior.

    sp_blitzlock error

    1 Comments

    1. I consider, that the theme is rather interesting. Give with you we will communicate in PM.

    Leave a Comment