Microsoft SQL Server 2005 Express Edition Service Pack 2 Error Code: 0x2B22

Hi i tried to install the Microsoft SQL Server 2005 Express Edition Service Pack 2 but was unable to do so. I got an error message saying: Error Code: 0x2B22

I went through what the message said, but i was unable to solve the problem. Below is the summary of the problem. Please help me solve it.

Time: 05/19/2007 12:32:24.781
KB Number: KB921896
Machine: DET-NB0631262
OS Version: Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Package Language: 1033 (ENU)
Package Platform: x86
Package SP Level: 2
Package Version: 3042
Command-line parameters specified:
/quiet
/allinstances
Cluster Installation: No

**********************************************************************************
Prerequisites Check & Status
SQLSupport: Passed

**********************************************************************************
Products Detected Language Level Patch Level Platform Edition
Express Database Services (SQLEXPRESS) ENU RTM 2005.090.1399.00 x86 EXPRESS
Express Database Services (SQLExpress) ENU SP2 x86 EXPRESS

**********************************************************************************
Products Disqualified & Reason
Product Reason
Express Database Services (SQLEXPRESS) Unable to start service

**********************************************************************************
Processes Locking Files
Process Name Feature Type User Name PID

**********************************************************************************
Product Installation Status
Product : Express Database Services (SQLEXPRESS)
Product Version (Previous): 1399
Product Version (Final) :
Status : Not Applied
Log File :
SQL Express Features : SQL_Data_Files,SQL_Engine,SQL_Replication,SQL_SharedTools
Error Number : 11042
Error Description : Unable to start service
-
Product : Express Database Services (SQLExpress)
Product Version (Previous):
Product Version (Final) :
Status : Not Applied
Log File :
SQL Express Features : Client_Components,Connectivity,SDK
Error Number : 0
Error Description :
-

**********************************************************************************
Summary
Unable to start service
Exit Code Returned: 11042

For me, several attempts to install "Microsoft SQL Server 2005 Express Edition Service Pack 2" via MS-update get stuck. The progress bar doesn't budge after a long lunch.

Microsoft SQL Server 2005 Express Edition Service Pack 2 ..Failure

Windows Update Web Page indicates I have BOTH a
SUCCESS and FAILURE for
SQL Server 2005 Microsoft SQL Server 2005 Express Edition Service Pack 2 (KB 921896)
?Is it possible for my machine to have TWO DIFFERENT MS SQL Server Express installations? Is the problem real or some small ghost issue?
I do have a trial CD from Microsoft .. Visual Studio 2005 Team Suite.

Please note that this is what windows update indicates on the web page
duplicate lines are on the web page .. not a copy and paste mistake.

SQL Server 2005 Microsoft SQL Server 2005 Express Edition Service Pack 2 (KB 921896) Tuesday, March 13, 2007 Microsoft Update
SQL Server 2005 Microsoft SQL Server 2005 Express Edition Service Pack 2 (KB 921896) Tuesday, March 13, 2007 Microsoft Update

LINK FOLLOWED
Installation Failure
Error Code: 0x652
Try to install the update again, or request help from one of the following resources

I include the logfile since it seems to convey useful informations to SQL Express experienced.

summary.txt logfile
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Time: 03/13/2007 12:28:02.906
KB Number: KB921896
Machine: somejunk
OS Version: Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Package Language: 1033 (ENU)
Package Platform: x86
Package SP Level: 2
Package Version: 3042
Command-line parameters specified:
/quiet
/allinstances
Cluster Installation: No

**********************************************************************************
Prerequisites Check & Status
SQLSupport: Passed

**********************************************************************************
Products Detected Language Level Patch Level Platform Edition
Express Database Services (SQLEXPRESS) ENU SP2 2005.090.3042.00 x86 EXPRESS
Express Database Services (SQLExpress) ENU RTM x86 EXPRESS

**********************************************************************************
Products Disqualified & Reason
Product Reason

**********************************************************************************
Processes Locking Files
Process Name Feature Type User Name PID

**********************************************************************************
Product Installation Status
Product : Express Database Services (SQLEXPRESS)
Product Version (Previous): 3042
Product Version (Final) :
Status : Not Selected
Log File :
SQL Express Features : SQL_Data_Files,SQL_Engine,SQL_Replication,SQL_SharedTools
Error Number : 0
Error Description :
-
Product : Express Database Services (SQLExpress)
Product Version (Previous):
Product Version (Final) : 3042
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9Express_Hotfix_KB921896_SQLEXPR.EXE
SQL Express Features : Client_Components,Connectivity,SDK
Error Number : 0
Error Description :
-

**********************************************************************************
Summary
Success
Exit Code Returned: 0

did you get the resolved? I'm haveing the same issue.

Sean

|||Me too. It continually tries to install although AFAIK it IS installed.
|||

No I did not get this resolved.

I suppose this creates uncertainty for me and perhaps others.

Please excuse my late reply.

|||

This has failed to install twice already this morning, and I've got a third Automatic Update message, which will probably be the same MS SQL Server trying and failing to install. This has been going on for at least a month--though not with multiple attempts in a day.

I wish I knew whether this was simply noise or whether it's something I should focus on, but characteristically, it's hidden behind opaque names and failure messages. I often feel like I don't own the computer I paid for; I'm simply maintaining it for MS.

|||I am having this same issue also - continuously tries to update but says it can't - any help out there?

jn|||

I'm having the same problem,

Has anybody been able to resolve this, its anoying the heck out of me?

Abe

|||Are you running ACT! on your computer? I am and it took an ACT! technician to get it resolved. It only took a full week of effort. LOL Yes I am serious a full week! One of the things you might try is uninstalling the SQL Server 2005 and then letting automatic update reinstall it. jn|||I uninstalled SQL Server 2005, reinstalled it and I am still having this problem. This is bad.|||

I got the same problem but got it resolved.
Apparently some of the ms sql server services (NOT any Express service) like SQL server active directory helper, and the sql server browser were disabled on my machine. I put them on an "Automatic" startup type and the update worked fine.

I hope it will help any of you.

Pieter

|||My automatic update of Microsoft SQL Server 2005 Express Edition Service Pack 2 (KB 921896) keeps failing and I do not even use SQL Server. How do I get rid of this nuisance?|||Following the advice of the previous posts I simply set the sql server express and sql browser services to manual start up and started the services (previously there were disabled and not running). Then I installed the service pack and it worked. Thankx for the advice.
|||

What version of ACT! are you running. I just installed ACT! 2007 and now have this issue. During the install, it corrupted .Net Framework 2.0 and SQL Server. Now all the other apps like QuickBooks, and OneCare Live don't operate the same.

Thanks,

JN2

|||

I am also running Act!2007(9) - I started having problems when auotmatic update tried to install the upgrade to version 9.0.1.162. The best thing for you to do is call Act and tell them you are having an installation problem. They'll give you free support for installation issues. That's what I did and they finally corrected the issue by having a technician take over my computer remotely. They had to make a lot of changes to the system files and then manually unistall ACT to get it worked out. Then I had to download the trial version of Act from their website - which is always the most current version - and re register it. It was VERY time consuming. Act techies worked on it for over 4 hours on 3 different occasions! Hopefully for you they have this figured out. Good luck.

jn

|||

I feel your pain. I was on the phone with them (ACT Support) yesterday for 3hours 50minutes for the install. They crashed and deleted my .NET Framework, killed my security damaged QuickBooks (somehow) and then told me to call the other vendors to restore my data. I don't know why I put myself through so much pain with Sage.

Thanks for the reply on SQL Exp SP2. Today I have not received the update error warnings. But the day is young. Once I get a solution, I'll post it.

JN2

sql

Microsoft SQL Server 2005 Express Edition Service Pack 2 ..Failure

Windows Update Web Page indicates I have BOTH a
SUCCESS and FAILURE for
SQL Server 2005 Microsoft SQL Server 2005 Express Edition Service Pack 2 (KB 921896)
?Is it possible for my machine to have TWO DIFFERENT MS SQL Server Express installations? Is the problem real or some small ghost issue?
I do have a trial CD from Microsoft .. Visual Studio 2005 Team Suite.

Please note that this is what windows update indicates on the web page
duplicate lines are on the web page .. not a copy and paste mistake.

SQL Server 2005 Microsoft SQL Server 2005 Express Edition Service Pack 2 (KB 921896) Tuesday, March 13, 2007 Microsoft Update
SQL Server 2005 Microsoft SQL Server 2005 Express Edition Service Pack 2 (KB 921896) Tuesday, March 13, 2007 Microsoft Update

LINK FOLLOWED
Installation Failure
Error Code: 0x652
Try to install the update again, or request help from one of the following resources

I include the logfile since it seems to convey useful informations to SQL Express experienced.

summary.txt logfile
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Time: 03/13/2007 12:28:02.906
KB Number: KB921896
Machine: somejunk
OS Version: Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Package Language: 1033 (ENU)
Package Platform: x86
Package SP Level: 2
Package Version: 3042
Command-line parameters specified:
/quiet
/allinstances
Cluster Installation: No

**********************************************************************************
Prerequisites Check & Status
SQLSupport: Passed

**********************************************************************************
Products Detected Language Level Patch Level Platform Edition
Express Database Services (SQLEXPRESS) ENU SP2 2005.090.3042.00 x86 EXPRESS
Express Database Services (SQLExpress) ENU RTM x86 EXPRESS

**********************************************************************************
Products Disqualified & Reason
Product Reason

**********************************************************************************
Processes Locking Files
Process Name Feature Type User Name PID

**********************************************************************************
Product Installation Status
Product : Express Database Services (SQLEXPRESS)
Product Version (Previous): 3042
Product Version (Final) :
Status : Not Selected
Log File :
SQL Express Features : SQL_Data_Files,SQL_Engine,SQL_Replication,SQL_SharedTools
Error Number : 0
Error Description :
-
Product : Express Database Services (SQLExpress)
Product Version (Previous):
Product Version (Final) : 3042
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9Express_Hotfix_KB921896_SQLEXPR.EXE
SQL Express Features : Client_Components,Connectivity,SDK
Error Number : 0
Error Description :
-

**********************************************************************************
Summary
Success
Exit Code Returned: 0

did you get the resolved? I'm haveing the same issue.

Sean

|||Me too. It continually tries to install although AFAIK it IS installed.
|||

No I did not get this resolved.

I suppose this creates uncertainty for me and perhaps others.

Please excuse my late reply.

|||

This has failed to install twice already this morning, and I've got a third Automatic Update message, which will probably be the same MS SQL Server trying and failing to install. This has been going on for at least a month--though not with multiple attempts in a day.

I wish I knew whether this was simply noise or whether it's something I should focus on, but characteristically, it's hidden behind opaque names and failure messages. I often feel like I don't own the computer I paid for; I'm simply maintaining it for MS.

|||I am having this same issue also - continuously tries to update but says it can't - any help out there?

jn|||

I'm having the same problem,

Has anybody been able to resolve this, its anoying the heck out of me?

Abe

|||Are you running ACT! on your computer? I am and it took an ACT! technician to get it resolved. It only took a full week of effort. LOL Yes I am serious a full week! One of the things you might try is uninstalling the SQL Server 2005 and then letting automatic update reinstall it. jn|||I uninstalled SQL Server 2005, reinstalled it and I am still having this problem. This is bad.|||

I got the same problem but got it resolved.
Apparently some of the ms sql server services (NOT any Express service) like SQL server active directory helper, and the sql server browser were disabled on my machine. I put them on an "Automatic" startup type and the update worked fine.

I hope it will help any of you.

Pieter

|||My automatic update of Microsoft SQL Server 2005 Express Edition Service Pack 2 (KB 921896) keeps failing and I do not even use SQL Server. How do I get rid of this nuisance?|||Following the advice of the previous posts I simply set the sql server express and sql browser services to manual start up and started the services (previously there were disabled and not running). Then I installed the service pack and it worked. Thankx for the advice.
|||

What version of ACT! are you running. I just installed ACT! 2007 and now have this issue. During the install, it corrupted .Net Framework 2.0 and SQL Server. Now all the other apps like QuickBooks, and OneCare Live don't operate the same.

