Re: stsadm failing with "command line error"

Tech-Archive recommends: Fix windows errors by optimizing your registry

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










.

Relevant Pages

  • Re: dcdiag - advertising errors on newley promoted domain controller
    ... Can you do the following on uksccmads01 ... The problem may actually have nothing to do with the new server but the ... From a command prompt try and see if you get any additional info ... Skipping site UK-CCM, this site is outside the scope ...
    (microsoft.public.windows.server.active_directory)
  • Re: dcdiag - advertising errors on newley promoted domain controller
    ... Can you do the following on uksccmads01 ... The problem may actually have nothing to do with the new server but the ... Active Directory Forest Replication GUIDs Found: ... From a command prompt try and see if you get any additional info ...
    (microsoft.public.windows.server.active_directory)
  • Re: dcdiag - advertising errors on newley promoted domain controller
    ... Default Server: uksccmads01.jw-uk.jameswalker.co.uk ... Output from dnslint on uksccmads01: No erros found, ... Active Directory Forest Replication GUIDs Found: ... From a command prompt try and see if you get any additional info ...
    (microsoft.public.windows.server.active_directory)
  • Re: dcdiag - advertising errors on newley promoted domain controller
    ... Then change the secondary DNS to the other site DNS server. ... Skipping site UK-CCM, this site is outside the scope provided ... command line arguments provided. ...
    (microsoft.public.windows.server.active_directory)
  • Re: dcdiag - advertising errors on newley promoted domain controller
    ... Both forward and reverse zones and server records have the correct IP ... Once you have found the error then on both servers, from a command ... Skipping site UK-CCM, this site is outside the scope provided ...
    (microsoft.public.windows.server.active_directory)