Known SMTP bug in .NET 2.0?

Hi All,

A while back I posted a message referring to an inability to send e-mail from SQL 2005 Database mail; the error being "Command not supported" - which appeared to be coming back from the Exchange Server.

Looking on the SQL Sentry forums (SQL Sentry having its own alerting function) they report the same errro testing their smtp code, with the post

This is the result of a known bug in .NET 2.0. when working with a server that does not support ESMTP. Microsoft will provide a fix in their next release.

Can anyone from MS confirm that this is a bug, and tell me how to either work round it, or enable ESMTP on the Exchange server?

Regards,

Richard

Just to close out this thread, should anyone be reading it in the future:

It appears that the exchange server is set up using non-standard ports to receive on, and also McAfee security is running to block data on all but the narrowly specified ports. Our exchange people kindly ommitted to tell us this, but the upshot is that nothing can send mail out through the Exchange server. The error message is a bit confusing, but the root cause is security, not SQL or the client.

Regards,

Rich

Known SMTP bug in .NET 2.0?

Hi All,

A while back I posted a message referring to an inability to send e-mail from SQL 2005 Database mail; the error being "Command not supported" - which appeared to be coming back from the Exchange Server.

Looking on the SQL Sentry forums (SQL Sentry having its own alerting function) they report the same errro testing their smtp code, with the post

This is the result of a known bug in .NET 2.0. when working with a server that does not support ESMTP. Microsoft will provide a fix in their next release.

Can anyone from MS confirm that this is a bug, and tell me how to either work round it, or enable ESMTP on the Exchange server?

Regards,

Richard

Just to close out this thread, should anyone be reading it in the future:

It appears that the exchange server is set up using non-standard ports to receive on, and also McAfee security is running to block data on all but the narrowly specified ports. Our exchange people kindly ommitted to tell us this, but the upshot is that nothing can send mail out through the Exchange server. The error message is a bit confusing, but the root cause is security, not SQL or the client.

Regards,

Rich

sql

Killing bug in ASP.Net 2, Report server is dead, 100% guaranteed

Hi,

I posted a message to the install forum a few days ago and no answers were made so far. This bug is 100% reproducible and kills Report Server.

I am cross-posting here with the hope that someone in Microsoft will take note and eventually give a solution.

If you go to the IIS6 ReportServer VD and click on the ASP.net 2 config button, You Kill Report Server.

Complete details are in this post

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=250225&SiteID=1

Thanks,

Philippe

Hi,

We have found the solution to this issue.

Just remove this

xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0"

From the WEB.config file in both ReportServer and ReportManager folders

Philippe

Killing a process does not help table that can't be read

I have a table that is locked by a process, but when I try to kill it using
Query Analyzer, I get the following message:
"SPID 136: transaction rollback in progress. Estimated rollback completion:
0%. Estimated time remaining: 0 seconds."
It has been saying this for a long time now and I need to get this table
functioning because it's my main customer table. Any help is appreciated.
I had a similar problem yesterday with a view yesterday, and I couldn't get
it cleared out until I restarted the server. It doesn't make sense to me
that I would have to restart an entire server to unlock this one table, does
it?
Jeremiah
Hi
It looks like people have contacted PSS regarding this in the past!
http://tinyurl.com/5opp6
You may want to check your version number and see if there are any more
up-to-date patches that fix it.
John
"Jeremiah Traxler" wrote:

> I have a table that is locked by a process, but when I try to kill it using
> Query Analyzer, I get the following message:
> "SPID 136: transaction rollback in progress. Estimated rollback completion:
> 0%. Estimated time remaining: 0 seconds."
> It has been saying this for a long time now and I need to get this table
> functioning because it's my main customer table. Any help is appreciated.
> I had a similar problem yesterday with a view yesterday, and I couldn't get
> it cleared out until I restarted the server. It doesn't make sense to me
> that I would have to restart an entire server to unlock this one table, does
> it?
> Jeremiah
sql

Killing a process does not help table that can't be read

I have a table that is locked by a process, but when I try to kill it using
Query Analyzer, I get the following message:
"SPID 136: transaction rollback in progress. Estimated rollback completion:
0%. Estimated time remaining: 0 seconds."
It has been saying this for a long time now and I need to get this table
functioning because it's my main customer table. Any help is appreciated.
I had a similar problem yesterday with a view yesterday, and I couldn't get
it cleared out until I restarted the server. It doesn't make sense to me
that I would have to restart an entire server to unlock this one table, does
it?
JeremiahHi
It looks like people have contacted PSS regarding this in the past!
http://tinyurl.com/5opp6
You may want to check your version number and see if there are any more
up-to-date patches that fix it.
John
"Jeremiah Traxler" wrote:

> I have a table that is locked by a process, but when I try to kill it usin
g
> Query Analyzer, I get the following message:
> "SPID 136: transaction rollback in progress. Estimated rollback completion
:
> 0%. Estimated time remaining: 0 seconds."
> It has been saying this for a long time now and I need to get this table
> functioning because it's my main customer table. Any help is appreciated.
> I had a similar problem yesterday with a view yesterday, and I couldn't ge
t
> it cleared out until I restarted the server. It doesn't make sense to me
> that I would have to restart an entire server to unlock this one table, do
es
> it?
> Jeremiah

Killing a process does not help table that can't be read

