Replace Scenario : USMT Break Office 2013

Hi guys, in the midst of a project to refresh client Operating Systems - the refresh involves using the User State Migration Tool version 5 to capture user settings/preferences and data from old devices and restore to new machines once the Operating
System and applications such as Office are deployed.
SCCM infrastructure is 2012 SP1. Source/old machines are running Windows Vista or Windows 7, Office 2007 and have the Enterprise Vault Add-In for Outlook version 9.0.2.1136. Target/new machines have Windows 7 SP1, Office 2013 and Enterprise Vault Add-In
for Outlook version 10.0.3.1090. All operating systems are 32-bit.
USMT 5 has been extended with the hotfix for Office 2013 (new MigApp.xml) - otherwise the capture is effectively vanilla.
On machines where the User State Migration Tool is used every time Outlook is opened the following error is presented:
Either there is no default mail client or the current mail client cannot fulfill the messaging request.
If Outlook is started using outlook.exe /safe it opens without issue. If I disable the Enterprise Vault Add-In within Outlook, it opens without issue.
I’ve been through the following to no avail:
http://support.microsoft.com/kb/813745
http://www.symantec.com/business/support/index?page=content&id=TECH20486&profileURL=https%3A%2F%2Fsymaccount-profile.symantec.com%2FSSO%2Findex.jsp%3FssoID%3D1377114331330xz9e5SBBuT28VInhuBHCHNIlGKF39rjY1sr1c
Removing the Enterprise Vault Add-In and re-installing doesn’t resolve the issue, neither does the ResetEVClient.exe utility.
Run fixmapi.exe to no avail.
A repair of Office itself fixes the problem, however this is not feasible across the thousands of machines we're looking to migrate!
What we have noted is that the issue affects every Windows profile on the machine, those copied over by the User State Migration Tool, but also new ones - so whatever is occurring is breaking Outlook/the Enterprise Vault Add-In for the machine, not a specific
profile.
Finally, if we don't use USMT (not viable on the number of machines we have to replace!) I'm able to logon, and under a fresh user profile can open Outlook without issue.
If anyone has any ideas please let me know!
MCTS 70-640 | MCTS 70-642 | Prince2 Practitioner| ITIL Foundation v3 | http://www.cb-net.co.uk

Finally have a workaround - known error caused by USMT. Working with MS PSS modification of the following reg key will resolve the issue without an Office repair:
HKLM\SOFTWARE\Clients\Mail\Microsoft Outlook\MSIComponentID
Set this to the following value to resolve the issue: (6DB1921F-8B40-4406-A18B-E906DBEEF0C9}Initial tests excluding this from capture/restore via a custom XML but this doesn't seem to work.
We're now using the following Run Command Line step in the USMT Task Sequence to resolve the issue:
reg add "HKLM\SOFTWARE\Clients\Mail\Microsoft Outlook" /v MSIComponentID /t REG_SZ /d {6DB1921F-8B40-4406-A18B-E906DBEEF0C9} /f
MCTS 70-640 | MCTS 70-642 | Prince2 Practitioner| ITIL Foundation v3 | http://www.cb-net.co.uk

Similar Messages

Windows Updates keeps BREAKING Office 2013, SkyDrive, ETC

Everytime I do the Updates my system and Office 2013 becomes completely unstable.
As a result I only do upgrades every 2 weeks. On Friday, April 24 I sat down to do my 2 week update and had almost 40 updates that had to be done. (goodbye 4 hours of my life)
After the updates, just like clockwork, office, sharepoint and onedrive stopped working. I am going to try to provide as much detail as possible so as to notify Microsost in hopes this stop and in case anyone else has the issues. I will also provide
the steps I took to fix some of the issues.
Note:
I am running Windows 8.1, 64-bit on HP-ENVY 17" touch laptop
I DO NOT have any virus', malware, etc. I have ran MalwareBytes, Windows Defender and Webroot (as I always do before and after updates)
I have office 2013 and subscribe to office 365 for business - I have a license key for Office 2013 but was told somewhere that it conflicts with the click-to-run we are forced to use with 365 so I only do the office 365 version
I do have Sharepoint Designer on my system as I am the administrator of our sharepoint site
I access our sharepoint documents via Windows Explorer
After the updates I have experienced the following
I tried to open a ppt, xls and doc file and nothing would open giving random errors. I then did the control panel --> office click to run --> change --> reinstall everything. I did this and then some of the documents opened fine (goodbye
another hour of my life)
After trying to open a file from my windows explorer in our sharepoint site I get a continuous and recoccuring popup from Microsoft OneDrive for Business that says "Sorry, we can't perform this action. Incompatible Office Products are installed
on your machine. If you have an administrator, please contact them for help." (The last part just makes me laugh because I AM the administrator)
This annoying popup NEVER stops. It keeps popping up every 60 seconds if I close it. I have kiiled the onedrive process, paused the syncing, killed the office click-to-run task. Shut down all office products. Nothing makes this stop except for a full reboot
Please HELP or tell me what to do so that I can once again open my sharepoint files (and all of my employees can do so as well!)

