I recall several instances where I killed a DBREINDEX after 20 minutes of
execution and it seemed to cancel surprisingly fast (I was expecting a
massive rollback)
We now have a situation where a DBREINDEX has been running over 12 hours.
If I were to kill this - could it be assumed that it would just become
available immediately or is there a chance of a BIG rollback (which could
possibly take another 12 hours)?
Thanks in advanceIt depends when you cancel it and what you've asked it to do.
If you have a dbreindex of a single very large index, and cancel it while
its still building the new index, it should cancel pretty fast as all it
does is deallocate all the new pages. If you cancel it while it's deleting
the old index, then it has to rollback all the deletes again.
If you have a dbreindex that's rebuilding 10 indexes, and you cancel it
after its done 5 of them, it will have to rollback the deletes of the 5 old
indexes, which will take time proportional to their size.
Several things to consider: why are you rebuilding and have you considered
using DBCC INDEXDEFRAG instead?
Checkout the whitepaper below for more info:
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx
Thanks
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"TJT" <TJT@.nospam.com> wrote in message
news:%23Hi2ZwjuFHA.1256@.TK2MSFTNGP09.phx.gbl...
>I recall several instances where I killed a DBREINDEX after 20 minutes of
> execution and it seemed to cancel surprisingly fast (I was expecting a
> massive rollback)
> We now have a situation where a DBREINDEX has been running over 12 hours.
> If I were to kill this - could it be assumed that it would just become
> available immediately or is there a chance of a BIG rollback (which could
> possibly take another 12 hours)?
> Thanks in advance
>
Showing posts with label instances. Show all posts
Showing posts with label instances. Show all posts
Monday, March 26, 2012
Killing a DBCC DBREINDEX - will this cause a massive rollback
I recall several instances where I killed a DBREINDEX after 20 minutes of
execution and it seemed to cancel surprisingly fast (I was expecting a
massive rollback)
We now have a situation where a DBREINDEX has been running over 12 hours.
If I were to kill this - could it be assumed that it would just become
available immediately or is there a chance of a BIG rollback (which could
possibly take another 12 hours)?
Thanks in advance
It depends when you cancel it and what you've asked it to do.
If you have a dbreindex of a single very large index, and cancel it while
its still building the new index, it should cancel pretty fast as all it
does is deallocate all the new pages. If you cancel it while it's deleting
the old index, then it has to rollback all the deletes again.
If you have a dbreindex that's rebuilding 10 indexes, and you cancel it
after its done 5 of them, it will have to rollback the deletes of the 5 old
indexes, which will take time proportional to their size.
Several things to consider: why are you rebuilding and have you considered
using DBCC INDEXDEFRAG instead?
Checkout the whitepaper below for more info:
http://www.microsoft.com/technet/pro.../ss2kidbp.mspx
Thanks
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"TJT" <TJT@.nospam.com> wrote in message
news:%23Hi2ZwjuFHA.1256@.TK2MSFTNGP09.phx.gbl...
>I recall several instances where I killed a DBREINDEX after 20 minutes of
> execution and it seemed to cancel surprisingly fast (I was expecting a
> massive rollback)
> We now have a situation where a DBREINDEX has been running over 12 hours.
> If I were to kill this - could it be assumed that it would just become
> available immediately or is there a chance of a BIG rollback (which could
> possibly take another 12 hours)?
> Thanks in advance
>
execution and it seemed to cancel surprisingly fast (I was expecting a
massive rollback)
We now have a situation where a DBREINDEX has been running over 12 hours.
If I were to kill this - could it be assumed that it would just become
available immediately or is there a chance of a BIG rollback (which could
possibly take another 12 hours)?
Thanks in advance
It depends when you cancel it and what you've asked it to do.
If you have a dbreindex of a single very large index, and cancel it while
its still building the new index, it should cancel pretty fast as all it
does is deallocate all the new pages. If you cancel it while it's deleting
the old index, then it has to rollback all the deletes again.
If you have a dbreindex that's rebuilding 10 indexes, and you cancel it
after its done 5 of them, it will have to rollback the deletes of the 5 old
indexes, which will take time proportional to their size.
Several things to consider: why are you rebuilding and have you considered
using DBCC INDEXDEFRAG instead?
Checkout the whitepaper below for more info:
http://www.microsoft.com/technet/pro.../ss2kidbp.mspx
Thanks
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"TJT" <TJT@.nospam.com> wrote in message
news:%23Hi2ZwjuFHA.1256@.TK2MSFTNGP09.phx.gbl...
>I recall several instances where I killed a DBREINDEX after 20 minutes of
> execution and it seemed to cancel surprisingly fast (I was expecting a
> massive rollback)
> We now have a situation where a DBREINDEX has been running over 12 hours.
> If I were to kill this - could it be assumed that it would just become
> available immediately or is there a chance of a BIG rollback (which could
> possibly take another 12 hours)?
> Thanks in advance
>
Killing a DBCC DBREINDEX - will this cause a massive rollback
I recall several instances where I killed a DBREINDEX after 20 minutes of
execution and it seemed to cancel surprisingly fast (I was expecting a
massive rollback)
We now have a situation where a DBREINDEX has been running over 12 hours.
If I were to kill this - could it be assumed that it would just become
available immediately or is there a chance of a BIG rollback (which could
possibly take another 12 hours)?
Thanks in advanceIt depends when you cancel it and what you've asked it to do.
If you have a dbreindex of a single very large index, and cancel it while
its still building the new index, it should cancel pretty fast as all it
does is deallocate all the new pages. If you cancel it while it's deleting
the old index, then it has to rollback all the deletes again.
If you have a dbreindex that's rebuilding 10 indexes, and you cancel it
after its done 5 of them, it will have to rollback the deletes of the 5 old
indexes, which will take time proportional to their size.
Several things to consider: why are you rebuilding and have you considered
using DBCC INDEXDEFRAG instead?
Checkout the whitepaper below for more info:
http://www.microsoft.com/technet/pr...n/ss2kidbp.mspx
Thanks
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"TJT" <TJT@.nospam.com> wrote in message
news:%23Hi2ZwjuFHA.1256@.TK2MSFTNGP09.phx.gbl...
>I recall several instances where I killed a DBREINDEX after 20 minutes of
> execution and it seemed to cancel surprisingly fast (I was expecting a
> massive rollback)
> We now have a situation where a DBREINDEX has been running over 12 hours.
> If I were to kill this - could it be assumed that it would just become
> available immediately or is there a chance of a BIG rollback (which could
> possibly take another 12 hours)?
> Thanks in advance
>
execution and it seemed to cancel surprisingly fast (I was expecting a
massive rollback)
We now have a situation where a DBREINDEX has been running over 12 hours.
If I were to kill this - could it be assumed that it would just become
available immediately or is there a chance of a BIG rollback (which could
possibly take another 12 hours)?
Thanks in advanceIt depends when you cancel it and what you've asked it to do.
If you have a dbreindex of a single very large index, and cancel it while
its still building the new index, it should cancel pretty fast as all it
does is deallocate all the new pages. If you cancel it while it's deleting
the old index, then it has to rollback all the deletes again.
If you have a dbreindex that's rebuilding 10 indexes, and you cancel it
after its done 5 of them, it will have to rollback the deletes of the 5 old
indexes, which will take time proportional to their size.
Several things to consider: why are you rebuilding and have you considered
using DBCC INDEXDEFRAG instead?
Checkout the whitepaper below for more info:
http://www.microsoft.com/technet/pr...n/ss2kidbp.mspx
Thanks
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"TJT" <TJT@.nospam.com> wrote in message
news:%23Hi2ZwjuFHA.1256@.TK2MSFTNGP09.phx.gbl...
>I recall several instances where I killed a DBREINDEX after 20 minutes of
> execution and it seemed to cancel surprisingly fast (I was expecting a
> massive rollback)
> We now have a situation where a DBREINDEX has been running over 12 hours.
> If I were to kill this - could it be assumed that it would just become
> available immediately or is there a chance of a BIG rollback (which could
> possibly take another 12 hours)?
> Thanks in advance
>
Wednesday, March 7, 2012
Keeping multiple SSRS instances syncrhonized?
Hi all,
I have a problem to solve for synchronizing report objects between multiple instances of reporting services. Our production data is distributed via replication from our head office to database servers at our remote offices. Likewise, we want to have an instance of reporting services co-located with each of the databases and therefore will be installing reporting services instances at the remote offices.
I would like to optimize for efficiency in keeping the report objects in sync, minimizing data transfer and as little manual intervention as possible so as to avoid mistakes. I have come up with several approaches to acheiving the SSRS replication I seek:
a) Use a scale-out deployment. This would mean creating multiple instances of the reports to account for the multiple DataSources I would need to configure, since I can't parameterize the DataSource in a linked report.
b) Manually replicate reports to each of my deployments using BIDS/SSMS. This would involve a ton of admin as all objects should be kept in sync.
c) Write RSS scripts to handle the synchronization of the servers. This shouldn't be too hard given that the webservices should play nicely with such a solution. It might take some effort to write the object comparison routine.
d) Have the replication engine take care of the replication of report objects between the servers. If I sync up the encryption keys, could I set up replication on all the tables I need synchronized and just be done with it? This would be my favored solution but I'm not sure it is possible.
Any ideas and suggestions would be appreciated.
Thanks,
Calvin
HTH, Jens SUessmeyer.
http://www.sqlserver2005.de|||I know this is already marked answered, but I figured I would put this up here since I ran across it today, probably would do what you needed
http://www.sqldbatips.com/showarticle.asp?ID=62
it worked for me at least 
Keeping multiple SSRS instances syncrhonized?
Hi all,
I have a problem to solve for synchronizing report objects between multiple instances of reporting services. Our production data is distributed via replication from our head office to database servers at our remote offices. Likewise, we want to have an instance of reporting services co-located with each of the databases and therefore will be installing reporting services instances at the remote offices.
I would like to optimize for efficiency in keeping the report objects in sync, minimizing data transfer and as little manual intervention as possible so as to avoid mistakes. I have come up with several approaches to acheiving the SSRS replication I seek:
a) Use a scale-out deployment. This would mean creating multiple instances of the reports to account for the multiple DataSources I would need to configure, since I can't parameterize the DataSource in a linked report.
b) Manually replicate reports to each of my deployments using BIDS/SSMS. This would involve a ton of admin as all objects should be kept in sync.
c) Write RSS scripts to handle the synchronization of the servers. This shouldn't be too hard given that the webservices should play nicely with such a solution. It might take some effort to write the object comparison routine.
d) Have the replication engine take care of the replication of report objects between the servers. If I sync up the encryption keys, could I set up replication on all the tables I need synchronized and just be done with it? This would be my favored solution but I'm not sure it is possible.
Any ideas and suggestions would be appreciated.
Thanks,
Calvin
HTH, Jens SUessmeyer.
http://www.sqlserver2005.de
|||I know this is already marked answered, but I figured I would put this up here since I ran across it today, probably would do what you needed
http://www.sqldbatips.com/showarticle.asp?ID=62
it worked for me at least
Monday, February 20, 2012
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:
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" пишет:
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
> >
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
> > >
> > >
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" пишет:
>
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:
>
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:
>
Subscribe to:
Posts (Atom)