Cannot reinstall MSDE on XP after uninstall it

I have trouble reinstalling MSDE 2000 on a XP machine after uninstalled it. I
did apply SP3a to the previous install of MSDE 2000 on the same XP machine.
Some of the component in an application did not work well so I had to
uninstall the MSDE 2000 SP3a completely. I removed all folders and even
registry entries. I kept getting this message, "Setup failed to configure the
server. Refer to the server error logs and setup logs for more information".
Unfortunately, those error and setup logs were useless. So, I used the /L*v
parameter to generate the setup log but it did not pinpoint why it failed. It
always fail at the last 4 seconds install period.
I ran the same setup on another XP machine. After uninstalled MSDE, removed
folders and registry entries, I was able to reinstall MSDE 2000 again.
Any help will be greatly appreciated.
Thank you.
KC
Here's a Knowledge Base article with instructions on how to manually
uninstall MSDE 2000.
http://support.microsoft.com/default...b;en-us;320873
Good luck,
Tony Sebion
"KC" <KC@.discussions.microsoft.com> wrote in message
news:F3C2F678-813C-46EA-A216-9469F13777C3@.microsoft.com:

> I have trouble reinstalling MSDE 2000 on a XP machine after uninstalled it. I
> did apply SP3a to the previous install of MSDE 2000 on the same XP machine.
> Some of the component in an application did not work well so I had to
> uninstall the MSDE 2000 SP3a completely. I removed all folders and even
> registry entries. I kept getting this message, "Setup failed to configure the
> server. Refer to the server error logs and setup logs for more information".
> Unfortunately, those error and setup logs were useless. So, I used the /L*v
> parameter to generate the setup log but it did not pinpoint why it failed. It
> always fail at the last 4 seconds install period.
> I ran the same setup on another XP machine. After uninstalled MSDE, removed
> folders and registry entries, I was able to reinstall MSDE 2000 again.
> Any help will be greatly appreciated.
> Thank you.
> KC
|||Thank you for the reply. First, I looked for those registry entries mentioned
in the article. None of them exists. So, I installed Windows Support Tools
for XP on the machine, ran the msizap with GUID, it found nothing.
The setup still fails with the same error message. What's next?
Thank you for the article though.
"Tony Sebion" wrote:

> Here's a Knowledge Base article with instructions on how to manually
> uninstall MSDE 2000.
> http://support.microsoft.com/default...b;en-us;320873
>
> Good luck,
> Tony Sebion
>
> "KC" <KC@.discussions.microsoft.com> wrote in message
> news:F3C2F678-813C-46EA-A216-9469F13777C3@.microsoft.com:
>
>
|||hi
KC wrote:
> Thank you for the reply. First, I looked for those registry entries
> mentioned in the article. None of them exists. So, I installed
> Windows Support Tools for XP on the machine, ran the msizap with
> GUID, it found nothing.
> The setup still fails with the same error message. What's next?
>
sometimes this is due to MDAC mess, so you have to fix it...
you can try reinstalling the used MDAC stack and, in case of WinXP sp2, fix
it as described in http://www.macropool.com/en/download/mdac_xp_sp2.html
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||KC wrote:
> I have trouble reinstalling MSDE 2000 on a XP machine after uninstalled it. I
> did apply SP3a to the previous install of MSDE 2000 on the same XP machine.
> Some of the component in an application did not work well so I had to
> uninstall the MSDE 2000 SP3a completely. I removed all folders and even
> registry entries. I kept getting this message, "Setup failed to configure the
> server. Refer to the server error logs and setup logs for more information".
> Unfortunately, those error and setup logs were useless. So, I used the /L*v
> parameter to generate the setup log but it did not pinpoint why it failed. It
> always fail at the last 4 seconds install period.
> I ran the same setup on another XP machine. After uninstalled MSDE, removed
> folders and registry entries, I was able to reinstall MSDE 2000 again.
> Any help will be greatly appreciated.
> Thank you.
> KC
Hi,
A had the same problem. I found that there isn't uninstalled
MSSQLServerADHelper service. I searched in registry and deletet
(almost;-) everything which contained MSSQL. That works (at least at my
PC). Maybe it'll work at yours too.
ukasz
|||Okay...Finally, I got it to reinstall after many tries. Thank you all for
your helps. First, MDAC was messed up. It was sqlsrv32.dll. Because I
upgraded my initial MSDE installed to SP3a, that DLL file got upgraded. I
replaced that DLL file from a good known XP machine. Then, re-registered all
MDAC using MDAC Repair Util. That didn't work. Later, I found out that there
were three DLLs missing from the System32 folder: sqlsrv32.rll, SQLWID.DLL &
SQLWOA.DLL. I copied them from a known good XP machine. Reinstalled MDAC 2.8
completely. After that, it installed just fine...Thank you.
"Andrea Montanari" wrote:

> hi
> KC wrote:
> sometimes this is due to MDAC mess, so you have to fix it...
> you can try reinstalling the used MDAC stack and, in case of WinXP sp2, fix
> it as described in http://www.macropool.com/en/download/mdac_xp_sp2.html
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>

Cannot rebuild full text catalogs

Recently moved database and full text catalogs to new server with SQL Server
2000 sp3a/SBS 2003 sp1
I am having problems rebuilding and repopulating the fulltext catalogs
restored to the new server.
The message I encounter is "Error 7635: The Microsoft Search cannot be
administered under the present user account".
I understand from the link I have been referred to
"http://support.microsoft.com/default.aspx?scid=kb;en-us;277549" states that
the service logon was changed through the control panel instead of the
Enterprise Manager therefore the service login for SQL Server does not have
administrative priviledges over the MSSearch service.
None of the service logins were changed through the control panel
I have tried the workround as suggested in the link but I still get the same
error message when I try to rebuild the full text catalog.
Any of you MVP's with another approach or suggestions to solve this problem?What account is MSSearch running under? It must be running under the local
system account. If it is not change it, you can change it through the
services applet in Control panel - Administrative Tasks.
Check that the builtin\Admins group is in the sysadmin role, and if not do
the following
use master
go
exec sp_grantlogin N'NT Authority\System'
exec sp_defaultdb N'NT Authority\System', N'master'
exec sp_defaultlanguage N'NT Authority\System','us_english'
exec sp_addsrvrolemember N'NT Authority\System', sysadmin
goThen change the SQL Server account to a the local system account in
Enterprise manger, right click on it and select properties and then select
the security tab and make the modifcation here, bounce it and the repeat the
process to have it run under a local adminstrators account.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jarvis Allen" <JarvisAllen@.discussions.microsoft.com> wrote in message
news:DA108BC7-E94F-4391-A71F-505CF6D42E0A@.microsoft.com...
> Recently moved database and full text catalogs to new server with SQL
> Server
> 2000 sp3a/SBS 2003 sp1
> I am having problems rebuilding and repopulating the fulltext catalogs
> restored to the new server.
> The message I encounter is "Error 7635: The Microsoft Search cannot be
> administered under the present user account".
> I understand from the link I have been referred to
> "http://support.microsoft.com/default.aspx?scid=kb;en-us;277549" states
> that
> the service logon was changed through the control panel instead of the
> Enterprise Manager therefore the service login for SQL Server does not
> have
> administrative priviledges over the MSSearch service.
> None of the service logins were changed through the control panel
> I have tried the workround as suggested in the link but I still get the
> same
> error message when I try to rebuild the full text catalog.
> Any of you MVP's with another approach or suggestions to solve this
> problem?|||"Hilary Cotter" wrote:
> What account is MSSearch running under? It must be running under the local
> system account. If it is not change it, you can change it through the
> services applet in Control panel - Administrative Tasks.
> Check that the builtin\Admins group is in the sysadmin role, and if not do
> the following
> use master
> go
> exec sp_grantlogin N'NT Authority\System'
> exec sp_defaultdb N'NT Authority\System', N'master'
> exec sp_defaultlanguage N'NT Authority\System','us_english'
> exec sp_addsrvrolemember N'NT Authority\System', sysadmin
> goThen change the SQL Server account to a the local system account in
> Enterprise manger, right click on it and select properties and then select
> the security tab and make the modifcation here, bounce it and the repeat the
> process to have it run under a local adminstrators account.
>
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Jarvis Allen" <JarvisAllen@.discussions.microsoft.com> wrote in message
> news:DA108BC7-E94F-4391-A71F-505CF6D42E0A@.microsoft.com...
> > Recently moved database and full text catalogs to new server with SQL
> > Server
> > 2000 sp3a/SBS 2003 sp1
> > I am having problems rebuilding and repopulating the fulltext catalogs
> > restored to the new server.
> > The message I encounter is "Error 7635: The Microsoft Search cannot be
> > administered under the present user account".
> >
> > I understand from the link I have been referred to
> > "http://support.microsoft.com/default.aspx?scid=kb;en-us;277549" states
> > that
> > the service logon was changed through the control panel instead of the
> > Enterprise Manager therefore the service login for SQL Server does not
> > have
> > administrative priviledges over the MSSearch service.
> > None of the service logins were changed through the control panel
> >
> > I have tried the workround as suggested in the link but I still get the
> > same
> > error message when I try to rebuild the full text catalog.
> >
> > Any of you MVP's with another approach or suggestions to solve this
> > problem?
> Thank you for your reply Hilary
The MS Search service is using the local system logon and built in admin has
the role of sydadmin.
I followed your instructions which was similiar to the instruction I
followed in the link i was reffered to inmy original message.
Unfortunately the your instructions I followed failed to cure the 7635 error
(cannot administer MS Search service under present user account).
Are ther any other slutions to try?
>|||"Jarvis Allen" wrote:
I have tried suggestions by Hilary and the problem still persists.
The MS Search is running under the local system account as it should which
seems to be the problem.
The problem seems to be getting the administer rights over the MS Search
service.
The SQL Server does start with the Domain Admin user.
For some reason the Domain Admin user can administer the MS Search service
even though I have used the suggested way to gain admin rights over the MS
Search!
Any other ideas from you SQL experts?
>
> "Hilary Cotter" wrote:
> > What account is MSSearch running under? It must be running under the local
> > system account. If it is not change it, you can change it through the
> > services applet in Control panel - Administrative Tasks.
> >
> > Check that the builtin\Admins group is in the sysadmin role, and if not do
> > the following
> >
> > use master
> > go
> > exec sp_grantlogin N'NT Authority\System'
> > exec sp_defaultdb N'NT Authority\System', N'master'
> > exec sp_defaultlanguage N'NT Authority\System','us_english'
> > exec sp_addsrvrolemember N'NT Authority\System', sysadmin
> > goThen change the SQL Server account to a the local system account in
> > Enterprise manger, right click on it and select properties and then select
> > the security tab and make the modifcation here, bounce it and the repeat the
> > process to have it run under a local adminstrators account.
> >
> >
> >
> > --
> > Hilary Cotter
> > Director of Text Mining and Database Strategy
> > RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> >
> > This posting is my own and doesn't necessarily represent RelevantNoise's
> > positions, strategies or opinions.
> >
> > Looking for a SQL Server replication book?
> > http://www.nwsu.com/0974973602.html
> >
> > Looking for a FAQ on Indexing Services/SQL FTS
> > http://www.indexserverfaq.com
> >
> >
> >
> > "Jarvis Allen" <JarvisAllen@.discussions.microsoft.com> wrote in message
> > news:DA108BC7-E94F-4391-A71F-505CF6D42E0A@.microsoft.com...
> > > Recently moved database and full text catalogs to new server with SQL
> > > Server
> > > 2000 sp3a/SBS 2003 sp1
> > > I am having problems rebuilding and repopulating the fulltext catalogs
> > > restored to the new server.
> > > The message I encounter is "Error 7635: The Microsoft Search cannot be
> > > administered under the present user account".
> > >
> > > I understand from the link I have been referred to
> > > "http://support.microsoft.com/default.aspx?scid=kb;en-us;277549" states
> > > that
> > > the service logon was changed through the control panel instead of the
> > > Enterprise Manager therefore the service login for SQL Server does not
> > > have
> > > administrative priviledges over the MSSearch service.
> > > None of the service logins were changed through the control panel
> > >
> > > I have tried the workround as suggested in the link but I still get the
> > > same
> > > error message when I try to rebuild the full text catalog.
> > >
> > > Any of you MVP's with another approach or suggestions to solve this
> > > problem?
> >
> > Thank you for your reply Hilary
> The MS Search service is using the local system logon and built in admin has
> the role of sydadmin.
> I followed your instructions which was similiar to the instruction I
> followed in the link i was reffered to inmy original message.
> Unfortunately the your instructions I followed failed to cure the 7635 error
> (cannot administer MS Search service under present user account).
> Are ther any other slutions to try?
> >|||>
> "Jarvis Allen" wrote:
> I have tried suggestions by Hilary and the problem still persists.
> The MS Search is running under the local system account as it should which
> seems to be the problem.
> The problem seems to be getting the administer rights over the MS Search
> service.
> The SQL Server does start with the Domain Admin user.
> For some reason the Domain Admin user cannot administer the MS Search service
> even though I have used the suggested way to gain admin rights over the MS
> Search!
> Any other ideas from you SQL experts?
> >
> >
> > "Hilary Cotter" wrote:
> >
> > > What account is MSSearch running under? It must be running under the local
> > > system account. If it is not change it, you can change it through the
> > > services applet in Control panel - Administrative Tasks.
> > >
> > > Check that the builtin\Admins group is in the sysadmin role, and if not do
> > > the following
> > >
> > > use master
> > > go
> > > exec sp_grantlogin N'NT Authority\System'
> > > exec sp_defaultdb N'NT Authority\System', N'master'
> > > exec sp_defaultlanguage N'NT Authority\System','us_english'
> > > exec sp_addsrvrolemember N'NT Authority\System', sysadmin
> > > goThen change the SQL Server account to a the local system account in
> > > Enterprise manger, right click on it and select properties and then select
> > > the security tab and make the modifcation here, bounce it and the repeat the
> > > process to have it run under a local adminstrators account.
> > >
> > >
> > >
> > > --
> > > Hilary Cotter
> > > Director of Text Mining and Database Strategy
> > > RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> > >
> > > This posting is my own and doesn't necessarily represent RelevantNoise's
> > > positions, strategies or opinions.
> > >
> > > Looking for a SQL Server replication book?
> > > http://www.nwsu.com/0974973602.html
> > >
> > > Looking for a FAQ on Indexing Services/SQL FTS
> > > http://www.indexserverfaq.com
> > >
> > >
> > >
> > > "Jarvis Allen" <JarvisAllen@.discussions.microsoft.com> wrote in message
> > > news:DA108BC7-E94F-4391-A71F-505CF6D42E0A@.microsoft.com...
> > > > Recently moved database and full text catalogs to new server with SQL
> > > > Server
> > > > 2000 sp3a/SBS 2003 sp1
> > > > I am having problems rebuilding and repopulating the fulltext catalogs
> > > > restored to the new server.
> > > > The message I encounter is "Error 7635: The Microsoft Search cannot be
> > > > administered under the present user account".
> > > >
> > > > I understand from the link I have been referred to
> > > > "http://support.microsoft.com/default.aspx?scid=kb;en-us;277549" states
> > > > that
> > > > the service logon was changed through the control panel instead of the
> > > > Enterprise Manager therefore the service login for SQL Server does not
> > > > have
> > > > administrative priviledges over the MSSearch service.
> > > > None of the service logins were changed through the control panel
> > > >
> > > > I have tried the workround as suggested in the link but I still get the
> > > > same
> > > > error message when I try to rebuild the full text catalog.
> > > >
> > > > Any of you MVP's with another approach or suggestions to solve this
> > > > problem?
> > >
> > > Thank you for your reply Hilary
> > The MS Search service is using the local system logon and built in admin has
> > the role of sydadmin.
> > I followed your instructions which was similiar to the instruction I
> > followed in the link i was reffered to inmy original message.
> > Unfortunately the your instructions I followed failed to cure the 7635 error
> > (cannot administer MS Search service under present user account).
> > Are ther any other slutions to try?
> > >

Cannot rebuild full text catalogs

Recently moved database and full text catalogs to new server with SQL Server
2000 sp3a/SBS 2003 sp1
I am having problems rebuilding and repopulating the fulltext catalogs
restored to the new server.
The message I encounter is "Error 7635: The Microsoft Search cannot be
administered under the present user account".
I understand from the link I have been referred to
"http://support.microsoft.com/default.aspx?scid=kb;en-us;277549" states that
the service logon was changed through the control panel instead of the
Enterprise Manager therefore the service login for SQL Server does not have
administrative priviledges over the MSSearch service.
None of the service logins were changed through the control panel
I have tried the workround as suggested in the link but I still get the same
error message when I try to rebuild the full text catalog.
Any of you MVP's with another approach or suggestions to solve this problem?
What account is MSSearch running under? It must be running under the local
system account. If it is not change it, you can change it through the
services applet in Control panel - Administrative Tasks.
Check that the builtin\Admins group is in the sysadmin role, and if not do
the following
use master
go
exec sp_grantlogin N'NT Authority\System'
exec sp_defaultdb N'NT Authority\System', N'master'
exec sp_defaultlanguage N'NT Authority\System','us_english'
exec sp_addsrvrolemember N'NT Authority\System', sysadmin
goThen change the SQL Server account to a the local system account in
Enterprise manger, right click on it and select properties and then select
the security tab and make the modifcation here, bounce it and the repeat the
process to have it run under a local adminstrators account.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jarvis Allen" <JarvisAllen@.discussions.microsoft.com> wrote in message
news:DA108BC7-E94F-4391-A71F-505CF6D42E0A@.microsoft.com...
> Recently moved database and full text catalogs to new server with SQL
> Server
> 2000 sp3a/SBS 2003 sp1
> I am having problems rebuilding and repopulating the fulltext catalogs
> restored to the new server.
> The message I encounter is "Error 7635: The Microsoft Search cannot be
> administered under the present user account".
> I understand from the link I have been referred to
> "http://support.microsoft.com/default.aspx?scid=kb;en-us;277549" states
> that
> the service logon was changed through the control panel instead of the
> Enterprise Manager therefore the service login for SQL Server does not
> have
> administrative priviledges over the MSSearch service.
> None of the service logins were changed through the control panel
> I have tried the workround as suggested in the link but I still get the
> same
> error message when I try to rebuild the full text catalog.
> Any of you MVP's with another approach or suggestions to solve this
> problem?
|||"Hilary Cotter" wrote:

> What account is MSSearch running under? It must be running under the local
> system account. If it is not change it, you can change it through the
> services applet in Control panel - Administrative Tasks.
> Check that the builtin\Admins group is in the sysadmin role, and if not do
> the following
> use master
> go
> exec sp_grantlogin N'NT Authority\System'
> exec sp_defaultdb N'NT Authority\System', N'master'
> exec sp_defaultlanguage N'NT Authority\System','us_english'
> exec sp_addsrvrolemember N'NT Authority\System', sysadmin
> goThen change the SQL Server account to a the local system account in
> Enterprise manger, right click on it and select properties and then select
> the security tab and make the modifcation here, bounce it and the repeat the
> process to have it run under a local adminstrators account.
>
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Jarvis Allen" <JarvisAllen@.discussions.microsoft.com> wrote in message
> news:DA108BC7-E94F-4391-A71F-505CF6D42E0A@.microsoft.com...
> Thank you for your reply Hilary
The MS Search service is using the local system logon and built in admin has
the role of sydadmin.
I followed your instructions which was similiar to the instruction I
followed in the link i was reffered to inmy original message.
Unfortunately the your instructions I followed failed to cure the 7635 error
(cannot administer MS Search service under present user account).
Are ther any other slutions to try?
>
|||"Jarvis Allen" wrote:
I have tried suggestions by Hilary and the problem still persists.
The MS Search is running under the local system account as it should which
seems to be the problem.
The problem seems to be getting the administer rights over the MS Search
service.
The SQL Server does start with the Domain Admin user.
For some reason the Domain Admin user can administer the MS Search service
even though I have used the suggested way to gain admin rights over the MS
Search!
Any other ideas from you SQL experts?[vbcol=seagreen]
>
> "Hilary Cotter" wrote:
> The MS Search service is using the local system logon and built in admin has
> the role of sydadmin.
> I followed your instructions which was similiar to the instruction I
> followed in the link i was reffered to inmy original message.
> Unfortunately the your instructions I followed failed to cure the 7635 error
> (cannot administer MS Search service under present user account).
> Are ther any other slutions to try?
|||[vbcol=seagreen]
>
> "Jarvis Allen" wrote:
> I have tried suggestions by Hilary and the problem still persists.
> The MS Search is running under the local system account as it should which
> seems to be the problem.
> The problem seems to be getting the administer rights over the MS Search
> service.
> The SQL Server does start with the Domain Admin user.
> For some reason the Domain Admin user cannot administer the MS Search service
> even though I have used the suggested way to gain admin rights over the MS
> Search!
> Any other ideas from you SQL experts?

Cannot rebuild full text catalogs

Recently moved database and full text catalogs to new server with SQL Server
2000 sp3a/SBS 2003 sp1
I am having problems rebuilding and repopulating the fulltext catalogs
restored to the new server.
The message I encounter is "Error 7635: The Microsoft Search cannot be
administered under the present user account".
I understand from the link I have been referred to
"http://support.microsoft.com/default.aspx?scid=kb;en-us;277549" states that
the service logon was changed through the control panel instead of the
Enterprise Manager therefore the service login for SQL Server does not have
administrative priviledges over the MSSearch service.
None of the service logins were changed through the control panel
I have tried the workround as suggested in the link but I still get the same
error message when I try to rebuild the full text catalog.
Any of you MVP's with another approach or suggestions to solve this problem?What account is MSSearch running under? It must be running under the local
system account. If it is not change it, you can change it through the
services applet in Control panel - Administrative Tasks.
Check that the builtin\Admins group is in the sysadmin role, and if not do
the following
use master
go
exec sp_grantlogin N'NT Authority\System'
exec sp_defaultdb N'NT Authority\System', N'master'
exec sp_defaultlanguage N'NT Authority\System','us_english'
exec sp_addsrvrolemember N'NT Authority\System', sysadmin
goThen change the SQL Server account to a the local system account in
Enterprise manger, right click on it and select properties and then select
the security tab and make the modifcation here, bounce it and the repeat the
process to have it run under a local adminstrators account.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jarvis Allen" <JarvisAllen@.discussions.microsoft.com> wrote in message
news:DA108BC7-E94F-4391-A71F-505CF6D42E0A@.microsoft.com...
> Recently moved database and full text catalogs to new server with SQL
> Server
> 2000 sp3a/SBS 2003 sp1
> I am having problems rebuilding and repopulating the fulltext catalogs
> restored to the new server.
> The message I encounter is "Error 7635: The Microsoft Search cannot be
> administered under the present user account".
> I understand from the link I have been referred to
> "http://support.microsoft.com/default.aspx?scid=kb;en-us;277549" states
> that
> the service logon was changed through the control panel instead of the
> Enterprise Manager therefore the service login for SQL Server does not
> have
> administrative priviledges over the MSSearch service.
> None of the service logins were changed through the control panel
> I have tried the workround as suggested in the link but I still get the
> same
> error message when I try to rebuild the full text catalog.
> Any of you MVP's with another approach or suggestions to solve this
> problem?|||"Hilary Cotter" wrote:

> What account is MSSearch running under? It must be running under the local
> system account. If it is not change it, you can change it through the
> services applet in Control panel - Administrative Tasks.
> Check that the builtin\Admins group is in the sysadmin role, and if not do
> the following
> use master
> go
> exec sp_grantlogin N'NT Authority\System'
> exec sp_defaultdb N'NT Authority\System', N'master'
> exec sp_defaultlanguage N'NT Authority\System','us_english'
> exec sp_addsrvrolemember N'NT Authority\System', sysadmin
> goThen change the SQL Server account to a the local system account in
> Enterprise manger, right click on it and select properties and then select
> the security tab and make the modifcation here, bounce it and the repeat t
he
> process to have it run under a local adminstrators account.
>
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Jarvis Allen" <JarvisAllen@.discussions.microsoft.com> wrote in message
> news:DA108BC7-E94F-4391-A71F-505CF6D42E0A@.microsoft.com...
> Thank you for your reply Hilary
The MS Search service is using the local system logon and built in admin has
the role of sydadmin.
I followed your instructions which was similiar to the instruction I
followed in the link i was reffered to inmy original message.
Unfortunately the your instructions I followed failed to cure the 7635 error
(cannot administer MS Search service under present user account).
Are ther any other slutions to try?
>|||"Jarvis Allen" wrote:
I have tried suggestions by Hilary and the problem still persists.
The MS Search is running under the local system account as it should which
seems to be the problem.
The problem seems to be getting the administer rights over the MS Search
service.
The SQL Server does start with the Domain Admin user.
For some reason the Domain Admin user can administer the MS Search service
even though I have used the suggested way to gain admin rights over the MS
Search!
Any other ideas from you SQL experts?[vbcol=seagreen]
>
> "Hilary Cotter" wrote:
>
> The MS Search service is using the local system logon and built in admin h
as
> the role of sydadmin.
> I followed your instructions which was similiar to the instruction I
> followed in the link i was reffered to inmy original message.
> Unfortunately the your instructions I followed failed to cure the 7635 err
or
> (cannot administer MS Search service under present user account).
> Are ther any other slutions to try?|||[vbcol=seagreen]
>
> "Jarvis Allen" wrote:
> I have tried suggestions by Hilary and the problem still persists.
> The MS Search is running under the local system account as it should which
> seems to be the problem.
> The problem seems to be getting the administer rights over the MS Search
> service.
> The SQL Server does start with the Domain Admin user.
> For some reason the Domain Admin user cannot administer the MS Search serv
ice
> even though I have used the suggested way to gain admin rights over the MS
> Search!
> Any other ideas from you SQL experts?

Cannot install server components

I have the beta version of RS running fine on Windows 2000 Server (SP4), IIS 5, and SQL Server 2000 Enterprise (SP3a). No issues at all.
However, when trying to install the RS release candidate, for some reason I am not presented with the server components option - I can only see the client tools option.
Can anyone assist?Did you receive any prereq warnings?
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ravinder" <Ravinder@.discussions.microsoft.com> wrote in message
news:0E870307-157B-4509-9003-B6CC934C4DDB@.microsoft.com...
> I have the beta version of RS running fine on Windows 2000 Server (SP4),
IIS 5, and SQL Server 2000 Enterprise (SP3a). No issues at all.
> However, when trying to install the RS release candidate, for some reason
I am not presented with the server components option - I can only see the
client tools option.
> Can anyone assist?|||I finally got the install working properly. As a last resort I re-installed Win2k SP4 and low and behold I am now able to install RS Server Components without any issues at all.
Microsoft might want to add this "known issue" to the install notes.
"Daniel Reib [MSFT]" wrote:
> Did you receive any prereq warnings?
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Ravinder" <Ravinder@.discussions.microsoft.com> wrote in message
> news:0E870307-157B-4509-9003-B6CC934C4DDB@.microsoft.com...
> > I have the beta version of RS running fine on Windows 2000 Server (SP4),
> IIS 5, and SQL Server 2000 Enterprise (SP3a). No issues at all.
> >
> > However, when trying to install the RS release candidate, for some reason
> I am not presented with the server components option - I can only see the
> client tools option.
> >
> > Can anyone assist?
>
>

Cannot get SP3a to install

We have the rtm version of SQL 2000 and have spent the last 2.5 hours trying to apply SP3a. Nothing on the microsoft support site has pointed us to the solution.

Basically, we start the install after shutting down the services, answer all the questions and then when it starts to copy files it fails with an error
'microsoft data access component failed (-1).

Looking in c:\winnt\datestup.log, the error is unknown. The c:\winnt\sqlsrp.log file is not touched.

We tried renaming the odbcconf.dll file per a microsoft article and no joy.

We also restored mdac_type.exe file per microsoft article and no joy.

Trying to install SP1 and SP2 - same results.

Anyone got any ideas besides it's time to call Microsoft?
:confused:When you unpacked the files for the SP did you unpack them in the default directory?|||I had the same like problem a couple of weeks ago. I did a fresh install on another machine (with the same installation CD) and applied the same service packs as on the original one, which I stored on my HDD. Then I compared (with Ghisler's Total Commander) the entire SQL directory and found some files to be different (corrupted??). You have to stop both SQL services first. I renamed the different files (I can't remember, but I thought is were only 2 files) on the original machine and replaced them with files from the new install. Then I started up the services.
After this, I could apply SP3a without any problem.

cannot generate SSPI context

Hi,
This only happens on a particular user's machine so far. the user is using
ms access, using odbc link to connect to SQL Server 2000 SP3a on W2k server.
With the MS Access running , suddenly the error happend when i ping the sql
server i can get its ip addr
i have checked the ms article on the SSPI but it does not seem to apply for
me in my case
appreciate any advise
tks & rdgs
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...tivity/200512/1One thing to check is the SQL Client Network stack. This is configured in th
e
(SQL Server) Client Network Utility. What you will probably find is that the
working clients either have Named Pipes before TCP/IP, or left out TCP/IP.
While the problem client will have TCP/IP first, or left out Named Pipes.
At a guess, you are running the SQL Server with a Domain Account, but it
does not have the permission to register the SQL Server's SPN (Service
Principal Name). This means that it cannot use delegation, which probably
isn't a problem for you guys. But when someone tries to attach using TCP/IP,
it can't use Kerberos and throws the error.
Clients that connect Named Pipes just by-pass Kerberos and security account
delegation.
I may have gotten a couple of the details mixed up, I'm not 100% on this.
There is a good Trouble Shooting page in the SQL Support and in BOL, under
Administering SQL Server is a page called "Security Account Delegation" that
is worth a read.
Good luck
"maxzsim via droptable.com" wrote:

> Hi,
>
> This only happens on a particular user's machine so far. the user is usin
g
> ms access, using odbc link to connect to SQL Server 2000 SP3a on W2k serve
r.
> With the MS Access running , suddenly the error happend when i ping the s
ql
> server i can get its ip addr
> i have checked the ms article on the SSPI but it does not seem to apply fo
r
> me in my case
> appreciate any advise
> tks & rdgs
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...tivity/200512/1
>

cannot generate SSPI context

Hi,
This only happens on a particular user's machine so far. the user is using
ms access, using odbc link to connect to SQL Server 2000 SP3a on W2k server.
With the MS Access running , suddenly the error happend when i ping the sql
server i can get its ip addr
i have checked the ms article on the SSPI but it does not seem to apply for
me in my case
appreciate any advise
tks & rdgs
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...ivity/200512/1
One thing to check is the SQL Client Network stack. This is configured in the
(SQL Server) Client Network Utility. What you will probably find is that the
working clients either have Named Pipes before TCP/IP, or left out TCP/IP.
While the problem client will have TCP/IP first, or left out Named Pipes.
At a guess, you are running the SQL Server with a Domain Account, but it
does not have the permission to register the SQL Server's SPN (Service
Principal Name). This means that it cannot use delegation, which probably
isn't a problem for you guys. But when someone tries to attach using TCP/IP,
it can't use Kerberos and throws the error.
Clients that connect Named Pipes just by-pass Kerberos and security account
delegation.
I may have gotten a couple of the details mixed up, I'm not 100% on this.
There is a good Trouble Shooting page in the SQL Support and in BOL, under
Administering SQL Server is a page called "Security Account Delegation" that
is worth a read.
Good luck
"maxzsim via droptable.com" wrote:

> Hi,
>
> This only happens on a particular user's machine so far. the user is using
> ms access, using odbc link to connect to SQL Server 2000 SP3a on W2k server.
> With the MS Access running , suddenly the error happend when i ping the sql
> server i can get its ip addr
> i have checked the ms article on the SSPI but it does not seem to apply for
> me in my case
> appreciate any advise
> tks & rdgs
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...ivity/200512/1
>

CANNOT GENERATE SSPI CONTENT