Hi,
"I tried to open a ppt, xls and doc file and nothing would open giving random errors." Could you please provide some of these errors to me? Then I can do some research based on the errors.
Based on your error message, please make sure you have installed this update:
February 10, 2015 update for Office 2013 (KB2920798)
We can also collect some event logs after the issues occur, press Win + R, type "eventvwr" in the blank box, press Enter.
Browse to Windows Logs -> Application, check if there are any logs about the issue.
You can send the logs to our email address, we will then help analyze the information. Please send the logs to this email address below:
[email protected]
Please add this thread's url in the email for easy tracking.
Regards,
Melon Chen
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 OCT Outlook Bug Observation

Just wanted to highlight an issue we've seen at my organisation where an MSP file is does not fully install the Outlook 2013 branch where it is modifying an existing installation where that branch is not installed.
The scenario is that Office 2013 SP1 has already been installed using an msp file which does not install access, outlook and lync branches. It also hides and locks these features.
We're then following this base install at a later date and enabling Outlook using another msp file. Despite the msp file installing all features for the branch, Outlook 2013 *does* then appear, but mapiph.dll (and potentially other files) are missing from
the installation.
One symptom of the missing mapiph.dll file is that local searching within outlook does not work, such as from the exchange offline cache.
Our workaround has been to enable these branches using config.xml instead. For example...
<Configuration Product="ProPlus">
<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
<OptionState Id="OUTLOOKFiles" State="local" Children="force" />
<Setting Id="SETUP_REBOOT" Value="Never" />
</Configuration>
As an aside, the msp files both had different names. I'm aware this is required.
Just thought I'd put this out there!

Hi,
Is this an issue globally at your organization?
There are lots of reasons for this kind of issue - a corrupted registry key, malware infection, incomplete installation, etc. Maybe re-download the file, make sure it is complete and then try again?
By the way, for the issue of missing mapiph.dll, you can fix it by repairing your Office installation:
http://support.microsoft.com/kb/2739049/en-us
Regards,
Ethan Hua
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.

Windows XP to Windows 7 USMT Replace Scenario requirements

Hi ,
I am looking for pointers to start planning with Replace scenario( old to new system) with USMT. I have config manager 2012 R2 with MDT 2013 integration. Looking for pointers to achieve this. Is it possible to achieve this using standalone media(I suspect),
If yes need some pointers around this how to go about this approach also.
Other alternative I am thinking on is using USMT manually for backing up profile\data on USB\Network and
then restore it on destination after installation on new machine. Any suggestions.
Thanks
Regards,

The easiest way to do this is to deploy a refresh task sequence to an existing XP client. It has become a little trickier in R2 (boot images issues).
See procedure here. This was for a previous version of ConfigMgr so look at the comments below.
http://www.gerryhampsoncm.blogspot.ie/2013/05/sccm-2012-sp1-step-by-step-guide-part.html
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

I have Microsoft Office 2008 and only use Word and Excel. It takes 980 mb. I am considering replacing it with Apple iWorks 2013. If I do, can I delete Office, and still access and modify my Word and Excel documents?

I have Microsoft Office 2008 and only use Word and Excel. It takes 980 mb. I am considering replacing it with Apple iWorks 2013. If I do, can I delete Office, and still access and modify my Word and Excel documents?
I have a MacBook Air and OS 10.9.4

