Re: stsadm failing with "command line error"
- From: "Paul" <paul.ashford@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 3 Feb 2006 11:33:40 -0000
Very Strange. managed to get it working now!!!!
Thanks for your help
"Peter Jakab" <someone@xxxxxxx> wrote in message
news:ubTB1LLKGHA.2628@xxxxxxxxxxxxxxxxxxxxxxx
maybe you mistype something.
What is the result if you type only
stsadm.exe -o addwppack
?
"msnews.microsoft.com" <paul.ashford@xxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:eI2rK$KKGHA.500@xxxxxxxxxxxxxxxxxxxxxxx
Still no joy, results below
C:\Documents and Settings\Administrator>cd \spswebparts
C:\SPSWebParts>
C:\SPSWebParts>stsadm.exe -o addwppack -filename
"C:\SPSWebParts\RemoteDesktopWe
bPart.Cab" -globalinstall
Command line error.
Usage:
stsadm.exe -o <operation> [<parameters>]
stsadm.exe -help [<operation>]
Operations:
addalternatedomain
addpath
addtemplate
adduser
addwppack
"Peter Jakab" <someone@xxxxxxx> wrote in message
news:eHH89zKKGHA.500@xxxxxxxxxxxxxxxxxxxxxxx
on the -filename parameter use the full path to the cab file, and put "
marks before and after like this:
stsadm -o addwppack -filename
"c:\......\somepart.cab" -globalinstall -force
HTH
Peter
"Peter Jakab" <someone@xxxxxxx> wrote in message
news:ONQvxsKKGHA.1848@xxxxxxxxxxxxxxxxxxxxxxx
what is the exact error message?
Peter
"msnews.microsoft.com" <paul.ashford@xxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:uCwfaWKKGHA.744@xxxxxxxxxxxxxxxxxxxxxxx
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
.
- References:
- stsadm failing with "command line error"
- From: msnews.microsoft.com
- Re: stsadm failing with "command line error"
- From: Peter Jakab
- Re: stsadm failing with "command line error"
- From: msnews.microsoft.com
- Re: stsadm failing with "command line error"
- From: Peter Jakab
- Re: stsadm failing with "command line error"
- From: Peter Jakab
- Re: stsadm failing with "command line error"
- From: msnews.microsoft.com
- Re: stsadm failing with "command line error"
- From: Peter Jakab
- stsadm failing with "command line error"
- Prev by Date: Re: How to create an untemplated site?
- Next by Date: Re: Prob.installing, even if i'm using the .chm . It doesn't displ
- Previous by thread: Re: stsadm failing with "command line error"
- Next by thread: Alert Problem.
- Index(es):
Relevant Pages
|