Comments on: STSADM: Command Line Error http://stevepietrek.com/2009/02/19/stsadm-command-line-error/ My continuous learning of SharePoint, Silverlight, WP7 Development, Office, VSTO, C#... Tue, 24 May 2011 06:39:09 +0000 hourly 1 http://wordpress.com/ By: James Cod http://stevepietrek.com/2009/02/19/stsadm-command-line-error/#comment-2156 Mon, 16 Nov 2009 10:18:56 +0000 http://stevepietrek.com/?p=520#comment-2156 Part 2:
——

Hi, this is James again, It worked !! stupid MS cmd , gotta switch Note++

]]> By: James Cod http://stevepietrek.com/2009/02/19/stsadm-command-line-error/#comment-2155 Mon, 16 Nov 2009 10:05:27 +0000 http://stevepietrek.com/?p=520#comment-2155 Post 1:
——-
Crazy workaround, I’m gonna try it now & post my response in few minutes

]]> By: Willem Bruinius http://stevepietrek.com/2009/02/19/stsadm-command-line-error/#comment-1605 Fri, 20 Feb 2009 09:28:39 +0000 http://stevepietrek.com/?p=520#comment-1605 Been a while since i last had this issue and posted from memory, saw my memory is somewhat sloppy on the issue so i figured i repost the correct sollution ;-)

The problem is one that has to do with applications encoding text as ANSI, the stsadm executambe is using the UTF-8 encoding to recieve input and thus the commans pasted in ANSI will fail.

Serge van den Oever has posted an article on his blog explaining the problem and a solution to once again copy and pate your way through implementations using the famous 128 character long stsadm commands .

His post can be found here: http://weblogs.asp.net/soever/archive/2007/12/22/sharepoint-stsadm-exe-and-the-infamous-quot-command-line-error-quot.aspx

In sumary his advise is to use an application like Notepad++ to paste the text in and then switch the encoding to UTF-8 from there a copy paste will once again work as expected.

Regards,

Willem Bruinius

]]> By: Willem Bruinius http://stevepietrek.com/2009/02/19/stsadm-command-line-error/#comment-1604 Fri, 20 Feb 2009 09:11:58 +0000 http://stevepietrek.com/?p=520#comment-1604 The problem is one that has to do with applications encoding text as unicode, the cmd window is using the ANSI encoding to display and recieve text and thus the unicode imports will be garbled.

Serge van den Oever has posted an article on his blog explaining the problem and a solution to once again copy and pate your way through implementations using the famous 128 character long stsadm commands ;-) .

His post can be found here: http://weblogs.asp.net/soever/archive/2007/12/22/sharepoint-stsadm-exe-and-the-infamous-quot-command-line-error-quot.aspx

In sumary his advise is to use an application like Notepad++ to paste the text in and then switch the encoding to ANSI from there a copy paste will once again work as expected.

Regards,

Willem Bruinius

]]> By: John Ferringer http://stevepietrek.com/2009/02/19/stsadm-command-line-error/#comment-1601 Thu, 19 Feb 2009 19:58:59 +0000 http://stevepietrek.com/?p=520#comment-1601 Yep. Smart quotes and dashes somehow get pasted into the Windows Command Shell when you’re coming from an application that uses them (such as Outlook or Word) and STSADM.exe doesn’t like smart quotes. This can *really* be a frustrating issue to sort out. Bottom line, when in doubt you should always type out your STSADM commands.

]]>