.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links

Error: Office 2003 SP3 "Command text was not set for the command object"

Posted By:      Posted Date: October 28, 2010    Points: 0   Category :Sql Server



I have a customer who is using Office 2003 pivot tables against AS2000 cubes. Last week they upgraded to SP3 of Office and now we are getting "Command text was not set for the command object" when trying to refresh / manipulate the pivot tables. Applies to existing pivot tables as well as new ones we create. I found a few references to interesting experiences with SP3, but none that mention this error. We know the cubes are OK because we can use pivot tables against them from another (server) machine that escaped the upgrade. Currently trying to prove or disprove that it was the upgrade specifically that caused the problem.


Has anyone else bumped into something like this? Found a way around it?


Thanks in advance

View Complete Post

More Related Resource Links

Error Opening Office Documents with Office 2003


Hi all,

Sharepoint 2007. When I try to open documents (clicking on it) in a sharepoint document Library with office 2003, i receive an error that say that the file is not valid and to check the path.

If i try to open document with the scroll down menu and the "edit command", the document open normaly.

Even if i try to open the same document with office 2007 it works normally. 

It seem something due to the read only opening of the file...


Can you help me?

Many thanks


Error while setting up application on Win7 using Visual Studio.NET 2003


Hi All,

Getting the below error while setting up application on Win 7 using visual studio.NET 2003.


cannot find the components for communiacting with the front page server extensions...


I understand by the error, i need to install Front page server extension, but not able to figure how to install using IIS 7.5.

I had XP machine with IIS 5.1, able to find the option.


Need your help in resolving this.




Smart Tags: Realize the Potential of Office 2003 by Creating Smart Tags in Managed Code


While you may well be excited about the prospect of building managed smart tags, there is little information available to help you create them using .NET. In this article the author fills in the blanks. Along the way he discusses the Microsoft Office Smart Tag List XML schema, advanced managed smart tags for Office 2003 and Office XP, and deploying these features in an organization.

Ben Waldron

MSDN Magazine February 2005

Office 2003: Secure and Deploy Business Solutions with Microsoft Visual Studio Tools for Office


Microsoft Visual Studio Tools for the Microsoft Office System is a new technology that brings the advanced features of Visual Studio .NET and the .NET Framework to applications built for Microsoft Office Word 2003 and Microsoft Office Excel 2003. Deploying solutions built with this technology requires that you understand how runtime security is enforced in managed applications and how to configure users' systems to run your solutions without introducing security holes.To promote that understanding, this article will demonstrate how to establish trust, explain policy considerations and permissions, and explain what trusted code is all about. Secure assembly deployment is also covered in detail.

Brian A. Randell and Ken Getz

MSDN Magazine March 2004

Office 2003: Host an Interactive Visio Drawing Surface in .NET Custom Clients


Microsoft Office Visio 2003 introduces a new drawing component that allows you to embed an interactive drawing surface into your application's user interface. You can drive the Visio drawing component from events in your host application or with data from a Web Service and an ADO.NET data adapter. The Visio drawing component supports the rich Visio application programming model, giving you control over how graphics are used and displayed on the drawing surface. This article explains how to embed the Visio drawing component into a C#-based Windows Forms client app that retrieves data from the Fabrikam 2.0 Web Service.

Mai-lan Tomsen Bukovec and Blair Shaw

MSDN Magazine December 2003

Office 2003: Bring the Power of Visual Studio .NET to Business Solutions Built with Microsoft Office


Microsoft Visual Studio Tools for the Microsoft Office System is a new technology that brings the advanced features of Visual Studio .NET and the .NET Framework to apps built on Microsoft Word 2003 and Excel 2003. Now you can use Visual Basic .NET and C# to write document-centric, managed code solutions that run in-process with Word 2003 or Excel 2003, taking advantage of the rich object models they expose. Along the way you get the benefits of the managed environment in which a fully compiled .NET-based application executes, including code access security.

Ken Getz and Brian A. Randell

MSDN Magazine September 2003

InfoPath: Turn User Input into XML with Custom Forms Using Office InfoPath 2003


Office InfoPath 2003 is a new Microsoft Office product that lets you design your own data collection forms that, when submitted, turn the user-entered data into XML for any XML-supporting process to use. With an InfoPath solution in place, you can convert all those commonly used paper forms into Microsoft Office-based forms and end the cycle of handwriting and reentering data into your systems. Today organizations are beginning to realize the value of the mountains of data they collect every day, how hard it is to access it, and are striving to mine it effectively. InfoPath will aid in the design of effective data collection systems. Here the author shows you how to get started.

Aaron Skonnard

MSDN Magazine September 2003

Editor's Note: Get Ready For Microsoft Office 2003


Over the years, we've celebrated a lot of anniversaries in this column. Who can forget our "Ten Years of ENIAC!" Editor's Note back in June 1957? Or the "How Far We've Come: Five Years of the Altair 8800" issue back in January 1980? Or even the "Macintosh Interface: 15 Years Without an Update" Editor's Note page just four years ago?.

