App-V 5 SP2 ODT Office 2013 32bit Package Import error

I have used ODT to package Office 2013/Project/Visio. The package is created without any errors. When I go to import the package using App-V Management Console i get the below error.
"There were problems interacting with the database on the server. The error was: String or binary data would be truncated.
The statement has been terminated."
There are no further errors and the import fails.
I have successfully imported the 64bit version using the exact same steps without issue. Can someone please advise?

Thanks for the escalation Brandon. Yes i have created the 32bit version without the Languages, and this has worked. so it looks as if there is a String that is being created which may exceed the limits of the Database.
I was able to open the Appv file in Sequencer and just change the name using that. I am now able to publish the App. I still find it strange that ODT allows the file to be created with such a long string and then throw an error.

Similar Messages

App-V 5 SP2 and Office 2013 Pro Plus

Hi
We have a terminal environment (RDS) of 20 servers and have implemented App-V 5 SP2 in it and deployed Office 2013 to it.
We don't publish Office 2013 globally because not all users are supposed to get Office 2013.
We have 2 different deployment configurations (XML's) that are configured to universal groups and the user's are members of that depending on which configuration they are supposed to have.
Now the problem, when we log a user onto the RDS and he is a member of one of the Office group he get's the Office packages and the Integrator runs and "Mail (Microsoft Office 2013)" cpl is created in Control panel and everything works fine.
When the user logs off and on again and goes to another server in our farm he gets the Office packages but no integrator runs and there is no "Mail (Microsoft Office 2013)" in control panel.
But if the users happens to log on to the same server as he landed in first place then he has access to "Mail (Microsoft Office 2013)" in control panel.
We are using network load balance and session broker for our farm.
The office 2013 was sequenced as the instructions said and no extra features or addons where implemented.
Best Regards Kristjan R. Halldorsson

Hello,
It is only supported if you publish the package globally and since you aren't publishing globally this is most likely the reason you have issues.
Nicke Källén | The Knack| Twitter:
@Znackattack

App-V 5 SP2 and Office 2013 - How to control user access?

What is the best way to control access to the Office 2013 application shortcuts?
Because it must be published globally, how can we only allow certain users to access Office 2013 on RDS servers when the default action would mean all users can access it?
Can removing the shortcuts using the DeploymentConfig file (see
here) followed by setting up something using the UserConfig file linked to an AD group work?
If so how would this be done?

See these threads:
http://social.technet.microsoft.com/Forums/en-US/a455d7e2-e0e6-4843-b07b-42afc18623e2/office-365-proplus-appv-50-package-installs-lync-outlook-infopath-and-onenote-even-though-they?forum=mdopappv#6fbcf59b-351c-48d1-8e63-539550a88b56
http://social.technet.microsoft.com/Forums/en-US/f4b47f1e-e494-4477-97e9-6942c4f8ec2d/office-2013-vl-appv-5-packages?forum=mdopappv#7f63bea4-57c3-40a7-bdf4-6f25320e5b68
Please remember to click "Mark as Answer" or "Vote as Helpful" on the post that answers your question (or click "Unmark as Answer" if a marked post does not actually
answer your question). This can be beneficial to other community members reading the thread.
This forum post is my own opinion and does not necessarily reflect the opinion or view of my employer, Microsoft, its employees, or other MVPs.
Twitter:
@stealthpuppy | Blog:
stealthpuppy.com |
The Definitive Guide to Delivering Microsoft Office with App-V

App-V 5.0 SP2 and Office 2013 Publishing Problem

Hi
I have a big problem with app-v 5.0 and Office 2013, the thing is that I have published it globally to a RDS servers in my farm and I have 4 different configuration xml's to publsih the package. I'm also using app-locker to prevent the users that are not supposed
to have the package doesn't get it published. That is working fine.
The default configuration xml is to publish the package to the computer with Excel, Word, Outlook, Powerpoint, onenote and Publisher and create shortcuts to All Programs.
I have 1 user configuration xml to a group (group 1) that has the default configuration but including 3 shortcuts to the desktop, Excel, Word and Outlook. I have another user configuration xml to group 2 that has all the application and all the shortcuts in
Office 2013 Pro and 4 shortcuts to the desktop. I have 1 user configuration xml for Excel only and another one for Word only.
This has been working well for 2-3 days but now users are getting error "The application failed to launch. The application belongs to a packages or a connection group that is scheduled to be unpublished. Error code: 0xA7E0E502-00000516".
And the Office 2013 is pending to unpublish globally on all servers even though no one has done anything except log in or log out.
What am I doing wrong, there are no connection groups on the app-v server but there where 2 or 3 long time ago and have been deleted.
Kind Regards
Kristján R. Halldórsson
Best Regards Kristjan R. Halldorsson

I ran the get-appvclientconnectiongroup -all on my servers and there where none listed.
I have also enabled the Virtualization Subsystem debuglog on the client and I'm not finding any error that might relate to this problem.
The thing is I had a group policy enabled that said Enable Global Refresh on Logon = true but I changed that to false and published the package again globally and I'm just waiting now to see if the package goes to unpublish state as it did before.
Best Regards Kristjan R. Halldorsson

Office 2010 App-V on machine with Office 2013 installed

Hi,
After a migration to locally installed Office 2013 I need to restore access to Access 2010 to some users for a legacy app. Ideally I want to use App-V. I have made an App-V package of Access 2010 following the MS guidance. It runs correctly
but every time after running it, the next time you run an Office 2013 app it causes Office 2013 to perform a repair operation, this succeeds but has to be done every time the 2010 Access is run. I can't find any reasons in the log files or in the event
viewer, any ideas?
Thanks

Thanks, I couldn't really find anything but it looks as though this could be just the way it is.
from http://support.microsoft.com/kb/2784668
When you start a version of Access on a computer that has multiple versions of Access installed, the Windows Installer may start, and
a message that states that the Windows Installer is preparing to install Access may be displayed before Access starts.
Every time that you start Access 2003, Access 2007, or Access 2010 after you use Access 2013, the Windows Installer repair operation registers
that version of Access. Similarly, the Windows Installer repair operation registers Access 2010 every time that you start it after you use an earlier version of Access. This does not occur when you start Access 2002, nor does it occur when you start the same
version of Access again.
Is this likely to also apply even when running App-V?

Unable to install Presenter 8 on Windows 8.1 Office 2013 32bit

I can't get Presenter 9 to install on my Windows 8.1 running Office 2013 32 bit. The error message:
Exit Code: 7
Please see specific errors below for troubleshooting. For example, ERROR: DS010 ...
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 4 error(s)
----------- Payload: Adobe Player for Embedding 3.3 3.3.0.0 {354D20E6-A25F-4728-9DA6-C9003D8F2928} -----------
ERROR: DS010: Invalid library file ARKCmdFS.dll. Cannot get GetCommandObject API address for command InstallAdobeVersionedFile(Seq 1)
----------- Payload: Adobe Player for Embedding x64 3.3 3.3.0.0 {9254D539-549A-41DD-A7DA-251766F2B76F} -----------
ERROR: DS010: Invalid library file ARKCmdFS.dll. Cannot get GetCommandObject API address for command WoW64FSReflection(Seq 1)
----------- Payload: Adobe Presenter Video Creator 9.0 (64 Bit) 9.0.0.0 {CBA6C15E-D6A3-11E2-B4B8-932C3C87F6B0} -----------
ERROR: DS010: Invalid library file ARKCmdFS.dll. Cannot get GetCommandObject API address for command WoW64FSReflection(Seq 1)
----------- Payload: Adobe Presenter 9.0 9.0.0.0 {AABAC03B-D6A3-11E2-B4B8-922E8DCBB854} -----------
ERROR: DS010: Invalid library file ARKCmdFS.dll. Cannot get GetCommandObject API address for command InstallFile(Seq 1)
I tried restarting.
Uninstalling and reinstalling.
Trying to install version 7 or 8 (none will install)
Making sure all were uninstalled via the control panel uninstall.

See if the following help document offers anything you haven't tried yet:
Exit Code: 6, Exit Code: 7 Installation Errors -
http://helpx.adobe.com/creative-suite/kb/errors-exit-code-6-exit.html

Office 2013 appv package upgrade to new service pack

scenario:
Office 2013 SP1 is published.
SP2 become available. What would be the steps for SP installation?
--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

Create a new package using the same steps as the first, the Office deployment tool will download and package the latest version available by default (by which time hopefully Microsoft have fixed the issue where the latest version doesn't convert to App-V
successfully!).
Then deploy the package as an update as you would for any other package. Since the package GUID should be the same for all Office 2013 packages unless you manually changed it, the App-V client should treat this as an upgraded package and only stream down
the blocks that have been updated.
Dan Gough - UK App-V MVP
Blog: packageology.com
Twitter: @packageologist
LinkedIn

PST Capture to Office 365 fails with Import error : Error opening PST File

Hello everybody
I was dealing for more than a week to make it work this tool, Capture PST.}
Already have all requirements: and tried to install in different environments like Server 2008r2 or Windows 8 (not 8.1)
PST Capture Console is installed on the Domain Joined Machine.
You have mentioned that the User Account (PST Capture Tool's Service Account) is a Local Administrator on the Machine running the Tool.
You also have the Outlook 2010 X64 installed
And you have created the outlook profile for that Service Account.
Also not have any non-email items on my pst, is only a test PST with 2MB emails as a test.
I came back from Office 365 forum and they said you are the best guys for this topic.
http://community.office365.com/en-us/f/158/p/318111/919839.aspx#919839
Jose Chavez IT Manager

Dear friend
Finally make it work after 2 weeks of war. Is not a product that you can use in your production environment, because have several complains.
Only works with PST which have Mail items (non calendars, or task, or contacts) and even you can not have a folder structure inside your Inbox, so it is not worth it.
Jose Chavez IT Manager

Visual Studio 2013 Nuget Package Manager error

Hello everyone,
I tried to add and use OpenCV library in my Visual Studio javascript windows application project, but I still get the same error.
This is my Package manager console:
PM> Install-Package OpenCV
Installing 'OpenCV 2.4.8'.
Successfully installed 'OpenCV 2.4.8'.
Adding 'OpenCV 2.4.8' to BlankSharedApp1.Windows.
Uninstalling 'OpenCV 2.4.8'.
Successfully uninstalled 'OpenCV 2.4.8'.
Install failed. Rolling back...
Install-Package : Could not install package 'OpenCV 2.4.8'. You are trying to install this package into a project that targets 'Windows,Version=v8.1', but the
package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
At line:1 char:1
+ Install-Package OpenCV
+ ~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Install-Package], InvalidOperationException
+ FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PowerShell.Commands.InstallPackageCommand
Thanks for answers.

