Automatically Rename Columns in Office 2013

I am using Power Pivot to pull in data from a SSAS tabular model and then creating an excel worksheet with data from the Power Pivot model. Unfortunately, the headings always include tablenamecolumnnamecolumnname (i.e. CustomerCustomerPhoneNumberCustomerPhoneNumber
and PhoneNumber). If I have a data base table or another worksheet that has a column for the long name and a column for the name I want for the column, would it be possible to automate the renaming of the headings with special programming in Excel?
If so, how? I haven't had any experience with doing anything like this. Any help will be greatly appreciated!

Hi,
This is the forum to discuss questions and feedback for Microsoft Excel, please post your question to the MSDN forum for Excel
http://social.msdn.microsoft.com/Forums/en-US/home?forum=exceldev&filter=alltypes&sort=lastpostdesc
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
George Zhao
TechNet Community Support

Similar Messages

Excel Calulates twice when set to Automatic in Office 2013

I have had a group of users who have raised an issue with Office 2013 running far slower for a number of spreadsheets. After investigating the fault, I have identified the issue as being due to the way in which Excel appears to be handling the calculations.
When I open the spreadsheet myself, on Office 2013 32 or 64 bit, I am asked to update the data, at which point the spreadsheet runs the calculations if I accept, and then runs them again. If I set this behaviour to manual, I can open the spreadsheet, request
an update, and then manually calculate, which only takes one pass at the data but provides the same results. The behaviour does not persist on an Excel 2010 machine, which does only a single pass on both manual and automatic. The spreadsheet does pull data
from an external sheet, but as this only occurs in Office 2013, I don't believe this to be intended behaviour.
Is there anyone who can shed some insight into why this acts this way, and how to prevent this. We are trying to upgrade our business to 2013, and are getting a huge amount of push back from this particular set of users over this issue

Hi,
According to your description, my understanding is that you want to calculate once time when the file opening or update data.
I suggest you can make the file always calculate manual.
You may try to do following steps:
Click File>Options>Formulas> Calculate Options> Manual
Then you can save it .
For more detail information, please refer to the following link:
http://office.microsoft.com/en-us/excel-help/change-formula-recalculation-iteration-or-precision-HP010054149.aspx
The article applies to Excel 2007, but we can refer to it.
Regards,
George.zhao

Automatic renaming of columns

Hi,
Due to new busines requirements, I have to comment couple of tables in the query object. When I start compiling after commenting out the conditions and tables, it starts throwing errors BAD BIND VARIABLE xxx NOT DEFINED. Report has automatically renamed a lot of columns by itself, for e.g. a column called name has been renamed to name1. There are PL/SQL programs which refer the column name. Now when I attempt to compile the report it starts throwing the error BAD BIND VARIABLE name NOT DEFINED because it has been renamed to name1, automatically by reports. I am baffelled at this as the columns does not have any relationship to the commented out tables. Is there a way to avoid this.
Thanks,
Bharath

The best way to avoid this is to alias the columns in the query. Whenever you make a change to the query, reports reparses the query. If other columns exist with the same name then a numeric suffix will be added. You could also apply the latest patch set (patch 10), as some fixes were made in this area.
Thanks,
Danny

Office 2013: 10 Best Features You Should Know About

The new Office 2013 has some key updates that, while aren’t quite as dramatic as theWindows 8 from Windows 7change, still have some pretty cool features for mobile and desktop. Office 2013, will ship sometime next year at prices that have not been announced
yet. Check out the top 10 features:
Going Mobile. Microsoft has geared the new software towards a more mobile-friendly audience, allowing users to interact more
efficiently on mobile and tablets including finger and stylus controls that may help to spur Office’s migration to mobile devices. Another decidedly mobile move is Office Home and Student 2013 RT, which includes Word, Excel, PowerPoint, and OneNote, will come
with ARM-based Windows 8 devices including Microsoft Surface .
In The Cloud. Microsoft’s SkyDrive cloud service is being positioned to play a key role in Office users’ daily computing
lives. Office 2013 will save your documents to SkyDrive by default, enabling you to access files from multiple devices, including a smartphone and tablet. When you sign into Office from another device, your personalized settings and recently used files
are already there for you. The new Office is available as a cloud-based subscription too. Office 365 is now also available for home-based users as well as businesses. Subscribers will get automatic upgrades, additional SkyDrive storage, multiple installs for
several users, and added perks such as international calls via Skype.
Finger and Stylus. Office 2013 embraces touch and pen input. The touch and stylus features are geared towards smartphones and
tablets, as well as multi-touch laptops. The touch features are the same as users are accustomed to on their smartphones and tablets; swipe a finger across the screen to turn a page, pinch and zoom to read documents, and write with a finger or stylus.
Metro Style. Office 2013 conforms to Microsoft’s “Metro” look that’s pervasive across the software developers latest mobile
apps. The Office Ribbon in Word 2013 has a flatter look than its predecessor in Word 2010.
PDF’s in Word. You can now edit PDF files in Word 2013 (yay!). Simply open a PDF as you would any other document. Word maintains
the formatting of the file which is fully editable. You can insert pictures and videos from online sites such as YouTube and Facebook as well. And readers can watch video clips from inside your document.
Excel. Excel offers some useful upgrades including new templates for budgets, calendars, forms, and reports. The new Quick
Analysis Lens lets you convert data to a chart or table in a couple of steps. Flash Fill recognizes patters in your data and automatically fills cells accordingly. For example: if you want to separate first and last names into separate columns simply begin
typing the first names in a new column, press Ctrl+E and Excel will copy the first names for you.
PowerPoint Has Gained Power. PowerPoint 2013 now sports an updated Start screen with a variety of new themes and color schemes.
The Presenter View now makes it easier to zoom in on a diagram, chart, or other detail that you want to emphasize to the audience. The Navigation Guide lets you switch slides, even move out of sequence, from a grid that you can see but your audience can’t.
Presentations can be worked on from different PCs by colleagues to create a single presentation. Comments are allowed and presentations are saved online by default to SkyDrive.
OneNote. OneNote automatically saves your notes to Skydrive, you don’t have to click “Save”, making your brainstorming sessions
readily available across multiple devices. OneNote 2013 allows you to grab screens and add them to your notebooks.
Skype Has Been Integrated. You can now integrate Skype contacts with Microsoft’s enterprise-oriented Lync communications platform
for calling and instant messaging. Office subscribers get 60 minutes of Skype international calls each month.
Going Social. Office now includes Yammer, a secure and private social network for businesses that Microsoft tentatively acquired.
Yammer integrates with SharePoint and Microsoft Dynamics, the company’s line of CRM and enterprise resource planning apps. Office 2013′s People Card tool provides detailed information about your contacts, including their status updates from Facebook and LinkedIn.

Awesome!
Thanks for sharing the greate experience here. This is a good summary of Office 2013 cool features which is definitely useful for those who want to learn about the new Office.
Thanks,
Ethan Hua CHN
TechNet Community Support

Office 2013 applications crash with Document Information Panel open

I am using Office Professional Plus 2013 to work with documents that reside in SharePoint 2010 document libraries.
The content type(s) in that SharePoint site collection are set to automatically show the Document Information Panel when opened in Office applications. By opening any of these documents in their desktop app (via browser or Skydrive Pro), I am able
to check-out and edit content; but the check-in step always crashes the application, giving a pop-up error: "An unknown errors has caused <office program> to stop working."
By choosing to NOT automatically show the Doc Info Panel for these SharePoint documents, Office 2013 programs can handle everything just fine (editing, versioning, etc.).
If I don't auto-show the Doc Info Panel, but then manually open the panel once I get inside the program, this crashes the program in the same way as before.
If I save a local copy of a document and show the Doc Info Panel in any way (auto or manual), Office 2013 crashes.
I couldn't find any postings on this error and I don't see this incompatibility listed in the
Office 2013 known issues article and was wondering if anyone has had a similar experience?

I am having the exact same issue. I have created a Custom Site Column which is defined as a CHOICE. I do not want to put in a Default so left it blanl but field must be populated. I then put this into a Document Library Content Type.
With documents that are already been uploaded and in the Library when I pull up in Office Web Apps, I can make changes to the document but when I try to save it crashes.   Also, when I pull up document and say edit in Office Web Apps there is no
way to change information in the Document Information Panel since this does not appear.   (I forgot to mention that I required DIF to display in Content Type also).
This only happens on blank column fields when trying to save. If I do a Quick EDIT of the list and change my blank Choice columns to something(I created as radio buttons) and then go through the process it works OK and will save. Not sure
if this pertains to your issue but, I just prepopulate all columns with what the should be, when a brand new document from word, excel etc is created it is created from the Desktop version of Word Excel and when IT saves to SharePoint, I get
a message to choose information to put into properties before it actually saves.
Hope this helps a little.

Office 2013 apps showing templates error after Sysprepping Windows 7 with CopyProfile setting

Here is my setup:
I installed Windows 7 Professional.
I entered Audit Mode (which automatically logged me in as the built-in Administrator user) and installed the entire Office 2013 Professional Plus suite.
In Audit Mode, I opened Word 2013 to get through the "new user" prompts, such as the opening movie that plays in all Office 2013 programs. I did this to ensure that any new users who log into the computer would not need to sit through these "new
user" prompts. I also rearmed Office 2013.
I ran Sysprep with the CopyProfile setting in the Unattend.xml file, with the /generalize switch, and the /oobe switch. The CopyProfile setting copies settings from the built-in Administrator account to any new user who logs into the system.
Both Windows and Office were successfully activated using KMS.
Everything seemed to work, but there is one problem: when any user -- all of which are standard users rather than administrator users -- logs into Windows and runs any Office 2013 program that has templates (such as Word, Excel, and PowerPoint), the templates
on the Start page do not appear. In their place, the following error message appears on the Start page where the templates would normally have been listed:
"Sorry, we had trouble getting the featured templates and can't show them right now."
Below the error message is a link that reads “Work Offline.” If you click the “Work Offline” link, the error message disappears and the templates appear as they should. However, the error message re-occurs when the application is closed and re-opened.
If I login as the built-in Administrator account (i.e., the account I used to modify the default profile), this problem does not occur at all when using Office 2013 programs.
Any ideas?

"logs into Windows and runs any Office 2013 program that has templates (such as Word, Excel, and PowerPoint), the templates on the Start page do not appear. In their place, the following error message appears on the Start page where the templates would normally
have been listed:
"Sorry, we had trouble getting the featured templates and can't show them right now." "
Is there any chance to let you skip the Start page for Office application? I mean that try to open Office application (such Word)and go to File > Options > Untick the option "Show the Start screen when this application starts". Try to re-launch
the application again to check if the error still pop-up. If yes, I'm afraid the default build-in template is corrupted somehow and we need to copy a healthy one from another computer or totally rename normal.dotm documents from %userprofile%\AppData\Roaming\Microsoft\template.
Afte that, please check if the issue still persists.
Here is another thread with the similar topic for your reference:
http://social.technet.microsoft.com/Forums/ie/en-US/09a69d4c-9e5f-489d-ba7b-2af79ff83596/deploying-normaldotm-through-oct-doesnt-work-in-office-2013?forum=officesetupdeploy
http://answers.microsoft.com/en-us/office/forum/office_2013_release-office_install/can-not-sign-into-office-2013-version/b6951c25-2fb5-4fc1-a667-2327b9da2f7f
Tony Chen
TechNet Community Support

Office 2013 latest update broke new profile creation on all network computers

Hi,
Reporting a bug here!
Setup details:
We're using samba 3 as our backend and all workstation are Windows 7 Pro x64.
Office 2013 Home and Business Retail (en-us) Click 2 Run version
Context:
Deployed to the whole network of one of our client using the Office Deployement Tool.
We update their base update (no updates) to the latest update 15.0.4569.1508
Everything was working alright after initial Office 2013 installation with no updates. After updating the all the PCs to the latest version as of 31/03/2014, the user profile creation broke for newly created user.
Symptoms and causes:
Trying to log on as a new user on the machine would give the following error on Logon before automatically loging off because it cannot copy the following file to the new user profile:
D:\Users\Default\AppData\Local\Microsoft\Windows Live\Bici\_00.sqm
D:\Users\Default\AppData\Local\Microsoft\Windows Live\Bici\_01.sqm
D:\Users\Default\AppData\Local\Microsoft\Windows Live\Bici\_02.sqm
The Bici folder has Read and Execute permissions for everyone but the _XX.sqm files inside only have permissions (Full Control) for SYSTEM and Administrators and LOCAL SERVICE with the all permissions EXCEPT:
- FULL CONTROL
- TRAVERSE FOLDERS/EXECUTE FILES
- CHANGE PERMISSIONS
- TAKE OWNERSHIP
Solution:
I gave "everyone" Read and Execute permission on those files and the new user could log in and his profile got created alright.
The files with broken permissions time stamp shows they've been modified during the Office 2013 update and Bici seems to be a OneDrive related service. This bug should get fixed ASAP.
Event log error:
Windows cannot copy file \\?\D:\Users\Default\AppData\Local\Microsoft\Windows Live\Bici\_01.sqm to location \\?\D:\Users\TEMP\AppData\Local\Microsoft\Windows Live\Bici\_01.sqm. This error may be caused by network problems or insufficient security rights.
DETAIL - Access is denied.
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-User Profiles General" Guid="{DB00DFB6-29F9-4A9C-9B3B-1F4F9E7D9770}" />
<EventID>1509</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2014-04-04T07:15:51.922563800Z" />
<EventRecordID>9615</EventRecordID>
<Correlation />
<Execution ProcessID="940" ThreadID="1764" />
<Channel>Application</Channel>
<Computer>F00241D1DAAAD</Computer>
<Security UserID="S-1-5-21-1582357797-4105456612-768596941-1206" />
</System>
- <EventData Name="EVENT_COPYERROR">
<Data Name="Source">\\?\D:\Users\Default\AppData\Local\Microsoft\Windows Live\Bici\_01.sqm</Data>
<Data Name="Target">\\?\D:\Users\TEMP\AppData\Local\Microsoft\Windows Live\Bici\_01.sqm</Data>
<Data Name="Error">Access is denied.</Data>
</EventData>
</Event>

Hi dude,
I appreciate that your sharing your experience and solution here. And, I would report it through our internal channel. Thanks again.
Tony Chen
TechNet Community Support

? Office 2013 to support Excel 2003 (XLS) spreadsheets containing VBA CommandBars references

Thanks in advance for reading this and offering any wisdom you have! I am not an expert in any of the following, so apologies if off base.
The basic problem is: I need to use Excel 2013 to support Excel 2003 (XLS) spreadsheets containing VBA 'CommandBars' references which don't seem to work in Excel 2013. Details below.
Most of our users are still using older desktop windows PCs and Office 2003! We are beginning to upgrade to laptops running Windows 8.1 with Office 2013. Of course, we IT technical people are using the new laptops first. These new laptops are
64 bit.
Years ago, someone did a lot of development with spreadsheets here in Excel 2003 file formats that automates many activities and routines. Now we with the new laptops are having to support this development using new machines.
There is a basic compatibility issue that appears when first opening these Excel 2003 files that have VBA code that I'll detail below; I seem able to get by that problem.
The current problem appears to be that the existing Excel 2003 VBA code has many references to: "For Each bar In Application.CommandBars". As I've learned, the Application.CommandBars VBA functionality is focused on older MS Office versions' menu
commands, but "...Starting from Office 2007 the Fluent UI is used instead." In other words, because MS Office isn't menu-driven beginning with version 2007 (uses 'the ribbon'), it appears that these references to: "For Each bar In Application.CommandBars"
create a basic incompatibility to opening these spreadsheets in Office 2013.
For a spreadsheet, after I resolve the issue detailed below and save it, when I reopen it I encounter error "Compile error: can't find project or library."
For example, the following code snippet:
Private Sub Workbook_Open()
For Each bar In Application.CommandBars
bar.Enabled = False
Next
results in: "Compile error: can't find project or library."
(Sorry, can't include images yet, I am not a VERIFIED USER of this forum yet.)
I went into VBE's menu: Tools>References and check for anything marked MISSING, which I deselected. But I am still receiving this error.
I don't want to get into changing the code a lot to support both Excel 2003 and 2013 (I am no VBA expert, just a dabbler).
And Microsoft officially says that Office 2003 is incompatible with Windows 8 although Application.CommandBars seem to be somewhat supported in Office 2013 .
Are you aware of a quick VBA workaround to get by this?
•I could comment out the validations, commands for: "For Each bar In Application.CommandBars" but then the spreadsheet code probably won't work for users using Office 2003.
Alternatives would be:
•Installing Office 2003 on my Win 8.1 64 bit laptop anyway, in spite of MS's saying incompatible, since this thread discusses at least one person has been able to use Office 2003
•Keeping one older PC with Office 2003 on it for us to support the old Office 2003 code until everyone upgrades their systems
Thanks
Basic compatibility issue that seems solvable:
Opening these spreadsheets displays this error:
Compile error:
The code in this project must be updated for use on 64-bit systems.
Please review and update Declare statements and then mark them with the PtrSafe attribute.
This seems resolvable by going into the VBA code and just adding element 'PtrSafe' where functions are declared; in other words, replacing VBA code "Declare Function" with "Declare PtrSafe Function" seems to get by this.

Hi Allan_L,
Please try the methods that provided above. And this is the forum to discuss questions and feedback for Microsoft Excel, your issue is related to Excel DEV, if you have further question, I recommend you post the question to the MSDN forum for Excel
http://social.msdn.microsoft.com/Forums/en-US/home?forum=exceldev&filter=alltypes&sort=lastpostdesc
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
George Zhao
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Microsoft office 2013 encountered an error during setup in Window 8.1

Initially, I got microsoft office 2013 64bit standard version installed in window 8.1. However, it suddenly got errors when opening office, and closed the program automatically. Therefore, I uninstalled it, and tried to re-install office.
However, I got the error "microsoft office 2013 encountered an error during setup" everytime when I try to install it.
I tried 32-bit and 64 bit version, and tried to install in clean boot, deleted registry, and modified the folder name "Microsoft Help", but none of them works.

Make sure you completely uninstall previous versions of Office. There may be remnants left behind, even after you uninstall Office using the normal procedure. I recommend using the “Fix It” utility to uninstall Office 2013 completely. Please refer to this
article: http://support.microsoft.com/kb/2739501/en-us you might also follow the manual steps provided on the same page.
If you still having problems, re-registering the Windows Installer and checking permissions on the %TEMP% folder and the C:\Windows\Installer folder to make sure you have full-control. To re-register the Windows Installer run the following commands:
msiexec /unregister
msiexec /register

Is it time yet for Microsoft to "Recall" Office 2013 and provide anyone who has a 2013 license a replacement Office 2010 license?

The interface is terrible and can't be changed. Every application in the suite locks up/crashes nearly constantly on any machine it is used on. The activation process is terrible and wastes hours of any support/IT dept's time. From a 'privacy
standpoint', the software is seemingly criminally intrusive. It is clearly a product that should never have been released and is so far from functional that it can't be repaired by any 'service pack', 'hotfix', or 'patch'. It needs to be completely
scrapped.
The only 'redeeming quality' of this software is that the guy who was in charge of creating it is gone from Microsoft. (Unfortunately, he is now President Obama's appointee for running the attempt at repairing the 'healthcare.gov' website...
out of the frying pan... )
When the software is installed using one profile (domain or machine account) and a different profile tries to use the software, it requires 're-activation' - which often fails because the software believes it has been installed multiple times. (This is particularly
frustrating because it has to be installed by an administrative user, but most of the time, the person who 'uses' the software is not the 'administrator' - so it is almost always being 'installed' using one profile and 'used' using another profile).
The necessary intrusion into privacy created by the requirement of a "Microsoft Account" to use the software is seemingly criminal.
The tracking of, and installation of licenses is absolutely ridiculous.
An example:
Many of my clients have many users and many computers (up to 75 or so).
I could create a "Microsoft User Account" for each 'user', but these machines get moved between users, and the software license is tied to the 'machine' and not to the 'user' so as soon as that happens, the licenses and the users are no longer
in line and become impossible to track.
I could create a "Microsoft User Account" for each 'computer'... and I can't even count the ways this would be a nightmare to try to track.
I actually did that up front for one client, and created Exchange email boxes for each computer so that "prove you are really you" emails from Microsoft could be received managed, and responded to, and passed out second usernames and passwords
to all of the users so they could "log-in" to their Office 2013 software, and created a database of the 'computer usernames and passwords' so I could track this... unfortunately, this confused the users (as it rightfully should) so they would change
the passwords for their computer's 'Microsoft User Account' thus locking me out and invalidating my database, ... and... CLUSTERF#%K!!!
As a 'best - worst case', I have had to create a single 'Microsoft User Account" for each of my clients' businesses so I can install and activate Office 2013 products. This is a whole new set of "Awesome Stupidity".
Now, I can put a new computer into a client's office and install their new license key for their oem Office 2013, and it shows up in the 'business's Microsoft User Account'. Then when I give the machine to the user, I get to 're-activate' the software
(hoping that it doesn't tell me to piss-off - which happens about 40% of the time. This is a process that can only be described as a "feat of engineering created by a group of monkeys whose former jobs included 'janitor at MAD magazine headquarters'
or 'beer-pong referee').
It starts with two hours of pressing phone buttons and ultimately talking to someone who tells me "yeah, nothin' I can do about that I'm just here for product activation" (which, incidentally, is done by machine until you pass through MS's ridiculous
labyrinth of repetitious keystroking until the machine is convinced you are just too stupid to punch in the right numbers and allows you to talk to a person... who then asks you for the exact same set of numbers and repeats back the exact same responding set
of numbers and acts dumbfounded when it still doesn't work - since it didn't work the first six times you punched or said it into the phone) followed by "I need to send you to the support group... but because it's 6:30 pm (in a process you started at
3:00pm) they are gone for the day and you'll have to call back on Monday morning"
At some point in the process, you get to log into the "Microsoft user account" and 'roll the roulette wheel of stupidity' by trying to activate the right software from a list of 40 different lines that all say "Microsoft Office 2013 Home and
Business oem", but none give any indicator or differentiating factor like for instance: license key, date installed, license key last 4 digits, mother's maiden name, phase of moon when software was first activated, color or type of blood of the user's
paperboy's dog's previous owner... NOTHING... RANDOM FREAKING STAB IN THE DARK - pick one, any one, hope its the license you are trying to install onto this machine, 'cause if not, you very well may kill the product on some other machine.
So through the process, the lucky support staff person gets' to waste roughly an hour and a half on average for every Microsoft Office 2013 installation. I have actually had to start telling my clients that they are going to likely have to pay an extra
$100 or so per machine in order to get their new Microsoft Office software which comes on their new computer activated - that number tends to work out roughly accurately - except that it is a terrible way of trying to 'please a client'.
Oh,... and did I mention... "THE SOFTWARE CONSISTANTLY FAILS"!?!
A client tries to open a document that they have been using for 8 years and Excel doesn't say "Hey, I don't know how to deal with some element of the file that you put in here using Excel 2003, or Office 2010 (both products, by the way, which worked
great) - no... instead,... it crashes. Doesn't really do any damage to the file it choked on, but the work you'd been doing on three other files which you also had open,... yeah,... that work is gone.
Yeah,.... over time, I have developed a pretty consistent spiel for client's needing new computers that goes over how absolutely terrible Office 2013 is, and explains that our options are further limited by Microsoft's yanking of all Office 2010 or previous
products from market availability, and explaining the merits of both LibreOffice and OpenOffice, as well as their drawbacks. I also have a strangely static response explaining how "larger companies are not burdened by these issues because they are
able to use MOPL which allows them to downgrade their productivity software to Office 2010 so they can continue to function happily, but this is really not a cost effective solution for smaller companies who primarily buy oem Office products with their replacement
computers".
Unfortunately, many clients still decide they want to go with Office 2013 because they apparently believe "it really can't be that bad". The value in my 'presale descriptions' are only really realized when they come back to me a week, two
weeks, or up to a month after the new machine is in place and say "wow,... you were right". The place I am left open for any further problems is when I don't impress upon them beforehand just HOW BAD OFFICE 2013 REALLY IS. In that case,
they still come back to me as though I have done something wrong foe selling them this piece of $#!% software and I have to remind them of our previous discussions.
Strangely, far too few heed the warnings and buy the software anyway - but the discussion has saved many clients the costs of Microsoft Project, because the discussion of LibreOffice and OpenOffice nearly always leads to at least a small philosophical conversation
about 'Open Source Software' in general, and my absolute favorite descriptive analogy in that discussion is to compare Microsoft Project at $600 v. ProjectLibre at $0 - and then further describe the costs of licensing and implementing the associated back-end
server solutions, etc.
This is a saving grace for me, because even though the client has been saddled with Office 2013, they have also saved substantially on Project and it is a rare (but granted, not absolutely absent) occasion that ProjectLibre is lacking some feature or function
that they actually need or want to use - and on those occasions, finding out has cost them absolutely nothing in software purchases.
Its not surprising, I suppose, that clients have grown to accept Office as a required 'cost', but still choke heavily on the price-tag of Project every time they have to buy it. The interesting thing to watch over the coming couple of years will be
'how many businesses stop accepting MS Office as a 'required cost' due to the failing of the software itself and the fact that most are being burned, at least once, by purchasing the software "against technical advice" and are learning, merely by
virtue of HOW BAD Office is, that there are other options out there that both cost less and work better... I mean,... LOTS BETTER.
How many businesses that are used to accepting the cost of Microsoft Office as a cost of doing business will be moved over to open source options and satisfied by them by the time Microsoft releases its next version - which will, presumably work - such that
they will no longer justify the cost of Microsoft's offering even if it is 'superior' to the open source offerings because the open source offerings are plenty sufficient and include a price tag of $0 and an installation/implementation time that is much, much
shorter than Microsoft's offering.
If Microsoft doesn't make some dramatic reparations, and do it soon, I expect their market share will be reduced in this area by a very significant margin.
I am suggesting either a 'Complete Recall' of Office 2013 including an 'uninstall 2013/install 2010' process driven by the automatic update engine, or at the very least, a free and easy downgrade rights offering for anybody who has already purchased 2013
and anyone who purchases it between now and the time the next "functional product" is released.

I understand the inconvenience you are experiencing when working with Office 2013.
If you have any feedback about Office 2013 product, click the and submit to Microsoft.
Microsoft will decide how to fix the problem for all customers.
For the activation mechanism, it intends to protect customers of their rights and interests.
For a retail version of Office, if it was purchased with a disk, Microsoft account is not necessary during the installation.
For volume license of Office, refer to the following link to deploy Office suites can be much efficient:
http://technet.microsoft.com/en-us/library/cc178982.aspx
For the problem Office 2013 keep crashing, check the following link to check:
http://support.microsoft.com/kb/2813143/en-us
http://support.microsoft.com/kb/2758592/en-us
Thanks,
Tyor Wang
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no
help.
If you have any feedback on our support, please click
here

Open Sharepoint services 3.0 documents with office 2013

Hi
we are using SharePoint services 3.0 with document libraries.
we have lookup fields on the library meta data.
problem started when upgraded users office to 2013 the document information panel is not
loading, the error they get is "the document information panel was unable to load".
office standard 2010 works fine
office 2013 pro plus works fine
office standard 2013 get this error

Hi,
Please check if this applies:
http://blogs.msdn.com/b/tehnoonr/archive/2012/05/17/sharepoint-2010-document-information-panel-fails-to-load-when-office-documents-are-opened-in-a-library-that-contains-lookup-columns.aspx
This problem is caused if your list contains lookup columns that were created programmatically or using custom features.
You may also have a look at this:
http://joranmarkx.wordpress.com/tag/document-information-panel/
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice.
Microsoft does not guarantee the accuracy of this information.
Regards,
Steve Fan
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Office 2013 VL and app-v 5 SP2 on RDS server - package add fails with script error

We have used the MS Office Depolyment Tool for click-to-run to download the latest Office 365 version, and flatten it into an app-v 5 package - not a problem.
When we try to add the package to our client machine (Server 2008R2 running the app-v 5 SP2 client software), it fails with an message that a script has failed and not returned a 0 code. We have not added any scripting to this automatically created
package, so it seems that the app-v client does not like the "official" package. Any hints and tips gratefully accepted, thanks
App-v client has scripting enabled.
The powershell command line we are using is:
PS C:\windows\system32> Set-ExecutionPolicy Unrestricted
PS C:\windows\system32> Add-AppvClientPackage -path file://hostname/app-v/o365-noaccess/ProPlusVolume_en-us_zh-cn_x86.appv -DynamicDeploymentConfiguration \
\hostname\app-v\O365-NoAccess\ProPlusVolume_en-us_zh-cn_x86_DeploymentConfig.xml
with a result of:
Add-AppvClientPackage : Embedded Script process exited with an error code indicating failure (return code other than 0). Please ensure that Embedded
Script process can complete successfully and exits with 0.
Operation attempted: Configure AppV Package.
AppV Error Code: 100000000C.
Please consult AppV Client Event Log for more details.
At line:1 char:1
+ Add-AppvClientPackage -path
file://hostname/app-v/o365-noaccess/ProPlusVolum ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~
    + CategoryInfo          : InvalidResult: (:) [Add-AppvClientPackage], ClientException
    + FullyQualifiedErrorId : ConfigurePackageError,Microsoft.AppV.AppvClientPowerShell.AddAppvPackage
and these are the error messages we see in the debug app-v client logs:
Script Launcher successfully waited for script with command line: '"C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D\Root\..\Scripts\Integrator.exe" /I /Msi /License /AppV PackageGUID=D24C3BDD-8FAD-44d3-998C-933F8F053682
PackageRoot="C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D\Root" MsiName=SPPRedist.msi,SPPRedist64.msi PidKey=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx,xxxxx-xxxxx-xxxxx-xxxxx-xxxxx,xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
PRIDName=ProPlusVolume'.
and...
Package {d24c3bdd-8fad-44d3-998c-933f8f053682} version {cd9725ce-4503-4932-863b-4fcda3f9551d} failed configuration in folder 'C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D' with error 0x79100E10-0xC.
and...
machine script for event AddPackage with command line: '"C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D\Root\..\Scripts\Integrator.exe"'
exited with failure error code: The extended attributes are inconsistent.. Because Rollback is set to true in the script definition, the current AppV Client operation was rolled back.
We believe this last error message is the kicker, but can't debug any further.

Just to validate the problem, I started again.
I have just downloaded the latest ODT from MS, and then downloaded the latest Office 2013 packaged - volume license. Then created the app-v package - all went perfectly, no error messages. Uploaded the package to the app-v 5 server and published
it. I have made NO changes to any of the files.
I have just built a brand new Windows Server 2008R2 Datacentre VM, patched it to the hilt, and installed the RDS role, powershell 3 and appv 5.0 SP2 client for RDS.
I then use powershell as above:
          scripting unrestricted
          app v client scripting enabled
         app v server added
          global and user update enabled
         add-appvclient package "url of office package.appv"
             and received exactly the same error message.
It is not complaining that scripting is not allowed, it is complaining that the script is invalid.
Help!!!!

Office 2013 and MS Server 2008 R2