Thanks,

JN2

|||

I am also running Act!2007(9) - I started having problems when auotmatic update tried to install the upgrade to version 9.0.1.162. The best thing for you to do is call Act and tell them you are having an installation problem. They'll give you free support for installation issues. That's what I did and they finally corrected the issue by having a technician take over my computer remotely. They had to make a lot of changes to the system files and then manually unistall ACT to get it worked out. Then I had to download the trial version of Act from their website - which is always the most current version - and re register it. It was VERY time consuming. Act techies worked on it for over 4 hours on 3 different occasions! Hopefully for you they have this figured out. Good luck.

jn

|||

I feel your pain. I was on the phone with them (ACT Support) yesterday for 3hours 50minutes for the install. They crashed and deleted my .NET Framework, killed my security damaged QuickBooks (somehow) and then told me to call the other vendors to restore my data. I don't know why I put myself through so much pain with Sage.

Thanks for the reply on SQL Exp SP2. Today I have not received the update error warnings. But the day is young. Once I get a solution, I'll post it.

JN2

Microsoft SQL Server 2005 Express Edition Service Pack 2 ..Failure

Windows Update Web Page indicates I have BOTH a
SUCCESS and FAILURE for
SQL Server 2005 Microsoft SQL Server 2005 Express Edition Service Pack 2 (KB 921896)
?Is it possible for my machine to have TWO DIFFERENT MS SQL Server Express installations? Is the problem real or some small ghost issue?
I do have a trial CD from Microsoft .. Visual Studio 2005 Team Suite.

Please note that this is what windows update indicates on the web page
duplicate lines are on the web page .. not a copy and paste mistake.

SQL Server 2005 Microsoft SQL Server 2005 Express Edition Service Pack 2 (KB 921896) Tuesday, March 13, 2007 Microsoft Update
SQL Server 2005 Microsoft SQL Server 2005 Express Edition Service Pack 2 (KB 921896) Tuesday, March 13, 2007 Microsoft Update

LINK FOLLOWED
Installation Failure
Error Code: 0x652
Try to install the update again, or request help from one of the following resources

I include the logfile since it seems to convey useful informations to SQL Express experienced.

summary.txt logfile
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Time: 03/13/2007 12:28:02.906
KB Number: KB921896
Machine: somejunk
OS Version: Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Package Language: 1033 (ENU)
Package Platform: x86
Package SP Level: 2
Package Version: 3042
Command-line parameters specified:
/quiet
/allinstances
Cluster Installation: No

**********************************************************************************
Prerequisites Check & Status
SQLSupport: Passed

**********************************************************************************
Products Detected Language Level Patch Level Platform Edition
Express Database Services (SQLEXPRESS) ENU SP2 2005.090.3042.00 x86 EXPRESS
Express Database Services (SQLExpress) ENU RTM x86 EXPRESS

**********************************************************************************
Products Disqualified & Reason
Product Reason

**********************************************************************************
Processes Locking Files
Process Name Feature Type User Name PID

**********************************************************************************
Product Installation Status
Product : Express Database Services (SQLEXPRESS)
Product Version (Previous): 3042
Product Version (Final) :
Status : Not Selected
Log File :
SQL Express Features : SQL_Data_Files,SQL_Engine,SQL_Replication,SQL_SharedTools
Error Number : 0
Error Description :
-
Product : Express Database Services (SQLExpress)
Product Version (Previous):
Product Version (Final) : 3042
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9Express_Hotfix_KB921896_SQLEXPR.EXE
SQL Express Features : Client_Components,Connectivity,SDK
Error Number : 0
Error Description :
-

**********************************************************************************
Summary
Success
Exit Code Returned: 0

did you get the resolved? I'm haveing the same issue.

Sean

|||Me too. It continually tries to install although AFAIK it IS installed.|||

No I did not get this resolved.

I suppose this creates uncertainty for me and perhaps others.

Please excuse my late reply.

|||

This has failed to install twice already this morning, and I've got a third Automatic Update message, which will probably be the same MS SQL Server trying and failing to install. This has been going on for at least a month--though not with multiple attempts in a day.

I wish I knew whether this was simply noise or whether it's something I should focus on, but characteristically, it's hidden behind opaque names and failure messages. I often feel like I don't own the computer I paid for; I'm simply maintaining it for MS.

|||I am having this same issue also - continuously tries to update but says it can't - any help out there?

jn|||

I'm having the same problem,

Has anybody been able to resolve this, its anoying the heck out of me?

Abe

|||Are you running ACT! on your computer? I am and it took an ACT! technician to get it resolved. It only took a full week of effort. LOL Yes I am serious a full week! One of the things you might try is uninstalling the SQL Server 2005 and then letting automatic update reinstall it. jn|||I uninstalled SQL Server 2005, reinstalled it and I am still having this problem. This is bad.|||

I got the same problem but got it resolved.
Apparently some of the ms sql server services (NOT any Express service) like SQL server active directory helper, and the sql server browser were disabled on my machine. I put them on an "Automatic" startup type and the update worked fine.

I hope it will help any of you.

Pieter

|||My automatic update of Microsoft SQL Server 2005 Express Edition Service Pack 2 (KB 921896) keeps failing and I do not even use SQL Server. How do I get rid of this nuisance?|||Following the advice of the previous posts I simply set the sql server express and sql browser services to manual start up and started the services (previously there were disabled and not running). Then I installed the service pack and it worked. Thankx for the advice.|||

What version of ACT! are you running. I just installed ACT! 2007 and now have this issue. During the install, it corrupted .Net Framework 2.0 and SQL Server. Now all the other apps like QuickBooks, and OneCare Live don't operate the same.

Thanks,

JN2

|||

I am also running Act!2007(9) - I started having problems when auotmatic update tried to install the upgrade to version 9.0.1.162. The best thing for you to do is call Act and tell them you are having an installation problem. They'll give you free support for installation issues. That's what I did and they finally corrected the issue by having a technician take over my computer remotely. They had to make a lot of changes to the system files and then manually unistall ACT to get it worked out. Then I had to download the trial version of Act from their website - which is always the most current version - and re register it. It was VERY time consuming. Act techies worked on it for over 4 hours on 3 different occasions! Hopefully for you they have this figured out. Good luck.

jn

|||

I feel your pain. I was on the phone with them (ACT Support) yesterday for 3hours 50minutes for the install. They crashed and deleted my .NET Framework, killed my security damaged QuickBooks (somehow) and then told me to call the other vendors to restore my data. I don't know why I put myself through so much pain with Sage.

Thanks for the reply on SQL Exp SP2. Today I have not received the update error warnings. But the day is young. Once I get a solution, I'll post it.

JN2

Microsoft SQL Server 2005 Express Edition Service Pack 2 ..Failure

Windows Update Web Page indicates I have BOTH a
SUCCESS and FAILURE for
SQL Server 2005 Microsoft SQL Server 2005 Express Edition Service Pack 2 (KB 921896)
?Is it possible for my machine to have TWO DIFFERENT MS SQL Server Express installations? Is the problem real or some small ghost issue?
I do have a trial CD from Microsoft .. Visual Studio 2005 Team Suite.

Please note that this is what windows update indicates on the web page
duplicate lines are on the web page .. not a copy and paste mistake.

SQL Server 2005 Microsoft SQL Server 2005 Express Edition Service Pack 2 (KB 921896) Tuesday, March 13, 2007 Microsoft Update
SQL Server 2005 Microsoft SQL Server 2005 Express Edition Service Pack 2 (KB 921896) Tuesday, March 13, 2007 Microsoft Update

LINK FOLLOWED
Installation Failure
Error Code: 0x652
Try to install the update again, or request help from one of the following resources

I include the logfile since it seems to convey useful informations to SQL Express experienced.

summary.txt logfile
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Time: 03/13/2007 12:28:02.906
KB Number: KB921896
Machine: somejunk
OS Version: Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Package Language: 1033 (ENU)
Package Platform: x86
Package SP Level: 2
Package Version: 3042
Command-line parameters specified:
/quiet
/allinstances
Cluster Installation: No

**********************************************************************************
Prerequisites Check & Status
SQLSupport: Passed

**********************************************************************************
Products Detected Language Level Patch Level Platform Edition
Express Database Services (SQLEXPRESS) ENU SP2 2005.090.3042.00 x86 EXPRESS
Express Database Services (SQLExpress) ENU RTM x86 EXPRESS

**********************************************************************************
Products Disqualified & Reason
Product Reason

**********************************************************************************
Processes Locking Files
Process Name Feature Type User Name PID

**********************************************************************************
Product Installation Status
Product : Express Database Services (SQLEXPRESS)
Product Version (Previous): 3042
Product Version (Final) :
Status : Not Selected
Log File :
SQL Express Features : SQL_Data_Files,SQL_Engine,SQL_Replication,SQL_SharedTools
Error Number : 0
Error Description :
-
Product : Express Database Services (SQLExpress)
Product Version (Previous):
Product Version (Final) : 3042
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9Express_Hotfix_KB921896_SQLEXPR.EXE
SQL Express Features : Client_Components,Connectivity,SDK
Error Number : 0
Error Description :
-

**********************************************************************************
Summary
Success
Exit Code Returned: 0

did you get the resolved? I'm haveing the same issue.

Sean

|||Me too. It continually tries to install although AFAIK it IS installed.
|||

No I did not get this resolved.

I suppose this creates uncertainty for me and perhaps others.

Please excuse my late reply.

|||

This has failed to install twice already this morning, and I've got a third Automatic Update message, which will probably be the same MS SQL Server trying and failing to install. This has been going on for at least a month--though not with multiple attempts in a day.

I wish I knew whether this was simply noise or whether it's something I should focus on, but characteristically, it's hidden behind opaque names and failure messages. I often feel like I don't own the computer I paid for; I'm simply maintaining it for MS.

|||I am having this same issue also - continuously tries to update but says it can't - any help out there?

jn|||

I'm having the same problem,

Has anybody been able to resolve this, its anoying the heck out of me?

Abe

|||Are you running ACT! on your computer? I am and it took an ACT! technician to get it resolved. It only took a full week of effort. LOL Yes I am serious a full week! One of the things you might try is uninstalling the SQL Server 2005 and then letting automatic update reinstall it. jn|||I uninstalled SQL Server 2005, reinstalled it and I am still having this problem. This is bad.|||

I got the same problem but got it resolved.
Apparently some of the ms sql server services (NOT any Express service) like SQL server active directory helper, and the sql server browser were disabled on my machine. I put them on an "Automatic" startup type and the update worked fine.

I hope it will help any of you.

Pieter

|||My automatic update of Microsoft SQL Server 2005 Express Edition Service Pack 2 (KB 921896) keeps failing and I do not even use SQL Server. How do I get rid of this nuisance?|||Following the advice of the previous posts I simply set the sql server express and sql browser services to manual start up and started the services (previously there were disabled and not running). Then I installed the service pack and it worked. Thankx for the advice.
|||

What version of ACT! are you running. I just installed ACT! 2007 and now have this issue. During the install, it corrupted .Net Framework 2.0 and SQL Server. Now all the other apps like QuickBooks, and OneCare Live don't operate the same.

Thanks,

JN2

|||

I am also running Act!2007(9) - I started having problems when auotmatic update tried to install the upgrade to version 9.0.1.162. The best thing for you to do is call Act and tell them you are having an installation problem. They'll give you free support for installation issues. That's what I did and they finally corrected the issue by having a technician take over my computer remotely. They had to make a lot of changes to the system files and then manually unistall ACT to get it worked out. Then I had to download the trial version of Act from their website - which is always the most current version - and re register it. It was VERY time consuming. Act techies worked on it for over 4 hours on 3 different occasions! Hopefully for you they have this figured out. Good luck.

jn

|||

I feel your pain. I was on the phone with them (ACT Support) yesterday for 3hours 50minutes for the install. They crashed and deleted my .NET Framework, killed my security damaged QuickBooks (somehow) and then told me to call the other vendors to restore my data. I don't know why I put myself through so much pain with Sage.

Thanks for the reply on SQL Exp SP2. Today I have not received the update error warnings. But the day is young. Once I get a solution, I'll post it.

JN2

Microsoft SQL Server 2000 SP4 is open for Public Beta

Microsoft SQL Server 2000 SP4 is open for Public Beta Testing
Sign up to test drive the newest service pack for SQL Server 2000 give us
your feedback. SQL Server 2000 SP4 is now open for public beta testing.
Instructions on how to signup for this beta program are below.
SQL Server 2000 Service Pack 4
SQL Server 2000 Service Pack 4 (SP4) includes a roll-up of bug fixes, added
platform support for AMD64, and Intel Extended Platforms in WOW so you can
use 32-bit applications on 64-bit architectures. This is the first service
pack to service the 64-bit release of SQL Server. SP4 is suitable for all
SQL Server 2000 customers who want to update their existing installations to
incorporate all changes since SP3a.
Who should participate?
Customers who want to use their 32-bit applications on 64-bit
hardware should consider the SQL Server 2000 SP4 beta.
Customers who want to update to this latest SQL Server 2000
service pack level, SP4 should consider the SP4 beta.
Instructions for Signing up for the Beta
To sign up for Microsoft's beta program for SQL Server 2000 SP4, go to the
following link, http://www.microsoft.com/sql/evaluat...ominations.asp
This posting is provided "AS IS" with no warranties, and confers no rights.
And we'll be hosting a public chat on the contents of Service Pack 4 on
February 15th at 2pm Pacific Time. It's listed at
http://www.microsoft.com/technet/com...s/default.mspx
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tara Nerurkar" <a-tarane@.online.microsoft.com> wrote in message
news:%23j1%23yWyAFHA.3836@.tk2msftngp13.phx.gbl...
> Microsoft SQL Server 2000 SP4 is open for Public Beta Testing
>
> Sign up to test drive the newest service pack for SQL Server 2000 give us
> your feedback. SQL Server 2000 SP4 is now open for public beta testing.
> Instructions on how to signup for this beta program are below.
>
> SQL Server 2000 Service Pack 4
>
> SQL Server 2000 Service Pack 4 (SP4) includes a roll-up of bug fixes,
> added platform support for AMD64, and Intel Extended Platforms in WOW so
> you can use 32-bit applications on 64-bit architectures. This is the first
> service pack to service the 64-bit release of SQL Server. SP4 is suitable
> for all SQL Server 2000 customers who want to update their existing
> installations to incorporate all changes since SP3a.
>
> Who should participate?
> Customers who want to use their 32-bit applications on 64-bit
> hardware should consider the SQL Server 2000 SP4 beta.
> Customers who want to update to this latest SQL Server 2000
> service pack level, SP4 should consider the SP4 beta.
>
>
> Instructions for Signing up for the Beta
> To sign up for Microsoft's beta program for SQL Server 2000 SP4, go to the
> following link,
> http://www.microsoft.com/sql/evaluat...ominations.asp
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
sql

Microsoft Search service vulnerabilities

I am working on a "best practices" document for my company and came across
the suggestion to disable any unnecessary SQL Server services. We do not us
e
full-text search so we have no need for the service. However, I would like
to be able to provide reasons why this service should be disabled. I've
searched for vulnerabilites related to the Microsoft Search service and have
come up empty. Does anyone know of any vulnerabilities?
Thanks!I'm not aware of any vulnerabilities but it's still a good idea to shut it
down if you know you are not going to use it. That way, if someone comes up
with an attack later, you aren't at risk. Reducing the surface that an
attacker can attack to only what's required is always a good idea.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"cltdba" <cltdba@.discussions.microsoft.com> wrote in message
news:14FA55C3-C274-458F-B7A8-ABB90EAD3E2C@.microsoft.com...
>I am working on a "best practices" document for my company and came across
> the suggestion to disable any unnecessary SQL Server services. We do not
> use
> full-text search so we have no need for the service. However, I would
> like
> to be able to provide reasons why this service should be disabled. I've
> searched for vulnerabilites related to the Microsoft Search service and
> have
> come up empty. Does anyone know of any vulnerabilities?
> Thanks!

Microsoft search service kills SQL 2000 server

Hi all,

This may be more of a Sharepoint or server question but I thought I would post it here to start off with. I have an installation of SQL 2000 SP4 and sharepoint services 2003 all on one server. For example the SQL 2000 (SP4), sharepoint and its indexes all on the one server (HP G4 DL380). I have installed the index service and the full text services on the SQL server then configured searching in sharepoint. The search worked fine for about a year until one day the server started randomly hanging for no apparent reason. After a hard reboot the server would begin to hand again after around 2-3 minutes of being online, sometimes less. After lots of problem shooting I nailed it down to being the Microsoft search service that caused the issue. Basically if I set this service to manual and boot I have no problem. As soon as I start the service the server will start to hang about 2-3 minutes later.

I tried this again last night after trying some fixed and got the same result. The only error I get are in the application log which are about 4 of these with different file types.

One or more documents stored in image columns with extension “X” did not get full-textindexed because loading the filter failed with error '0x1'

The server continues to log messages while it is hanging and you can ping the server but you can not access sharepoint, remote in to the server, you can login locally but as soon as you try anything like bring up the start menu all resources will freeze up. During this time there is no disk activity and the CPU usage is 1-3% and mem usage is low.

Can anyone suggest anything to fix this problem so I can start the Microsoft search service and use search in sharepoint again.

Thanks,

LS

I've moved this into the general engine thread since the question is in no way related to Broker.|||Thanks. Sorry for the misplacement.sql

Microsoft Search Service Fails on Boot!

I have been having a problem with the microsoft sesarch service failing on
boot up. All that I get from the event logs is: Event ID: 7009-"Timeout
(30000 milliseconds) waiting for the Microsoft Search Service to connect."
and Event ID: 7000-"The Microsoft Search service failed to start due to the
following error: The service did not respond to the start or control request
in a timely fashion.". The box has SQL 2000 w/SP3a on it and is running
Small business server 2003. I have reregistered several of the .dll files
associated with the search service. If I manually start after being logged
in it starts fine with no errors. Is there any type of detailed debugging
that can be run along side this? I have already tried posting in the SBS
Newsgroup with no success. Any help would be greatly appreciated.
Thanks,
Russ GrotewoldRuss,
See my reply in the fulltext newsgroup.
Thanks,
John
"Russ" <Russ@.alias.com> wrote in message
news:#$SbbTuzDHA.2456@.TK2MSFTNGP10.phx.gbl...
> I have been having a problem with the microsoft sesarch service failing on
> boot up. All that I get from the event logs is: Event ID: 7009-"Timeout
> (30000 milliseconds) waiting for the Microsoft Search Service to connect."
> and Event ID: 7000-"The Microsoft Search service failed to start due to
the
> following error: The service did not respond to the start or control
request
> in a timely fashion.". The box has SQL 2000 w/SP3a on it and is running
> Small business server 2003. I have reregistered several of the .dll files
> associated with the search service. If I manually start after being logged
> in it starts fine with no errors. Is there any type of detailed debugging
> that can be run along side this? I have already tried posting in the SBS
> Newsgroup with no success. Any help would be greatly appreciated.
> Thanks,
> Russ Grotewold
>

Microsoft Search service can't start after SQL2005 installation!

Hi
The version numbers in your post seem to be inconsistent!
I assume that you have removed SQL 2000 and only have a named instance of
SQL 2005. If you want the instance of SQL 2005 to be the default instance you
will need to install SQL 2005 again anyhow, and possibly remove the named
instance of SQL 2005 if it is not wanted. If you want to reinstall the
current named instance you can install it from the command line with the
REINSTALLMODE=OMUS option see
http://msdn2.microsoft.com/en-us/library/ms144259.aspx#reinstallmode
REINSTALLMODE=O will replace the missing file, but it would probably not do
any harm having the other options.
John
"PG" wrote:

> Hi everybody I had a server with SQL2000 Standard on Server2003 Standard
> working, but I was told to uninstall and install SQl2005 Standard, but now
> when I start the server I receive an error saying that a service could not
> start, I went to see what service the server was talking about and it was
> the Microsoft Search service. The error says that the specified file can't
> be found, so I went to "C:\Program Files\Common
> Files\System\MSSearch\Bin\mssearch.exe" and the file mssearch.exe is
> missing!!!
> Was it the uninstall of SQL2000 that screwed this up, or the installation of
> SQL2005?
> I dont know what to do from here, what can I do?...Any help would be
> appreciated.
> Thanks in advance..
>
>
Hi
"PG" wrote:

> I'm sorry if I didn't make myself clear, what I did was uninstall SQL2000
> and afterwards install SQL2005 on the same machine (WindowsServer2003).
>
mssearch.exe is for SQL 2000 if you want to reinstall it see
http://support.microsoft.com/default.aspx/kb/827449 but if you have SQL 2005
you should see an instance of SQL Server FullText Search (MSSQLSERVER) in
your services which runs "C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Binn\msftesql.exe". The article also shows how to
remove it.
John
|||John Bell from BCSI?
Jason

Quote:

Originally Posted by John Bell

Hi
"PG" wrote:

> I'm sorry if I didn't make myself clear, what I did was uninstall SQL2000
> and afterwards install SQL2005 on the same machine (WindowsServer2003).
>
mssearch.exe is for SQL 2000 if you want to reinstall it see
http://support.microsoft.com/default.aspx/kb/827449 but if you have SQL 2005
you should see an instance of SQL Server FullText Search (MSSQLSERVER) in
your services which runs "C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Binn\msftesql.exe". The article also shows how to
remove it.
John

Microsoft Search service can't start after SQL2005 installation!

Hi everybody I had a server with SQL2000 Standard on Server2003 Standard
working, but I was told to uninstall and install SQl2005 Standard, but now
when I start the server I receive an error saying that a service could not
start, I went to see what service the server was talking about and it was
the Microsoft Search service. The error says that the specified file can't
be found, so I went to "C:\Program Files\Common
Files\System\MSSearch\Bin\mssearch.exe" and the file mssearch.exe is
missing!!!
Was it the uninstall of SQL2000 that screwed this up, or the installation of
SQL2005?
I dont know what to do from here, what can I do?...Any help would be
appreciated.
Thanks in advance..Hi
The version numbers in your post seem to be inconsistent!
I assume that you have removed SQL 2000 and only have a named instance of
SQL 2005. If you want the instance of SQL 2005 to be the default instance you
will need to install SQL 2005 again anyhow, and possibly remove the named
instance of SQL 2005 if it is not wanted. If you want to reinstall the
current named instance you can install it from the command line with the
REINSTALLMODE=OMUS option see
http://msdn2.microsoft.com/en-us/library/ms144259.aspx#reinstallmode
REINSTALLMODE=O will replace the missing file, but it would probably not do
any harm having the other options.
John
"PG" wrote:
> Hi everybody I had a server with SQL2000 Standard on Server2003 Standard
> working, but I was told to uninstall and install SQl2005 Standard, but now
> when I start the server I receive an error saying that a service could not
> start, I went to see what service the server was talking about and it was
> the Microsoft Search service. The error says that the specified file can't
> be found, so I went to "C:\Program Files\Common
> Files\System\MSSearch\Bin\mssearch.exe" and the file mssearch.exe is
> missing!!!
> Was it the uninstall of SQL2000 that screwed this up, or the installation of
> SQL2005?
> I dont know what to do from here, what can I do?...Any help would be
> appreciated.
> Thanks in advance..
>
>|||I'm sorry if I didn't make myself clear, what I did was uninstall SQL2000
and afterwards install SQL2005 on the same machine (WindowsServer2003).
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:82ECF7F8-D4A2-4213-9A68-76656BC41C79@.microsoft.com...
> Hi
> The version numbers in your post seem to be inconsistent!
> I assume that you have removed SQL 2000 and only have a named instance of
> SQL 2005. If you want the instance of SQL 2005 to be the default instance
> you
> will need to install SQL 2005 again anyhow, and possibly remove the named
> instance of SQL 2005 if it is not wanted. If you want to reinstall the
> current named instance you can install it from the command line with the
> REINSTALLMODE=OMUS option see
> http://msdn2.microsoft.com/en-us/library/ms144259.aspx#reinstallmode
> REINSTALLMODE=O will replace the missing file, but it would probably not
> do
> any harm having the other options.
> John
> "PG" wrote:
>> Hi everybody I had a server with SQL2000 Standard on Server2003 Standard
>> working, but I was told to uninstall and install SQl2005 Standard, but
>> now
>> when I start the server I receive an error saying that a service could
>> not
>> start, I went to see what service the server was talking about and it was
>> the Microsoft Search service. The error says that the specified file
>> can't
>> be found, so I went to "C:\Program Files\Common
>> Files\System\MSSearch\Bin\mssearch.exe" and the file mssearch.exe is
>> missing!!!
>> Was it the uninstall of SQL2000 that screwed this up, or the installation
>> of
>> SQL2005?
>> I dont know what to do from here, what can I do?...Any help would be
>> appreciated.
>> Thanks in advance..
>>|||Hi
"PG" wrote:
> I'm sorry if I didn't make myself clear, what I did was uninstall SQL2000
> and afterwards install SQL2005 on the same machine (WindowsServer2003).
>
mssearch.exe is for SQL 2000 if you want to reinstall it see
http://support.microsoft.com/default.aspx/kb/827449 but if you have SQL 2005
you should see an instance of SQL Server FullText Search (MSSQLSERVER) in
your services which runs "C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Binn\msftesql.exe". The article also shows how to
remove it.
John

Microsoft Search service can't start after SQL2005 installation!

Hi everybody I had a server with SQL2000 Standard on Server2003 Standard
working, but I was told to uninstall and install SQl2005 Standard, but now
when I start the server I receive an error saying that a service could not
start, I went to see what service the server was talking about and it was
the Microsoft Search service. The error says that the specified file can't
be found, so I went to "C:\Program Files\Common
Files\System\MSSearch\Bin\mssearch.exe" and the file mssearch.exe is
missing!!!
Was it the uninstall of SQL2000 that screwed this up, or the installation of
SQL2005?
I dont know what to do from here, what can I do?...Any help would be
appreciated.
Thanks in advance..Hi
The version numbers in your post seem to be inconsistent!
I assume that you have removed SQL 2000 and only have a named instance of
SQL 2005. If you want the instance of SQL 2005 to be the default instance yo
u
will need to install SQL 2005 again anyhow, and possibly remove the named
instance of SQL 2005 if it is not wanted. If you want to reinstall the
current named instance you can install it from the command line with the
REINSTALLMODE=OMUS option see
http://msdn2.microsoft.com/en-us/li...x#reinstallmode
REINSTALLMODE=O will replace the missing file, but it would probably not do
any harm having the other options.
John
"PG" wrote:

> Hi everybody I had a server with SQL2000 Standard on Server2003 Standard
> working, but I was told to uninstall and install SQl2005 Standard, but now
> when I start the server I receive an error saying that a service could not
> start, I went to see what service the server was talking about and it was
> the Microsoft Search service. The error says that the specified file can't
> be found, so I went to "C:\Program Files\Common
> Files\System\MSSearch\Bin\mssearch.exe" and the file mssearch.exe is
> missing!!!
> Was it the uninstall of SQL2000 that screwed this up, or the installation
of
> SQL2005?
> I dont know what to do from here, what can I do?...Any help would be
> appreciated.
> Thanks in advance..
>
>|||I'm sorry if I didn't make myself clear, what I did was uninstall SQL2000
and afterwards install SQL2005 on the same machine (WindowsServer2003).
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:82ECF7F8-D4A2-4213-9A68-76656BC41C79@.microsoft.com...[vbcol=seagreen]
> Hi
> The version numbers in your post seem to be inconsistent!
> I assume that you have removed SQL 2000 and only have a named instance of
> SQL 2005. If you want the instance of SQL 2005 to be the default instance
> you
> will need to install SQL 2005 again anyhow, and possibly remove the named
> instance of SQL 2005 if it is not wanted. If you want to reinstall the
> current named instance you can install it from the command line with the
> REINSTALLMODE=OMUS option see
> http://msdn2.microsoft.com/en-us/li...x#reinstallmode
> REINSTALLMODE=O will replace the missing file, but it would probably not
> do
> any harm having the other options.
> John
> "PG" wrote:
>

'Microsoft Search service cannot be administered under the present user error' SP3

Hi,
We have SQL Server private installation on which we are developing an
application and public installation on whict we will be deploying the
application. All instances have run Windows 2003 Enterprise Edition with SQL
2000 SP3. However, the public installation MS Search is not functioning
correctly. Basically it will not full-text indeed databases and produces
the following error
1> exec sp_fulltext_database 'enable'
2> go
(1 row affected)
Msg 7635, Level 16, State 1, Server SIMP001, Procedure sp_fulltext_database,
Lin
e 46
The Microsoft Search service cannot be administered under the present user
account
Now, we have tried many things to try and solve this error, mainly based on
search newsgroups, which are itemized below:
1 Reboot System and reexecute sp_
2 Complete reinstall of SQL on system, then reapplication of SP3
3 Same as above (2) but reapply SP3a
4 Remove SQL Server installation subkey in order that can reinstall
full-text search only, then reapply SP3
5 Check from keys under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\A pplications\ to make sure
SQL Server was there. It wasn't, removed SQL subkey and reinstalled,
re-adding full-text search as an option (to re-install full-text) then
reapplied SP3
6 Try reinstall, but do not reapply SP3 until have full-text enabled the
database.
None of the above worked. We still have a none functioning mssearch and
full-text disabled database on the system.
We have even tried enabling on a blank database. This does not work either.
PLEASE HELP! Getting desperate as the whole application depends on having
search ability.
Thanks
Oz
Oz,
In addition to the many things you tried below... a couple of things
specific to MSSearch and the MSSQLServer services...
1. Is the MSSearch service started and running under the System
(LocalSystem) account? If not, then change it to LocalSystem and stop and
re-start this service.
2. Have you or anyone else change the MSSQLServer account &/or password via
Win2K's Component service? IF so, then you MUST re-change the change via the
Enterprise Manager's server property security tab as this is the only place
where the two services security are kept in sync. See KB article 277549
(Q277549) PRB: Unable to Build Full-Text Catalog After You Modify
MSSQLServer Logon Account Through [NT4.0) Control Panel [or Win2K Component
Services] at http://support.microsoft.com/default...B;EN-US;277549
3. Have you or anyone else removed or modified the BUILTIN\Administrator
login on this server? If so, you MUST either re-add it with all of it's
normal default rights, especially sysadmin rights and with the default
database as master and the default language of English or use the following
T-SQL code to add the correct permissions:
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
Additionally, but not necessarily related to the error in the subject line,
has this server ever been upgrade from SQL Server 7.0 or is this SQL Server
2000 a "named instance" with a default installation of SQL Server 7.0? As
this might be related to a post-SP3 bug. See KB 814035 (Q814035) FIX: A
Full-Text Population Fails After You Apply SQL Server 2000 Service Pack 3
at:
http://support.microsoft.com/default...b;en-us;814035 (80004002 -
No such interface supported)
Regards,
John
"Oz" <Oz(no_spam)@.nospam.com> wrote in message
news:eytulHGNEHA.2468@.TK2MSFTNGP11.phx.gbl...
> Hi,
> We have SQL Server private installation on which we are developing an
> application and public installation on whict we will be deploying the
> application. All instances have run Windows 2003 Enterprise Edition with
SQL
> 2000 SP3. However, the public installation MS Search is not functioning
> correctly. Basically it will not full-text indeed databases and produces
> the following error
> 1> exec sp_fulltext_database 'enable'
> 2> go
> (1 row affected)
> Msg 7635, Level 16, State 1, Server SIMP001, Procedure
sp_fulltext_database,
> Lin
> e 46
> The Microsoft Search service cannot be administered under the present user
> account
> Now, we have tried many things to try and solve this error, mainly based
on
> search newsgroups, which are itemized below:
> 1 Reboot System and reexecute sp_
> 2 Complete reinstall of SQL on system, then reapplication of SP3
> 3 Same as above (2) but reapply SP3a
> 4 Remove SQL Server installation subkey in order that can reinstall
> full-text search only, then reapply SP3
> 5 Check from keys under
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\A pplications\ to make
sure
> SQL Server was there. It wasn't, removed SQL subkey and reinstalled,
> re-adding full-text search as an option (to re-install full-text) then
> reapplied SP3
> 6 Try reinstall, but do not reapply SP3 until have full-text enabled the
> database.
> None of the above worked. We still have a none functioning mssearch and
> full-text disabled database on the system.
> We have even tried enabling on a blank database. This does not work
either.
> PLEASE HELP! Getting desperate as the whole application depends on having
> search ability.
> Thanks
> Oz
>
|||Hi John,
Thanks for replying to my message. Unfortunately i forgot to add these items
as items i had also tried.
- Have not modified Administrator account, but i ran the SQL script anyway.
- MS Search has always been running as local system
- Changed the security settings using Ent Mgr to Local System and back again
to the user account.
- SQL account is not a local administrator. Tried adding it Administrators,
still, no joy.
Thanks
O
"John Kane" <jt-kane@.comcast.net> wrote in message
news:eaSiYlKNEHA.2976@.TK2MSFTNGP10.phx.gbl...
> Oz,
> In addition to the many things you tried below... a couple of things
> specific to MSSearch and the MSSQLServer services...
> 1. Is the MSSearch service started and running under the System
> (LocalSystem) account? If not, then change it to LocalSystem and stop and
> re-start this service.
> 2. Have you or anyone else change the MSSQLServer account &/or password
via
> Win2K's Component service? IF so, then you MUST re-change the change via
the
> Enterprise Manager's server property security tab as this is the only
place
> where the two services security are kept in sync. See KB article 277549
> (Q277549) PRB: Unable to Build Full-Text Catalog After You Modify
> MSSQLServer Logon Account Through [NT4.0) Control Panel [or Win2K
Component
> Services] at
http://support.microsoft.com/default...B;EN-US;277549
> 3. Have you or anyone else removed or modified the BUILTIN\Administrator
> login on this server? If so, you MUST either re-add it with all of it's
> normal default rights, especially sysadmin rights and with the default
> database as master and the default language of English or use the
following
> T-SQL code to add the correct permissions:
> 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
> Additionally, but not necessarily related to the error in the subject
line,
> has this server ever been upgrade from SQL Server 7.0 or is this SQL
Server[vbcol=seagreen]
> 2000 a "named instance" with a default installation of SQL Server 7.0? As
> this might be related to a post-SP3 bug. See KB 814035 (Q814035) FIX: A
> Full-Text Population Fails After You Apply SQL Server 2000 Service Pack 3
> at:
> http://support.microsoft.com/default...b;en-us;814035 (80004002 -
> No such interface supported)
> Regards,
> John
>
> "Oz" <Oz(no_spam)@.nospam.com> wrote in message
> news:eytulHGNEHA.2468@.TK2MSFTNGP11.phx.gbl...
> SQL
produces[vbcol=seagreen]
> sp_fulltext_database,
user[vbcol=seagreen]
> on
> sure
> either.
having
>
|||John
Is there a log file somewhere that i could try and see what precisely is
causing this problem.
Thanks
"John Kane" <jt-kane@.comcast.net> wrote in message
news:eaSiYlKNEHA.2976@.TK2MSFTNGP10.phx.gbl...
> Oz,
> In addition to the many things you tried below... a couple of things
> specific to MSSearch and the MSSQLServer services...
> 1. Is the MSSearch service started and running under the System
> (LocalSystem) account? If not, then change it to LocalSystem and stop and
> re-start this service.
> 2. Have you or anyone else change the MSSQLServer account &/or password
via
> Win2K's Component service? IF so, then you MUST re-change the change via
the
> Enterprise Manager's server property security tab as this is the only
place
> where the two services security are kept in sync. See KB article 277549
> (Q277549) PRB: Unable to Build Full-Text Catalog After You Modify
> MSSQLServer Logon Account Through [NT4.0) Control Panel [or Win2K
Component
> Services] at
http://support.microsoft.com/default...B;EN-US;277549
> 3. Have you or anyone else removed or modified the BUILTIN\Administrator
> login on this server? If so, you MUST either re-add it with all of it's
> normal default rights, especially sysadmin rights and with the default
> database as master and the default language of English or use the
following
> T-SQL code to add the correct permissions:
> 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
> Additionally, but not necessarily related to the error in the subject
line,
> has this server ever been upgrade from SQL Server 7.0 or is this SQL
Server[vbcol=seagreen]
> 2000 a "named instance" with a default installation of SQL Server 7.0? As
> this might be related to a post-SP3 bug. See KB 814035 (Q814035) FIX: A
> Full-Text Population Fails After You Apply SQL Server 2000 Service Pack 3
> at:
> http://support.microsoft.com/default...b;en-us;814035 (80004002 -
> No such interface supported)
> Regards,
> John
>
> "Oz" <Oz(no_spam)@.nospam.com> wrote in message
> news:eytulHGNEHA.2468@.TK2MSFTNGP11.phx.gbl...
> SQL
produces[vbcol=seagreen]
> sp_fulltext_database,
user[vbcol=seagreen]
> on
> sure
> either.
having
>
|||You're welcome, Oz,
Yes, there are MSSearch gatherer log files located under
\FTDATA\SQLServer\GatherLogs\ that can be "read" using gthrlog.vbs, however,
they most likely will have the same error (MSSearch service cannot be
admin..), so they are of little value in this issue.
Is this SQL Server installed on a Domain Controller (DC) server or is the
MSSQLServer startup account the DOMAIN\Administrator account?
While this should work, it's been my experience that with Full-Text Search
(FTS) on DC's that this is a problem for the "Microsoft Search" (MSSearch)
service. If you are using the DOMAIN\Administrator account, create a local
machine account and add this account into the DC's Administrator Group and
then change the MSSQLServer startup account in the Enterprise Manager (this
change MUST be done here) server's security tab. This should stop and
restart SQL Server and if all is successfully completed, FTS on a DC
*should* work...
Regards,
John
"Oz" <Oz(no_spam)@.nospam.com> wrote in message
news:OqqhS1ONEHA.3348@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> John
> Is there a log file somewhere that i could try and see what precisely is
> causing this problem.
> Thanks
> "John Kane" <jt-kane@.comcast.net> wrote in message
> news:eaSiYlKNEHA.2976@.TK2MSFTNGP10.phx.gbl...
and[vbcol=seagreen]
> via
> the
> place
> Component
> http://support.microsoft.com/default...B;EN-US;277549
BUILTIN\Administrator[vbcol=seagreen]
> following
> line,
> Server
As[vbcol=seagreen]
3[vbcol=seagreen]
(80004002 -[vbcol=seagreen]
with[vbcol=seagreen]
functioning[vbcol=seagreen]
> produces
> user
based[vbcol=seagreen]
the[vbcol=seagreen]
and
> having
>
|||Hi John,
Yes, it is running on a DC. I will try your suggestions and see if it makes
any difference.
Thanks
Oz
"John Kane" <jt-kane@.comcast.net> wrote in message
news:OeY1j4QNEHA.2144@.TK2MSFTNGP10.phx.gbl...
> You're welcome, Oz,
> Yes, there are MSSearch gatherer log files located under
> \FTDATA\SQLServer\GatherLogs\ that can be "read" using gthrlog.vbs,
however,
> they most likely will have the same error (MSSearch service cannot be
> admin..), so they are of little value in this issue.
> Is this SQL Server installed on a Domain Controller (DC) server or is the
> MSSQLServer startup account the DOMAIN\Administrator account?
> While this should work, it's been my experience that with Full-Text Search
> (FTS) on DC's that this is a problem for the "Microsoft Search" (MSSearch)
> service. If you are using the DOMAIN\Administrator account, create a local
> machine account and add this account into the DC's Administrator Group and
> then change the MSSQLServer startup account in the Enterprise Manager
(this[vbcol=seagreen]
> change MUST be done here) server's security tab. This should stop and
> restart SQL Server and if all is successfully completed, FTS on a DC
> *should* work...
> Regards,
> John
>
> "Oz" <Oz(no_spam)@.nospam.com> wrote in message
> news:OqqhS1ONEHA.3348@.TK2MSFTNGP09.phx.gbl...
> and
password[vbcol=seagreen]
via[vbcol=seagreen]
277549[vbcol=seagreen]
> BUILTIN\Administrator
it's[vbcol=seagreen]
> As
A[vbcol=seagreen]
Pack[vbcol=seagreen]
> 3
> (80004002 -
an[vbcol=seagreen]
the[vbcol=seagreen]
> with
> functioning
present[vbcol=seagreen]
> based
make[vbcol=seagreen]
then
> the
> and
>
|||Hi John,
It's just occurred, to me, there is nothing in those directories as i cannot
enable the database for full-text!
"John Kane" <jt-kane@.comcast.net> wrote in message
news:OeY1j4QNEHA.2144@.TK2MSFTNGP10.phx.gbl...
> You're welcome, Oz,
> Yes, there are MSSearch gatherer log files located under
> \FTDATA\SQLServer\GatherLogs\ that can be "read" using gthrlog.vbs,
however,
> they most likely will have the same error (MSSearch service cannot be
> admin..), so they are of little value in this issue.
> Is this SQL Server installed on a Domain Controller (DC) server or is the
> MSSQLServer startup account the DOMAIN\Administrator account?
> While this should work, it's been my experience that with Full-Text Search
> (FTS) on DC's that this is a problem for the "Microsoft Search" (MSSearch)
> service. If you are using the DOMAIN\Administrator account, create a local
> machine account and add this account into the DC's Administrator Group and
> then change the MSSQLServer startup account in the Enterprise Manager
(this[vbcol=seagreen]
> change MUST be done here) server's security tab. This should stop and
> restart SQL Server and if all is successfully completed, FTS on a DC
> *should* work...
> Regards,
> John
>
> "Oz" <Oz(no_spam)@.nospam.com> wrote in message
> news:OqqhS1ONEHA.3348@.TK2MSFTNGP09.phx.gbl...
> and
password[vbcol=seagreen]
via[vbcol=seagreen]
277549[vbcol=seagreen]
> BUILTIN\Administrator
it's[vbcol=seagreen]
> As
A[vbcol=seagreen]
Pack[vbcol=seagreen]
> 3
> (80004002 -
an[vbcol=seagreen]
the[vbcol=seagreen]
> with
> functioning
present[vbcol=seagreen]
> based
make[vbcol=seagreen]
then
> the
> and
>
|||Also John,
I have always been running a local (i.e. Domain user) account as the SQL
account, althought it is not a member of the administrators group. This is
one of the things i tried (adding it to the admins group), but didn't help.
Thanks
"John Kane" <jt-kane@.comcast.net> wrote in message
news:OeY1j4QNEHA.2144@.TK2MSFTNGP10.phx.gbl...
> You're welcome, Oz,
> Yes, there are MSSearch gatherer log files located under
> \FTDATA\SQLServer\GatherLogs\ that can be "read" using gthrlog.vbs,
however,
> they most likely will have the same error (MSSearch service cannot be
> admin..), so they are of little value in this issue.
> Is this SQL Server installed on a Domain Controller (DC) server or is the
> MSSQLServer startup account the DOMAIN\Administrator account?
> While this should work, it's been my experience that with Full-Text Search
> (FTS) on DC's that this is a problem for the "Microsoft Search" (MSSearch)
> service. If you are using the DOMAIN\Administrator account, create a local
> machine account and add this account into the DC's Administrator Group and
> then change the MSSQLServer startup account in the Enterprise Manager
(this[vbcol=seagreen]
> change MUST be done here) server's security tab. This should stop and
> restart SQL Server and if all is successfully completed, FTS on a DC
> *should* work...
> Regards,
> John
>
> "Oz" <Oz(no_spam)@.nospam.com> wrote in message
> news:OqqhS1ONEHA.3348@.TK2MSFTNGP09.phx.gbl...
> and
password[vbcol=seagreen]
via[vbcol=seagreen]
277549[vbcol=seagreen]
> BUILTIN\Administrator
it's[vbcol=seagreen]
> As
A[vbcol=seagreen]
Pack[vbcol=seagreen]
> 3
> (80004002 -
an[vbcol=seagreen]
the[vbcol=seagreen]
> with
> functioning
present[vbcol=seagreen]
> based
make[vbcol=seagreen]
then
> the
> and
>
|||Ok,
Will do.
I'm talking about the FTData directory. It was there, but it was blank. So
i couldn't check for gatherer files etc.
Thanks
"John Kane" <jt-kane@.comcast.net> wrote in message
news:uBU3C6pNEHA.1340@.TK2MSFTNGP12.phx.gbl...
> You're welcome, Oz,
> When you said "It's just occurred, to me, there is nothing in those
> directories as i cannot enable the database for full-text!"
> What directories were you referring to?
> Could you change the MSSQLServer service startup account to the system
> account (LocalSystem) via the Enterprise Manager's server property
security
> tab? This should stop and restart SQL Server and attempt to FT-enable the
> Pubs database and the authors table and let me know the result of the
that?[vbcol=seagreen]
> Thanks,
> John
>
> "Oz" <Oz(no_spam)@.nospam.com> wrote in message
> news:usHda6lNEHA.3944@.tk2msftngp13.phx.gbl...
> is
> help.
> the
> Search
> (MSSearch)
> local
> and
precisely[vbcol=seagreen]
> is
things[vbcol=seagreen]
> stop
change[vbcol=seagreen]
> only
> default
> subject
SQL[vbcol=seagreen]
> 7.0?
> FIX:
developing[vbcol=seagreen]
deploying[vbcol=seagreen]
> Edition
mainly[vbcol=seagreen]
> reinstall
to[vbcol=seagreen]
> reinstalled,
full-text)[vbcol=seagreen]
> enabled
> mssearch
> work
on
>
|||Identical error on pubs database John.
Thanks
"John Kane" <jt-kane@.comcast.net> wrote in message
news:uBU3C6pNEHA.1340@.TK2MSFTNGP12.phx.gbl...
> You're welcome, Oz,
> When you said "It's just occurred, to me, there is nothing in those
> directories as i cannot enable the database for full-text!"
> What directories were you referring to?
> Could you change the MSSQLServer service startup account to the system
> account (LocalSystem) via the Enterprise Manager's server property
security
> tab? This should stop and restart SQL Server and attempt to FT-enable the
> Pubs database and the authors table and let me know the result of the
that?[vbcol=seagreen]
> Thanks,
> John
>
> "Oz" <Oz(no_spam)@.nospam.com> wrote in message
> news:usHda6lNEHA.3944@.tk2msftngp13.phx.gbl...
> is
> help.
> the
> Search
> (MSSearch)
> local
> and
precisely[vbcol=seagreen]
> is
things[vbcol=seagreen]
> stop
change[vbcol=seagreen]
> only
> default
> subject
SQL[vbcol=seagreen]
> 7.0?
> FIX:
developing[vbcol=seagreen]
deploying[vbcol=seagreen]
> Edition
mainly[vbcol=seagreen]
> reinstall
to[vbcol=seagreen]
> reinstalled,
full-text)[vbcol=seagreen]
> enabled
> mssearch
> work
on
>

'Microsoft Search service cannot be administered under the present user error' SP3

Hi,
We have SQL Server private installation on which we are developing an
application and public installation on whict we will be deploying the
application. All instances have run Windows 2003 Enterprise Edition with SQL
2000 SP3. However, the public installation MS Search is not functioning
correctly. Basically it will not full-text indeed databases and produces
the following error
1> exec sp_fulltext_database 'enable'
2> go
(1 row affected)
Msg 7635, Level 16, State 1, Server SIMP001, Procedure sp_fulltext_database,
Lin
e 46
The Microsoft Search service cannot be administered under the present user
account
Now, we have tried many things to try and solve this error, mainly based on
search newsgroups, which are itemized below:
1 Reboot System and reexecute sp_
2 Complete reinstall of SQL on system, then reapplication of SP3
3 Same as above (2) but reapply SP3a
4 Remove SQL Server installation subkey in order that can reinstall
full-text search only, then reapply SP3
5 Check from keys under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\A pplications\ to make sure
SQL Server was there. It wasn't, removed SQL subkey and reinstalled,
re-adding full-text search as an option (to re-install full-text) then
reapplied SP3
6 Try reinstall, but do not reapply SP3 until have full-text enabled the
database.
None of the above worked. We still have a none functioning mssearch and
full-text disabled database on the system.
We have even tried enabling on a blank database. This does not work either.
PLEASE HELP! Getting desperate as the whole application depends on having
search ability.
Thanks
Oz
You will probably need to use the steps in the following article to bypass
this error:
How to manually reinstall the Microsoft Search service for an instance of
SQL Server 2000
http://support.microsoft.com/default.aspx?scid=kb;[LN];827449
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Oz,
In addition to the many things you tried below... a couple of things
specific to MSSearch and the MSSQLServer services...
1. Is the MSSearch service started and running under the System
(LocalSystem) account? If not, then change it to LocalSystem and stop and
re-start this service.
2. Have you or anyone else change the MSSQLServer account &/or password via
Win2K's Component service? IF so, then you MUST re-change the change via the
Enterprise Manager's server property security tab as this is the only place
where the two services security are kept in sync. See KB article 277549
(Q277549) PRB: Unable to Build Full-Text Catalog After You Modify
MSSQLServer Logon Account Through [NT4.0) Control Panel [or Win2K Component
Services] at http://support.microsoft.com/default...B;EN-US;277549
3. Have you or anyone else removed or modified the BUILTIN\Administrator
login on this server? If so, you MUST either re-add it with all of it's
normal default rights, especially sysadmin rights and with the default
database as master and the default language of English or use the following
T-SQL code to add the correct permissions:
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
Additionally, but not necessarily related to the error in the subject line,
has this server ever been upgrade from SQL Server 7.0 or is this SQL Server
2000 a "named instance" with a default installation of SQL Server 7.0? As
this might be related to a post-SP3 bug. See KB 814035 (Q814035) FIX: A
Full-Text Population Fails After You Apply SQL Server 2000 Service Pack 3
at:
http://support.microsoft.com/default...b;en-us;814035 (80004002 -
No such interface supported)
Regards,
John
"Oz" <Oz(no_spam)@.nospam.com> wrote in message
news:eytulHGNEHA.2468@.TK2MSFTNGP11.phx.gbl...
> Hi,
> We have SQL Server private installation on which we are developing an
> application and public installation on whict we will be deploying the
> application. All instances have run Windows 2003 Enterprise Edition with
SQL
> 2000 SP3. However, the public installation MS Search is not functioning
> correctly. Basically it will not full-text indeed databases and produces
> the following error
> 1> exec sp_fulltext_database 'enable'
> 2> go
> (1 row affected)
> Msg 7635, Level 16, State 1, Server SIMP001, Procedure
sp_fulltext_database,
> Lin
> e 46
> The Microsoft Search service cannot be administered under the present user
> account
> Now, we have tried many things to try and solve this error, mainly based
on
> search newsgroups, which are itemized below:
> 1 Reboot System and reexecute sp_
> 2 Complete reinstall of SQL on system, then reapplication of SP3
> 3 Same as above (2) but reapply SP3a
> 4 Remove SQL Server installation subkey in order that can reinstall
> full-text search only, then reapply SP3
> 5 Check from keys under
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\A pplications\ to make
sure
> SQL Server was there. It wasn't, removed SQL subkey and reinstalled,
> re-adding full-text search as an option (to re-install full-text) then
> reapplied SP3
> 6 Try reinstall, but do not reapply SP3 until have full-text enabled the
> database.
> None of the above worked. We still have a none functioning mssearch and
> full-text disabled database on the system.
> We have even tried enabling on a blank database. This does not work
either.
> PLEASE HELP! Getting desperate as the whole application depends on having
> search ability.
> Thanks
> Oz
>
|||Hi John,
Thanks for replying to my message. Unfortunately i forgot to add these items
as items i had also tried.
- Have not modified Administrator account, but i ran the SQL script anyway.
- MS Search has always been running as local system
- Changed the security settings using Ent Mgr to Local System and back again
to the user account.
- SQL account is not a local administrator. Tried adding it Administrators,
still, no joy.
Thanks
O
"John Kane" <jt-kane@.comcast.net> wrote in message
news:eaSiYlKNEHA.2976@.TK2MSFTNGP10.phx.gbl...
> Oz,
> In addition to the many things you tried below... a couple of things
> specific to MSSearch and the MSSQLServer services...
> 1. Is the MSSearch service started and running under the System
> (LocalSystem) account? If not, then change it to LocalSystem and stop and
> re-start this service.
> 2. Have you or anyone else change the MSSQLServer account &/or password
via
> Win2K's Component service? IF so, then you MUST re-change the change via
the
> Enterprise Manager's server property security tab as this is the only
place
> where the two services security are kept in sync. See KB article 277549
> (Q277549) PRB: Unable to Build Full-Text Catalog After You Modify
> MSSQLServer Logon Account Through [NT4.0) Control Panel [or Win2K
Component
> Services] at
http://support.microsoft.com/default...B;EN-US;277549
> 3. Have you or anyone else removed or modified the BUILTIN\Administrator
> login on this server? If so, you MUST either re-add it with all of it's
> normal default rights, especially sysadmin rights and with the default
> database as master and the default language of English or use the
following
> T-SQL code to add the correct permissions:
> 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
> Additionally, but not necessarily related to the error in the subject
line,
> has this server ever been upgrade from SQL Server 7.0 or is this SQL
Server[vbcol=seagreen]
> 2000 a "named instance" with a default installation of SQL Server 7.0? As
> this might be related to a post-SP3 bug. See KB 814035 (Q814035) FIX: A
> Full-Text Population Fails After You Apply SQL Server 2000 Service Pack 3
> at:
> http://support.microsoft.com/default...b;en-us;814035 (80004002 -
> No such interface supported)
> Regards,
> John
>
> "Oz" <Oz(no_spam)@.nospam.com> wrote in message
> news:eytulHGNEHA.2468@.TK2MSFTNGP11.phx.gbl...
> SQL
produces[vbcol=seagreen]
> sp_fulltext_database,
user[vbcol=seagreen]
> on
> sure
> either.
having
>
|||John
Is there a log file somewhere that i could try and see what precisely is
causing this problem.
Thanks
"John Kane" <jt-kane@.comcast.net> wrote in message
news:eaSiYlKNEHA.2976@.TK2MSFTNGP10.phx.gbl...
> Oz,
> In addition to the many things you tried below... a couple of things
> specific to MSSearch and the MSSQLServer services...
> 1. Is the MSSearch service started and running under the System
> (LocalSystem) account? If not, then change it to LocalSystem and stop and
> re-start this service.
> 2. Have you or anyone else change the MSSQLServer account &/or password
via
> Win2K's Component service? IF so, then you MUST re-change the change via
the
> Enterprise Manager's server property security tab as this is the only
place
> where the two services security are kept in sync. See KB article 277549
> (Q277549) PRB: Unable to Build Full-Text Catalog After You Modify
> MSSQLServer Logon Account Through [NT4.0) Control Panel [or Win2K
Component
> Services] at
http://support.microsoft.com/default...B;EN-US;277549
> 3. Have you or anyone else removed or modified the BUILTIN\Administrator
> login on this server? If so, you MUST either re-add it with all of it's
> normal default rights, especially sysadmin rights and with the default
> database as master and the default language of English or use the
following
> T-SQL code to add the correct permissions:
> 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
> Additionally, but not necessarily related to the error in the subject
line,
> has this server ever been upgrade from SQL Server 7.0 or is this SQL
Server[vbcol=seagreen]
> 2000 a "named instance" with a default installation of SQL Server 7.0? As
> this might be related to a post-SP3 bug. See KB 814035 (Q814035) FIX: A
> Full-Text Population Fails After You Apply SQL Server 2000 Service Pack 3
> at:
> http://support.microsoft.com/default...b;en-us;814035 (80004002 -
> No such interface supported)
> Regards,
> John
>
> "Oz" <Oz(no_spam)@.nospam.com> wrote in message
> news:eytulHGNEHA.2468@.TK2MSFTNGP11.phx.gbl...
> SQL
produces[vbcol=seagreen]
> sp_fulltext_database,
user[vbcol=seagreen]
> on
> sure
> either.
having
>
|||You're welcome, Oz,
Yes, there are MSSearch gatherer log files located under
\FTDATA\SQLServer\GatherLogs\ that can be "read" using gthrlog.vbs, however,
they most likely will have the same error (MSSearch service cannot be
admin..), so they are of little value in this issue.
Is this SQL Server installed on a Domain Controller (DC) server or is the
MSSQLServer startup account the DOMAIN\Administrator account?
While this should work, it's been my experience that with Full-Text Search
(FTS) on DC's that this is a problem for the "Microsoft Search" (MSSearch)
service. If you are using the DOMAIN\Administrator account, create a local
machine account and add this account into the DC's Administrator Group and
then change the MSSQLServer startup account in the Enterprise Manager (this
change MUST be done here) server's security tab. This should stop and
restart SQL Server and if all is successfully completed, FTS on a DC
*should* work...
Regards,
John
"Oz" <Oz(no_spam)@.nospam.com> wrote in message
news:OqqhS1ONEHA.3348@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> John
> Is there a log file somewhere that i could try and see what precisely is
> causing this problem.
> Thanks
> "John Kane" <jt-kane@.comcast.net> wrote in message
> news:eaSiYlKNEHA.2976@.TK2MSFTNGP10.phx.gbl...
and[vbcol=seagreen]
> via
> the
> place
> Component
> http://support.microsoft.com/default...B;EN-US;277549
BUILTIN\Administrator[vbcol=seagreen]
> following
> line,
> Server
As[vbcol=seagreen]
3[vbcol=seagreen]
(80004002 -[vbcol=seagreen]
with[vbcol=seagreen]
functioning[vbcol=seagreen]
> produces
> user
based[vbcol=seagreen]
the[vbcol=seagreen]
and
> having
>
|||Hi John,
Yes, it is running on a DC. I will try your suggestions and see if it makes
any difference.
Thanks
Oz
"John Kane" <jt-kane@.comcast.net> wrote in message
news:OeY1j4QNEHA.2144@.TK2MSFTNGP10.phx.gbl...
> You're welcome, Oz,
> Yes, there are MSSearch gatherer log files located under
> \FTDATA\SQLServer\GatherLogs\ that can be "read" using gthrlog.vbs,
however,
> they most likely will have the same error (MSSearch service cannot be
> admin..), so they are of little value in this issue.
> Is this SQL Server installed on a Domain Controller (DC) server or is the
> MSSQLServer startup account the DOMAIN\Administrator account?
> While this should work, it's been my experience that with Full-Text Search
> (FTS) on DC's that this is a problem for the "Microsoft Search" (MSSearch)
> service. If you are using the DOMAIN\Administrator account, create a local
> machine account and add this account into the DC's Administrator Group and
> then change the MSSQLServer startup account in the Enterprise Manager
(this[vbcol=seagreen]
> change MUST be done here) server's security tab. This should stop and
> restart SQL Server and if all is successfully completed, FTS on a DC
> *should* work...
> Regards,
> John
>
> "Oz" <Oz(no_spam)@.nospam.com> wrote in message
> news:OqqhS1ONEHA.3348@.TK2MSFTNGP09.phx.gbl...
> and
password[vbcol=seagreen]
via[vbcol=seagreen]
277549[vbcol=seagreen]
> BUILTIN\Administrator
it's[vbcol=seagreen]
> As
A[vbcol=seagreen]
Pack[vbcol=seagreen]
> 3
> (80004002 -
an[vbcol=seagreen]
the[vbcol=seagreen]
> with
> functioning
present[vbcol=seagreen]
> based
make[vbcol=seagreen]
then
> the
> and
>
|||Hi John,
It's just occurred, to me, there is nothing in those directories as i cannot
enable the database for full-text!
"John Kane" <jt-kane@.comcast.net> wrote in message
news:OeY1j4QNEHA.2144@.TK2MSFTNGP10.phx.gbl...
> You're welcome, Oz,
> Yes, there are MSSearch gatherer log files located under
> \FTDATA\SQLServer\GatherLogs\ that can be "read" using gthrlog.vbs,
however,
> they most likely will have the same error (MSSearch service cannot be
> admin..), so they are of little value in this issue.
> Is this SQL Server installed on a Domain Controller (DC) server or is the
> MSSQLServer startup account the DOMAIN\Administrator account?
> While this should work, it's been my experience that with Full-Text Search
> (FTS) on DC's that this is a problem for the "Microsoft Search" (MSSearch)
> service. If you are using the DOMAIN\Administrator account, create a local
> machine account and add this account into the DC's Administrator Group and
> then change the MSSQLServer startup account in the Enterprise Manager
(this[vbcol=seagreen]
> change MUST be done here) server's security tab. This should stop and
> restart SQL Server and if all is successfully completed, FTS on a DC
> *should* work...
> Regards,
> John
>
> "Oz" <Oz(no_spam)@.nospam.com> wrote in message
> news:OqqhS1ONEHA.3348@.TK2MSFTNGP09.phx.gbl...
> and
password[vbcol=seagreen]
via[vbcol=seagreen]
277549[vbcol=seagreen]
> BUILTIN\Administrator
it's[vbcol=seagreen]
> As
A[vbcol=seagreen]
Pack[vbcol=seagreen]
> 3
> (80004002 -
an[vbcol=seagreen]
the[vbcol=seagreen]
> with
> functioning
present[vbcol=seagreen]
> based
make[vbcol=seagreen]
then
> the
> and
>
|||Also John,
I have always been running a local (i.e. Domain user) account as the SQL
account, althought it is not a member of the administrators group. This is
one of the things i tried (adding it to the admins group), but didn't help.
Thanks
"John Kane" <jt-kane@.comcast.net> wrote in message
news:OeY1j4QNEHA.2144@.TK2MSFTNGP10.phx.gbl...
> You're welcome, Oz,
> Yes, there are MSSearch gatherer log files located under
> \FTDATA\SQLServer\GatherLogs\ that can be "read" using gthrlog.vbs,
however,
> they most likely will have the same error (MSSearch service cannot be
> admin..), so they are of little value in this issue.
> Is this SQL Server installed on a Domain Controller (DC) server or is the
> MSSQLServer startup account the DOMAIN\Administrator account?
> While this should work, it's been my experience that with Full-Text Search
> (FTS) on DC's that this is a problem for the "Microsoft Search" (MSSearch)
> service. If you are using the DOMAIN\Administrator account, create a local
> machine account and add this account into the DC's Administrator Group and
> then change the MSSQLServer startup account in the Enterprise Manager
(this[vbcol=seagreen]
> change MUST be done here) server's security tab. This should stop and
> restart SQL Server and if all is successfully completed, FTS on a DC
> *should* work...
> Regards,
> John
>
> "Oz" <Oz(no_spam)@.nospam.com> wrote in message
> news:OqqhS1ONEHA.3348@.TK2MSFTNGP09.phx.gbl...
> and
password[vbcol=seagreen]
via[vbcol=seagreen]
277549[vbcol=seagreen]
> BUILTIN\Administrator
it's[vbcol=seagreen]
> As
A[vbcol=seagreen]
Pack[vbcol=seagreen]
> 3
> (80004002 -
an[vbcol=seagreen]
the[vbcol=seagreen]
> with
> functioning
present[vbcol=seagreen]
> based
make[vbcol=seagreen]
then
> the
> and
>
|||You're welcome, Oz,
When you said "It's just occurred, to me, there is nothing in those
directories as i cannot enable the database for full-text!"
What directories were you referring to?
Could you change the MSSQLServer service startup account to the system
account (LocalSystem) via the Enterprise Manager's server property security
tab? This should stop and restart SQL Server and attempt to FT-enable the
Pubs database and the authors table and let me know the result of the that?
Thanks,
John
"Oz" <Oz(no_spam)@.nospam.com> wrote in message
news:usHda6lNEHA.3944@.tk2msftngp13.phx.gbl...
> Also John,
> I have always been running a local (i.e. Domain user) account as the SQL
> account, althought it is not a member of the administrators group. This
is
> one of the things i tried (adding it to the admins group), but didn't
help.[vbcol=seagreen]
> Thanks
> "John Kane" <jt-kane@.comcast.net> wrote in message
> news:OeY1j4QNEHA.2144@.TK2MSFTNGP10.phx.gbl...
> however,
the[vbcol=seagreen]
Search[vbcol=seagreen]
(MSSearch)[vbcol=seagreen]
local[vbcol=seagreen]
and[vbcol=seagreen]
> (this
is[vbcol=seagreen]
stop[vbcol=seagreen]
> password
> via
only[vbcol=seagreen]
> 277549
> it's
default[vbcol=seagreen]
subject[vbcol=seagreen]
7.0?[vbcol=seagreen]
FIX:[vbcol=seagreen]
> A
> Pack
> an
> the
Edition[vbcol=seagreen]
> present
reinstall[vbcol=seagreen]
> make
reinstalled,[vbcol=seagreen]
> then
enabled[vbcol=seagreen]
mssearch[vbcol=seagreen]
work
>

'Microsoft Search service cannot be administered under the present user error' SP3

Hi,
We have SQL Server private installation on which we are developing an
application and public installation on whict we will be deploying the
application. All instances have run Windows 2003 Enterprise Edition with SQL
2000 SP3. However, the public installation MS Search is not functioning
correctly. Basically it will not full-text indeed databases and produces
the following error
1> exec sp_fulltext_database 'enable'
2> go
(1 row affected)
Msg 7635, Level 16, State 1, Server SIMP001, Procedure sp_fulltext_database,
Lin
e 46
The Microsoft Search service cannot be administered under the present user
account
Now, we have tried many things to try and solve this error, mainly based on
search newsgroups, which are itemized below:
1 Reboot System and reexecute sp_
2 Complete reinstall of SQL on system, then reapplication of SP3
3 Same as above (2) but reapply SP3a
4 Remove SQL Server installation subkey in order that can reinstall
full-text search only, then reapply SP3
5 Check from keys under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Se
arch\1.0\Applications\ to make sure
SQL Server was there. It wasn't, removed SQL subkey and reinstalled,
re-adding full-text search as an option (to re-install full-text) then
reapplied SP3
6 Try reinstall, but do not reapply SP3 until have full-text enabled the
database.
None of the above worked. We still have a none functioning mssearch and
full-text disabled database on the system.
We have even tried enabling on a blank database. This does not work either.
PLEASE HELP! Getting desperate as the whole application depends on having
search ability.
Thanks
OzYou will probably need to use the steps in the following article to bypass
this error:
How to manually reinstall the Microsoft Search service for an instance of
SQL Server 2000
http://support.microsoft.com/defaul...scid=kb;[LN];827449
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Oz,
In addition to the many things you tried below... a couple of things
specific to MSSearch and the MSSQLServer services...
1. Is the MSSearch service started and running under the System
(LocalSystem) account? If not, then change it to LocalSystem and stop and
re-start this service.
2. Have you or anyone else change the MSSQLServer account &/or password via
Win2K's Component service? IF so, then you MUST re-change the change via the
Enterprise Manager's server property security tab as this is the only place
where the two services security are kept in sync. See KB article 277549
(Q277549) PRB: Unable to Build Full-Text Catalog After You Modify
MSSQLServer Logon Account Through [NT4.0) Control Panel [or Win2K Co
mponent
Services] at http://support.microsoft.com/defaul...KB;EN-US;277549
3. Have you or anyone else removed or modified the BUILTIN\Administrator
login on this server? If so, you MUST either re-add it with all of it's
normal default rights, especially sysadmin rights and with the default
database as master and the default language of English or use the following
T-SQL code to add the correct permissions:
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
Additionally, but not necessarily related to the error in the subject line,
has this server ever been upgrade from SQL Server 7.0 or is this SQL Server
2000 a "named instance" with a default installation of SQL Server 7.0? As
this might be related to a post-SP3 bug. See KB 814035 (Q814035) FIX: A
Full-Text Population Fails After You Apply SQL Server 2000 Service Pack 3
at:
http://support.microsoft.com/defaul...kb;en-us;814035 (80004002 -
No such interface supported)
Regards,
John
"Oz" <Oz(no_spam)@.nospam.com> wrote in message
news:eytulHGNEHA.2468@.TK2MSFTNGP11.phx.gbl...
> Hi,
> We have SQL Server private installation on which we are developing an
> application and public installation on whict we will be deploying the
> application. All instances have run Windows 2003 Enterprise Edition with
SQL
> 2000 SP3. However, the public installation MS Search is not functioning
> correctly. Basically it will not full-text indeed databases and produces
> the following error
> 1> exec sp_fulltext_database 'enable'
> 2> go
> (1 row affected)
> Msg 7635, Level 16, State 1, Server SIMP001, Procedure
sp_fulltext_database,
> Lin
> e 46
> The Microsoft Search service cannot be administered under the present user
> account
> Now, we have tried many things to try and solve this error, mainly based
on
> search newsgroups, which are itemized below:
> 1 Reboot System and reexecute sp_
> 2 Complete reinstall of SQL on system, then reapplication of SP3
> 3 Same as above (2) but reapply SP3a
> 4 Remove SQL Server installation subkey in order that can reinstall
> full-text search only, then reapply SP3
> 5 Check from keys under
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Se
arch\1.0\Applications\ to make
sure
> SQL Server was there. It wasn't, removed SQL subkey and reinstalled,
> re-adding full-text search as an option (to re-install full-text) then
> reapplied SP3
> 6 Try reinstall, but do not reapply SP3 until have full-text enabled the
> database.
> None of the above worked. We still have a none functioning mssearch and
> full-text disabled database on the system.
> We have even tried enabling on a blank database. This does not work
either.
> PLEASE HELP! Getting desperate as the whole application depends on having
> search ability.
> Thanks
> Oz
>|||Hi John,
Thanks for replying to my message. Unfortunately i forgot to add these items
as items i had also tried.
- Have not modified Administrator account, but i ran the SQL script anyway.
- MS Search has always been running as local system
- Changed the security settings using Ent Mgr to Local System and back again
to the user account.
- SQL account is not a local administrator. Tried adding it Administrators,
still, no joy.
Thanks
O
"John Kane" <jt-kane@.comcast.net> wrote in message
news:eaSiYlKNEHA.2976@.TK2MSFTNGP10.phx.gbl...
> Oz,
> In addition to the many things you tried below... a couple of things
> specific to MSSearch and the MSSQLServer services...
> 1. Is the MSSearch service started and running under the System
> (LocalSystem) account? If not, then change it to LocalSystem and stop and
> re-start this service.
> 2. Have you or anyone else change the MSSQLServer account &/or password
via
> Win2K's Component service? IF so, then you MUST re-change the change via
the
> Enterprise Manager's server property security tab as this is the only
place
> where the two services security are kept in sync. See KB article 277549
> (Q277549) PRB: Unable to Build Full-Text Catalog After You Modify
> MSSQLServer Logon Account Through [NT4.0) Control Panel [or Win2K
Component
> Services] at
http://support.microsoft.com/defaul...KB;EN-US;277549
> 3. Have you or anyone else removed or modified the BUILTIN\Administrator
> login on this server? If so, you MUST either re-add it with all of it's
> normal default rights, especially sysadmin rights and with the default
> database as master and the default language of English or use the
following
> T-SQL code to add the correct permissions:
> 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
> Additionally, but not necessarily related to the error in the subject
line,
> has this server ever been upgrade from SQL Server 7.0 or is this SQL
Server
> 2000 a "named instance" with a default installation of SQL Server 7.0? As
> this might be related to a post-SP3 bug. See KB 814035 (Q814035) FIX: A
> Full-Text Population Fails After You Apply SQL Server 2000 Service Pack 3
> at:
> http://support.microsoft.com/defaul...kb;en-us;814035 (80004002 -
> No such interface supported)
> Regards,
> John
>
> "Oz" <Oz(no_spam)@.nospam.com> wrote in message
> news:eytulHGNEHA.2468@.TK2MSFTNGP11.phx.gbl...
> SQL
produces[vbcol=seagreen]
> sp_fulltext_database,
user[vbcol=seagreen]
> on
> sure
> either.
having[vbcol=seagreen]
>|||John
Is there a log file somewhere that i could try and see what precisely is
causing this problem.
Thanks
"John Kane" <jt-kane@.comcast.net> wrote in message
news:eaSiYlKNEHA.2976@.TK2MSFTNGP10.phx.gbl...
> Oz,
> In addition to the many things you tried below... a couple of things
> specific to MSSearch and the MSSQLServer services...
> 1. Is the MSSearch service started and running under the System
> (LocalSystem) account? If not, then change it to LocalSystem and stop and
> re-start this service.
> 2. Have you or anyone else change the MSSQLServer account &/or password
via
> Win2K's Component service? IF so, then you MUST re-change the change via
the
> Enterprise Manager's server property security tab as this is the only
place
> where the two services security are kept in sync. See KB article 277549
> (Q277549) PRB: Unable to Build Full-Text Catalog After You Modify
> MSSQLServer Logon Account Through [NT4.0) Control Panel [or Win2K
Component
> Services] at
http://support.microsoft.com/defaul...KB;EN-US;277549
> 3. Have you or anyone else removed or modified the BUILTIN\Administrator
> login on this server? If so, you MUST either re-add it with all of it's
> normal default rights, especially sysadmin rights and with the default
> database as master and the default language of English or use the
following
> T-SQL code to add the correct permissions:
> 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
> Additionally, but not necessarily related to the error in the subject
line,
> has this server ever been upgrade from SQL Server 7.0 or is this SQL
Server
> 2000 a "named instance" with a default installation of SQL Server 7.0? As
> this might be related to a post-SP3 bug. See KB 814035 (Q814035) FIX: A
> Full-Text Population Fails After You Apply SQL Server 2000 Service Pack 3
> at:
> http://support.microsoft.com/defaul...kb;en-us;814035 (80004002 -
> No such interface supported)
> Regards,
> John
>
> "Oz" <Oz(no_spam)@.nospam.com> wrote in message
> news:eytulHGNEHA.2468@.TK2MSFTNGP11.phx.gbl...
> SQL
produces[vbcol=seagreen]
> sp_fulltext_database,
user[vbcol=seagreen]
> on
> sure
> either.
having[vbcol=seagreen]
>|||You're welcome, Oz,
Yes, there are MSSearch gatherer log files located under
\FTDATA\SQLServer\GatherLogs\ that can be "read" using gthrlog.vbs, however,
they most likely will have the same error (MSSearch service cannot be
admin..), so they are of little value in this issue.
Is this SQL Server installed on a Domain Controller (DC) server or is the
MSSQLServer startup account the DOMAIN\Administrator account?
While this should work, it's been my experience that with Full-Text Search
(FTS) on DC's that this is a problem for the "Microsoft Search" (MSSearch)
service. If you are using the DOMAIN\Administrator account, create a local
machine account and add this account into the DC's Administrator Group and
then change the MSSQLServer startup account in the Enterprise Manager (this
change MUST be done here) server's security tab. This should stop and
restart SQL Server and if all is successfully completed, FTS on a DC
*should* work...
Regards,
John
"Oz" <Oz(no_spam)@.nospam.com> wrote in message
news:OqqhS1ONEHA.3348@.TK2MSFTNGP09.phx.gbl...
> John
> Is there a log file somewhere that i could try and see what precisely is
> causing this problem.
> Thanks
> "John Kane" <jt-kane@.comcast.net> wrote in message
> news:eaSiYlKNEHA.2976@.TK2MSFTNGP10.phx.gbl...
and[vbcol=seagreen]
> via
> the
> place
> Component
> http://support.microsoft.com/defaul...KB;EN-US;277549
BUILTIN\Administrator[vbcol=seagreen]
> following
> line,
> Server
As[vbcol=seagreen]
3[vbcol=seagreen]
(80004002 -[vbcol=seagreen]
with[vbcol=seagreen]
functioning[vbcol=seagreen]
> produces
> user
based[vbcol=seagreen]
the[vbcol=seagreen]
and[vbcol=seagreen]
> having
>|||Hi John,
Yes, it is running on a DC. I will try your suggestions and see if it makes
any difference.
Thanks
Oz
"John Kane" <jt-kane@.comcast.net> wrote in message
news:OeY1j4QNEHA.2144@.TK2MSFTNGP10.phx.gbl...
> You're welcome, Oz,
> Yes, there are MSSearch gatherer log files located under
> \FTDATA\SQLServer\GatherLogs\ that can be "read" using gthrlog.vbs,
however,
> they most likely will have the same error (MSSearch service cannot be
> admin..), so they are of little value in this issue.
> Is this SQL Server installed on a Domain Controller (DC) server or is the
> MSSQLServer startup account the DOMAIN\Administrator account?
> While this should work, it's been my experience that with Full-Text Search
> (FTS) on DC's that this is a problem for the "Microsoft Search" (MSSearch)
> service. If you are using the DOMAIN\Administrator account, create a local
> machine account and add this account into the DC's Administrator Group and
> then change the MSSQLServer startup account in the Enterprise Manager
(this
> change MUST be done here) server's security tab. This should stop and
> restart SQL Server and if all is successfully completed, FTS on a DC
> *should* work...
> Regards,
> John
>
> "Oz" <Oz(no_spam)@.nospam.com> wrote in message
> news:OqqhS1ONEHA.3348@.TK2MSFTNGP09.phx.gbl...
> and
password[vbcol=seagreen]
via[vbcol=seagreen]
277549[vbcol=seagreen]
> BUILTIN\Administrator
it's[vbcol=seagreen]
> As
A[vbcol=seagreen]
Pack[vbcol=seagreen]
> 3
> (80004002 -
an[vbcol=seagreen]
the[vbcol=seagreen]
> with
> functioning
present[vbcol=seagreen]
> based
make[vbcol=seagreen]
then[vbcol=seagreen]
> the
> and
>|||Hi John,
It's just occurred, to me, there is nothing in those directories as i cannot
enable the database for full-text!
"John Kane" <jt-kane@.comcast.net> wrote in message
news:OeY1j4QNEHA.2144@.TK2MSFTNGP10.phx.gbl...
> You're welcome, Oz,
> Yes, there are MSSearch gatherer log files located under
> \FTDATA\SQLServer\GatherLogs\ that can be "read" using gthrlog.vbs,
however,
> they most likely will have the same error (MSSearch service cannot be
> admin..), so they are of little value in this issue.
> Is this SQL Server installed on a Domain Controller (DC) server or is the
> MSSQLServer startup account the DOMAIN\Administrator account?
> While this should work, it's been my experience that with Full-Text Search
> (FTS) on DC's that this is a problem for the "Microsoft Search" (MSSearch)
> service. If you are using the DOMAIN\Administrator account, create a local
> machine account and add this account into the DC's Administrator Group and
> then change the MSSQLServer startup account in the Enterprise Manager
(this
> change MUST be done here) server's security tab. This should stop and
> restart SQL Server and if all is successfully completed, FTS on a DC
> *should* work...
> Regards,
> John
>
> "Oz" <Oz(no_spam)@.nospam.com> wrote in message
> news:OqqhS1ONEHA.3348@.TK2MSFTNGP09.phx.gbl...
> and
password[vbcol=seagreen]
via[vbcol=seagreen]
277549[vbcol=seagreen]
> BUILTIN\Administrator
it's[vbcol=seagreen]
> As
A[vbcol=seagreen]
Pack[vbcol=seagreen]
> 3
> (80004002 -
an[vbcol=seagreen]
the[vbcol=seagreen]
> with
> functioning
present[vbcol=seagreen]
> based
make[vbcol=seagreen]
then[vbcol=seagreen]
> the
> and
>|||Also John,
I have always been running a local (i.e. Domain user) account as the SQL
account, althought it is not a member of the administrators group. This is
one of the things i tried (adding it to the admins group), but didn't help.
Thanks
"John Kane" <jt-kane@.comcast.net> wrote in message
news:OeY1j4QNEHA.2144@.TK2MSFTNGP10.phx.gbl...
> You're welcome, Oz,
> Yes, there are MSSearch gatherer log files located under
> \FTDATA\SQLServer\GatherLogs\ that can be "read" using gthrlog.vbs,
however,
> they most likely will have the same error (MSSearch service cannot be
> admin..), so they are of little value in this issue.
> Is this SQL Server installed on a Domain Controller (DC) server or is the
> MSSQLServer startup account the DOMAIN\Administrator account?
> While this should work, it's been my experience that with Full-Text Search
> (FTS) on DC's that this is a problem for the "Microsoft Search" (MSSearch)
> service. If you are using the DOMAIN\Administrator account, create a local
> machine account and add this account into the DC's Administrator Group and
> then change the MSSQLServer startup account in the Enterprise Manager
(this
> change MUST be done here) server's security tab. This should stop and
> restart SQL Server and if all is successfully completed, FTS on a DC
> *should* work...
> Regards,
> John
>
> "Oz" <Oz(no_spam)@.nospam.com> wrote in message
> news:OqqhS1ONEHA.3348@.TK2MSFTNGP09.phx.gbl...
> and
password[vbcol=seagreen]
via[vbcol=seagreen]
277549[vbcol=seagreen]
> BUILTIN\Administrator
it's[vbcol=seagreen]
> As
A[vbcol=seagreen]
Pack[vbcol=seagreen]
> 3
> (80004002 -
an[vbcol=seagreen]
the[vbcol=seagreen]
> with
> functioning
present[vbcol=seagreen]
> based
make[vbcol=seagreen]
then[vbcol=seagreen]
> the
> and
>|||You're welcome, Oz,
When you said "It's just occurred, to me, there is nothing in those
directories as i cannot enable the database for full-text!"
What directories were you referring to?
Could you change the MSSQLServer service startup account to the system
account (LocalSystem) via the Enterprise Manager's server property security
tab? This should stop and restart SQL Server and attempt to FT-enable the
Pubs database and the authors table and let me know the result of the that?
Thanks,
John
"Oz" <Oz(no_spam)@.nospam.com> wrote in message
news:usHda6lNEHA.3944@.tk2msftngp13.phx.gbl...
> Also John,
> I have always been running a local (i.e. Domain user) account as the SQL
> account, althought it is not a member of the administrators group. This
is
> one of the things i tried (adding it to the admins group), but didn't
help.
> Thanks
> "John Kane" <jt-kane@.comcast.net> wrote in message
> news:OeY1j4QNEHA.2144@.TK2MSFTNGP10.phx.gbl...
> however,
the[vbcol=seagreen]
Search[vbcol=seagreen]
(MSSearch)[vbcol=seagreen]
local[vbcol=seagreen]
and[vbcol=seagreen]
> (this
is[vbcol=seagreen]
stop[vbcol=seagreen]
> password
> via
only[vbcol=seagreen]
> 277549
> it's
default[vbcol=seagreen]
subject[vbcol=seagreen]
7.0?[vbcol=seagreen]
FIX:[vbcol=seagreen]
> A
> Pack
> an
> the
Edition[vbcol=seagreen]
> present
reinstall[vbcol=seagreen]
> make
reinstalled,[vbcol=seagreen]
> then
enabled[vbcol=seagreen]
mssearch[vbcol=seagreen]
work[vbcol=seagreen]
>sql