Hi Fačko,
Normally, we won't get any errors if we create a new project. Since you get this error when using OpenCV library and it is a third-party product, I think you need to ask in
OpenCV forum for better response.
Thank you for your understanding!
Best regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Office 2013 converting to app-v gives xml error in manifest file

Hello,
I'm trying to create na app-v package (v.5 SP2) of Office 2013.
I downloaded the Office Deployment Tool for Click-to-Run from here:
http://www.microsoft.com/en-us/download/details.aspx?id=36778
I installed it into C:\Office2013pck shared that folder as
\\APPVMANAGER\Office2013 and mapped as Z:\.
I changed the configuration.xml file to:
<Configuration>
<Add OfficeClientEdition="32" >
<Product ID="ProPlusVolume">
<Language ID="en-us" />
</Product>
<Product ID="VisioProVolume">
<Language ID="en-us" />
</Product>
</Add>
</Configuration>
Then I ran in na elevated cmd:
>Z:
>\\APPV-CL-WIN7DEF\Office2013\setup.exe /download \\APPV-CL-WIN7DEF\Office2013\configuration.xml
and
>\\APPV-CL-WIN7DEF\Office2013\setup.exe /packager \\APPV-CL-WIN7DEF\Office2013\configuration.xml \\APPV-CL-WIN7DEF\Office2013\Appv
Everything seemed to work fine.
The creted folder had Office\Data\15.0.4649.1001 folder (I guessed this is a version number)
When I tried to add the package to App-V Server (in the Console) I get the following error:
An unexpected error occurred while retrieving AppV package manifest. Windows error code: 1465 - Windows was unable to parse the requested XML data.
From the Event Log I got this additional information:
There was a problem retrieving the requested package \\APPVMANAGER\AppVpck\Office\VisioProVolume_ProPlusVolume_en-us_x86.appv for import. Error message: Unspecified error
Element '{http://schemas.microsoft.com/appv/2010/manifest}UsedKnownFolders' is unexpected according to content model of parent element '{http://schemas.microsoft.com/appx/2010/manifest}Package'.
I tryied creating a package for 32 and 64 bits, only office, office and visio, and office visio and project.
I haven't found any indication of which file is the manifest app-v file.
I also haven't found any .xml with the "UsedKnownFolders" tag (I changed the .appv package extension to .zip and explored some of the files).
So... what's happening?
Thanks in advance for any help.

Sounds like the same issue as this thread:
http://social.technet.microsoft.com/Forums/en-US/98e5508b-7898-4b2b-b24d-3fd0194bbbc7/office-2013-with-visio-and-project-error-package-manifest-is-invalid?forum=mdopappv
What I would suggest is try to add the package manually via powershell, and if you get the same error post in the above forum so its in the same place.

App-V 5 Client + Office 2013 (Administrator OK, user Not OK)

Dear MS,
I've installed App-V environment onto our Windows 2008 RDS farm with your tech documents successfully.
Then I test it with a simple sequenced app (Mozilla Firefox and XML notepad) and it ran successfully.
I've also sequenced Office 2013 with ODT (Office Deployment Tool), no errors at the end.
But now the problems starts: when I log in as a normal user, then Office 2013 will show in Start menu, but disappears after a short time.
Logging in as Administrator doesn't have the issue, Office 2013 works perfectly.
The MS Office 2013 has been sequenced onto Win 2008 and 2012.
(yes, I know the 2012 sequencer is not ok for 2008 RDS, but the Firefox and Notepad were sequenced on Win 2012 and ran perfectly on Win 2008).
I did'n found related information on the technet forums.
What could it be? Kind of permissions on VFS? Where can I fix it? Or is the issue related to the sequencer?
ps. also tried installing MS hot fix 4 (and 5) for App-V 5 client, but the issues keep coming back.

What messages are in the App-V log in event viewer that might be applicable?
The message beneath viewed when an user log in. As an administrator, the event doesn't show up
Part or all packages publish failed.
published: 2 (Firevox and XML notepad)
failed: 1 (Office 2013)
Please check the error events of 'Configure/Publish Package' before this message for the details of the failure.
EventID 19104
Are you redirecting the Start Menu to the network?
Nope, the start menu shows only default applications when the user logs in.
The App-V Folder in Start Menu from Firefox and XML notepad are visible, but the office folder doesn't come up.
As an administrator, both Firefox, XML notepad AND Office folders are visible.
-but-
When I use Start Menu folder redirection, no one App-V application is visible (Event shows that Applications are loaded), how can I fix it here?
What are you using to manage user profiles?
I use AD User and Computer configuration to manage profiles
Does the application run if you browse to the EXE in Windows Explorer?
What does this to do with app-v? Because when you sequence the app, then is it no more EXE.
But, these EXE runs flawless in Windows Explorer (so there is no problem with the OS and the application).
Please help?

Deploy Office 2013 ProPlus Updates SCCM App-V

Hi,
I'm trying App-V and building the Office 2013 Pro Plus package worked fine, and to stop slow starting of applications I am (at the moment) looking at deploying App-V packages to stations during OSD in SCCM 2012 R2. Deploying the applications is working
great this way, except I can't find any information on how to deploy office updates to the App-V packages as they are released.
Usually with Office deployed the traditional way office updates are deployed through Software updates in SCCM. But this doesn't happen when Office is deployed as an App-V package. I don't really want to "stream" the packages to the
internal stations. Is there a way to automatically send out the updates to update the App-V office package that has been deployed to stations using the Install Application step of an SCCM OSD Task Sequence? (Preferably Automated).
Thanks,
Andy

As stated, you just have to generate and deploy a new Office package. Thankfully the client is clever enough to only stream down the blocks that have changed so you don't have to wait for users to re-download the entire package in order to apply the update!
Deploying Office as App-V is fine... until you come across an application that integrates with Office but is incompatible with App-V. Also managing plugins with connection groups is difficult. I always recommend deploying Office locally unless you have good
reasons to do otherwise.
Dan Gough - UK App-V MVP
Blog: packageology.com
Twitter: @packageologist
LinkedIn

Office 2013 with Visio and Project Error - Package manifest is invalid

In July I successfully created an App-V install of Office 2013 VL using the ODT. This week I decided to try just doing Visio as we don't install it or Project on all systems. I used my same customconfig.xml and just changed the ProPlusVolume to VisioProVolume
and changed the source path. Everything downloaded and packaged fine. I was able to import into SCCM just fine and create a deployment to my test collection. However when I run the install out of Software Center I get (as part of a much longer error) the message
in AppEnforce.log that the package manifest is invalid. Thinking that maybe I had to include Office as long with Visio I tried packaing all three items but still get the same error. Has anyone else seen this behavior and/or ideas how to fix it? Can I sequence
just Visio or just Project? I'm including my config.xml just in case I've got something wrong with it that I haven't caught. Thanks
<Configuration>
<Add SourcePath="<networkpath>\Microsoft\AppVOffice2013\Sept\" OfficeClientEdition="32" >
<Product ID="ProPlusVolume">
<Language ID="en-us" />
</Product>
<Product ID="VisioProVolume">
<Language ID="en-us" />
</Product>
<Product ID="ProjectProVolume">
<Language ID="en-us" />
</Product>
</Add>
<Display Level="None" AcceptEULA="TRUE" />
<Logging Name="OfficeSetup.txt" Path="%temp%" />
<Property Name="AUTOACTIVATE" Value="1" />
</Configuration>

Hy. I'm having the same problema.
I'm trying to create na app-v package (v.5 SP2) of Office 2013.
I downloaded the Office Deployment Tool for Click-to-Run from here:
http://www.microsoft.com/en-us/download/details.aspx?id=36778
I installed it into C:\Office2013pck shared that folder as
\\APPVMANAGER\Office2013 and mapped as Z:\.
I changed the configuration.xml file to:
<Configuration>
<Add OfficeClientEdition="32" >
<Product ID="ProPlusVolume">
<Language ID="en-us" />
</Product>
<Product ID="VisioProVolume">
<Language ID="en-us" />
</Product>
</Add>
</Configuration>
Then I ran in na elevated cmd:
>Z:
>\\APPV-CL-WIN7DEF\Office2013\setup.exe /download
\\APPV-CL-WIN7DEF\Office2013\configuration.xml
and
>\\APPV-CL-WIN7DEF\Office2013\setup.exe /packager
\\APPV-CL-WIN7DEF\Office2013\configuration.xml
\\APPV-CL-WIN7DEF\Office2013\Appv
Everything seemed to work fine.
The creted folder had Office\Data\15.0.4649.1001 folder (I guessed this is a version number)
When I tried to add the package to App-V Server (in the Console) I get the following error:
An unexpected error occurred while retrieving AppV package manifest. Windows error code: 1465 - Windows was unable to parse the requested XML data.
I tryied to publish it from powershell, getting the same error message agalluci image post shows.
From the Event Log I got this additional information:
There was a problem retrieving the requested package \\APPVMANAGER\AppVpck\Office\VisioProVolume_ProPlusVolume_en-us_x86.appv for import. Error message: Unspecified error
Element '{http://schemas.microsoft.com/appv/2010/manifest}UsedKnownFolders' is unexpected according to content model of parent element '{http://schemas.microsoft.com/appx/2010/manifest}Package'.
I haven't found any indication of which file is the manifest app-v file.
I also haven't found any .xml with the "UsedKnownFolders" tag (I changed the .appv package extension to .zip and explored some of the files).
I tryied creating a package for 32 and 64 bits, only office, office and visio, and office visio and project running Windos 7 and Windows 2012.
Thanks in advance for any help.

Deploying Office 2013 through SCCM 2012 SP1 leaves Office 2010 Tools and Sharepoint behind

I apologize in advance, but I have searched similar topics to this, but I haven't seen an answer yet that describes where and how to accomplish this. I'm also a bit new to SCCM and I'm still finding the nuances.
Scenario: Running SCCM 2012 SP1. Office 2013 32bit is added as an application and deployed properly with an accompanied .msp file stored in the source folder. The configuration is to have Office
2010 uninstalled silently. The deployment runs flawless and the user doesn't know otherwise. Success in anyone's book, right?
Except... Office 2010 Tools and SharePoint Workspace 2010 are left over. Manual uninstallation is not an option. This is for hundreds of PC's in several global locations.
I've seen it hinted to write a script. That's fine I suppose, but what do I write, where do I store the script, and can I have SCCM2012 automatically run it before the installation of 2013?
Our favorite IT tool Google hasn't quite returned what I'm looking for. Does anyone here have ideas or perhaps have experienced a similar issue?
Thanks,

1st, save the following content as a XML file on a server share, named as "config.xml".
<Configuration Product="ProPlus">
<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
<Setting Id="SETUP_REBOOT" Value="Never" />
</Configuration>
Run the following script during or before the installation of Office 2013:
"C:\Program Files\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\setup.exe" /uninstall ProPlus /config \\servershare\Config.xml
For more SCCM specific topics, we'd recommend you to visit the SCCM forums at:
http://technet.microsoft.com/en-us/systemcenter/gg191847
Max Meng
TechNet Community Support

How to add MS Office add-in from inside a Thinapp 5 virtual application to a MS Office 2013 suite that is installed on a base image

Hi,
We have the following solution:
VMware Horizon View 5.3.1
Non-persistent Linked-clone pool with delete VM after logoff
Windows 8.1 Update 1 Enterprise 64 bit
MS Office 2013 32-bit installed on image
Thinapps registered for each user from logonscript with thinreg.exe command. Thinapps is located on a network share
Native Windows roaming profiles with appdata/roaming, appdata/local without appdata/locallow(persona management does not support Windows 8.1 in View 5.3.1)
This is our issue:
We have a 3rd party application with a couple Thinapp entrypoints(exe files) and in the Thinapp package process we also installed Office addins. We tested that the Add-ins was opened inside Outlook, Word and Powerpoint before post installation scan.
The problem is that the add-ins is not added to Office 2013 before or after the Thinapp is started on a test client.
I have tried several changes in the package.ini and virtual filesystem attributes(no registry changes yet):
Package.ini:
ChildProcessEnvironmentExceptions=WINWORD.EXE;EXCEL.EXE;POWERPNT.EXE;OUTLOOK.EXE;
ChildProcessEnvironmentDefault=External
ChildProcessEnvironmentExceptions=excel.exe;outlook.exe;powerpnt.exe;winword.exe
ChildProcessEnvironmentDefault=Virtual
VirtualizeExternalOutOfProcessCOM=0
DirectoryIsolationMode=Merged
RegistryIsolationMode=Merged
I have also read that you could make entrypoints to the locally installed Office 2013, but I get errors on the build process. ref. link: http://edwinfriesen.nl/content/?p=105#comments
The best thing would be if the add-ins were added in the logon process together with thinreg.exe, but if that is not supported, the add-ins must be added to Office either in a custom Office shortcut/entry point or after starting the Thinapp virtual application.
Remember that the application needs to registered every times the user logon, because we use a non-persistent View pool.
I would really appreciate if somebody could tell me how to add Office add-ins from inside a Thinapp virtual application/package to a locally installed MS Office 2013 suite on a Windows "base" image?
We do not want to add the whole Office suite to the Thinapp virtual package and not add the add-ins trough GPO,SCCM etc.

What about the COM object parameters in package.ini ?
We can live with scripting in logon or changed logon scripts etc.
And you don't no need to lock in the project files.
From package.ini documentation:
ObjectTypes Parameter
The ObjectTypes parameter specifies a list of virtual COM object types that are visible to other applications in
the physical environment. You can use scripts, such as VBScripts, to call objects that start captured applications.
An object type is registered to only one native or virtual application at a time. If you install Office 2003 on the
native machine and want to use a virtual Office 2007 package, you must determine whether to have the virtual
or native application handle the object types.
If you want the virtual Office 2007 to handle the object types, you can leave the ObjectTypes setting in the
Package.ini file, build the package, and register it using the thinreg.exe utility. If you want the native Office
2003 to handle the object types, you must remove the ObjectTypes setting from the Package.ini file before
building and registering the package.
You cannot add random entries to the ObjectTypes parameter.
You can only remove entries that were generated by the capture process.
Example: Starting a Virtual Application When a COM Object is Created
If a script or a native application creates an Excel.Application COM object or other COM objects listed in the
ObjectTypes parameter, ThinApp starts the virtual package.
[Microsoft Office Excel 2007.exe]
ObjectTypes=Excel.Application;Excel.Application.12;Excel.Chart;
Excel.Macrosheet;Excel.Sheet; Excel.Workspace

App-V 5 SP2 ODT Office 2013 32bit Package Import error

Similar Messages

Maybe you are looking for