Re: stsadm failing with "command line error"

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi Peter.

Yes I have placed the details in the path vars and tried it using the full
directory name but still have the same problem. SPS and SQL are on the same
server and we can access the portal site with no problems. I have tried with
the local admin account and the domain admin accounts still with no joy!!!

P

"Peter Jakab" <someone@xxxxxxx> wrote in message
news:OrR4rKKKGHA.3120@xxxxxxxxxxxxxxxxxxxxxxx
P,

the path for stsadm.exe is normally not in the path environment variable.

So: you open a command prompt, then navigat to the folder that contains
stsadm.exe (in a normal installation its located in the
"C:\Program Files\Common Files\Microsoft Shared\web server
extensions\60\BIN" directory, so you type
cd "C:\Program Files\Common Files\Microsoft Shared\web server
extensions\60\BIN"
on the command prompt, and run the stsadm -o addwppack .... command.

Also make sure, that the user, with that you are working has the necessary
permissions on the SQL Server SPS Content database, otherwise the command
will also fail!
If the database and front end servers are on separate machines, the sql
client tools must also be installed on the front end server machine to
work with stsadm!

HTH

Peter

"msnews.microsoft.com" <paul.ashford@xxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:%23dKtT9JKGHA.2828@xxxxxxxxxxxxxxxxxxxxxxx
Ok. Can't find any information on this. Trying to register the remote
desktop component on our sharepoint portal server and each time it comes
back with "command line error". Even tried with different components and
different local/domain admin accounts.

I'm running the command line, and I have tried this using the correct
case information (as found in other posts)

stsadm.exe -o addwppack -filename RemoteDesktopWebPart.Cab -globalinstall


Any asisstance would be gr8
P






.

Relevant Pages

  • Guide to Reinstall - Migrate SPS 2003 to SQL 2005 (CTP)
    ... Just succeeded in setting up my server in running SPS 2003 on SQL 2005 ... The task was to use the same kit of hardware and have SPS and SQL2005 on the ... You set up your SQL 2005 Enterprise by selecting all default options - ... be used to modify later on the config database that you will create. ...
    (microsoft.public.sharepoint.portalserver)
  • Re: "True" hardware requirements for SPPS
    ... Win2K3 Server ... > I find it easiest to think of it as being 3 systems; SQL, SPS and Indexer. ... > it needs CPU and about 1GB of ram, indexing is all about CPU and disk memory ...
    (microsoft.public.sharepoint.portalserver)
  • Re: "True" hardware requirements for SPPS
    ... > Win2K3 Server ... >> I find it easiest to think of it as being 3 systems; SQL, SPS and Indexer. ... >> it needs CPU and about 1GB of ram, indexing is all about CPU and disk memory ...
    (microsoft.public.sharepoint.portalserver)
  • Re: How to Cluster Portal Server 2003
    ... your sps server will act as your web server, job/index server, search server. ... sql holding all the data config etc. ... as sps basically runs on top of sql, if your sql fails your cluster wull ...
    (microsoft.public.sharepoint.portalserver)
  • IBM INFORMIX ODBC DRIVER 3.00.00.13223 - ICLIT09B.DLL EXCEPTION_AC
    ... then use a link server – Microsoft OLE DB Provider for ODBC Driver. ... and Linked server test connection successfully and I can return most records ... A severe error occurred on the current command. ... Here's my SQL and ERRORS ...
    (microsoft.public.sqlserver.odbc)