Sunday, March 25, 2012
Can't Administer
SEARCH. I can successfully use it on other similar servers. When I try to
add a FULL TEXT CATALOG to a database I get this message when the wizard is
trying to do the work:
The Microsoft Search Service cannot be administered under the present
account.
I am logged in with an account in the Administrator group. The Search
Service is started. The server is itself is running with an account in the
Administrator group. I have checked and rechecked and everything I can think
of is the same as systems where I can make this work. I am likely missing
the obvious but can't find it. Any ideas.
Thanks
Tom G.
Can you verify that the MSSearch account is running under the local system
account. Has anyone modified the SQL Server service account through the
services applet in control panel as opposed to using EM? To fix this, right
click on your server in EM, select properties, click the security tab,
change it to run under the system account, bounce your SQL Server, and then
modify it again to run under a local admin account.
Also verify that no one has removed the builtin\admin account from the
system administrators role. To do this connect to your SQL Server in EM,
expand the security folder and expand the server roles node. Double click on
the system administrator role and ensure the builtin\administrators account
is present.
if not run the following in qa.
if not exists (select * from master.dbo.syslogins where
loginname = N'NT Authority\System')
exec sp_grantlogin N'NT Authority\System'
exec sp_defaultdb N'NT Authority\System', N'master'
exec sp_defaultlanguage N'NT Authority\System',
N'us_english'
GO
exec sp_addsrvrolemember N'NT Authority\System', sysadmin
GO
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Tom Groszko" <newscorrespondent@.charter.net> wrote in message
news:%238ktUtRmEHA.2504@.TK2MSFTNGP14.phx.gbl...
> I am trying for the first time on this SQL server to use the FULL TEXT
> SEARCH. I can successfully use it on other similar servers. When I try to
> add a FULL TEXT CATALOG to a database I get this message when the wizard
is
> trying to do the work:
> The Microsoft Search Service cannot be administered under the present
> account.
> I am logged in with an account in the Administrator group. The Search
> Service is started. The server is itself is running with an account in the
> Administrator group. I have checked and rechecked and everything I can
think
> of is the same as systems where I can make this work. I am likely missing
> the obvious but can't find it. Any ideas.
> Thanks
> Tom G.
>
|||I am curious as to whether this solved the problem. I am having the same
problem and can't seem to resolve. I am trying to execute
sp_fulltext_database in Query Analyzer and get the following error
.. Msg 7635 The Microsoft Search service cannot be administered under the
present user account
1) The builtin\admin account is a member of the System Administrators roles
2) The MSSearch service is running under a Local System account (Log On tab
in services). I have also tried the "This account" selection using a local
administrator account"
3) MSSQLSERVER service is running under a local admin account, changed
through EM per your instructions below. I have also tried running it under a
System Account.
4) I guess I am confused about what the correct combination for MSSearch
and SQL Server is with regards to accounts.
5) Any help would be greatly appreciated.
Thanks,
Tom Shalloe
"Hilary Cotter" wrote:
> Can you verify that the MSSearch account is running under the local system
> account. Has anyone modified the SQL Server service account through the
> services applet in control panel as opposed to using EM? To fix this, right
> click on your server in EM, select properties, click the security tab,
> change it to run under the system account, bounce your SQL Server, and then
> modify it again to run under a local admin account.
> Also verify that no one has removed the builtin\admin account from the
> system administrators role. To do this connect to your SQL Server in EM,
> expand the security folder and expand the server roles node. Double click on
> the system administrator role and ensure the builtin\administrators account
> is present.
> if not run the following in qa.
> if not exists (select * from master.dbo.syslogins where
> loginname = N'NT Authority\System')
> exec sp_grantlogin N'NT Authority\System'
> exec sp_defaultdb N'NT Authority\System', N'master'
> exec sp_defaultlanguage N'NT Authority\System',
> N'us_english'
> GO
> exec sp_addsrvrolemember N'NT Authority\System', sysadmin
> GO
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Tom Groszko" <newscorrespondent@.charter.net> wrote in message
> news:%238ktUtRmEHA.2504@.TK2MSFTNGP14.phx.gbl...
> is
> think
>
>
|||Tom,
Is the master the default database for the BUILTIN\Administrator account as
well as a member of the Sysadmin role?
When you changed it to run under the System Account (LocalSystem) did you do
this via the Enterprise Manager's server security tab?
The Enterprise Manager code runs an internal system extended proc -
xp_updateFTSSQLAccount - when any change to the MSSQLServer account is
executed, this xp proc makes similar change to the MSSearch service as well.
You should review the following KB articles:
317746 (Q317746) PRB: SQL Server Full-Text Search Does Not Populate Catalogs
http://support.microsoft.com/default...b;en-us;317746
277549 (Q277549) PRB: Unable to Build Full-Text Catalog After You Modify
MSSQLServer Logon Account Through [NT4.0) Control Panel [or Win2K Component
Services]
http://support.microsoft.com/default...B;EN-US;277549
Regards,
John
"Shallotx" <Shallotx@.discussions.microsoft.com> wrote in message
news:35629999-FB98-4407-98C8-5307CF9EF861@.microsoft.com...
> I am curious as to whether this solved the problem. I am having the same
> problem and can't seem to resolve. I am trying to execute
> sp_fulltext_database in Query Analyzer and get the following error
> .. Msg 7635 The Microsoft Search service cannot be administered under
the
> present user account
> 1) The builtin\admin account is a member of the System Administrators
roles
> 2) The MSSearch service is running under a Local System account (Log On
tab
> in services). I have also tried the "This account" selection using a
local
> administrator account"
> 3) MSSQLSERVER service is running under a local admin account, changed
> through EM per your instructions below. I have also tried running it
under a[vbcol=seagreen]
> System Account.
> 4) I guess I am confused about what the correct combination for MSSearch
> and SQL Server is with regards to accounts.
> 5) Any help would be greatly appreciated.
> Thanks,
> Tom Shalloe
> "Hilary Cotter" wrote:
system[vbcol=seagreen]
right[vbcol=seagreen]
then[vbcol=seagreen]
click on[vbcol=seagreen]
account[vbcol=seagreen]
to[vbcol=seagreen]
wizard[vbcol=seagreen]
the[vbcol=seagreen]
missing[vbcol=seagreen]
Thursday, March 8, 2012
Cannot uninstall sql server express
I have successfully uninstalled instance of sql server, but I cannot uninstall the workstation.
here are the log that I have :
=== Verbose logging started: 11/23/2006 13:06:11 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: E:\Original\SQL2005Ent\32 bit\Servers\setup.exe ===
MSI (c) (04:28) [13:06:11:021]: Resetting cached policy values
MSI (c) (04:28) [13:06:11:021]: Machine policy value 'Debug' is 0
MSI (c) (04:28) [13:06:11:021]: ******* RunEngine:
******* Product: E:\Original\SQL2005Ent\32 bit\Servers\Setup\SqlSupport.msi
******* Action:
******* CommandLine: **********
MSI (c) (04:28) [13:06:11:021]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (04:28) [13:06:11:021]: Grabbed execution mutex.
MSI (c) (04:28) [13:06:11:036]: Cloaking enabled.
MSI (c) (04:28) [13:06:11:036]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (04:28) [13:06:11:068]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (c) (04:28) [13:06:11:068]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (04:28) [13:06:11:068]: MainEngineThread is returning 1618
=== Verbose logging stopped: 11/23/2006 13:06:11 ===
Please help
What error are you seeing? Can you search your install/uninstall logs for the text string "value 3" and post the error message a few lines above?
Thanks,
Sam Lester (MSFT)
Uninstall workstation?
What workstation you're referring.
|||Error 1618 means: Another installation is already in progress. Complete that installation before proceeding with this install.
There was another installation running at the same time you tried to uninstall SQL Express. Uninstall will work when you kick off setup later again.
Cannot uninstall sql server express
I have successfully uninstalled instance of sql server, but I cannot uninstall the workstation.
here are the log that I have :
=== Verbose logging started: 11/23/2006 13:06:11 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: E:\Original\SQL2005Ent\32 bit\Servers\setup.exe ===
MSI (c) (04:28) [13:06:11:021]: Resetting cached policy values
MSI (c) (04:28) [13:06:11:021]: Machine policy value 'Debug' is 0
MSI (c) (04:28) [13:06:11:021]: ******* RunEngine:
******* Product: E:\Original\SQL2005Ent\32 bit\Servers\Setup\SqlSupport.msi
******* Action:
******* CommandLine: **********
MSI (c) (04:28) [13:06:11:021]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (04:28) [13:06:11:021]: Grabbed execution mutex.
MSI (c) (04:28) [13:06:11:036]: Cloaking enabled.
MSI (c) (04:28) [13:06:11:036]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (04:28) [13:06:11:068]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (c) (04:28) [13:06:11:068]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (04:28) [13:06:11:068]: MainEngineThread is returning 1618
=== Verbose logging stopped: 11/23/2006 13:06:11 ===
Please help
What error are you seeing? Can you search your install/uninstall logs for the text string "value 3" and post the error message a few lines above?
Thanks,
Sam Lester (MSFT)
Uninstall workstation?
What workstation you're referring.
|||Error 1618 means: Another installation is already in progress. Complete that installation before proceeding with this install.
There was another installation running at the same time you tried to uninstall SQL Express. Uninstall will work when you kick off setup later again.
Friday, February 24, 2012
cannot shrink transaction log
receiving the infamous "the log file for database is full".
I have tried:
backup log database with truncate_only
go
dbcc shrinkfile (database _log,0)
go
I receive this message when I am importing a large excel spreadsheet.
The error occurs on line 7956. Again, this is large, so what can I do to
make sure this works. This import is daily.
Thanks!!
*** Sent via Developersdex http://www.examnotes.net ***Joey,
Sounds like you have two issues.
1. >I have not been able to successfully shrink my transaction log.
Are there any open transactions (can use DBCC OPENTRAN to determine and KILL
to end).
Also see:
http://groups.google.com/group/micr...9c56843a0f1d1db
2. Import issue - ensure adequate log space is available by increasing the
size of the log file as well as ensuring auto-growth is enabled. You can
use DBCC SQLPERF(LOGSPACE) to track the log usage. If the table has a high
number of indexes you may consider dropping the indexes prior to the import
then recreating them following the import. Minimally logged op with BCP or
BULK COPY is another option - but probably not waranted here.
HTH
Jerry
"Joey Martin" <joey@.infosmiths.net> wrote in message
news:OtHjosX2FHA.3592@.TK2MSFTNGP12.phx.gbl...
>I have not been able to successfully shrink my transaction log. I'm
> receiving the infamous "the log file for database is full".
> I have tried:
> backup log database with truncate_only
> go
> dbcc shrinkfile (database _log,0)
> go
> I receive this message when I am importing a large excel spreadsheet.
> The error occurs on line 7956. Again, this is large, so what can I do to
> make sure this works. This import is daily.
> Thanks!!
>
>
> *** Sent via Developersdex http://www.examnotes.net ***|||What version of SQL Server are you using? What service pack? I've seen
this problem before, but I think it went away when I installed SP3.
Have you tried shrinking the file using Enterprise Manager?
You might try adding a second log file on another disk, truncate and shrink
the first file, and then remove the second log file. I'm not sure if that
will work, but it's worth a try.
Another option would be to replace the log file: detach the database using
sp_detach_db, delete the log file and then reattach the database using
sp_attach_single_file_db. If the log file wasn't created on the correct
physical disk drive, detach the database using sp_detach_db, move the log
file onto the log disk drive, and then reattach the database using
sp_attach_db.
"Joey Martin" <joey@.infosmiths.net> wrote in message
news:OtHjosX2FHA.3592@.TK2MSFTNGP12.phx.gbl...
>I have not been able to successfully shrink my transaction log. I'm
> receiving the infamous "the log file for database is full".
> I have tried:
> backup log database with truncate_only
> go
> dbcc shrinkfile (database _log,0)
> go
> I receive this message when I am importing a large excel spreadsheet.
> The error occurs on line 7956. Again, this is large, so what can I do to
> make sure this works. This import is daily.
> Thanks!!
>
>
> *** Sent via Developersdex http://www.examnotes.net ***
Friday, February 10, 2012
Cannot restore databae successfully
I backed up a database called Citrix_DB through Enterprise Manager from a standalone MSSQL 2000. I tried to restore the DB to another MSSQL 2000 Cluster but failed. Would anyone know how to get it fixed? Thanks a lot. And below is the error message: -
Microsoft SQL-DMO (ODBC SQLState: 42000)
Cannot use file 'e\SQL-Data\MSSQL\data\Citrix_DB_Data.MDF' for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used. File 'Citrix_DB_Data' cannot be restored to 'e:\SQL-Data\MSSQL\data\Citrix_DB_Data.MDF'. Use WITH MOVE to identify a valid location for the file.
Cannot use file 'e\SQL-Data\MSSQL\data\Citrix_DB_Data.LDF' for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used. File 'Citrix_DB_Log' cannot be restored to 'e:\SQL-Data\MSSQL\data\Citrix_DB_Data.LDF'. Use WITH MOVE to identify a valid location for the file.
RESTORE DATABASE is terminating abnormally.
Regards,
On your new cluster, you have not made drive E: a dependency for SQL Server.
If you have a shared drive E:, then:
1) Take SQL Server offline
2) Create a disk resource for drive E:
3) Bring up the properties for the SQL Server service and make drive E: a
dependency
4) Bring the SQL Server group online
5) Restore your DB
If you don't have a drive E:, then restore the backup to another drive which
is a dependency for SQL Server.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"vt2006" <someone@.somewhere.com> wrote in message
news:uYNrFdH8GHA.4572@.TK2MSFTNGP02.phx.gbl...
Hi all,
I backed up a database called Citrix_DB through Enterprise Manager from a
standalone MSSQL 2000. I tried to restore the DB to another MSSQL 2000
Cluster but failed. Would anyone know how to get it fixed? Thanks a lot. And
below is the error message: -
Microsoft SQL-DMO (ODBC SQLState: 42000)
Cannot use file 'e\SQL-Data\MSSQL\data\Citrix_DB_Data.MDF' for clustered
server. Only formatted files on which the cluster resource of the server has
a dependency can be used. File 'Citrix_DB_Data' cannot be restored to
'e:\SQL-Data\MSSQL\data\Citrix_DB_Data.MDF'. Use WITH MOVE to identify a
valid location for the file.
Cannot use file 'e\SQL-Data\MSSQL\data\Citrix_DB_Data.LDF' for clustered
server. Only formatted files on which the cluster resource of the server has
a dependency can be used. File 'Citrix_DB_Log' cannot be restored to
'e:\SQL-Data\MSSQL\data\Citrix_DB_Data.LDF'. Use WITH MOVE to identify a
valid location for the file.
RESTORE DATABASE is terminating abnormally.
Regards,