Tuesday, July 10, 2007

STSADM “Command Line Error”

Today I was deploying a solution to my server through the command line. After pasting command that I had copied from a web I received the "Command Line Error". The solution is to write the command without paste. The reason is the encoding of the pasted text. I found the explanation in the blog in the related links.

Related Links:
http://blogs.msdn.com/sharepoint/archive/2007/02/24/updated-installation-guide-for-the-20-server-admin-application-templates-for-wss-3-0.aspx



 

16 comments:

Anonymous said...

Fixed it for me, thanks for that one!

Serge van den Oever [Macaw] said...

Yep it is the encoding. See http://weblogs.asp.net/soever/archive/2007/12/22/sharepoint-stsadm-exe-and-the-infamous-quot-command-line-error-quot.aspx for more information.

Anonymous said...

Worked for me too!!!!! Thank you.

Popovic Sasa said...

You saved me with this post. Thank you very much!

Anonymous said...

I am lucky I found your post!
Thanks so much!

Anonymous said...

Hi,

It was a Wonderful tip. i suffer a lot because this error

thanks once again
Keep up the Good work

BK

Anonymous said...

thanks for the post, nice one microsoft :P

Anonymous said...

Thanks for your post...It is helped me a lot...GK

hamidi said...

wow! i could think about any reason other than this! when a line is pasted in the command line, it includes no encoding, even if it had been copied with encoding. this was what i thought. in the command line every character is a single byte, isn't it? command line can't hold unicode characters, ain't i right?

Lex said...

Thanks for this! I thought I was going insane...

Anonymous said...

any more posts coming ?

Anonymous said...

Thats it.. Thanks a lotttttt...
I saved me .. Gud work Dude..

Anonymous said...

Legend! Thank you so much :)

Anonymous said...

Million Thanks!
bts

Anonymous said...

Nearly five years later, and this post is still applicable! It fixed me. I cheated a little... I copied and pasted it to Notepad (which fixed the encoding) and then copied and pasted it back in to the command prompt. Thanks for the tip, I'd of never figured that out on my own.

Anonymous said...

Saved my day - thank you!

 
Online Visitors