MSDN Magazine May 2003

Office 2003 integration with MOSS 2007



All my documents are opening as read-only when I open from SharePoint sites even when I click on "Edit in ..." option on some machines.

The users seem to have correct permissions on the site.



Office 2003 integration with MOSS 2007


Hi ,

All my files/docs in MOSS 2007 open as read-only with Office 2003 standard edition in some machines.

The user seems to have sufficient permissions to edit but still not able to do so.

Any suggestion?




Office 2010 will not open Office 2003 Documents on SharePoint

Going directly to a document in the document view and selecting any of them will present the Read Only/Edit prompt and when clicking Read Only Word or Excel 2010 depending on the document type will open to a blank page and just sit there. If you do a search and then click on the documents that are returned in the search results, it opens as expected.

Sharepoint 2003 + Windows Terminal Server 2008 + Office 2007 problem?

Hi, We have a customer where some users runs Windows Terminal Server 2008 with Office 2007. They open documents from a Sharepoint 2003 site. When they open an excel sheet they get a button in the document which says "Server workbook: Click edit workbook to edit this workbook" and there is a button: "edit workbook" The users clicks "edit workbook" but get an error message saying there is no connection to the server.  They are able to edit the document, but not save it back to the sharepoint site. Most other users work on their local computer with Office 2003. Here, everything works fine and there are no button/message stating its a server workbook.   Is this caused due to some compatability issues between Sharepoint 2003 and Office 2007?   Best regards, Thomas Hansen ErgoGroup AS

Office 2010 Web Applications Install Error

We have a SharePoint 2010 Server setup in a farm configuration with a SQL 2008R2 clustered back-end that we are attempting to install Office Web Applications on.  We are following the technet article http://technet.microsoft.com/en-us/library/ff431687.aspx#bkmk_ins_exis_farm.  When we attempt to install the Office Web Applications on the SharePoint 2010 server (logged in as a member of the Administrators/farm admins) the progress bar completes and then displays the error "Microsoft Office Web Apps encountered an error during setup".  Looking through the Wac Server Setup.log file that setup generates doesn't yield much or any clues as to what is failing (it's lengthy and appears to just be detailing applications of a variety of languages installing and then rolling back).  The event logs are also filled with messages about the various Web Apps installing in a variety of languages and then rolling back when setup fails.  The only MsiInstaller event in the event logs that looks of any consequence is: "Windows Installer installed the product. Product Name: Microsoft Office Web Apps Application Server Components. Product Version: 14.0.4763.1000. Product Language: 0. Manufacturer: Microsoft Corporation. Installation success or error status: 1603." Does anyone have any experience with this issue or any suggestions/guidance?

Sharepoint 2010 integration with Office 2010, 2007,2003

hi, i am looking, if some one know about the details or link, for the details about the Sharepoint 2010 integration with Office 2003, 2007 and 2010 versions. We will be migrate in couple of months to 2010 but we have mixed flavor of the office version in our environment. We have 2003, 2007 and 2010. Is their any blog post or anyone know what is now possible with 2010 but not in the 2007 or 2003. like a comparison chart.   thanks WSi am at entry level administrator

Office document are not opened correctly! (XLSX gives error. XLS asks login)

I have SharePoint 2010 based farm and MS Office 2007. SharePoint have Enterprise feature enabled. In my test I'm opening documents in the front-end machine. Problem 1: When XLSX excel documents are tried to be opened, it try to open to the browser. Error is given: Your request can not be handled. Please wait few minutes and try again.(free translation from local language) Because of error I started Excel services, but nothing changed. Problem 2: When XLS excel documeents are opened, it opens to the Office Excel client, but it request login. After login xls document is opened correctly. Why I need to login? Problem 3: When DOC word documeents are opened, it opens to the Office Word client, but it request login. After login doc document is opened correctly. Why I need to login?Kenny_I

Using a Variable in SSIS - Error - "Command text was not set for the command object.".

Hi All, i am using a OLE DB Source in my dataflow component and want to select rows from the source based on the Name I enter during execution time. I have created two variables, enterName - String packageLevel (will store the name I enter) myVar - String packageLevel. (to store the query) I am assigning this query to the myVar variable, "Select * from db.Users where (UsrName =  " + @[User::enterName] + " )" Now in the OLE Db source, I have selected as Sql Command from Variable, and I am getting the variable, enterName,. I select that and when I click on OK am getting this error.   Error at Data Flow Task [OLE DB Source [1]]: An OLE DB error has occurred. Error code: 0x80040E0C.An OLE DB record is available.  Source: "Microsoft SQL Native Client"  Hresult: 0x80040E0C  Description: "Command text was not set for the command object.". Can Someone guide me whr am going wrong? myVar variable, i have set the ExecuteAsExpression  Property to true too. Please let me know where am going wrong? Thanks in advance.
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend