App-V 5 and Office 2013 import: Database error when importing into the AppV Mgmt Server

After creating an Office 2013 package, generated with the current Office Deployment Tool for Click-to-Run (ODT) version (24/02/2014), the import in the App-V Management Server fails.

App-V 5 package import error (Office 2013)

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.

Applying the latest hotfix for the management server didn’t fixed this issue.

I created and imported several Office 2013 packages before, but never had this issue. The only difference between them is that this package contains not only Office 2013 ProPlus, but also Project & Visio and four languages. This results in a huge file name and package name.

After opening the package for Update Edit with the AppV Sequencer, and shorten the Package Name the import went fine!


This issue reminds me of an old Softgrid issue :

The Office Deployment Tool should make our life easier. But in the real world it generates packages with names that are to long to import into the Management Server.


April 11, 2014

SCCM 2012 R2: Deploy Console Hotfix kb2905002 as an application

If you are not able, or don’t want to use SCUP as a solution to install the console hotfix, you could make an application of the hotfix instead. With this solution, you only need to deploy the hotfix application, and the console will be fully installed. Below, I will explain all the necessary steps.

1.You need to create an application for .NET Framework 4. (this is necessary for the console)
Create a DeploymentType with commandline: dotNetFx40_Full_x86_x64.exe /q /norestart /ChainingPackage ADMINDEPLOYMENT
For detection method, use the following:

No requirements or dependencies needed.

2. You need to make an application of the SCCM 2012 R2 console. Use adminconsole.msi & consolesetup.exe as sourcefiles.
The sourcefiles for the Adminconsole are located on the Primary Site Server in the Configuration Manager installation folder under Tools\ConsoleSetup.
Create a new application.

Enter general info for the app. Press next until you need to configure Deployment Types. Click Add.
Select Script Installer.
Select a content location for the sourcefiles and specify the install cmd: consolesetup.exe /q TargetDir=C:\ConfigMgrConsole EnableSQM=0
Uninstall cmd: Consolesetup /uninstall /q

For the detection method, use windows installer with the adminconsole.msi
Create a dependency with the dotnet 4 application.

3. Create an application of the Console hotfix.

Use Configmgr2012adminui-r2-kb2905002-i386.msp as sourcefile.

Installation program: msiexec.exe /p configmgr2012adminui-r2-kb2905002-i386.msp /L*v %TEMP%\configmgr2012adminui-r2-kb2905002-i386.msp.LOG /q REINSTALL=ALL REINSTALLMODE=mous

uninstall cmd: Consolesetup.exe /uninstall /q

For detection method, use the following:

Create a dependency for the SCCM 2012 R2 console app, made in the previous step. This one needs to be installed before the hotfix is applied.

Make sure you distribute all the content to your Distribution Points. Now you can deploy the Console application hotfix, made in step 3. The system will check if the R2 console has been installed along with Netfx4. After that, it will apply the hotfix.

You can easily check the version of CreateTsMediaAdm.dll on the destination pc, to make sure the hotfix has been applied. Browse to the installation folder of the console: .\Bin\I386\CreateTsMediaAdm.dll


March 27, 2014

App-V 5 Error publish connection groups

While synchronizing packages from the App-V 5.0 server, I encountered some issues with connection groups.

Sync-AppvPublishingServer : There were errors encountered when trying to publish connection groups from the server.
Operation attempted: RefreshPublishingServer.
AppV Error Code: 070000000F.
Please consult AppV Client Event Log for more details.


Above errors doesn’t say much, but here is an entry from the Event Log:

The connection group {xxx} version {xxx} could not be published because the virtual COM settings of the individual packages conflict. 
Verify that the virtual COM settings are the same for all member packages and try again.
Error code: 0x8E90070A – 0x3000F

OK, now we are getting somewhere!

After verifying the User and Deployment XML’s, there was a clear difference in the virtual COM settings of both packages.

XML files package #1:

<COM Mode=”Isolated”>
        <IntegratedCOMAttributes OutOfProcessEnabled=”true” InProcessEnabled=”false” />

XML files package #2:

      <COM Mode=”Integrated”>
        <IntegratedCOMAttributes OutOfProcessEnabled=”true” InProcessEnabled=”true” />


By editing both XML files to reflect the settings in package #2 it should be resolved .. In my dreams, the error remains.

After changing the following line in both Deployment and User XML files:

<Objects Enabled=”false” />

(was set to “true” in package #1).

After setting the virtual COM settings in both packages the connection group was loaded from the App-V 5.0 server as it should!


Good read about this issue:

Roel Beijnes:

January 14, 2014

App-V 5.0 SP2 Client and the pain to upgrade

Microsoft released the long awaited SP2 for the App-V 5.0 client. With new features like better integration with the local OS (shell extensions!), the possibility to sequence some dependencies like MsXML and Visual C++ run times. A welcome change with this release is that the volume license editions of Office 2013 Standard and Professional, Visio 2013 Std & Pro and Prject 2013 Std & Pro are supported! Many customers will look at App-V 5.0 again!

It’s time to deploy the new App-V client to workstations!

As I’m always trying to get my hands on the MSI’s to deploy software, the first thing I did was getting and extracting the sources. Once I had played arround with the MSI’s I decided to take a walk to consider things and throw the MSI’s gently in the bin and install the EXE wrapper instead!! The next step was to find the required confguration parameters and finally deploy to workstations.

Prepare the sources

Get the App-V Client 5.0 SP2 binaries from the MDP ISO and extract the contents from it.

APPV_CLIENT_SETUP.EXE /Layout /LayoutDir=c:\temp

This will extract all the MSI’s from the EXE. The result is the App-V Client MSI and the all language pack(s) available.


I’m only interested in the English version, I will install only one language pack.


Install the App-V client (MSI) and language packs

Command-line to install the App-V client:

msiexec /i appv_client_MSI_x64.msi /qn /NORESTART AcceptEULA=1 /L*v “LogPath\appv5SP2_client_MSI_x64.log”

English Language Pack:

msiexec /i “appv_client_LP_enus_x64.msi” /qn /NORESTART AcceptEULA=1 /L*v “LogPath\appv5SP2_appv_client_LP_enus_x64.log”

So far so good!

Issue’s with upgrading SP1 to SP2

A clean SP2 client installation works fine by using the MSI’s, but upgrading a previous version gave nothing but errors.


Sync-AppvPublishingServer : CoCreateInstance() failed

 Get-AppvClientPackage : CoCreateInstance() failed. The Microsoft Application Virtualization Service may not have been started. Please verify that the service is running.

It’s clear that the AppV service wasn’t running, but I wasn’t able to get it up and running again.

Reinstalling the AppV Client solved this issue, using the EXE wrapper!  … Then I decided to use the default EXE wrapper instead.

Install the App-V client (EXE)

I’m using these setup paramaters against the AppV client installer.






/Log “<myLogPath>\appv5SP2_client_EXE_x64.log”

Don’t forget the /AcceptEULA paramater, apart from the information in the log file “Initializing string variable ‘ACCEPTEULA’ to value ’0′” you will get an meaningless error;

Exit code: 0x68e

But this silent install gave the same error when upgrading an SP1 App-V Client!

All things considered, I gave up and ended up with a manual installation of APPV_CLIENT_SETUP.EXE :-S

Luckily I had only some POC workstations with AppV client 5.0 SP1 installed! For new installations the MSI’s did the job.


With the deployment of the SP1 client, I used a Powershell script to configure the client. There are also ADMX templates avalaible to deploy with GPO’s and the MSI/EXE installers accept switches to configure the client.


My intention was to blog about the deployment of the App-V Client 5.0 SP2 using the MSI installer. But it became a total failure, I’m publishing this post just to start a discussion and maybe to find a solution over time.



December 6, 2013

HELP – I have the infamous error 80091007 during a task sequence!

In my previous post on the error 2148077575, I already mentioned that my top 1 most feared error in SCCM is the 80091007.

I decided to list all causes that I have either personally experienced or found on other sources

In most cases you will not get the error all the time -> god help you !

First thing to do is to update the package that is reported by the error.  If this still fails you can recreate the package.  If this still fails, it may not be a package problem…

It happens only on physical machines ?  In an environment where the sccm server is running on ESX 5.1 it seems you can have problems because of  the E1000 NIC on ESX 5.1 – you should change it to VMXNET3 and the problem will go away.

It happens only behind some switches? Check if portfast is enabled and jumbo frame is enabled.

It happens on only one machine ? you might have bad RAM!

Is there anything special in the IIS logs? Maybe the problem is a blocked file extension or filtering rule !

Try disabling the antivirus on the SCCM server (or at least have the appropriate exclusions for SCCM in place)

If multicast fails, try with unicast

It only happens if your OS image size is bigger than 10 GB?


quite a long list of causes isn’t it. feel free to comment if you have gotten this error but caused by something else!

October 12, 2013

Error during Task Sequence: 2148077575

It’s been a while since my last post, not that I have been sitting in a quiet corner…

I want to share an experience I got last week with the error 2148077575 during testing with an MDT integrated Task Sequence in SCCM 2012 SP1.

as I found using the logfiles (thank god we have them – I know many of you hate having so much logfiles…) this error in my case was caused by three different things:

- during the Task Sequence the sccm client cache became too small to be able to download an application (so I increased the cache to solve this one)

- detection method problem when installing oracle. the detection method was set on the presence of the folder c:\oracle. the thing is that I saw a timing problem. the folder c:\oracle only appeared when the next application started to install. (I created a package of oracle instead)

- return code 1 during an application installation. although the installation AND detection both where ok (still figuring out how to solve this, but I set return code 1 for that app as success temporarily)

So this error code 2148077575 is now in my top 3 of most hated and headache-causing sccm problems, right after the feared 80091007 !

October 12, 2013

Sms writer service does not exist or is not running

Last week I noticed that the SMS_Site_backup component was marked with the red error icon, so I examined what could be wrong.

the description of the component (message id: 5045): site backup could not find the sms writer in the list of writers provided by the VSS.  proceeded by another error (message id : 5060): site backup failed. error: gatherwritermetadata failed. please see smsbkup.log

ok, so what does the smsbkup.log tell us?


at the same time the event 4354 is logged in the application event log:


the first check would be to verify if the service SMS_Site_VSS_writer is running? Yes, it was!

second check would be to verify if the SMS writer is still listed in VSS (use the commandline vssadmin list writers) ?

Hey, it’s not there!

apparently if you restart the service SMS_Site_VSS_writer it will list itself again and the backup will also start again…

but that solution is not something we want to do everyday, don’t we?

so I decided to create a status filter rule with the following configuration:



the startbackup.cmd script contains this:

net.exe stop “SMS_SITE_VSS_WRITER” && net.exe start “SMS_SITE_VSS_WRITER”  


June 3, 2013

Service Pack 1 released for App-V 5.0

April 10, 2013

Dynamically join Computer to AD OU during OSD with SCCM

Recently I kept getting the same question over and over: Is it possible to dynamically join a new computer to an AD OU during OSD with SCCM?

Well, it sure is…

The solution I’m describing involves almost no scripting, you could also create your own solution using powershell or a HTA file to achieve the same result.

a) unknown computer

1. use the powershell script from our friend to duplicate your AD ou structure in SCCM, or create the structure yourself (see the example):


2. the next step is that you have to define a new variable in each collection, I have used the variable ‘OU’

3. declare a value for that variable in every collection:


4. then declare the variable ‘OU’ also on the ‘all unknown computers’ collection, but leave it empty so that you will be prompted to enter the value during OSD

5. in your Task Sequence, change the step ‘apply network settings’ to join a workgroup instead of a domain

create a new group ‘join domain’ with as many ‘join domain’ steps as you have collections/AD OUs:


every single ‘join domain’ must be properly configured to join the correct domain and the specified OU:


and create in every join domain step a condition linked to the ‘OU’ variable:


This can off course also be leveraged to install department/OU specific applications in the same task sequence…

wonderful, isn’t it?

for reference the TS I used:


you might also see the step ‘set computer description’, which was also a question recently. I have used the information from  to implement this, so basically when I boot an unknown computer, I will have to enter three variables:


and the machine will recieve its definitive name, will be joined to the proper OU in AD, will receive the common applications and the applications that are necessary on the AD OU AND will have its description put into AD

this description can be seen in AD:


b) known computer

downside of using known computers is that you have to import them and that you cannot use the variables/prompts I declared on the ‘all unknown computers’ collection.  So what do you have to do if you have no other option than to use known computers?

the first thing you need is to have the AD structure in SCCM, so again look at step 1 from the unknown computer example

2. the next step is that you have to define a new variable in each collection, now you should use the variable OSDDOMAINOUNAME:


and define the value referencing to the LDAP path of the OU in AD

3. in your TS, modify the step ‘apply network settings’ like :


4. Import the computer(s) in SCCM and place it in the correct collection to do the OSD and also in the collection where you want the computer to be joined in AD



April 1, 2013

European App-V User Group 2013

The 2nd European App-V User Group conference is landing in Amterdam in Februari. Almost all European App-V MVP’s will attend this meeting. A great opportunity to get some inside information on the App-V 5.0 release.

Check out for more details.

January 2, 2013