Ron
Just adding to what CSound has said.
Pages and Numbers will change Word and Excel documents when they open and close them.
Sometimes the change is subtle and sometimes not. With the latest versions of Pages and Numbers, more likely not.
So don't think you are going to work with MsOffice files without problems. You will always have something not right and in some cases really annoyingly not right. Like having all the text from Pages appear bold in MsWord, or page breaks in the wrong place or some objects and graphics not appearing in one or the other.
If working between different Operating Systems and MsOffice files, I also recommend LibreOffice. It opens and saves nearly all file formats. Unfortunately not .pages or numbers. Yet. The folks at LibreOffice are busy adding to it all the time, and making sure it works in all Operating systems, Mac, Windows and Linux and they are promising iOS as well soon.
Peter

Office 2013 partialy virtualized breaks Outlook2013

Hi,
We tryed to virtualize Access Visio and Project 2013 in one package using the Click to Run method. For this method we made a xml file with the following content:
<Configuration>
    <Add SourcePath="C:\Temp\Project\Download" OfficeClientEdition="32" >
    <Product ID="ProPlusVolume" >
      <Language ID="nl-nl" />
      
<ExcludeApp ID= "Outlook" />
      <ExcludeApp ID= "Excel" />
      <ExcludeApp ID= "Groove" />
      <ExcludeApp ID= "InfoPath" />
      <ExcludeApp ID= "Lync" />
      <ExcludeApp ID= "OneNote" />
      <ExcludeApp ID= "PowerPoint" />
      <ExcludeApp ID= "Publisher" />
      <ExcludeApp ID= "SharePointDesigner" />
      <ExcludeApp ID= "Word" />
    </Product>
    <Product ID="ProjectProVolume" >
      <Language ID="nl-nl" />
      
    </Product>
    <Product ID="VisioProVolume" >
      <Language ID="nl-nl" />
      
    </Product>
</Add>
  
<Display Level="None" AcceptEULA="TRUE" />
  <Logging Name="Office2013Setup.txt" Path="%temp%" />
  <Property Name="AUTOACTIVATE" Value="1" />
</Configuration>
When using this xml to download and build the appv package the ExcludeApp tags seem to be ignored. I end up with a package containing all parts. But this is only problem 1 there is a second problem: When the AppV package is deployed on a machine with Outlook
2013 and installed in the base image with the Office 2013 installer. Then each time Outlook is started it gets repaired. When the AppV is unpublished this behaviour stops.
The question i have is it supported to deploy Office 2013 half native and half as AppV on the same system. This sounds wierd but many organisations only want part of their employers to have tools like Access. In case of deploying on terminal server it is
nice to give most users the base like Outlook,Word,Excel and Accessruntime. And some privileged users the Access,Visio Project AppV package as addition.
Is this scenario possible with AppV 5 or should all parts be installed native and use a some sort of user profile control to control who gets what?
regards,
Leon.

Use a clean machine for ODT, I use a VM with snapshots.
See:
https://social.technet.microsoft.com/Forums/en-US/2bda7882-80d1-4ebc-a6e8-32d47f74aaad/office-2013-packageguid?forum=mdopappv#9c5478e8-9cac-434d-bd50-f59b0aae13f7

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

Office 2013 breaks vfpoledb ?

Hi
I've used this function for getting vfp data into Word (up to Office 2010) for a long while :
.ActiveDocument.MailMerge.OpenDataSource(lcDBPath,0,0,0,0,0,"","",0,"","",lcConnect,lcSQL)
... now with 32-bit Word 2013 it always breaks and I get a dialog 'Could not find installable ISAM'.
I have the latest version of vfpoledb installed.
In further testing, if in Word or Excel I open the data connection wizard, choose 'Other/advance' and then select 'Microsoft OLEDB Provider for Visual Foxpro' and click 'Next ' I always get 'Microsoft Excel (/Word) has stopped working': ie a crash!
I've tested this out on 3 different machines with Win7 and Win8 installed and always get the same result. Other OLEDB providers all work fine.
I could of course work around this, but I'm interested to know- does vfpoledb just not work with Office 2013, or is there some workaround, or ... ?
Brian Abbott
Brian Abbott

OK I've been doing a bit more experimenting.
In Word 2010 this string works:
.ActiveDocument.MailMerge.OpenDataSource(lcDBPath,0,0,0,0,0,"","",0,"","",lcConnect,lcSQL)
... where
lcConnect = "DSN=Visual FoxPro Database;UID=;PWD=;SourceDB=" + lcDBPath + ;
";SourceType=DBF;Exclusive=No;BackgroundFetch=Yes;Collate=Machine;"
As you say Olaf this in fact uses the DSN - that is, ODBC (something that had escaped me, I for some reason thought it was using OLEDB - though since I wasn't using any VFP6+ table features that didn't matter).
With Word 2013 the above doesn't work but I eventually found that it can be made to work by changing the .Opendatasource call very slightly:
.ActiveDocument.MailMerge.OpenDataSource("",0,0,0,0,0,"","",0,"","",lcConnect,lcSQL)
(that is, the first parameter is empty rather than specifying the source DBF location).
Separately to this, is the issue of a call to VFPOLEDB from Word.
In Word 2010 I can select VFPOLDB and it generates an .odc file whose meat is this:
<meta name=SourceType content=OLEDB>
<meta name=Table content=tosend>
<title>(Default) tosend</title>
<xml id=docprops><o:DocumentProperties
xmlns:o="urn:schemas-microsoft-com:office:office"
xmlns="http://www.w3.org/TR/REC-html40">
<o:Name>(Default) tosend</o:Name>
</o:DocumentProperties>
</xml><xml id=msodc><odc:OfficeDataConnection
xmlns:odc="urn:schemas-microsoft-com:office:odc"
xmlns="http://www.w3.org/TR/REC-html40">
<odc:Connection odc:Type="OLEDB">
<odc:ConnectionString>Provider=VFPOLEDB.1;Data Source=D:\VFP\WINSIMS;Mode=Share Deny None;Extended Properties="";User ID="";Mask Password=False;Cache Authentication=False;Encrypt Password=False;Collating Sequence=MACHINE;DSN="";DELETED=True;CODEPAGE=1252;MVCOUNT=16384;ENGINEBEHAVIOR=90;TABLEVALIDATE=3;REFRESH=5;VARCHARMAPPING=False;ANSI=True;REPROCESS=5</odc:ConnectionString>
<odc:CommandType>Table</odc:CommandType>
<odc:CommandText>`tosend`</odc:CommandText>
</odc:Connection>
</odc:OfficeDataConnection>
</xml>
... and this works fine.
With Word 2013, on several different machines, it always breaks at the point when I specify VFP OLEDB in the dialog. (I don't have Office 2007 so can't test that).
Brian Abbott

Excel COM object calls break with Office 2013 upgrade on 64-bit OS?

Out of the 1000+ computers in the company mine is the only one running 64-bit windows 7. I have noticed that when i try to run a small DLL i created to convert Excel files to Tab Delimited files it is crashing only on my computer.
I have debugged the source code and found that there is no real exception being thrown except a popup does appear in the background stating "We're sorry, but Excel has run into an error that is preventing it from working correctly. Excel will need to
be closed as a result. Would you like us to repair now? [Repair Now][Help][Close]"
If i open excel via the main application this same popup comes up and when i click repair excel closes. when re-opened Excel re-activates and then works fine.
here is a sample of my (VERY simple) code which has worked for years on office 2007 with 64-bit OS:
Dim excelPath As String = "C:\test.xlsx"
Try
objXL = CreateObject("Excel.Application")
With objXL.Application
.displayalerts = False
.Visible = False
.workbooks.Open(excelPath)
.Workbooks(ExcelFileName).SaveAs(csvPath & csvFileName, Excel.XlFileFormat.xlCurrentPlatformText, , , , , Excel.XlSaveAsAccessMode.xlNoChange, , , , , )
.workbooks(csvFileName).Close(csvPath & csvFileName, savechanges:=True)
End With
Catch ex2 As Exception
Throw ex2
Finally
objXL.Quit()
objXL = Nothing
End Try
I have isolated the exact line that is causing the exception to be thrown...
.Visible = False
Why would hiding the Excel UI cause an error of "We're sorry, but Excel has run into an error that is preventing it from working correctly" to be displayed?
If i remark out this line then the application seems to work properly for me...

That I do not know. Do you have another machine where Office 2013 is installed, and where you can test? It could be system configuration issue, could be a change in the application behavior or a difference between 32-bit and 64-bit. You are updating
at least a couple of generations of software and now running in a 64-bit environment so there is always the potential for changes in behavior and software defects.
Unfortunately, I do not have Office 2013 64-bit installed so I cannot test this scenario.
You could also try posting to the
Excel for Developers forum to see if anyone has encountered the same issue when using Excel automation.
Paul ~~~~ Microsoft MVP (Visual Basic)

Activating Office 2013 for Small Business Scenarios

Some advice required please. We're a small VAR and supply hardware and software to small businesses with no in house IT department.
When customers have purchased Office Licences in the past, we've maintained a log of the number of licences held by a given customer, and a list of licences. This has worked well for Office 2007 and Office 2010.
Please correct me if I am wrong, but I do not seem to be able to activate Office 2013 unless I associate it with a given email address, and I have issues with this approach. It is not ideal in a number of scenarios.
Is there any way to activate Office 2013 without having to associate the licence with a given users email address?
Stuart

No, we don't have to associate the licence with a given users email address.
The method to associate the licence with a email address is one of the available licensing methods, apart from which, we also have the traditional licensing method that is using product key.
For more licensing and purchase related topics, I'd suggest you to contact the Customer Service to obtain help:
http://www.microsoft.com/licensing/how-to-buy/how-to-buy.aspx
Also check the Buyer's guide:
http://www.microsoft.com/licensing/about-licensing/office.aspx
Max Meng
TechNet Community Support

USMT + UNC + Replace Scenario

Hi folks,
Have a customer that's looking to do USMT to a UNC path in a Replace Scenario. The drawback of course is that we can't use the State Migration Point, so Requesting/Releasing the Mig file is out; nor can we use a %ComputerName% variable, given the new computer
name.
Any ideas on how to accomplish this?
Thanks

I'm a bit unclear why the State Migration point is out and the UNC path is being used. Is it out simply because that's what the customer wants?
That said, at the end of the day USMT is just another package being delivered and run by SCCM so there's no reason you couldn't do it provided the UNC was setup with appropriate permissions.
Just set your task sequence to run the command while selecting your USMT package of choice (remember if you are still playing the Windows XP game you will need to find an older version of USMT to use than what is installed with SCCM by default).
Some syntax can be found here (this is for scanstate):
https://technet.microsoft.com/en-us/library/dd560781%28v=ws.10%29.aspx
During your replace sequence you'll simply have to prompt for the profile info so it can run the Loadstate. I'd recommend using MDT or something similar so you can make a "nice looking" UDI page. Just set a radio button that prompts
if there's a profile to restore then in your task sequence you can make a task sequence group based on the variable (so it skips the section for machines that are new deployments). If you want to get clever, during your profile backup, store the profile
in a way that you can auto-generate the restore path using the SMSTSUSers variable. THen there's one less question to ask (or at least it gets replaced with a question like "who's machine will this be").

Office 2013 app-v packages

In this article, http://blogs.windows.com/itpro/2013/12/02/announcing-mdop-2013-r2/   I see mention of an Office version called "Office 2013 ProPlus
App-V Package".    Is this a download? I don't see it available as one when I login to my VLSC site.
We plan to install Office 2013 pro plus VLA LOCALLY (on C:) in our vdisk for virtual machines, but will want to stream Visio,Project,Access 2013 to our users' VMs, using App-V.    (We used to use Citrix XenApp to stream them)
In the Citrix world, "streaming" is the opposite of Publishing or Hosting (running the app ON the server). Streaming means it copies over the files to the user's C: drive on their VM when they launch the appl.
Please advise.

Hi,
As far as I know, Microsoft Office 2013 App-V packages are created by using the Office Deployment Tool (ODT). The created packages may have Subscription Licensing or Volume Licensing.
You need to download Office applications through the ODT first, then convert it into an Office 2013 App-V package with ODT tool.
For more details, please refer to this KB article:
http://support.microsoft.com/kb/2915745/en-us
More reference:
Supported scenarios for deploying Microsoft Office as an App-V package:
http://support.microsoft.com/kb/2772509/en-us
Regards,
Ethan Hua
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.

Office 2013 Click-to-Run

All,
We are having issues with some customers that have the Office 2013 Home and Business Click-to-Run version of office installed. Users are randomly having their installation corrupted. This interestingly enough didn't start happening until SP1 was released
for Office 2013. I am aware that click-to-run installations of office don't update via Windows Updates direct but through another method. Is anyone else seeing this happen? Any thoughts would be appreciated.
Some of the symptoms are as follows:
1. None of the Office apps open. You double-click but nothing happens nor are there any processes running.
2. If you open an office document direct you might get a message something to the effect of There was a Problem sending the command to the program. None of the documented fixes appear to correct the issue for this type of error.
3. A system restore point fixes it but it breaks again within a day or two.
4. The only fix at this point is to uninstall (Using FixIt KB2739501) and reinstall which of course pulls down the latest build with SP1.

Hi,
You can probably fix the issue by updating the video driver to the latest.
Please refer to this thread below, many users had the same issue and solved it by updating the video driver:
http://social.technet.microsoft.com/Forums/en-US/34401d63-6c3b-47e6-ab20-9ed9b70d890b/outlook-2013-sp1-unusable-since-sp1-update-?forum=officesetupdep
Thanks,
Melon Chen
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

Problem with multiple copies of Office 2013 in the same account

This week our company purchased five more copies of Office Home & Business 2013. I followed the steps to redeem online and try to activate it. Now the problem I can't add any more license into this account (it already have 8 licenses
of office 2013). How many license can register in one account? How can I find out which one is which one? It is a pain to install a copy of office 2013. Due to this situation I am sure I had made a misktake and used the same key twice...now
I need to find out which key is reused and try to fix the problem. Can Microsoft make it easier for us? Please!!!

Hello friend,
I've never heard the limit of the number for one Microsoft Account, there shouldn't be a limit as I know, and One product key should only be able to activate one machine, if you attempt to use it activate a second machine, there should be a prompt.
It seems you don't have "too many" machines in your organization, you can refer to the below:
http://www.msoutlook.info/question/537
We can find the license keys for Office 2013 via a script from Microsoft:
Office 2013 (32-bit) on a 32-bit version of Windows
cscript
"C:\Program Files\Microsoft Office\Office15\OSPP.VBS" /dstatus
Office 2013 (32-bit) on a 64-bit version of Windows
cscript
"C:\Program Files (x86)\Microsoft Office\Office15\OSPP.VBS" /dstatus
Office 2013 (64-bit) on a 64-bit version of Windows
cscript
"C:\Program Files\Microsoft Office\Office15\OSPP.VBS" /dstatus
It only displays the last 5 characters, but in most cases you can tell which key this machine is using.
You may also need contact Microsoft's phone service when you need activation issue:
http://support.microsoft.com/gp/customer-service-phone-numbers/en-us
I hope this helps on your scenario.

Problem with multiple copies of Office 2013 in same account

Hi,
Over the last year or more we have replaced PCs in the office and bought one copy of Office Home & Business 2013 for each. We follow the correct installation procedure and each time another Office Home & Business gets added to the list in our office.com
account. They all look identical - there is nothing to indicate when they were installed, the PC they were installed on etc.
Recently, we had one install of Office that refused to start. We tried and failed to repair the installation as suggested, so moved on to uninstall/reinstall. I noticed there was an different id in the code of each of the install buttons when we look at
the long list of identical 30 Office H+Bs we have in our account. No idea which we should pick, or whether it matters, so picked a random one. Installation finished. I had to phone up to activate as it complained that this was already a registered
product. Completed this and got Office back working.
That was yesterday. Today I switched on another PC which was very recently set up but not in use yet and found Office had stopped working on this too. I'm concerned now that the installation download is locked to one particular installation and if so, how
do I know which one is which, so I don't spend the rest of the year wandering round reinstalling office on PCs and finding I've broken it on another one each time?!
Yes, I know volume licensing may be more sensible for a business but we don't renew everything at once, and most of our PCs now have a standalone license which covers them probably for at least 4-5 years.
thanks
Darren

What is the error that the Office stopped working for? I wonder if it's Key related. Try running it in Safe Mode to test the result.
Generally, if you just uninstalled and reinstalled, you don't need to put in the product key again. If you really need to know "which one is which", try this:
http://www.msoutlook.info/question/537
We can find the license keys for Office 2013 via a script from Microsoft:
Office 2013 (32-bit) on a 32-bit version of Windows
cscript
"C:\Program Files\Microsoft Office\Office15\OSPP.VBS" /dstatus
Office 2013 (32-bit) on a 64-bit version of Windows
cscript
"C:\Program Files (x86)\Microsoft Office\Office15\OSPP.VBS" /dstatus
Office 2013 (64-bit) on a 64-bit version of Windows
cscript
"C:\Program Files\Microsoft Office\Office15\OSPP.VBS" /dstatus
It only displays the last 5 characters, but should be enough to tell which is which.

Replace Scenario : USMT Break Office 2013

Similar Messages

Maybe you are looking for