I have a table that is locked by a process, but when I try to kill it using
Query Analyzer, I get the following message:
"SPID 136: transaction rollback in progress. Estimated rollback completion:
0%. Estimated time remaining: 0 seconds."
It has been saying this for a long time now and I need to get this table
functioning because it's my main customer table. Any help is appreciated.
I had a similar problem yesterday with a view yesterday, and I couldn't get
it cleared out until I restarted the server. It doesn't make sense to me
that I would have to restart an entire server to unlock this one table, does
it?
JeremiahHi
It looks like people have contacted PSS regarding this in the past!
http://tinyurl.com/5opp6
You may want to check your version number and see if there are any more
up-to-date patches that fix it.
John
"Jeremiah Traxler" wrote:
> I have a table that is locked by a process, but when I try to kill it using
> Query Analyzer, I get the following message:
> "SPID 136: transaction rollback in progress. Estimated rollback completion:
> 0%. Estimated time remaining: 0 seconds."
> It has been saying this for a long time now and I need to get this table
> functioning because it's my main customer table. Any help is appreciated.
> I had a similar problem yesterday with a view yesterday, and I couldn't get
> it cleared out until I restarted the server. It doesn't make sense to me
> that I would have to restart an entire server to unlock this one table, does
> it?
> Jeremiah

kill a large spid

hi,
from profiler, i've a spid that has a value of 1994834. the kill command
won't work... The error message is:
Msg 6101, Level 16, State 1, Line 1
Process ID 1994834is not a valid process ID. Choose a number between 1 and
1024.
here is the sql info for the box...
Microsoft SQL Server 2005 - 9.00.3161.00 (X64) Apr 3 2007 11:14:20
Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on
Windows NT 5.2 (Build 3790: Service Pack 2)Why are you using profiler to view the SPID? What does sp_who2 show as a
SPID for that process?
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"light_wt" <lightwt@.discussions.microsoft.com> wrote in message
news:C5420913-B755-44B3-8885-172D02FC2FD1@.microsoft.com...
> hi,
> from profiler, i've a spid that has a value of 1994834. the kill command
> won't work... The error message is:
> Msg 6101, Level 16, State 1, Line 1
> Process ID 1994834is not a valid process ID. Choose a number between 1 and
> 1024.
> here is the sql info for the box...
> Microsoft SQL Server 2005 - 9.00.3161.00 (X64) Apr 3 2007 11:14:20
> Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit)
> on
> Windows NT 5.2 (Build 3790: Service Pack 2)|||You could also use the Activity Monitor.
--
Ekrem Ã?nsoy
"light_wt" <lightwt@.discussions.microsoft.com> wrote in message
news:C5420913-B755-44B3-8885-172D02FC2FD1@.microsoft.com...
> hi,
> from profiler, i've a spid that has a value of 1994834. the kill command
> won't work... The error message is:
> Msg 6101, Level 16, State 1, Line 1
> Process ID 1994834is not a valid process ID. Choose a number between 1 and
> 1024.
> here is the sql info for the box...
> Microsoft SQL Server 2005 - 9.00.3161.00 (X64) Apr 3 2007 11:14:20
> Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit)
> on
> Windows NT 5.2 (Build 3790: Service Pack 2)|||i was using profiler to see other things and bump into that spid.
that process is cleared, now. profiler showed me it had duration over
2000000 and using 5 cpu. after clearning that process, it released the
memory pressure of the box; released 20% of the memory.
how else would be a better way to find run away process (like extra long
duration) and find the assoicated spid on an 05 box? sp_who2 doesn't have
"duration".
thanks.|||Profiler will only show duration after the statement or sp is completed. So
in the case of long running code that you may want to kill it does not help
very much. You might want to take a look at sys.dm_exec_requests and some of
the associated dmvs.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"light_wt" <lightwt@.discussions.microsoft.com> wrote in message
news:B21F4598-393E-43B5-950D-3E2AA1CC32AA@.microsoft.com...
>i was using profiler to see other things and bump into that spid.
> that process is cleared, now. profiler showed me it had duration over
> 2000000 and using 5 cpu. after clearning that process, it released the
> memory pressure of the box; released 20% of the memory.
> how else would be a better way to find run away process (like extra long
> duration) and find the assoicated spid on an 05 box? sp_who2 doesn't have
> "duration".
> thanks.

Key Relationship

This is the message that i get when trying to assign keys when creating diagrams in visual express:

'tbh_Polls' table saved successfully
'tbh_PollOptions' table
- Unable to create relationship 'FK_tbh_PollOptions_tbh_Polls'.
The ALTER TABLE statement conflicted with the FOREIGN KEY constraint "FK_tbh_PollOptions_tbh_Polls". The conflict occurred in database "C:\USERS\STICKER\DOCUMENTS\MY WEB SITES\PERCSHARP\APP_DATA\ASPNETDB.MDF", table "dbo.tbh_Polls", column 'PollID'.

PollID is my primary key in tbh_Polls

And PollID is in tbh_PollOptions table

No matter what I do, I get this message, I'm Lost!

Help plz.

Thanks

hi,

It seems to me the underlying tables are already populated, and there's a row (at least) in the referencing table (tbh_PollOptions) not satisfying the relationship you like to enforce..

you could define the foreign key constraint WITH NOCHECK, meaning the already inserted rows will not be validated at constraint creation, so that the exception will not raise.. but you stay with invalid relationship in the underlying table to the referenced table.. this option, WITH NOCHECK, should be used when you already know the relationship is already satified and you do not have "bad data"..

regards

|||

So in order for me to create the relationship is to get rid of the data i have in these 2 tables and then create the fk?

That's not a proble because i only populated them with a sample data and not a real thing. I'll try that first and see if it will work.

Thanks a lot.

|||

IT WORKED

YEAAAAHHHHHH!

Thanks a milion!

You know, i only started with programing 2 months ago and i'm already hooked, especially when there are people who happen to know what's causing the bugs. Untill i learn more i'll have to ask often. so thanks!

|||

hi,

Kliker wrote:

So in order for me to create the relationship is to get rid of the data i have in these 2 tables and then create the fk?

no, you have to get rid of "bad data", that's to say the row(s) where the referencing column does/do not match the referenced table values... or fix it/them..

That's not a proble because i only populated them with a sample data and not a real thing. I'll try that first and see if it will work.

Thanks a lot.

you're welcome..

regards

Key not valid for use in specified state?

Hi!
I just ran into the same old problem that I got a few months back.
Reporting Server stops working and logs the message "Key not valid for use
in specified state".
I did never manage to solve the problem when it occured before but at that
time it happened on a development server, this time it is worse as it is
on one of our production servers.
I know that there was several people suffering from the same problem after
applying .Net Framework 1.1 SP1.
Did anyone find a solution?
Best regards,
Per SalmiHello Per,
Based on my research, I recommend you perform the following steps to
resolve the issue:
Step 1: Deleting the files which represent Microsoft SQL Server Reporting
Services Key Container
===============================================================
Search for files with the pattern "1aedd7b5699f3d6a88e354100b596aae_*".
These files represent the Microsoft SQL Server Reporting Services Key
Container.
Backup these files first. Then delete the original files.
You may find the file in the folder "\documents and settings\<machine
name>\aspnet\application data\microsoft\crypto\rsa\<user
sid>\1aedd7b5699f3d6a88e354100b596aae_*".
Try to start Reporting Server.
If you receive "The report server cannot decrypt the symmetric key used to
access sensitive or encrypted data in a report server database. You must
either restore a backup key or delete all encrypted content and then
restart the service. Check the documentation", please continue with the
following steps:
Step 2: Back up Reportserver and ReportserverTempDB databases
===========================================
Step 3: Reapplying the symmetric keys
==================================
1. Run Rskeymgmt -e to extract the keys
2. Run Rskeymgmt -d to delete the keys
3. Run rskeymgmt -a to reapply the keys and restart the windows service.
4. Run Rsactivate -c to activate the service
For detailed information about the RsKeyMgmt utility, please access the
following web site:
http://www.msdn.microsoft.com/library/default.asp?url=/library/en-us/rsuiref
/htm/cpu_rsconfig_v1_29ly.asp
I hope above information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.

Key column information is insufficient or incorrect. Too many rows were affected by u

I have edit sql server 2000 table record by vb or direct enterprise mangafer and i have recived one message "Key column information is insufficient or incorrect. Too many rows were affected by update." any guys know this problem pl send the solution

Manish jain

ThanksThe Name Of Allah
hi

In the following table, for example, the error message appears if you attempt to delete one or both of the rows containing "abc" by using SQL Enterprise Manager with the following steps:
1. Right-click on the table.
2. Click on Open table, and then click on Return All Rows.
3. Highlight the rows, and then press the Delete button.

Character_Column1 Character_Column2
abc abc
abc abc
zxy zxy
fgt art

Eng. Maged

kerberos logon failure

I recently started receiveing an error message on a Win2K server that has SQ
L 2000 on it. Yesterday. users began having read-only access to a database
that clearly states they have read/write access. At around the same time th
at this occured, I noticed
in the security log that the Kerberos account experienced logon failure with
Event ID 537. This error code just states unable to logon for unknown reas
on. Any help/suggestions is greatly appreciated.
DaveNot sure I understand the question - what do you mean by read-only access?
If you look at sp_protects or something similar in the database are the
user's permissions changed?
Richard Waymire, MCSE, MCDBA
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dave" <anonymous@.discussions.microsoft.com> wrote in message
news:6AAC7FF7-98A2-4E3A-872A-C84594EF887D@.microsoft.com...

quote:

---

> I recently started receiveing an error message on a Win2K server that has

---

SQL 2000 on it. Yesterday. users began having read-only access to a
database that clearly states they have read/write access. At around the
same time that this occured, I noticed in the security log that the Kerberos
account experienced logon failure with Event ID 537. This error code just
states unable to logon for unknown reason. Any help/suggestions is greatly
appreciated.

quote:

---

> Dave

---

|||The kerberos error could be caused by duplicate Netbios names. This could
be due to parent child/domains.
This would happen if the machine with same netbios name exists in the
parent
domain. So when a user in parent domain gets authenticated, he accesses the
machine
account listed in AD users and computers for the machine account in parent
domain.
However the child domain user will access the machine in child domain.
Also, when
using the IP or FQDN, the duplicate netbios names are not causing problems
and
hence would work.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

KDC - 11

I have a Windows Server 2000 (SP4) with SQL Server 2000 (2 instances). My
server is domain controller also.
I frequently receiving next message in the Event Log:
Source: KDC
ID: 11
There are multiple accounts with name MSSQLSvc/comp.dom.ru:1433 of type 10.
I'm finding the 321044 article of the Microsoft Knowledge Base.
I'm using the LDP utility and type next filter:
servicePrincipalName=MSSQLSvc/comp.dom.ru:1433
I received next reply:
***Searching...
ldap_search_s(ld, "DC=dom,DC=ru", 2,
"servicePrincipalName=MSSQLSvc/comp.dom.ru:1433", attrList, 0, &msg)
Result <0>: (null)
Matched DNs:
Getting 2 entries:[vbcol=seagreen]
1> canonicalName: dom.ru/Domain Controllers/comp;
1> cn: comp;
1> distinguishedName: CN=comp,OU=Domain Controllers,DC=dom,DC=ru;
5> objectClass: top; person; organizationalPerson; user; computer;
1> name: comp;[vbcol=seagreen]
1> canonicalName: <ldp: Binary blob>;
1> cn: <ldp: Binary blob>;
1> description: <ldp: Binary blob>;
1> distinguishedName: <ldp: Binary blob>;
4> objectClass: top; person; organizationalPerson; user;
1> name: <ldp: Binary blob>;
And what? Must I delete comp account? But comp is domain controller.
What can I do?
Michael S. Androsov
That's one of the reason why it's better not to install SQL on a domain
server.
In mine opinion the trouble comes from LDAP but I'rm not a specialist.
Try a post on the forum concerned.
P.RUELLO
DBA
"Michael S. Androsov" wrote:

> I have a Windows Server 2000 (SP4) with SQL Server 2000 (2 instances). My
> server is domain controller also.
> I frequently receiving next message in the Event Log:
> Source: KDC
> ID: 11
> There are multiple accounts with name MSSQLSvc/comp.dom.ru:1433 of type 10.
> I'm finding the 321044 article of the Microsoft Knowledge Base.
> I'm using the LDP utility and type next filter:
> servicePrincipalName=MSSQLSvc/comp.dom.ru:1433
> I received next reply:
> ***Searching...
> ldap_search_s(ld, "DC=dom,DC=ru", 2,
> "servicePrincipalName=MSSQLSvc/comp.dom.ru:1433", attrList, 0, &msg)
> Result <0>: (null)
> Matched DNs:
> Getting 2 entries:
> 1> canonicalName: dom.ru/Domain Controllers/comp;
> 1> cn: comp;
> 1> distinguishedName: CN=comp,OU=Domain Controllers,DC=dom,DC=ru;
> 5> objectClass: top; person; organizationalPerson; user; computer;
> 1> name: comp;
> 1> canonicalName: <ldp: Binary blob>;
> 1> cn: <ldp: Binary blob>;
> 1> description: <ldp: Binary blob>;
> 1> distinguishedName: <ldp: Binary blob>;
> 4> objectClass: top; person; organizationalPerson; user;
> 1> name: <ldp: Binary blob>;
> And what? Must I delete comp account? But comp is domain controller.
> What can I do?
> Michael S. Androsov
>
|||What is the forum?
Michael S. Androsov
"P.Ruello" пишет:
[vbcol=seagreen]
> That's one of the reason why it's better not to install SQL on a domain
> server.
> In mine opinion the trouble comes from LDAP but I'rm not a specialist.
> Try a post on the forum concerned.
> --
> P.RUELLO
> DBA
>
> "Michael S. Androsov" wrote:

KDC - 11

I have a Windows Server 2000 (SP4) with SQL Server 2000 (2 instances). My
server is domain controller also.
I frequently receiving next message in the Event Log of the Windows Server
2000 & 2003 computers:
Source: KDC
ID: 11
There are multiple accounts with name MSSQLSvc/comp.dom.ru:1118 of type 10.
I'm finding the 321044 article of the Microsoft Knowledge Base.
I'm using the LDP utility and type next filter:
servicePrincipalName=MSSQLSvc/comp.dom.ru:1433
I received next reply:
***Searching...
ldap_search_s(ld, "DC=dom,DC=ru", 2,
"servicePrincipalName=MSSQLSvc/comp.dom.ru:1118", attrList, 0, &msg)
Result <0>: (null)
Matched DNs:
Getting 2 entries:[vbcol=seagreen]
1> canonicalName: dom.ru/Domain Controllers/comp;
1> cn: comp;
1> distinguishedName: CN=comp,OU=Domain Controllers,DC=dom,DC=ru;
5> objectClass: top; person; organizationalPerson; user; computer;
1> name: comp;[vbcol=seagreen]
1> canonicalName: <ldp: Binary blob>;
1> cn: <ldp: Binary blob>;
1> description: <ldp: Binary blob>;
1> distinguishedName: <ldp: Binary blob>;
4> objectClass: top; person; organizationalPerson; user;
1> name: <ldp: Binary blob>;
And what? Must I delete comp account? But comp is domain controller.
What can I do?
Michael S. Androsov
Hi
Check out the part in the KB that talks about using ADIEdit. You need to
change the incorrect SPN.
John
"Michael S. Androsov" wrote:

> I have a Windows Server 2000 (SP4) with SQL Server 2000 (2 instances). My
> server is domain controller also.
> I frequently receiving next message in the Event Log of the Windows Server
> 2000 & 2003 computers:
> Source: KDC
> ID: 11
> There are multiple accounts with name MSSQLSvc/comp.dom.ru:1118 of type 10.
> I'm finding the 321044 article of the Microsoft Knowledge Base.
> I'm using the LDP utility and type next filter:
> servicePrincipalName=MSSQLSvc/comp.dom.ru:1433
> I received next reply:
> ***Searching...
> ldap_search_s(ld, "DC=dom,DC=ru", 2,
> "servicePrincipalName=MSSQLSvc/comp.dom.ru:1118", attrList, 0, &msg)
> Result <0>: (null)
> Matched DNs:
> Getting 2 entries:
> 1> canonicalName: dom.ru/Domain Controllers/comp;
> 1> cn: comp;
> 1> distinguishedName: CN=comp,OU=Domain Controllers,DC=dom,DC=ru;
> 5> objectClass: top; person; organizationalPerson; user; computer;
> 1> name: comp;
> 1> canonicalName: <ldp: Binary blob>;
> 1> cn: <ldp: Binary blob>;
> 1> description: <ldp: Binary blob>;
> 1> distinguishedName: <ldp: Binary blob>;
> 4> objectClass: top; person; organizationalPerson; user;
> 1> name: <ldp: Binary blob>;
> And what? Must I delete comp account? But comp is domain controller.
> What can I do?
> Michael S. Androsov
>
|||Hi! Thank you very much for answer.
Excuse me. I'm not master in to the ADSIEdit and AD tools.
Can you help me? What I must doing after ADSIEDit loaded? What I search and
what is the part? I see the partition: Domain NC; Configuration Container and
Schema.
I don't know where I must seeking dublicate SPN.
Thanks,
Michael S. Androsov
"John Bell" пишет:
[vbcol=seagreen]
> Hi
> Check out the part in the KB that talks about using ADIEdit. You need to
> change the incorrect SPN.
> John
> "Michael S. Androsov" wrote:
|||Hi
Your duplicate spn is probably MSSQLSvc/comp.dom.ru. I am not an AD expert
but the following tells you how to search using ADSI Edit
http://support.microsoft.com/default...b;en-us;312299
You may want to post in
http://www.microsoft.com/technet/com...tive_directory
or
http://www.microsoft.com/technet/com...ve_di rectory
John
"Michael S. Androsov" wrote:
[vbcol=seagreen]
> Hi! Thank you very much for answer.
> Excuse me. I'm not master in to the ADSIEdit and AD tools.
> Can you help me? What I must doing after ADSIEDit loaded? What I search and
> what is the part? I see the partition: Domain NC; Configuration Container and
> Schema.
> I don't know where I must seeking dublicate SPN.
> Thanks,
> Michael S. Androsov
> "John Bell" пишет:

KDC - 11

I have a Windows Server 2000 (SP4) with SQL Server 2000 (2 instances). My
server is domain controller also.
I frequently receiving next message in the Event Log:
Source: KDC
ID: 11
There are multiple accounts with name MSSQLSvc/comp.dom.ru:1433 of type 10.
I'm finding the 321044 article of the Microsoft Knowledge Base.
I'm using the LDP utility and type next filter:
servicePrincipalName=MSSQLSvc/comp.dom.ru:1433
I received next reply:
***Searching...
ldap_search_s(ld, "DC=dom,DC=ru", 2,
"servicePrincipalName=MSSQLSvc/comp.dom.ru:1433", attrList, 0, &msg)
Result <0>: (null)
Matched DNs:
Getting 2 entries:
>> Dn: CN=comp,OU=Domain Controllers,DC=dom,DC=ru
1> canonicalName: dom.ru/Domain Controllers/comp;
1> cn: comp;
1> distinguishedName: CN=comp,OU=Domain Controllers,DC=dom,DC=ru;
5> objectClass: top; person; organizationalPerson; user; computer;
1> name: comp;
>> Dn: CN=Administrator,CN=Users,DC=dom,DC=ru
1> canonicalName: <ldp: Binary blob>;
1> cn: <ldp: Binary blob>;
1> description: <ldp: Binary blob>;
1> distinguishedName: <ldp: Binary blob>;
4> objectClass: top; person; organizationalPerson; user;
1> name: <ldp: Binary blob>;
And what? Must I delete comp account? But comp is domain controller.
What can I do?
Michael S. AndrosovThat's one of the reason why it's better not to install SQL on a domain
server.
In mine opinion the trouble comes from LDAP but I'rm not a specialist.
Try a post on the forum concerned.
--
P.RUELLO
DBA
"Michael S. Androsov" wrote:
> I have a Windows Server 2000 (SP4) with SQL Server 2000 (2 instances). My
> server is domain controller also.
> I frequently receiving next message in the Event Log:
> Source: KDC
> ID: 11
> There are multiple accounts with name MSSQLSvc/comp.dom.ru:1433 of type 10.
> I'm finding the 321044 article of the Microsoft Knowledge Base.
> I'm using the LDP utility and type next filter:
> servicePrincipalName=MSSQLSvc/comp.dom.ru:1433
> I received next reply:
> ***Searching...
> ldap_search_s(ld, "DC=dom,DC=ru", 2,
> "servicePrincipalName=MSSQLSvc/comp.dom.ru:1433", attrList, 0, &msg)
> Result <0>: (null)
> Matched DNs:
> Getting 2 entries:
> >> Dn: CN=comp,OU=Domain Controllers,DC=dom,DC=ru
> 1> canonicalName: dom.ru/Domain Controllers/comp;
> 1> cn: comp;
> 1> distinguishedName: CN=comp,OU=Domain Controllers,DC=dom,DC=ru;
> 5> objectClass: top; person; organizationalPerson; user; computer;
> 1> name: comp;
> >> Dn: CN=Administrator,CN=Users,DC=dom,DC=ru
> 1> canonicalName: <ldp: Binary blob>;
> 1> cn: <ldp: Binary blob>;
> 1> description: <ldp: Binary blob>;
> 1> distinguishedName: <ldp: Binary blob>;
> 4> objectClass: top; person; organizationalPerson; user;
> 1> name: <ldp: Binary blob>;
> And what? Must I delete comp account? But comp is domain controller.
> What can I do?
> Michael S. Androsov
>|||What is the forum?
Michael S. Androsov
"P.Ruello" пиÑ?еÑ?:
> That's one of the reason why it's better not to install SQL on a domain
> server.
> In mine opinion the trouble comes from LDAP but I'rm not a specialist.
> Try a post on the forum concerned.
> --
> P.RUELLO
> DBA
>
> "Michael S. Androsov" wrote:
> > I have a Windows Server 2000 (SP4) with SQL Server 2000 (2 instances). My
> > server is domain controller also.
> > I frequently receiving next message in the Event Log:
> > Source: KDC
> > ID: 11
> > There are multiple accounts with name MSSQLSvc/comp.dom.ru:1433 of type 10.
> >
> > I'm finding the 321044 article of the Microsoft Knowledge Base.
> > I'm using the LDP utility and type next filter:
> > servicePrincipalName=MSSQLSvc/comp.dom.ru:1433
> > I received next reply:
> > ***Searching...
> > ldap_search_s(ld, "DC=dom,DC=ru", 2,
> > "servicePrincipalName=MSSQLSvc/comp.dom.ru:1433", attrList, 0, &msg)
> > Result <0>: (null)
> > Matched DNs:
> > Getting 2 entries:
> > >> Dn: CN=comp,OU=Domain Controllers,DC=dom,DC=ru
> > 1> canonicalName: dom.ru/Domain Controllers/comp;
> > 1> cn: comp;
> > 1> distinguishedName: CN=comp,OU=Domain Controllers,DC=dom,DC=ru;
> > 5> objectClass: top; person; organizationalPerson; user; computer;
> > 1> name: comp;
> > >> Dn: CN=Administrator,CN=Users,DC=dom,DC=ru
> > 1> canonicalName: <ldp: Binary blob>;
> > 1> cn: <ldp: Binary blob>;
> > 1> description: <ldp: Binary blob>;
> > 1> distinguishedName: <ldp: Binary blob>;
> > 4> objectClass: top; person; organizationalPerson; user;
> > 1> name: <ldp: Binary blob>;
> >
> > And what? Must I delete comp account? But comp is domain controller.
> >
> > What can I do?
> >
> > Michael S. Androsov
> >

KDC - 11

I have a Windows Server 2000 (SP4) with SQL Server 2000 (2 instances). My
server is domain controller also.
I frequently receiving next message in the Event Log of the Windows Server
2000 & 2003 computers:
Source: KDC
ID: 11
There are multiple accounts with name MSSQLSvc/comp.dom.ru:1118 of type 10.
I'm finding the 321044 article of the Microsoft Knowledge Base.
I'm using the LDP utility and type next filter:
servicePrincipalName=MSSQLSvc/comp.dom.ru:1433
I received next reply:
***Searching...
ldap_search_s(ld, "DC=dom,DC=ru", 2,
"servicePrincipalName=MSSQLSvc/comp.dom.ru:1118", attrList, 0, &msg)
Result <0>: (null)
Matched DNs:
Getting 2 entries:
>> Dn: CN=comp,OU=Domain Controllers,DC=dom,DC=ru
1> canonicalName: dom.ru/Domain Controllers/comp;
1> cn: comp;
1> distinguishedName: CN=comp,OU=Domain Controllers,DC=dom,DC=ru;
5> objectClass: top; person; organizationalPerson; user; computer;
1> name: comp;
>> Dn: CN=Administrator,CN=Users,DC=dom,DC=ru
1> canonicalName: <ldp: Binary blob>;
1> cn: <ldp: Binary blob>;
1> description: <ldp: Binary blob>;
1> distinguishedName: <ldp: Binary blob>;
4> objectClass: top; person; organizationalPerson; user;
1> name: <ldp: Binary blob>;
And what? Must I delete comp account? But comp is domain controller.
What can I do?
Michael S. AndrosovHi
Check out the part in the KB that talks about using ADIEdit. You need to
change the incorrect SPN.
John
"Michael S. Androsov" wrote:
> I have a Windows Server 2000 (SP4) with SQL Server 2000 (2 instances). My
> server is domain controller also.
> I frequently receiving next message in the Event Log of the Windows Server
> 2000 & 2003 computers:
> Source: KDC
> ID: 11
> There are multiple accounts with name MSSQLSvc/comp.dom.ru:1118 of type 10.
> I'm finding the 321044 article of the Microsoft Knowledge Base.
> I'm using the LDP utility and type next filter:
> servicePrincipalName=MSSQLSvc/comp.dom.ru:1433
> I received next reply:
> ***Searching...
> ldap_search_s(ld, "DC=dom,DC=ru", 2,
> "servicePrincipalName=MSSQLSvc/comp.dom.ru:1118", attrList, 0, &msg)
> Result <0>: (null)
> Matched DNs:
> Getting 2 entries:
> >> Dn: CN=comp,OU=Domain Controllers,DC=dom,DC=ru
> 1> canonicalName: dom.ru/Domain Controllers/comp;
> 1> cn: comp;
> 1> distinguishedName: CN=comp,OU=Domain Controllers,DC=dom,DC=ru;
> 5> objectClass: top; person; organizationalPerson; user; computer;
> 1> name: comp;
> >> Dn: CN=Administrator,CN=Users,DC=dom,DC=ru
> 1> canonicalName: <ldp: Binary blob>;
> 1> cn: <ldp: Binary blob>;
> 1> description: <ldp: Binary blob>;
> 1> distinguishedName: <ldp: Binary blob>;
> 4> objectClass: top; person; organizationalPerson; user;
> 1> name: <ldp: Binary blob>;
> And what? Must I delete comp account? But comp is domain controller.
> What can I do?
> Michael S. Androsov
>|||Hi! Thank you very much for answer.
Excuse me. I'm not master in to the ADSIEdit and AD tools.
Can you help me? What I must doing after ADSIEDit loaded? What I search and
what is the part? I see the partition: Domain NC; Configuration Container and
Schema.
I don't know where I must seeking dublicate SPN.
Thanks,
Michael S. Androsov
"John Bell" пиÑ?еÑ?:
> Hi
> Check out the part in the KB that talks about using ADIEdit. You need to
> change the incorrect SPN.
> John
> "Michael S. Androsov" wrote:
> > I have a Windows Server 2000 (SP4) with SQL Server 2000 (2 instances). My
> > server is domain controller also.
> > I frequently receiving next message in the Event Log of the Windows Server
> > 2000 & 2003 computers:
> > Source: KDC
> > ID: 11
> > There are multiple accounts with name MSSQLSvc/comp.dom.ru:1118 of type 10.
> >
> > I'm finding the 321044 article of the Microsoft Knowledge Base.
> > I'm using the LDP utility and type next filter:
> > servicePrincipalName=MSSQLSvc/comp.dom.ru:1433
> > I received next reply:
> > ***Searching...
> > ldap_search_s(ld, "DC=dom,DC=ru", 2,
> > "servicePrincipalName=MSSQLSvc/comp.dom.ru:1118", attrList, 0, &msg)
> > Result <0>: (null)
> > Matched DNs:
> > Getting 2 entries:
> > >> Dn: CN=comp,OU=Domain Controllers,DC=dom,DC=ru
> > 1> canonicalName: dom.ru/Domain Controllers/comp;
> > 1> cn: comp;
> > 1> distinguishedName: CN=comp,OU=Domain Controllers,DC=dom,DC=ru;
> > 5> objectClass: top; person; organizationalPerson; user; computer;
> > 1> name: comp;
> > >> Dn: CN=Administrator,CN=Users,DC=dom,DC=ru
> > 1> canonicalName: <ldp: Binary blob>;
> > 1> cn: <ldp: Binary blob>;
> > 1> description: <ldp: Binary blob>;
> > 1> distinguishedName: <ldp: Binary blob>;
> > 4> objectClass: top; person; organizationalPerson; user;
> > 1> name: <ldp: Binary blob>;
> >
> > And what? Must I delete comp account? But comp is domain controller.
> >
> > What can I do?
> >
> > Michael S. Androsov
> >
> >|||Hi
Your duplicate spn is probably MSSQLSvc/comp.dom.ru. I am not an AD expert
but the following tells you how to search using ADSI Edit
http://support.microsoft.com/default.aspx?scid=kb;en-us;312299
You may want to post in
http://www.microsoft.com/technet/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.windows.server.active_directory
or
http://www.microsoft.com/technet/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.win2000.active_directory
John
"Michael S. Androsov" wrote:
> Hi! Thank you very much for answer.
> Excuse me. I'm not master in to the ADSIEdit and AD tools.
> Can you help me? What I must doing after ADSIEDit loaded? What I search and
> what is the part? I see the partition: Domain NC; Configuration Container and
> Schema.
> I don't know where I must seeking dublicate SPN.
> Thanks,
> Michael S. Androsov
> "John Bell" пиÑ?еÑ?:
> > Hi
> >
> > Check out the part in the KB that talks about using ADIEdit. You need to
> > change the incorrect SPN.
> >
> > John
> >
> > "Michael S. Androsov" wrote:
> >
> > > I have a Windows Server 2000 (SP4) with SQL Server 2000 (2 instances). My
> > > server is domain controller also.
> > > I frequently receiving next message in the Event Log of the Windows Server
> > > 2000 & 2003 computers:
> > > Source: KDC
> > > ID: 11
> > > There are multiple accounts with name MSSQLSvc/comp.dom.ru:1118 of type 10.
> > >
> > > I'm finding the 321044 article of the Microsoft Knowledge Base.
> > > I'm using the LDP utility and type next filter:
> > > servicePrincipalName=MSSQLSvc/comp.dom.ru:1433
> > > I received next reply:
> > > ***Searching...
> > > ldap_search_s(ld, "DC=dom,DC=ru", 2,
> > > "servicePrincipalName=MSSQLSvc/comp.dom.ru:1118", attrList, 0, &msg)
> > > Result <0>: (null)
> > > Matched DNs:
> > > Getting 2 entries:
> > > >> Dn: CN=comp,OU=Domain Controllers,DC=dom,DC=ru
> > > 1> canonicalName: dom.ru/Domain Controllers/comp;
> > > 1> cn: comp;
> > > 1> distinguishedName: CN=comp,OU=Domain Controllers,DC=dom,DC=ru;
> > > 5> objectClass: top; person; organizationalPerson; user; computer;
> > > 1> name: comp;
> > > >> Dn: CN=Administrator,CN=Users,DC=dom,DC=ru
> > > 1> canonicalName: <ldp: Binary blob>;
> > > 1> cn: <ldp: Binary blob>;
> > > 1> description: <ldp: Binary blob>;
> > > 1> distinguishedName: <ldp: Binary blob>;
> > > 4> objectClass: top; person; organizationalPerson; user;
> > > 1> name: <ldp: Binary blob>;
> > >
> > > And what? Must I delete comp account? But comp is domain controller.
> > >
> > > What can I do?
> > >
> > > Michael S. Androsov
> > >
> > >

KDC - 11

I have a Windows Server 2000 (SP4) with SQL Server 2000 (2 instances). My
server is domain controller also.
I frequently receiving next message in the Event Log of the Windows Server
2000 & 2003 computers:
Source: KDC
ID: 11
There are multiple accounts with name MSSQLSvc/comp.dom.ru:1118 of type 10.
I'm finding the 321044 article of the Microsoft Knowledge Base.
I'm using the LDP utility and type next filter:
servicePrincipalName=MSSQLSvc/comp.dom.ru:1433
I received next reply:
***Searching...
ldap_search_s(ld, "DC=dom,DC=ru", 2,
"servicePrincipalName=MSSQLSvc/comp.dom.ru:1118", attrList, 0, &msg)
Result <0>: (null)
Matched DNs:
Getting 2 entries:[vbcol=seagreen]
1> canonicalName: dom.ru/Domain Controllers/comp;
1> cn: comp;
1> distinguishedName: CN=comp,OU=Domain Controllers,DC=dom,DC=ru;
5> objectClass: top; person; organizationalPerson; user; computer;
1> name: comp;[vbcol=seagreen]
1> canonicalName: <ldp: Binary blob>;
1> cn: <ldp: Binary blob>;
1> description: <ldp: Binary blob>;
1> distinguishedName: <ldp: Binary blob>;
4> objectClass: top; person; organizationalPerson; user;
1> name: <ldp: Binary blob>;
And what? Must I delete comp account? But comp is domain controller.
What can I do?
Michael S. AndrosovHi
Check out the part in the KB that talks about using ADIEdit. You need to
change the incorrect SPN.
John
"Michael S. Androsov" wrote:

> I have a Windows Server 2000 (SP4) with SQL Server 2000 (2 instances). My
> server is domain controller also.
> I frequently receiving next message in the Event Log of the Windows Server
> 2000 & 2003 computers:
> Source: KDC
> ID: 11
> There are multiple accounts with name MSSQLSvc/comp.dom.ru:1118 of type 10
.
> I'm finding the 321044 article of the Microsoft Knowledge Base.
> I'm using the LDP utility and type next filter:
> servicePrincipalName=MSSQLSvc/comp.dom.ru:1433
> I received next reply:
> ***Searching...
> ldap_search_s(ld, "DC=dom,DC=ru", 2,
> "servicePrincipalName=MSSQLSvc/comp.dom.ru:1118", attrList, 0, &msg)
> Result <0>: (null)
> Matched DNs:
> Getting 2 entries:
> 1> canonicalName: dom.ru/Domain Controllers/comp;
> 1> cn: comp;
> 1> distinguishedName: CN=comp,OU=Domain Controllers,DC=dom,DC=ru;
> 5> objectClass: top; person; organizationalPerson; user; computer;
> 1> name: comp;
> 1> canonicalName: <ldp: Binary blob>;
> 1> cn: <ldp: Binary blob>;
> 1> description: <ldp: Binary blob>;
> 1> distinguishedName: <ldp: Binary blob>;
> 4> objectClass: top; person; organizationalPerson; user;
> 1> name: <ldp: Binary blob>;
> And what? Must I delete comp account? But comp is domain controller.
> What can I do?
> Michael S. Androsov
>|||Hi! Thank you very much for answer.
Excuse me. I'm not master in to the ADSIEdit and AD tools.
Can you help me? What I must doing after ADSIEDit loaded? What I search and
what is the part? I see the partition: Domain NC; Configuration Container an
d
Schema.
I don't know where I must seeking dublicate SPN.
Thanks,
Michael S. Androsov
"John Bell" пишет:
[vbcol=seagreen]
> Hi
> Check out the part in the KB that talks about using ADIEdit. You need to
> change the incorrect SPN.
> John
> "Michael S. Androsov" wrote:
>|||Hi
Your duplicate spn is probably MSSQLSvc/comp.dom.ru. I am not an AD expert
but the following tells you how to search using ADSI Edit
http://support.microsoft.com/defaul...kb;en-us;312299
You may want to post in
http://www.microsoft.com/technet/co...ctive_directory
or
http://www.microsoft.com/technet/co...ctive_directory
John
"Michael S. Androsov" wrote:
[vbcol=seagreen]
> Hi! Thank you very much for answer.
> Excuse me. I'm not master in to the ADSIEdit and AD tools.
> Can you help me? What I must doing after ADSIEDit loaded? What I search an
d
> what is the part? I see the partition: Domain NC; Configuration Container
and
> Schema.
> I don't know where I must seeking dublicate SPN.
> Thanks,
> Michael S. Androsov
> "John Bell" пишет:
>

KDC - 11

I have a Windows Server 2000 (SP4) with SQL Server 2000 (2 instances). My
server is domain controller also.
I frequently receiving next message in the Event Log:
Source: KDC
ID: 11
There are multiple accounts with name MSSQLSvc/comp.dom.ru:1433 of type 10.
I'm finding the 321044 article of the Microsoft Knowledge Base.
I'm using the LDP utility and type next filter:
servicePrincipalName=MSSQLSvc/comp.dom.ru:1433
I received next reply:
***Searching...
ldap_search_s(ld, "DC=dom,DC=ru", 2,
"servicePrincipalName=MSSQLSvc/comp.dom.ru:1433", attrList, 0, &msg)
Result <0>: (null)
Matched DNs:
Getting 2 entries:[vbcol=seagreen]
1> canonicalName: dom.ru/Domain Controllers/comp;
1> cn: comp;
1> distinguishedName: CN=comp,OU=Domain Controllers,DC=dom,DC=ru;
5> objectClass: top; person; organizationalPerson; user; computer;
1> name: comp;[vbcol=seagreen]
1> canonicalName: <ldp: Binary blob>;
1> cn: <ldp: Binary blob>;
1> description: <ldp: Binary blob>;
1> distinguishedName: <ldp: Binary blob>;
4> objectClass: top; person; organizationalPerson; user;
1> name: <ldp: Binary blob>;
And what? Must I delete comp account? But comp is domain controller.
What can I do?
Michael S. AndrosovThat's one of the reason why it's better not to install SQL on a domain
server.
In mine opinion the trouble comes from LDAP but I'rm not a specialist.
Try a post on the forum concerned.
P.RUELLO
DBA
"Michael S. Androsov" wrote:

> I have a Windows Server 2000 (SP4) with SQL Server 2000 (2 instances). My
> server is domain controller also.
> I frequently receiving next message in the Event Log:
> Source: KDC
> ID: 11
> There are multiple accounts with name MSSQLSvc/comp.dom.ru:1433 of type 10
.
> I'm finding the 321044 article of the Microsoft Knowledge Base.
> I'm using the LDP utility and type next filter:
> servicePrincipalName=MSSQLSvc/comp.dom.ru:1433
> I received next reply:
> ***Searching...
> ldap_search_s(ld, "DC=dom,DC=ru", 2,
> "servicePrincipalName=MSSQLSvc/comp.dom.ru:1433", attrList, 0, &msg)
> Result <0>: (null)
> Matched DNs:
> Getting 2 entries:
> 1> canonicalName: dom.ru/Domain Controllers/comp;
> 1> cn: comp;
> 1> distinguishedName: CN=comp,OU=Domain Controllers,DC=dom,DC=ru;
> 5> objectClass: top; person; organizationalPerson; user; computer;
> 1> name: comp;
> 1> canonicalName: <ldp: Binary blob>;
> 1> cn: <ldp: Binary blob>;
> 1> description: <ldp: Binary blob>;
> 1> distinguishedName: <ldp: Binary blob>;
> 4> objectClass: top; person; organizationalPerson; user;
> 1> name: <ldp: Binary blob>;
> And what? Must I delete comp account? But comp is domain controller.
> What can I do?
> Michael S. Androsov
>|||What is the forum?
Michael S. Androsov
"P.Ruello" пишет:
[vbcol=seagreen]
> That's one of the reason why it's better not to install SQL on a domain
> server.
> In mine opinion the trouble comes from LDAP but I'rm not a specialist.
> Try a post on the forum concerned.
> --
> P.RUELLO
> DBA
>
> "Michael S. Androsov" wrote:
>