I see an increasingly number of people having trouble with office 2012 running on 2008 R2 RDS servers, but i still am yet to find any good solution from Microsoft themselves.
We now have two customers with 2008 R2 RDS servers and Office 2013, where users are reporting that Outlook is slow when opening messages, typing messages, searching in the mailbox and sometimes everything also freezes for a few seconds if they are working
with an Office application. Similar problems are also happening with Word and Excel.
We have tried all the usual tweaks so far:
Ajusting RDP-settings to 16-bit color and no animations.
Disabling hardware acceleration for Office.
Disabling animations reg-key.
The servers are all virtual, running on vmware on some of the latest hardware from dell, so resource-wise there should be no problem. Increasing memory and CPU is not helping at all anyway.
The customer we have that are running RDS on 2012 and 2012 R2 also had this problem, but adjusting the visual effects solved all problems for these. But not for those on 2008 R2.
I am stuck at the moment, and the frustration is rising at my customers. Does anyone actually have anything that solved this problem for them? Or do we actually have to roll back to Office 2010 (where we had no problems)?

Hi,
For Office 2013 there should not be any concerns since it is windows installer based and things will be handled automatically. For the other software you could simply put the session in install mode in every case. For the servers/workstations
where install mode doesn't apply the change user /install and change user /execute will simply fail without any harmful effects.
You may check whether or not the machine is a terminal server using WMI, for example:
wmic /namespace:\\root\CIMV2\TerminalServices PATH Win32_TerminalServiceSetting Get TerminalServerMode
0 = Remote Administration mode (not a RDSH/TS)
1 = Application Server mode (aka RDSH/Terminal server)
-TP
When I run the command from the command line, it works, but when I try it in a "IF" statement, nothing happens. I am I doing something wrong using the wmic code in the IF statement?

Problem with URL:s containing scandinavian characters (Office 2013 / Firefox / SP 2010)

We are encountering problems with document opening when URL contains scandinavian characters (ä,ö). This issue occurs only with Office 2013 when using Firefox. With IE it works just fine. And Office 2010 works nicely as well.
Error message: "We can't connect to 'https://intra.../Test powerpoint.pptx' Please make sure you're using the correct web address".
This issue only occurs when document or document set name contains scandinavian characters. If I rename it, document opens without any problems.
Any idea how I could fix this?

Hi Law, try changing the settings in the library to "open in client application." You should also read the following links for solutions:
http://sharepoint.stackexchange.com/questions/16938/why-is-word-document-created-from-template-saved-locally-instead-of-to-the-docu
http://social.technet.microsoft.com/Forums/sharepoint/en-US/ec048a1f-e6cc-481d-8f46-308823568b56/cannot-save-documents-to-sharepoint?forum=sharepointadminprevious
cameron rautmann

Printer driver hangs when printing with Office 2013/Windows 8 64 bit

Printer: HP Color LaserJet CM1312nfi
Printer Driver: V5.1 (up to date, downloaded from HP support website) or Generic V5.6
OS: Windows 8 Professional 64bit
When I try to print a certain Excel document with Excel 2013 and printer driver V5.1, the program hangs and needs to be terminated via task manager. This happens always with the same document, but not with all documents. The program hangs also when opening the print preview for the same document.
The same document prints fine with the generic printer driver V5.6 and with the driver that comes with Windows 8.
The same document prints fine with driver V5.1 under Windows 7 and Office 2010. The combination Windows 7/Office 2013 was not tested. The combination Windows 8/Office 2010 was also not tested.
When I try to print an empty document with Word 2013 and generic printer driver V5.6, the program hangs and needs to be terminated via task manager.
My conclusion is that the HP printer drivers have a problem with either Windows 8 or Office 2013 or a combination of both.
The printer driver that comes with Windows 8 and is automatically installed is useful as a temporary workaround, but it lacks certain options, e.g. manual duplex.
On request, I am ready to send the Excel document by e-mail for verification of the problem.
Any help or suggestions will be very much appreciated.
Thanks in advance,
Uli
This question was solved.
View Solution.

From what you describe you are having issues printing from MS Office. Have you had trouble printing from other resources on your computer (e.g. from the internet or another program)? The first thing I am going to suggest is that we start by uninstalling and reinstalling the printer from the resources available online.
First if you use a USB cord, make sure to remove it (this is important). Do not plug it back in until the software directs you to. Then go through the Devices and Printers, Programs and Features and Device Manager folders and insure that all copies, files, and programs related to the printer are removed. Then as directed, restart the computer.
In the START menu type "%temp%" and press ENTER. Here I want you to press Ctrl+A and hit DELETE. Some of the files will not allow you to delete them, skip those files and delete the majority that allows it.
http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?prodNameId=3562006&lang=en&cc=us...
Install that and let me know the result!
Have a great day!

Automatically Rename Columns in Office 2013

Similar Messages

Maybe you are looking for