Logo 
Search:

MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

MOSS2007 "DBA-Created databases" psconfig error

  Asked By: Michael    Date: Nov 05    Category: MOSS    Views: 2149

I'm following the instructions at
technet2.microsoft.com/.../356d3a0b-fc26-455c-9a
fb-6d2ffdceef841033.mspx?mfr=true to set up a new farm using DBA-created
databases. I've set the databases up and I'm running the following
psconfig command to create the farm:

psconfig -cmd configdb -create -server ourdbserver -database
our_Config_db -user ourdomain\farmacct -password "pw"
-admincontentdatabase Our_AdminContent_db

The command returns "The -create command is invalid". The PSCDiagnostics
log shows the following snippet:

Entering function CommandLine.Parse
Found command line arguments, so will start parsing and validating
CommandLine.IsCommand: The arg -cmd is a command cmd using delimiter -

Found a command key cmd
Trying to find command configdb
Entering function get CommandCollection.this[string key]
Entering function CommandCollectionBase.Get
Found value in collection for key configdb
Leaving function CommandCollectionBase.Get
Found command configdb in collection
Leaving function get CommandCollection.this[string key]
Found a command for configdb for arg configdb
The command configdb has parameters, so I will parse those now
Entering function CommandLine.ParseCommandParameters
Parsing parameters for command configdb
Starting to parse parameters for command configdb
Entering function Command.AreAllParametersChosen
Parameter create for command configdb is not chosen
Leaving function Command.AreAllParametersChosen
CommandLine.IsCommand: The arg -create is not a command cmd

It looks like it wants more parameters, but I've fed it everything
specified by the MS doc. Do I need to specify a domain and an OU as
well? If so, how do you decide on what domain and OU to give it?

Share: 

 

7 Answers Found

 
Answer #1    Answered By: Himanshu Gohil     Answered On: Nov 05

I ran it today exactly the same way and it didn't return "The -create
command is invalid". It complained about an incorrect password, then an
incorrect database collation, and then (once all that was fixed) it
succeeded.

Is there a timer job that could affect the behaviour of psconfig?

 
Answer #2    Answered By: Ashton Schroeder     Answered On: Nov 05

Now I'm getting an error  configuring the WSS Search database. I ran:

Stsadm -o spsearch -action start  <Farm Service Account>
<DomainName\UserName> -farmservicepassword <password>
-farmcontentaccessaccount <DomainName\UserName>
-farmcontentaccesspassword <password> -databaseserver <Databaseserver>
-databasename <SqlWSSSearchDatabaseName>



...and I got an event 10035 warning in the WFE application log:

"Could not import the registry hive into the registry because it does
not exist in the configuration database."

The next entry in the WFE application log is informational and says:

"Successfully stored the application configuration registry snapshot in
the database. Context: 'Search index file on the search server'" (ID
10044)

Does this mean that stsadm recovered from the failed registry hive
import? Is it safe to carry on?

 
Answer #3    Answered By: Iris Ballard     Answered On: Nov 05

Not even a nibble. It's pretty lonely in this thread!

 
Answer #4    Answered By: Jamila Guthrie     Answered On: Nov 05

Configuring search is not my cup if tea. However, why are you using stsadm
rather than the user interface.

 
Answer #5    Answered By: Kalpana Ghatge     Answered On: Nov 05

So that I can specify the database for it to use.

 
Answer #6    Answered By: Bobbie Rodgers     Answered On: Nov 05

I had the "-farmservicepassword" parameter messed up. Just tried it
again as:

Stsadm -o spsearch -action start  -farmserviceaccount
<DomainName\UserName> -farmservicepassword <password>
farmcontentaccessaccount <DomainName\UserName>
-farmcontentaccesspassword <password> -databaseserver <Databaseserver>
-databasename <SqlWSSSearchDatabaseName>


and it succeeded.

 
Answer #7    Answered By: Bhumi Gokhale     Answered On: Nov 05

Don't forget that 'stsadm.exe -o spsearch' is WSS V3, and 'stsadm.exe -o
osearch' is SharePoint Server Search.

MOSS Search command  Line:

· Stsadm.exe -o osearch can be used to set  a variety of things from
server Search roles to propagation locations. The following are examples of
osearch commands:

· Stsadm.exe -o osearch -action start  -role Index -farmcontactemail
searchadmin@... -farmperformancelevel Maximum -farmserviceaccount
trainsbydave\safarm -farmservicepassword P@ssw0rd -defaultindexlocation
c:\indexes -propagationlocatoin c:\qindexes

· You may change many of the above parameters  as follows:

· -action can be List, Start, or Stop

· -role can be Index, Query, or IndexQuery

· -farmperformancelevel can be Reduced, PartlyReduced, or Maximum

· You may also use the -f parameter to suppress prompts

Osearchdiacriticsensitive (CAUTION)

· Stsadm.exe -o osearchdiacriticsensitive -ssp <"SSP name"> -setstatus
true | false -noreset -force enables Sharepoint Server Search to recognize and
index diacritic marks, also called accent marks. For example, stsadm.exe -o
spsearchdiacriticsensitive -setstatus true will now index 'ñ' and 'n' as
different characters. By default, they are both indexed as 'n'. Caution should
be exercised if you choose to not use -noreset, because a full Index reset will
occur.

WSS V3 Command Line:

Stsadm.exe -o spsearch is used to manage the WSS V3 Search service. You can
start or stop Full and Incremental crawls, change content database search server
association, change the default content access account, and modify the Index
file location. For example, stsadm.exe -o spsearch -action list will display all
WSS Search Servers in the farm  including the Index file location, status of
diacritic marks, and the content database/Search Server associations. Following
are the command line  options for spsearch.

[-action <list|start|stop|attachcontentdatabase|detachcontentdatabase|fullc

awlstart|fullcrawlstop>]

[-f (suppress prompts)]

[-farmperformancelevel <Reduced|PartlyReduced|Maximum>]

[-farmserviceaccount <DOMAIN\name> (service credentials)]

[-farmservicepassword <password>]

[-farmcontentaccessaccount <DOMAIN\name>]

[-farmcontentaccesspassword <password>]

[-indexlocation <new index location>]

[-databaseserver <server\instance> (default: <current server>)]

[-databasename <database name> (default: <current search DB)]

[-sqlauthlogin <SQL authenticated database user>]

[-sqlauthpassword <password>]

-action list

-action stop

[-f (suppress prompts)]

-action start

-farmserviceaccount <DOMAIN\name> (service credentials)

[-farmservicepassword <password>]

-action attachcontentdatabase

[-databaseserver <server\instance> (default: <current server)]

-databasename <content database name>

[-searchserver <search server name> (default: <current server)]

-action detachcontentdatabase

[-databaseserver <server\instance> (default: <current server>)]

-databasename <content database name>

[-f (suppress prompts)]

-action fullcrawlstart

-action fullcrawlstop

Spsearchdiacriticsensitive (CAUTION)

· Stsadm.exe -o spsearchdiacriticsensitive -setstatus [True | False]
[-noreset][-force] enables WSS Search to recognize and index diacritic marks,
also called accent marks. For example, stsadm.exe -o spsearchdiacriticsensitive
-setstatus true will now index all 'ñ' and 'n' as different characters. By
default, they are both indexed as 'n'. Caution should be exercised if you choose
to not use -noreset, because a full Index reset will occur.

 
Didn't find what you were looking for? Find more on MOSS2007 "DBA-Created databases" psconfig error Or get search suggestion and latest updates.




Tagged: