App-V 5.0 SP1 Client package publishing error 0x4C401C0C-0x80070057

Hi there
I need some help with some specific error which others also seem to have. But because there are different threads with partial different error codes and scenarios, i decided to create a new thread for my problem with exact environment specifications. So
someone can maybe help me better this way.
I've sequenced 15 packages on App-V 5.0 (SP1) so far and 3 of them have this specific error with code 0x4C401C0C-0x80070057:
Package {package-GUID} version
{version-GUID} failed configuration in folder 'C:\ProgramData\App-V\{package-GUID}\{version-GUID}' with error 0x4C401C0C-0x80070057.
The 3 packages are GIMP, XMind (some Mindmap Software) and Audacity (an audio editing software). But i don't think it's a problem with the software itself...
My environment is:
App-V Streaming Server -> Windows Server 2012 with SQL 2012 Standard (most packages streaming flawless, so i don't think the error is to search in the server)
App-V Sequencers -> Tried to sequence the package (especially XMind was the one i took for further testing) on Windows 7 Enterprise with SP1 (x86) one with all the local packages installed which are on a normal client like (Java, Flashplayer, Office
etc.) and another Win7 Ent SP1 x86 without any additional software installed. Also i set up a fresh Win8 Enterprise x64 and tried to sequence the package there. Of course the Sequencer is also 5.0 SP1!
Sequencing always goes without any errors (only warnings about excluded files or not supported shell extensions, but thats normal i believe... i also removed the unsupported shell extensions from virtual registry, but that didn't help)
Client is (always 5.0 SP1) installed on Win8 Enterprise x64 or Win7 Enterprise x64, error occurs on both OS.
The errors i've got in the event viewer:
App-V -> Client -> Admin Log says as mentioned before: Package {73069ba1-3d65-4b8e-a6e9-09d5cef967c9} version {f86e76b2-78c7-490c-a42b-e53fc2bfb6fb} failed configuration in folder 'C:\ProgramData\App-V\73069BA1-3D65-4B8E-A6E9-09D5CEF967C9\F86E76B2-78C7-490C-A42B-E53FC2BFB6FB'
with error 0x4C401C0C-0x80070057.
App-V -> Streaming-Manager -> Debug:
Information: Microsoft AppV Streaming Manager Session created for URI \\apvserveradress\AppV_Content$\Diverse\XMind_3_GE_x64\XMind_3_GE_x64.appv and user SID S-1-5-21-933032516-4060937889-my-user.
(Some values anonymized ;))
Information: Microsoft AppV Streaming Manager Stage-Package initiated.
ERROR: Failed to retrieve package source root opt out setting from machine policy for package version {f86e76b2-78c7-490c-a42b-e53fc2bfb6fb} with status 4490208696731238406. (this error appears with or without package source
root set with GPO to %programdata%\App-V)
Information: Microsoft AppV Streaming Manager Session deleted for URI \\apvserveradress\AppV_Content$\Diverse\XMind_3_GE_x64\XMind_3_GE_x64.appv and user SID S-1-5-21-933032516-4060937889-my-user.
ERROR: Microsoft AppV Streaming Manager Stage-Package failed with status wrong parameter., Package Version {f86e76b2-78c7-490c-a42b-e53fc2bfb6fb}.
Hmm i didn't activated all detailed logs... i did now and try a reboot... but it's really strange because i didn't do something special while sequencing this packages or the one's which are working without any errors... so i also didn't get the wrong parameter
message, i compared the userconfig and the deploymentconfig files with one which didn't produce any errors and can't see any differences which could be a wrong parameter...
Help please... if someone thinks there should be more errors somewhere, let me know... i - as i said - activated now all detailed logs unter Microsoft -> App-V in the event viewer...
i don't get the problem myself, sorry guys... :(
greets
Stephan

Hello Stephan,
I too am experiencing the same issue.
Rather than starting with the full App-V infrastructure though I simply installed the sequencer (App-V 5.0 SP1) on a clean VM running Windows 7 Enterprise 32-bit (including SP1 and fully patched). I then sequenced one of the simplest apps we use (Workrave)
and tried to 'install' it as a stand-alone app onto another clean VM again running Windows 7 Enterprise 32-bit (including SP1 and fully patched). I believed that this would be the cleanest solution and would allow me to 'test' the applications before
going to the trouble of configuring the full infrastructure.
Running the .msi file gave me the same error as you: (ref. your post Tuesday, May 07, 2013 10:26 AM).
I got the same error when trying to install via PowerShell:
PS C:\Windows\system32> Set-ExecutionPolicy Unrestricted -Scope CurrentUser
PS C:\Windows\system32> Import-Module Appvclient
PS C:\Windows\system32> Add-AppvClientPackage -Path 'C:\AppTest_1.10.0_x86\AppTest_1.10.0_x86.appv'
Add-AppvClientPackage : Application Virtualization Service failed to complete requested operation.
Operation attempted: Configure AppV Package.
AppV Error Code: 0C80070057.
Error module: Streaming Manager. Internal error detail: 4C401C0C80070057.
Please consult AppV Client Event Log for more details.
At line:1 char:1
+ Add-AppvClientPackage -Path 'C:\AppTest_1.10.0_x86\AppTest_1.10.0_x86.appv
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidResult: (:) [Add-AppvClientPackage], ClientException
+ FullyQualifiedErrorId : ConfigurePackageError,Microsoft.AppV.AppvClientPowerShell.AddAppvPackage
I have re-built both the sequencer and client VMs from scratch and tried it all again. No luck. I then tried using 64-bit versions of Windows but encountered the same issue.
I too have enabled the Analytic and Debug Logs for AppV in Event Manager and see
some of same error events as you:
\AppV\Client\Admin
\AppV\Client-Orchestration\Debug
\AppV\Client\Streaming-Manager\Debug
I do not however have anything in:
\AppV\Client-RegistryNotification
I suppose it might just be the application I chose to sequence but it is rather putting me off trying anything more complicated...
Please do let us know if you get to the bottom of it...

Similar Messages

App-v 5.0 Client Package Installation - Error Code: 0C80070003 ( App v Error Code) 74F00F0C80070003 ( Internal error Code )

Hi,
I have converted my previous version package which was build upon 4.6, using sequencer to 5.0 app-v client.
I didn't have any errors & warnings. But, when I tried to install the package , I'm getting the error with error code
Error Code:
0C80070003 ( App v Error Code)
74F00F0C80070003 ( Internal error Code )
Bala.R

Hi there,
It was my mistake and the way we published app connection groups in the past. In the past we published the applications directly through an connection group without publishing the applications themself. In app-v 5.0 sp3 I needed to publish the packages itself
also....

App-V 5.0 SP2 user applications published via SCCM 2012 to VDI workstations with roaming only

Hi,
The environment consists of App-V 5.0 SP2 (KB2956985) user based applications published via SCCM 2012 to Windows 7 VDI snapshotted workstations that are reset at user logoff.
When a user logs on the SCCM 2012 client initiates App-V client package publishing. After a couple of minutes after logon the shortcuts appear and the user can launch their applications.
The issue is that at logoff, even with roaming enabled, the publishing information disappears. This causes the next logon process for that user to repeat, the applications are not available until the SCCM client has completed it's publishing cycle.
Roaming profiles are implemented. %APPDATA% is redirected to a UNC path. The following registry key is set
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\Integration\PreserveUserIntegrationsOnLogin=1
U-EV, global publishing of applications, and AppLocker rules are not an option. Also, I have read this already - http://technet.microsoft.com/en-us/library/dn659478.aspx#BKMK_PE
I do not want to wait for the SCCM client to kick in prior to the user applications being available. What do I need to roam or run to create a seamless transition for the user between sessions?
Eddie.

Hi Tywin (bad username considering the last GoT Episode ;))
If you ask Microsoft, they always recommend using SCCM for deploying App-V packages and reuse your current SCCM infrastructure if that is already in place. Problem is, as you now experience, is that there is some big caveats both in regards to publishing
time and to roaming of settings.
As Nické states I would suggest looking into the Full Infrastructure Model for App-V 5.x, which gives you much better performance in what I call "from no apps" to "being able to click the shortcut" - the add and publishing phase. If you don't have the time/budget/whatever
to start looking into that, you could look into some community tools like App-V Scheduler which is developed specific by Citrix guys to ease the publishing and management in a Citrix world.
Microsoft have a great article about Performance Guidelines, which you have read, but it mostly presumes you work with Full Infrastructure. Have you looked into Steve Thomas' session from TechEd NA? It talks about "implementation trends".
Senior Consultant at Atea Denmark - http://Atea.dk Atea Technical Evangelist for App-V NoLightPeople - http://NoLightPeople.com Access Director - http://www.nolightpeople.com/index.aspx#accessdirector

Enterp App Client Packaging Error

Hello,
I'm trying to make work this simple example:
https://glassfish.dev.java.net/javaee5/ejb/examples/Sless.html
Basically it's this:
1) A Stateless Session bean that has a Remote business interface with a single business method.
package ejb30;
import javax.ejb.Remote;
@Remote
public interface Sless {
public String hello();
2) a bean implementation :
package ejb30;
import javax.ejb.Stateless;
@Stateless
public class SlessBean implements Sless {
public String hello() {
return "hello, world!\n";
3) An Enterprise Application Client:
package ejb30;
import javax.ejb.EJB;
public class SlessAppClient {
@EJB
private static Sless sless;
public static void main(String args[]) {
System.out.println("Sless bean says : " + sless.hello());
If you build these files in Netbeans (one projet for the EJB and another for the AppClient) it doesn't work.
The AppServer (SunJavaSystemAppServer 9.01) issues the folloing exceptions:
"Class [ Lcom/sun/tutorial/javaee/ejb/ConverterRemote; ] not found. Error while loading [ class com.sun.tutorial.javaee.ejb.ConverterClient ]"
"Error in annotation processing: java.lang.NoClassDefFoundError: Lcom/sun/tutorial/javaee/ejb/ConverterRemote;"
The Application Client "run" tab window shows the following exception:
"java.lang.NullPointerException"
Comparing the generated files, we see that the Netbeans doesn't include the business interface ".class" in the Jar file, although it's listed and checked for packaging in the project's Properties/Libraries.
Is this a bug in Netbeans 5.5? Is there some workaround? How can we force to package something in the resulting Jar?
By the way, I can't find an official forum to discuss Netbeans. Does anyone knows if there is such forum?
Thanks in advance,
Marcos

It really seems to be a bug in Netbeans.
The workaround is to add the Remote Interface .class file in the sources listing:
Right click the AppClient project, Properties, Sources and click on the "Add Folder..." button to add a new "Source Package Folder"

App-V 5.0 SP1 application icons not showing up

Hi,
I've set up clean App-V 5.0 SP1 environment (Server, Sequencer and Clients). Published applications works when accessing them from %Localappdata%\Microsoft\AppV\Client\Integration\... folder, but for some reason the application shortcut icons are not showing
up correctly either in start menu or in desktop (defined desktop folder for shortcuts in App-V Server settings just for test).
So, there is this shortut on start menu, but it's not showing application icon and when opening shortcut properties it does not show application, it only shows "start in" folder (which is %localappdata%\etc..).
I've tried this now on Windows 7, Windows 8 and on 2008R2 server (rds client). Same "error" appears on all machines, and application icon is not showing up correctly.
Matti

That sounds very strange. Have you checked out the event viewer logs? You should enable the Advanced view and check them out. Also may be worth while making a copy of the .appv file and renaming it to zip, opening up and looking for the shortcuts in the
AppXManifest.XML file...see if you notice anything a miss there. Also the most obvious would be to take a copy of the package, open it for upgrade and ensure the shortcuts appear under Shortcuts and FTAs.
PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog:
rorymon.com Twitter: @Rorymon

App-V 5.0 SP1 and Outlook and Lync 2013

I am trying to sequence Outlook 2013 with App-V 5.0 SP1 but have run into an issue with using the virtualized package of Outlook 2013. When I try and open the application I get the following error:
Error: Cannot start Microsoft Outlook. Cannot initialize Microsoft shared utilities. Restart or reinstall Microsoft Outlook.
I am running the package locally and it has been published globally.
It seems as if the package is missing something. Any help would be appreciated.

I wasn't at first and that is possibly why I was getting that error. I have been trying to unsuccessfully today to use the Office 365 click to run.
I downloaded the click to run setup files. and now I'm trying to create the package.
Command Line to create the package: c:\setup.exe /packager C:\configuration.xml c:\package
I think the problem is with my config file:
<Configuration>





</Configuration>
when ever i try and run the Packager I get this error:
Windows cannot find 'C:\users....\Clientx86\integratedoffice.exe'. Make sure you typed the name correctly, and then try again.
I am pretty certain that my SourcePath is wrong. but what do i point it at?

Replace APP-V 4.6 Sp1 with APP-V 5.0

Hi All,
I have been using APP-V 4.6 Sp1 in my production. Now as the APP-V 5.0 is available I want to replace the APP-V 4.6 Sp1 with APP-V 5.0 using SCCM 2012. I have already created the TS for it. I have also created a vb script to uninstall the APP-V 4.6 Sp1.
The TS ran successfully and uninstalled the APP-V 4.6 Sp1 and installed the APP-V 5.0 Client and configured it. All of the applications launched successfully ( I have created a separate package of all of the applications with APP-V 5.0 sequencer).
What issue I am facing is that the Outlook 2012 sequenced with APP-V 5.0 is not picking up the older ost file and is asking again to configure an account. By default it should pick the ost file for the already configured account. But this is not happening
to me.
Can someone suggest me the way to migrate from APP-V 4.6 Sp1 to APP-V 5.0. I don't want to run two differnet version of APP-V altogether and I want to replace the previous version of APP-V Client with that of 5.0.
Gaurav Ranjan

Dim WshShell
Dim WshProcEnv
Dim system_architecture
Dim process_architecture
Dim abcd
Set WshShell = CreateObject("WScript.Shell")
Set WshProcEnv = WshShell.Environment("Process")
process_architecture= WshProcEnv("PROCESSOR_ARCHITECTURE")
If process_architecture = "x86" Then
system_architecture= WshProcEnv("PROCESSOR_ARCHITEW6432")
If system_architecture = "" Then
system_architecture = "x86"
End if
Else
system_architecture = process_architecture
End If
'WScript.Echo "Running as a " & process_architecture & " process on a " _
& system_architecture & " system."
Set oShell = CreateObject("WScript.Shell")
If system_architecture = "x86" Then
sRegKey = "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\Configuration\"
Else
sRegKey = "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\Client\Configuration\"
End If
sRegValue = "" ' init value in case value does not exist
On Error Resume Next
sRegValue = oShell.RegRead(sRegKey & "ProductCode")
On Error Goto 0
Dim objShell
Set objShell = WScript.CreateObject ("WScript.shell")
s1 = " msiexec /uninstall "
s2 = sRegValue
s3= " /qn >C:Result.txt"
s4= s1&s2&s3
objShell.run "cmd /c"&abcd3
Set objShell = Nothing
Gaurav Ranjan

Upgrade App-V 5.0 sp1 to SP2 Hotfix4

long time reader first time poster
we currently have a App-V 5.0 SP1 native environment, we deploy the App-V client via SCCM and use the MSI in the command line ( msiexec
/i "appv_client_MSI_x86.msi" /q /norestart ACCEPTEULA=1 /l "C:\<log directory>" )
I would like to upgrade our environment to SP2 HF4 ( in a test lab first and then schedule to live )
Now is it better to create 2 new SCCM packages one for SP2 and one for the HF4? or is there a way to combine them?
also would you put the ClientUI install in the same package?
any advice or web URL either way would be very much appreciated

just to add, I am unable to get Hotfix 4 installed successfully either via a command line ( Msiexec /p mspfile ) or right clicking the MSP and selecting Apply
The HF installs and once you reboot you are no longer able to use App-V 5.0 Client UI or any of the App-V delivered apps.
The client has SP1 and was then upgraded to SP2 using the command line in my top post without the hotfix installed works as expected.
Does anyone have a guide to how to use the MSP file?
Update - it appears that the Hotfix removes the SP2 client

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.

Windows 7 SP1 client shows status of "Not Applicable" for every single update

Windows 7 SP1 client
Every update, including all Critical Updates for Windows 7, show a status of "Not Applicable" when running a "Computer Detailed Status Report"
The computer is current in updating its status with the WSUS server.
I am hoping that you can suggest reasons why this would be.
Thanks!
mk

It is only the one computer that has all of its updates listed as 'Not Applicable'
Some of these are the same updates that other computers show as 'Installed'
Any other ideas?
Yep!
Every update, including all Critical Updates for Windows 7, show a status of "Not Applicable" when running a "Computer Detailed Status Report"
The computer is current in updating its status with the WSUS server.
One of those two statements is not true.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Locked SCCM Client Package waiting for prestaged content, Cant use Client Push

Hi there,
I am having an issue with client push. When initiated the client is unable to find the client install package on the DP. The CCMSETUP log file on the client reads "MP xxxxx.xxx.com didnt return DP locations for client package with the expected
version". This could be caused by a boundry issue but the boundry information is set up correctly, and published into AD.
The SCCM Client on the site server is not getting replicated properly to the DP's that we have setup and I think that this is causing the issue. The reason why its not gettiog to the DP is due to this error: "Distribution Manager is waiting for Package SG100001
content to be prestaged on the distribution point" when we look at the content status of the SCCM client Package.
We are unable to change the prestaged distribution point settings "automatic" as the package is the locked as its the SCCM client installation package and its waiting for us to prestage it on the DP. I have tried prestaging it, but it didnt
work
Any ideas as I have been stuck for two days on this now...
Thanks in advanced.
George

Torsten you were right, The solution was as follows for anyone else having the same issue.
As soon as you create a DP it appears that the client installation package automatically tries to distribute to the DP. If you created the DP as "Enabled for Prestage" while doing the setup then the SCCM client package will just wait for you to
copy it manually. To reslove this I had to remove the "Enabled for Prestage Content" from the DP then go into the SCCM client Package, content location tab, select the DP and redistribute the package to the DP.
Checking the Distribution Manager and PkgXferMgr.log assisted me in monitoring the content transfer to the new location.
Thanks for your assistance.
George
George, I too concur that this fixed the issue.
I had the same problem with my SCCM 2012 R2 CU4, where i updated the distribution point for the Configuration Manager Client Package. Thanks a million!

SCCM 2012 R2 Configuration Manager Client Package - stuck "In Progress"

Hi Team; I’m having 2 issues with SCCM 2012 R2:
Issue 1: I'm having a strange issue with the default XXX00002 package - "Configuration Manager Client Package",
it will not deploy to the Secondary Site DP. The console is saying "In Progress" - below is the output from the
distmgr.log file.
~Package BDC00002 does not have a preferred sender.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.443+240><thread=6032 (0x1790)>
~CDistributionSrcSQL::UpdateAvailableVersion PackageID=BDC00002, Version=1, Status=2301
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.444+240><thread=6032 (0x1790)>
~StoredPkgVersion (1) of package BDC00002. StoredPkgVersion in database is 1.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.462+240><thread=6032 (0x1790)>
~SourceVersion (1) of package BDC00002. SourceVersion in database is 1.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.462+240><thread=6032 (0x1790)>
~Package BDC00003 does not have a preferred sender.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.443+240><thread=6092 (0x17CC)>
~CDistributionSrcSQL::UpdateAvailableVersion PackageID=BDC00003, Version=1, Status=2301
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.464+240><thread=6092 (0x17CC)>
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BBK-SCCM-PRI.bbk2310.com SITE=PRI PID=2768 TID=6032 GMTDATE=Mon Mar 17 20:00:23.476 2014
ISTR0="Configuration Manager Client Package" ISTR1="BDC00002" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="BDC00002"
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.477+240><thread=6032 (0x1790)>
StateTable::CState::Handle - (2301:1 2014-03-17 20:00:23.476+00:00) >> (0:0 2014-02-28 16:33:45.383+00:00)
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.484+240><thread=6032 (0x1790)>
CStateMsgReporter::DeliverMessages - Queued message: TT=1401 TIDT=0 TID='8ACCAE01-5079-4FCD-A988-C1CD3004B698' SID=2301 MUF=0 PCNT=2, P1='PRI' P2='2014-03-17 20:00:23.476+00:00' P3='' P4=''
P5='' $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.495+240><thread=6032 (0x1790)>
~StoredPkgVersion (1) of package BDC00003. StoredPkgVersion in database is 1.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.496+240><thread=6092 (0x17CC)>
~SourceVersion (1) of package BDC00003. SourceVersion in database is 1.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.497+240><thread=6092 (0x17CC)>
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BBK-SCCM-PRI.bbk2310.com SITE=PRI PID=2768 TID=6092 GMTDATE=Mon Mar 17 20:00:23.510 2014
ISTR0="Configuration Manager Client Upgrade Package" ISTR1="BDC00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400
AVAL0="BDC00003" $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.510+240><thread=6092 (0x17CC)>
StateTable::CState::Handle - (2301:1 2014-03-17 20:00:23.510+00:00) >> (0:0 2014-02-28 16:33:45.383+00:00)
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.515+240><thread=6092 (0x17CC)>
CStateMsgReporter::DeliverMessages - Queued message: TT=1401 TIDT=0 TID='8ACCAE01-5079-4FCD-A988-C1CD3004B698' SID=2301 MUF=0 PCNT=2, P1='PRI' P2='2014-03-17 20:00:23.510+00:00' P3='' P4=''
P5='' $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.526+240><thread=6092 (0x17CC)>
CStateMsgReporter::DeliverMessages - Created state message file: D:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\1sfb1dbj.SMX
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.571+240><thread=6032 (0x1790)>
Successfully send state change notification 8ACCAE01-5079-4FCD-A988-C1CD3004B698
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.572+240><thread=6032 (0x1790)>
~Exiting package processing thread.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.574+240><thread=6032 (0x1790)>
CStateMsgReporter::DeliverMessages - Created state message file: D:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\abaibh8y.SMX
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.637+240><thread=6092 (0x17CC)>
Successfully send state change notification 8ACCAE01-5079-4FCD-A988-C1CD3004B698
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.683+240><thread=6092 (0x17CC)>
~Exiting package processing thread.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.685+240><thread=6092 (0x17CC)>
Sleep 30 minutes...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:26.886+240><thread=2936 (0xB78)>
~Used 0 out of 3 allowed processing threads.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:27.948+240><thread=4900 (0x1324)>
~Sleep 3600 seconds...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:27.950+240><thread=4900 (0x1324)>
Sleep 30 minutes...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:31.934+240><thread=2936 (0xB78)>
~Used 0 out of 3 allowed processing threads.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:33.021+240><thread=4900 (0x1324)>
~Sleep 3600 seconds...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:33.023+240><thread=4900 (0x1324)>
~Used 0 out of 3 allowed processing threads.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:38.108+240><thread=4900 (0x1324)>
~Sleep 3600 seconds...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:38.111+240><thread=4900 (0x1324)>
Sleeping for 60 minutes before content cleanup task starts.~
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:06:28.094+240><thread=4968 (0x1368)>
Sleep 30 minutes...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:30:52.271+240><thread=2936 (0xB78)>
Sleep 30 minutes...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 17:01:10.002+240><thread=2936 (0xB78)>
~Used 0 out of 3 allowed processing threads.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 17:01:10.977+240><thread=4900 (0x1324)>
~Sleep 3600 seconds...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 17:01:10.979+240><thread=4900 (0x1324)>
Sleeping for 60 minutes before content cleanup task starts.~
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 17:06:55.337+240><thread=4968 (0x1368)>
Issue 2: I'm trying to deploy a couple of Packages/Applications using SCCM 2012 R2 running on Win2K8 R2 with no luck, knowing that I could install the packages
on a test VM “in the DataCenter site”, but when trying to deploy the packages to production PC “in the Office Site”,
the status is packages deployment compliance stuck at 0%
Infrastructure:
3 SCCM servers: CAS, PRI & SEC. Both CAS and PRI are in the DataCenter site, and SEC is in the Office site. The office site has several IP subnets.
Boundaries are configured through Forest Discovery “IP Ranges and AD Sites” since that the AD site should contain all the IP subnets that the AD site contains, Boundaries groups are also configured and a site reference
server is configured for each group respectively.
A OU based Collection has been configured that contains 13 PC "the collection contains the PCs that the packages should be installed.
Packages/Applications are configured correctly since that I could successfully deploy the packages to the test VM which is on the same subnet as the CAS and the PRI servers "the DataCenter subnet". The issue
is that I can't deploy the packages to production PCs in the Office subnet!
Firewall rules are configured and applied via GP, and I even turned Windows Firewall off, and still nothing! I tried to manually initiate Computer Policy download via the SCCM GUI and via a script, still no luck!
I tried configuring IP Subnet Boundaries, still no luck!!
Here are the last 2 lines in the LocationServices.log of a client PC at the Office Site:
<![LOG[MPLIST requests are throttled for 00:00:44]LOG]!><time="14:47:00.766+240" date="03-17-2014" component="LocationServices" context="" type="2" thread="5776"
file="lssecurity.cpp:4528"> <![LOG[Current AD site of machine is Default-First-Site-Name]LOG]!><time="14:47:00.777+240" date="03-17-2014" component="LocationServices" context="" type="1"
thread="4884" file="lsad.cpp:770">
And here are the last 4 lines in the ClientLocation.log
<![LOG[Rotating assigned management point, new management point [1] is: BBK-SCCM-PRI.bbk2310.com (7958) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState"
Value="0"/></Capabilities>]LOG]!><time="14:49:04.880+240" date="03-17-2014" component="ClientLocation" context="" type="1" thread="3600" file="lsad.cpp:6311">
<![LOG[Assigned MP changed from <BBK-SCCM-PRI.bbk2310.com> to <BBK-SCCM-PRI.bbk2310.com>.]LOG]!><time="14:49:04.891+240" date="03-17-2014" component="ClientLocation" context="" type="1"
thread="3600" file="lsad.cpp:1532"> <![LOG[Rotating proxy management point, new management point [1] is: BBK-SCCM-SEC.bbk2310.com (7958) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState"
Value="0"/></Capabilities>]LOG]!><time="14:49:05.345+240" date="03-17-2014" component="ClientLocation" context="" type="1" thread="3600" file="lsad.cpp:6374">
<![LOG[Rotating local management point, new management point [1] is: BBK-SCCM-SEC.bbk2310.com (7958) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>]LOG]!><time="14:49:05.786+240"
date="03-17-2014" component="ClientLocation" context="" type="1" thread="3600" file="lsad.cpp:6436">
It looks like clients in the Office Site can’t connect to the DP/MP of the Secondary Site server which is also a DP.
While on the PC that the application was installed on I see the folowing in the LocationService.log:
<![LOG[Distribution Point='http://BBK-SCCM-PRI.bbk2310.com/SMS_DP_SMSPKG$/Content_69547d2a-339f-4ac4-9523-238c79ff8a52.1', Locality='LOCAL', DPType='SERVER', Version='7958', Capabilities='<Capabilities SchemaVersion="1.0"><Property
Name="SSLState" Value="0"/></Capabilities>', Signature='http://BBK-SCCM-PRI.bbk2310.com/SMS_DP_SMSSIG$/Content_69547d2a-339f-4ac4-9523-238c79ff8a52.1.tar', ForestTrust='TRUE',]LOG]!><time="14:42:59.506+240"
date="03-17-2014" component="LocationServices" context="" type="1" thread="224" file="lsutils.cpp:415"> <![LOG[Calling back with locations for location request {144620BC-4BF0-4878-9554-F67D305ECCF8}]LOG]!><time="14:42:59.522+240"
date="03-17-2014" component="LocationServices" context="" type="1" thread="224" file="replylocationsendpoint.cpp:220">
Is there something wrong with the Distribution point on the Secondary Site server?
Please help…
Thanks..

Update:
I fixed the issue with the default XXX00002 package - "Configuration Manager Client Package", it will not deploy to the Secondary Site DP. I did that through "Update Distribution Points" option, and after a while the status was 100%.
However; the second issue is still unsolved...
Please help..

Unable to copy hidden package "Configuration Manager Client Package" to local DP

Content status lists it as successfully distributed to all DPs (including the local site server)
However, component status for SMS_DISTRIBUTION_MANAGER continually logs these events:
Distribution Manager failed to process package "Configuration Manager Client Package" (package ID = CDW00001).
Possible cause: Distribution manager does not have access to either the package source directory or the distribution point.
Solution: Verify that distribution manager can access the package source directory/distribution point.
Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system.
Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility.
Possible cause: There is not enough disk space available on the site server computer or the distribution point.
Solution: Verify that there is enough free disk space available on the site server computer and on the distribution point.
Possible cause: The package source directory contains files that might be in use by an active process.
Solution: Close any processes that maybe using files in the source directory. If this failure persists, create an alternate copy of the source directory and update the package source to point to it.
NOTE: It appears to not be any of these causes.
If I look at the smsdpmon.log on the server in question, the following is logged every half hour:
Intializing DP Monitoring Manager...    SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Getting monitoring thread priority SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Getting content library root path SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Getting site code SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Getting algorithm ID SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Failed to find algorighm ID from registry. Use default algorithm. SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Getting DP Cert Type SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Failed to find DP cert type from registry. Use default type. SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Getting this DP NALPath SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Failed to create certificate store from encoded certificate..
An error occurred during encode or decode operation. (Error: 80092002; Source: Windows) SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Failed to initialize DP monitoring object. Error code: 0x80092002 SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
distmgr.log shows the following:
STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BRICK-CONFIGMGR.corp.COMPANY.com SITE=CDW PID=2212 TID=2124 GMTDATE=Wed Jan 02 19:29:45.109 2013 ISTR0="CDW00001" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CDW00001"   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Retrying package CDW00001   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
No action specified for the package CDW00001.   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Start validating package CDW00001 on server ["Display=\\BRICK-CONFIGMGR.corp.COMPANY.com\"]MSWNET:["SMS_SITE=CDW"]\\BRICK-CONFIGMGR.corp.COMPANYNAME.com\...   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Failed to start DP health monitoring task for package 'CDW00001'. Error code: -1   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Updating package info for package CDW00001   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Only retrying local DP update for package CDW00001, no need to replicate package definition to child sites or DP info to parent site.   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
StoredPkgVersion (2) of package CDW00001. StoredPkgVersion in database is 2.   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
SourceVersion (2) of package CDW00001. SourceVersion in database is 2.   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BRICK-CONFIGMGR.corp.COMPANYNAME.com SITE=CDW PID=2212 TID=2124 GMTDATE=Wed Jan 02 19:29:45.213 2013 ISTR0="Configuration Manager Client Package" ISTR1="CDW00001" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CDW00001"   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Failed to process package CDW00001 after 41 retries, will retry 59 more times   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Exiting package processing thread.   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Used 0 out of 3 allowed processing threads.   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:50 PM   3784 (0x0EC8)
Sleep 1825 seconds...   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:50 PM   3784 (0x0EC8)

Both errors are certificate related. Is there anything special about your configuration such as special ACLs on the certificate store or FIPS compliance mode (see
http://support.microsoft.com/kb/811833) being enabled?
Nothing special with certificates; I've used the basic stuff for intranet management of clients.
The only related thing I can think of that may have affected this, is that I discovered earlier today that my MP installation got hosed (error 500) due to a broken client install on the site server itself. I uninstalled the client manually and the server
(as indicated by the component status views) appears to have repaired the MP install. Perhaps it didn't repair it completely? Would a site reset do me any good?

App-V PowerShell: Script to Query XenApp Servers for App-V Publishing Errors and Output an Excel Document with the Results

Please Vote if you find this to be helpful!
App-V PowerShell: Script to Query XenApp Servers for App-V Publishing Errors and Output an Excel Document with the Results
Just posted this to the wiki:
http://social.technet.microsoft.com/wiki/contents/articles/25323.app-v-powershell-script-to-query-xenapp-servers-for-app-v-publishing-errors-and-output-an-excel-document-with-the-results.aspx

Hi petro_jemes,
Just a little claritification, you need to add the value to the variable "[string]$ou", and also change the language in the variable "$emailbody" in the function "Get-ADUserPasswordExpirationDate".
I hope this helps.

When I opened iweb it opened as a file I deleated. I have a published website with godaddy and would like to update. How can I open the existing iWeb app to the site that is already published?

When I opened iweb it opened as a file I deleated. I have a published website with godaddy and would like to update. How can I open the existing iWeb app to the site that is already published?

You cannot retrieve the already published site as iWeb CANNOT open it - it has no import facility.
You need your domain.sites file, which you can find under User/Library/Application Support/iWeb/domain.sites. You do not need any kind of account for this because it is your domain.sites file that resides on the hard drive of your Mac anyway. Find this file and you can alter your website.
Use a spotlight search to try and find it and if this does not work you can download something called Find Any File. If you really can't find it, then you'll have to start from scratch because iWeb cannot open a site that is already published.

App-V 5.0 SP1 Client package publishing error 0x4C401C0C-0x80070057

Similar Messages

Maybe you are looking for