Dear support,
I'm running SQL Server Enterprise Edition with SP3a on Windows Advanced
Server SP4. However, when I register the SQL Server through Enterprise
Manager (or connect the SQL Server through Query Analyzer), the error:
A CONNECTION COULD NOT BE ESTABLISTHED TO <my SQL Server>
REASON: CANNOT GENERATE SSPI CONTENT
PLEASE VERIFY SQL SERVER IS RUNNING AND CHECK YOUR SQL SERVER REGISRATION
PROPERTIES (BY RIGHT-CLICKING ON THE <my SQL Server> NODE) AND TRY AGAIN
However, I can succesfully register by typing the IP Address.
Can anyone help?Maybe the server is unable to resolve the "mySQLServer" name? Can you ping
it? Are you trying to connect using Named Pipes? Is it using port 1433?
I would consider adding an Alias to the client network utility that points
"mySQLServer" at the IP address that works correctly (and of course points
to the correct port).
Or, if it ain't broke, don't fix it; since IP address works, use the IP
address?
--
http://www.aspfaq.com/
(Reverse address to reply.)
"jenny" <jenny@.discussions.microsoft.com> wrote in message
news:B808753B-9601-4E94-9984-3C717EF093AA@.microsoft.com...
> Dear support,
> I'm running SQL Server Enterprise Edition with SP3a on Windows Advanced
> Server SP4. However, when I register the SQL Server through Enterprise
> Manager (or connect the SQL Server through Query Analyzer), the error:
> A CONNECTION COULD NOT BE ESTABLISTHED TO <my SQL Server>
> REASON: CANNOT GENERATE SSPI CONTENT
> PLEASE VERIFY SQL SERVER IS RUNNING AND CHECK YOUR SQL SERVER REGISRATION
> PROPERTIES (BY RIGHT-CLICKING ON THE <my SQL Server> NODE) AND TRY AGAIN
> However, I can succesfully register by typing the IP Address.
> Can anyone help?
>|||Probably problem is with your DNS, on the computer on which SQL server is
installed check computer name and primary DNS suffix.
Regards,
Daniel
"jenny" <jenny@.discussions.microsoft.com> wrote in message
news:B808753B-9601-4E94-9984-3C717EF093AA@.microsoft.com...
> Dear support,
> I'm running SQL Server Enterprise Edition with SP3a on Windows Advanced
> Server SP4. However, when I register the SQL Server through Enterprise
> Manager (or connect the SQL Server through Query Analyzer), the error:
> A CONNECTION COULD NOT BE ESTABLISTHED TO <my SQL Server>
> REASON: CANNOT GENERATE SSPI CONTENT
> PLEASE VERIFY SQL SERVER IS RUNNING AND CHECK YOUR SQL SERVER REGISRATION
> PROPERTIES (BY RIGHT-CLICKING ON THE <my SQL Server> NODE) AND TRY AGAIN
> However, I can succesfully register by typing the IP Address.
> Can anyone help?
>|||Hi all,
I can successfully ping my SQL server (with my SQL server name is the same
as my Server name).
It is quite impossible to use IP as my system (a lot of programs and
configure) has been developed and is using SQL server name for the SQL
connection.
BTW, I have many SQL server and only this SQL server got the "Cannot
generate SSPI content" problem. Any more hints ?
"Daniel Joskovski" wrote:
> Probably problem is with your DNS, on the computer on which SQL server is
> installed check computer name and primary DNS suffix.
> Regards,
> Daniel
> "jenny" <jenny@.discussions.microsoft.com> wrote in message
> news:B808753B-9601-4E94-9984-3C717EF093AA@.microsoft.com...
> > Dear support,
> >
> > I'm running SQL Server Enterprise Edition with SP3a on Windows Advanced
> > Server SP4. However, when I register the SQL Server through Enterprise
> > Manager (or connect the SQL Server through Query Analyzer), the error:
> > A CONNECTION COULD NOT BE ESTABLISTHED TO <my SQL Server>
> > REASON: CANNOT GENERATE SSPI CONTENT
> > PLEASE VERIFY SQL SERVER IS RUNNING AND CHECK YOUR SQL SERVER REGISRATION
> > PROPERTIES (BY RIGHT-CLICKING ON THE <my SQL Server> NODE) AND TRY AGAIN
> > However, I can succesfully register by typing the IP Address.
> >
> > Can anyone help?
> >
> >
>
>|||> It is quite impossible to use IP as my system (a lot of programs and
> configure) has been developed and is using SQL server name for the SQL
> connection.
(a) the name of the data source should not be hard-coded into programs. At
the very least, all of your applications should get this kind of global
parameter from a single, central location. In your current state, what are
you going to do when you change the SQL auth password? Or switch from SQL
auth to Windows auth? Or move the database to a server with a different
name?
(b) barring (a), have you seen my suggestion to add the server name -> IP
mapping in the client network utility on the workstations that can't connect
to this SQL Server by name?
--
http://www.aspfaq.com/
(Reverse address to reply.)|||Hi Aaron,
Thanks first.
The SQL server name is not hardcode... It is stored in the configuration
file or database value. To be more accurate, now my system is working fine
by using the SQL Server Name except for the following cases:
- Register the SQL Server through Enterprise Manager
- Connect to the SQL Server through Query Analyzer
- Run osql command with connection typed with the SQL Server Name
Some of my predefined script are coded with the SQL Server Name and is
worked fine for other SQL Servers except the one I mentioned. I even got the
same problem when I connect the SQL Server on the same Server. (e.g. The SQL
Server A is installed in the Windows Server A.) However, I have one finding
that if I add the SQL Server IP entry in the "host" file, I can then solve
the above 3 problems. I wonder, is adding the host file the only
(appropriate) way to solve the problem ? Is there any other methods as I
only got one SQL Server having this problem. Thanks a lot again.
For more information, my SQL Server is running cluster, using NamePiped and
TCP/IP connection with port 1433.
For your option (b), I'll consider... But curious that why other SQL servers
of my system works without problem (they have similar settings during
installation)
"Aaron [SQL Server MVP]" wrote:
> > It is quite impossible to use IP as my system (a lot of programs and
> > configure) has been developed and is using SQL server name for the SQL
> > connection.
> (a) the name of the data source should not be hard-coded into programs. At
> the very least, all of your applications should get this kind of global
> parameter from a single, central location. In your current state, what are
> you going to do when you change the SQL auth password? Or switch from SQL
> auth to Windows auth? Or move the database to a server with a different
> name?
> (b) barring (a), have you seen my suggestion to add the server name -> IP
> mapping in the client network utility on the workstations that can't connect
> to this SQL Server by name?
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>|||It is possible to ping your server name and still have problems with DNS,
try to ping FQDN for example instead of Ping Stockholm, ping
Stockholm.nwtraders.msft or better check full name of computer on which is
SQL server installed.
Regards,
Daniel
"jenny" <jenny@.discussions.microsoft.com> wrote in message
news:952A3B38-2035-4D64-95FA-0CC2F0F2BB87@.microsoft.com...
> Hi all,
> I can successfully ping my SQL server (with my SQL server name is the same
> as my Server name).
> It is quite impossible to use IP as my system (a lot of programs and
> configure) has been developed and is using SQL server name for the SQL
> connection.
> BTW, I have many SQL server and only this SQL server got the "Cannot
> generate SSPI content" problem. Any more hints ?
> "Daniel Joskovski" wrote:
> > Probably problem is with your DNS, on the computer on which SQL server
is
> > installed check computer name and primary DNS suffix.
> > Regards,
> > Daniel
> >
> > "jenny" <jenny@.discussions.microsoft.com> wrote in message
> > news:B808753B-9601-4E94-9984-3C717EF093AA@.microsoft.com...
> > > Dear support,
> > >
> > > I'm running SQL Server Enterprise Edition with SP3a on Windows
Advanced
> > > Server SP4. However, when I register the SQL Server through
Enterprise
> > > Manager (or connect the SQL Server through Query Analyzer), the error:
> > > A CONNECTION COULD NOT BE ESTABLISTHED TO <my SQL Server>
> > > REASON: CANNOT GENERATE SSPI CONTENT
> > > PLEASE VERIFY SQL SERVER IS RUNNING AND CHECK YOUR SQL SERVER
REGISRATION
> > > PROPERTIES (BY RIGHT-CLICKING ON THE <my SQL Server> NODE) AND TRY
AGAIN
> > > However, I can succesfully register by typing the IP Address.
> > >
> > > Can anyone help?
> > >
> > >
> >
> >
> >

CANNOT GENERATE SSPI CONTENT

Dear support,
I'm running SQL Server Enterprise Edition with SP3a on Windows Advanced
Server SP4. However, when I register the SQL Server through Enterprise
Manager (or connect the SQL Server through Query Analyzer), the error:
A CONNECTION COULD NOT BE ESTABLISTHED TO <my SQL Server>
REASON: CANNOT GENERATE SSPI CONTENT
PLEASE VERIFY SQL SERVER IS RUNNING AND CHECK YOUR SQL SERVER REGISRATION
PROPERTIES (BY RIGHT-CLICKING ON THE <my SQL Server> NODE) AND TRY AGAIN
However, I can succesfully register by typing the IP Address.
Can anyone help?
Maybe the server is unable to resolve the "mySQLServer" name? Can you ping
it? Are you trying to connect using Named Pipes? Is it using port 1433?
I would consider adding an Alias to the client network utility that points
"mySQLServer" at the IP address that works correctly (and of course points
to the correct port).
Or, if it ain't broke, don't fix it; since IP address works, use the IP
address?
http://www.aspfaq.com/
(Reverse address to reply.)
"jenny" <jenny@.discussions.microsoft.com> wrote in message
news:B808753B-9601-4E94-9984-3C717EF093AA@.microsoft.com...
> Dear support,
> I'm running SQL Server Enterprise Edition with SP3a on Windows Advanced
> Server SP4. However, when I register the SQL Server through Enterprise
> Manager (or connect the SQL Server through Query Analyzer), the error:
> A CONNECTION COULD NOT BE ESTABLISTHED TO <my SQL Server>
> REASON: CANNOT GENERATE SSPI CONTENT
> PLEASE VERIFY SQL SERVER IS RUNNING AND CHECK YOUR SQL SERVER REGISRATION
> PROPERTIES (BY RIGHT-CLICKING ON THE <my SQL Server> NODE) AND TRY AGAIN
> However, I can succesfully register by typing the IP Address.
> Can anyone help?
>
|||Probably problem is with your DNS, on the computer on which SQL server is
installed check computer name and primary DNS suffix.
Regards,
Daniel
"jenny" <jenny@.discussions.microsoft.com> wrote in message
news:B808753B-9601-4E94-9984-3C717EF093AA@.microsoft.com...
> Dear support,
> I'm running SQL Server Enterprise Edition with SP3a on Windows Advanced
> Server SP4. However, when I register the SQL Server through Enterprise
> Manager (or connect the SQL Server through Query Analyzer), the error:
> A CONNECTION COULD NOT BE ESTABLISTHED TO <my SQL Server>
> REASON: CANNOT GENERATE SSPI CONTENT
> PLEASE VERIFY SQL SERVER IS RUNNING AND CHECK YOUR SQL SERVER REGISRATION
> PROPERTIES (BY RIGHT-CLICKING ON THE <my SQL Server> NODE) AND TRY AGAIN
> However, I can succesfully register by typing the IP Address.
> Can anyone help?
>
|||Hi all,
I can successfully ping my SQL server (with my SQL server name is the same
as my Server name).
It is quite impossible to use IP as my system (a lot of programs and
configure) has been developed and is using SQL server name for the SQL
connection.
BTW, I have many SQL server and only this SQL server got the "Cannot
generate SSPI content" problem. Any more hints ?
"Daniel Joskovski" wrote:

> Probably problem is with your DNS, on the computer on which SQL server is
> installed check computer name and primary DNS suffix.
> Regards,
> Daniel
> "jenny" <jenny@.discussions.microsoft.com> wrote in message
> news:B808753B-9601-4E94-9984-3C717EF093AA@.microsoft.com...
>
>
|||> It is quite impossible to use IP as my system (a lot of programs and
> configure) has been developed and is using SQL server name for the SQL
> connection.
(a) the name of the data source should not be hard-coded into programs. At
the very least, all of your applications should get this kind of global
parameter from a single, central location. In your current state, what are
you going to do when you change the SQL auth password? Or switch from SQL
auth to Windows auth? Or move the database to a server with a different
name?
(b) barring (a), have you seen my suggestion to add the server name -> IP
mapping in the client network utility on the workstations that can't connect
to this SQL Server by name?
http://www.aspfaq.com/
(Reverse address to reply.)
|||Hi Aaron,
Thanks first.
The SQL server name is not hardcode... It is stored in the configuration
file or database value. To be more accurate, now my system is working fine
by using the SQL Server Name except for the following cases:
- Register the SQL Server through Enterprise Manager
- Connect to the SQL Server through Query Analyzer
- Run osql command with connection typed with the SQL Server Name
Some of my predefined script are coded with the SQL Server Name and is
worked fine for other SQL Servers except the one I mentioned. I even got the
same problem when I connect the SQL Server on the same Server. (e.g. The SQL
Server A is installed in the Windows Server A.) However, I have one finding
that if I add the SQL Server IP entry in the "host" file, I can then solve
the above 3 problems. I wonder, is adding the host file the only
(appropriate) way to solve the problem ? Is there any other methods as I
only got one SQL Server having this problem. Thanks a lot again.
For more information, my SQL Server is running cluster, using NamePiped and
TCP/IP connection with port 1433.
For your option (b), I'll consider... But curious that why other SQL servers
of my system works without problem (they have similar settings during
installation)
"Aaron [SQL Server MVP]" wrote:

> (a) the name of the data source should not be hard-coded into programs. At
> the very least, all of your applications should get this kind of global
> parameter from a single, central location. In your current state, what are
> you going to do when you change the SQL auth password? Or switch from SQL
> auth to Windows auth? Or move the database to a server with a different
> name?
> (b) barring (a), have you seen my suggestion to add the server name -> IP
> mapping in the client network utility on the workstations that can't connect
> to this SQL Server by name?
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
|||It is possible to ping your server name and still have problems with DNS,
try to ping FQDN for example instead of Ping Stockholm, ping
Stockholm.nwtraders.msft or better check full name of computer on which is
SQL server installed.
Regards,
Daniel
"jenny" <jenny@.discussions.microsoft.com> wrote in message
news:952A3B38-2035-4D64-95FA-0CC2F0F2BB87@.microsoft.com...[vbcol=seagreen]
> Hi all,
> I can successfully ping my SQL server (with my SQL server name is the same
> as my Server name).
> It is quite impossible to use IP as my system (a lot of programs and
> configure) has been developed and is using SQL server name for the SQL
> connection.
> BTW, I have many SQL server and only this SQL server got the "Cannot
> generate SSPI content" problem. Any more hints ?
> "Daniel Joskovski" wrote:
is[vbcol=seagreen]
Advanced[vbcol=seagreen]
Enterprise[vbcol=seagreen]
REGISRATION[vbcol=seagreen]
AGAIN[vbcol=seagreen]