Sccm 2012 r2 connector stops synchronizing at 11percent

Hi ,
Faced same problem , SCCM connector synchronization fails at 11%
About the environment setup
1. SCCM 2012 R2 CU1
2. SCSM 2012 R2
Event logscontains the below
Inner Exception:
Exception message:Invalid object name 'SCCM_Ext.vex_GS_NETWORK_ADAPTER'..
StackTrace:
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior)
at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable)
at Microsoft.EnterpriseManagement.ObjectOrientedDatabaseLayer.DatabaseAccessLayer.GetDataSet(DataSetRequest request).
StackTrace:
at Microsoft.EnterpriseManagement.ServiceManager.Connector.SessionManager.DataProvider.throwConnectorException(String method, String message, Object[] values)
at Microsoft.EnterpriseManagement.ServiceManager.Connector.SessionManager.DataProvider.createBatchInfoForRealSource(SessionBase session, Int32 SessionTableId, EnumTableStatus status)
at Microsoft.EnterpriseManagement.ServiceManager.Connector.SessionManager.DataProvider.PrepareBatchInfo(SessionBase session)
at Microsoft.EnterpriseManagement.ServiceManager.Connector.SessionManager.DataProvider.GetNextBatch(IConnectorSession connectorSession, Boolean batchInfoOnly)
at Microsoft.EnterpriseManagement.ServiceManager.Connector.Datacenter.SessionHost.DataSync()
log indicates some sccm object is missing 'SCCM_Ext.vex_GS_NETWORK_ADAPTER'
Any suggestions???

Hi,
I used 2012 connector to to connect 2012 R2 SCCM environment.
The log is telling Invalid object name 'SCCM_Ext.vex_GS_NETWORK_ADAPTER'
We have 3 primary site servers, synchronization of the first two site servers were successfull, but the thrid one is failing
Regards,
Kalai

Similar Messages

How to stop Application deployment in sccm 2012?

Hi All
If a application is wrongly deployed to wrong collection in sccm 2012
how to stop that and where to change settings like we used to do in sccm 2007 we can
stop it by program properties.

You have kind of the same feature with Applications in CM2012. You can just right-click an Application, and select "Retire".
That will change the status of the Application from "Active" to "Retired", and should prevent installations. When you've fixed the problem, you can just "Reinstate" the Application again, and everything should be back to normal.
But I totally agree with Jason. Make sure you do the proper testing, so you won't have to do this at all :-)
Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs:
www.ronnipedersen.com/ and www.SCUG.dk/ | Twitter
@ronnipedersen

SCCM 2012 connector not working roperly in Service Manager 2012 Sp1

I'm using SCSM 2012 Sp1 and I've SCCM 2012 in my environment. I already configured the SCCM connector in SCSM. But it not showing the software inventory on the software tab. Reather then software inventory it showing every things.
Please any one help me to solve this issue.
Mithun Dey Web: http://cloudmithun.wordpress.com If this may give your necessary resolution please mark it as Answre.

Hi
It can be the
Asset Intelligence that you have to enable in SCCM.
Look here how you do it:
http://www.windows-noob.com/forums/index.php?/topic/1225-what-is-asset-intelligence-and-how-can-i-use-it-in-sccm/
Remy BOVI

Question in Installing exchange connector in SCCM 2012 R2

Hi,
I am installing Exchange connector in SCCM 2012 R2 environment. I have Exchange 2010 SP3 in my environment.
While adding the exchange connector wizard, in the Settings page, I am confused which option to select in
"ALLOW EXTERNAL MOBILE DEVICE MANAGEMENT". The options are
Exchange Default, Allowed and Prohibited.
As per my requirement, i just need the mobile device inventory. Nothing else is required. I have found that incorrect settings here will not allow the users to receive mails.
Can anyone please guide me that which option needs to be selected here as all the settings will be managed by Exchange only and SCCM just requires the inventory information.
Thanks.
-AB
-Thanks AB

So, I think the correct option should be Exchange(Default). Please correct me if I am wrong.
You would have to ask your Exchange admin how it is configured. Wally already provided the link which explains it: "If the mobile device synchronizes with Exchange Server, set the Exchange flag
AllowExternalDeviceManagement to ensure that the mobile device continues to receive email from Exchange after it is enrolled by Configuration Manager. If you install the Configuration Manager Exchange Server connector, you
can set this flag by configuring the option External mobile device management in the Exchange Server connector properties" So it has to be set to "allowed" somehow (either by specifying it in the connector's
properties or using the Exchange settings).
Torsten Meringer | http://www.mssccmfaq.de

SCCM 2012 SP1 and Exchange 2013 Connector Get-Recipient cmdlet failed

I have been trying to get my Exchange Connector working with SCCM 2012 SP1 for a week or so now. Every post tells me that the Get-Recipient cmdlet failed is a security permissions error. I have given the service account running the connector full Exchange
Server Management rights including Recipient Management and Organization View-Only. I have even tested remote power shell to the CAS server and run the cmdlet with no issues.
For some reason it just does not want to work for me. Has anyone been running into this issue?

Now before you read the following error and say oh this is a permission issue I am telling you it is not. I have given the account full Exchange admin rights and I have even tested the Get-Recipient cmdlet remotely to the Exchange server and it works with
no issues. I have also noticed multiple forum posts with the exact same issues.
I have noticed one thing that stands outs "Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean"
I believe this issue may be related to changes in the powershell commands with Exchange 2013, but I do not know where or how to edit the ps1 script.
I am getting the error below:
ERROR: [MANAGED] Invoking cmdlet Get-Recipient failed. Exception: System.Management.Automation.RemoteException: Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to
type System.Boolean."~~ at System.Management.Automation.PowerShell.CoreInvoke[TOutput](IEnumerable input, PSDataCollection`1 output, PSInvocationSettings settings)~~ at System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSettings
settings)~~ at System.Management.Automation.PowerShell.Invoke()~~ at Microsoft.ConfigurationManager.ExchangeConnector.Connector.Invoke(PSCommand cmd)
SMS_EXCHANGE_CONNECTOR 9/19/2013 12:00:01 AM
4200 (0x1068)
STATMSG: ID=8817 SEV=W LEV=M SOURCE="SMS Server" COMP="SMS_EXCHANGE_CONNECTOR" SYS=MySite SITE=MySiteID PID=xxx TID=xxx GMTDATE=Thu Sep 19 07:00:01.653 2013 ISTR0="Get-Recipient" ISTR1="ParameterBindingFailed,Microsoft.Exchange.Management.RecipientTasks.GetRecipient"
ISTR2="Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean."" ISTR3="" ISTR4="" ISTR5="" ISTR6=""
ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_EXCHANGE_CONNECTOR 9/19/2013 12:00:01 AM
4200 (0x1068)
ERROR: [MANAGED] Exception: Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean."
SMS_EXCHANGE_CONNECTOR 9/19/2013 12:00:01 AM
4200 (0x1068)

SCCM 2012 SP1 CU1 Exchange connector error

Hi, I have configured the Exchange connector on SCCM 2012 SP1 CU1 towards an Exchange 2013. I get this error in easdisk.log:
ERROR: [MANAGED] Invoking cmdlet Get-Recipient failed. Exception: System.Management.Automation.RemoteException: Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The
value "$true" could not be converted to type System.Boolean."~~ at System.Management.Automation.PowerShell.CoreInvoke[TOutput](IEnumerable input, PSDataCollection`1 output, PSInvocationSettings settings)~~ at System.Management.Automation.PowerShell.Invoke(IEnumerable
input, PSInvocationSettings settings)~~ at System.Management.Automation.PowerShell.Invoke()~~ at Microsoft.ConfigurationManager.ExchangeConnector.Connector.Invoke(PSCommand cmd)
If I launch the same command (Get-recipient), using the same account SCCM uses, directly in PSRemote on the Exchange server, it works correctly. I tried also to make the account Organization Manager, but same result.
Any hints?
thanks,
David Papini
MCSA, MCT

I made a thread about unmanageable devices. I had this error too after updating my environement. In my scenario this particular error only occured after I updated to Exchange 2013 CU1. Therefore I believe this error is an Exchange related bug.
SCCM 2012 with Exchange 2013 gave me this error:
ERROR: [MANAGED] Invoking cmdlet Set-ActiveSyncMailboxPolicy failed. Exception: System.Management.Automation.RemoteException: A parameter cannot be found that matches parameter name 'IsDefaultPolicy'.
SCCM 2012 CU1 with Exchange 2013 gave me the same error:
ERROR: [MANAGED] Invoking cmdlet Set-ActiveSyncMailboxPolicy failed. Exception: System.Management.Automation.RemoteException: A parameter cannot be found that matches parameter name 'IsDefaultPolicy'.
SCCM 2012 CU1 with Exchange 2013 CU1 gave me your error:
ERROR: [MANAGED] Invoking cmdlet Get-Recipient failed.
Exception: System.Management.Automation.RemoteException: Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean."

Issue stopping specific update on SCCM 2012

Hi All,
We have recently started to have an issue with KB2863911. The icon for outlook disappears and stays blue. Now that we know that update is an issue we want to be able to stop it deploying out to computers in our system.
I have read many notes on how to do this in SCCM 2012 and the best is apparently to create a folder under All Software Updates and place these updates in there. We have done this, but we still believe these updates are going out.
Can any tell me for sure if it is that this technique is stopping the deployment of these updates or anyway I can check if it is. At this point in time other than waiting a week and every day redeploying a script to remove this update, I have no way to see
if I am really combatting it.
Thanks,
Richard

What I am after is stopping the update going out to any more computers. All the computers have windows updates been managed by SCCM. and they are getting updates from that server so they are been deployed somehow. I am not sure how and I need to work out
so I can stop one off updates like this one going out to more computers once we have identified issues. This is not the first update this year to cause issues to computers in our organisation and so we NEED a way to manage them. This includes stopping updates
going out that cause issues!
I am all for updates, and in 99% of cases believe they do a world of good, but when they break things we would like to say that one we don't want going out.
In this case I have a application deployment uninstalling but that is going to do no good if the SUP is going to go around and install that update again.

SCCM 2012 and Exchange 2013 Connector

Hello all,
I hope that you are well!
I have an issue that I can't explain for the moment, maybe someone can help me.
Actually we have SCCM 2012 SP1 and Exchange 2013 Enterprise in our LAN.
Now I did the configuration within SCCM of creating a new Exchange Server Connectors, everything seem's to be okay, no warning, no active alert, the Exchange server connection account and so on..
But I can't see the mobile devices from my user into the All Mobile Devices within SCCM 2012.
Do I miss something into this specific configuration, certificate or something related !
Best regards to all of you
Stephane

Hello Gerry,
This is what I got on EassDisc.log
ERROR: [MANAGED] Invoking cmdlet Get-Recipient failed. Exception: System.Management.Automation.RemoteException: Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean."~~
at System.Management.Automation.PowerShell.CoreInvoke[TOutput](IEnumerable input, PSDataCollection`1 output, PSInvocationSettings settings)~~   at System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSettings settings)~~
at System.Management.Automation.PowerShell.Invoke()~~   at Microsoft.ConfigurationManager.ExchangeConnector.Connector.Invoke(PSCommand cmd)
ERROR: [MANAGED] Exception: Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean."
ERROR: Failed to check status of discovery thread of managed COM. error = Unknown error 0x80131501
But that is old error, since I configure the Account properly
Regards to you,
Stephane

Adobe Creative Cloud Enterprise Deployment Issues using SCCM 2012 R2

Hi,
I have been trying to deploy Adobe Creative Cloud Enterprise to Windows 8.1 machines that are identical, using SCCM 2012 R2.
The Adobe package seems fine, because it seems to deploy successfully to some machines. And SCCM 2012 R2 has been configured correctly, as I can deploy other software using it, and again, it deploys Adobe CC successfully to some of the machines.
I have tried comparing the package that is downloaded on the test machine/client machine, with the original package on the distribution point, using Beyond Compare, and there are no differences.
I have contacted Adobe Enterprise Support, and they asked me to send to them log files from Event Viewer, the msi installer, and other Adobe logs, from the machine that failed the deployment. However, after Adobe studying them, they told me that they could not identify any problems... Strange, because I could have sworn that I saw error 1603 pop up over 20 times on different machines indicating that the 'Set-up.dat' file had a problem with it.
After all the testing on over 20 identical machines (same hardware/same software), using different configurations on SCCM 2012 R2 and the client machines, I still can't seem to have a reliable solution to deploying Adobe CC.
The fact that it deploys successfully on one machine and fails on another, or sometimes deploy to two machines and fail on another (simultaneously), is something that I don't understand.
Another thing is that, if I retry the deployment 10-15 times after it failed the first time, it might go through...
Adobe Enterprise Support asked me if they could remote into a machine that failed the deployment to have a look at it and I agreed to that option, but it seems like my issue has been ignored because they never got back to me.
Has anyone had this kind of problem or anything similar before?
I need to be able to deploy this remotely to 100+ machines. So installing manually is not an option.
Any help is appreciated.
This was posted in the wrong section a few days ago. I'm hoping I can get some help here.
Case Number: 1862659812
UPDATE: I spoke to Adobe Customer Support and after 1.5 hours on the phone with a remote session going on, problem was still not solved or identified. Additional log files have been sent and now I'm waiting for a call back.

Hi Robert,
We seem to be having a very similar issue. Our installs would randomly fail with error code 1603 and an error message about a fault in Set-up.dat. Failure rate was near 95% on our 900 machines. Adobe Support and Karl having been looking into our issues but so far no solution has been found.
Having done a lot of investigating we've managed to deploy our package using a schedule task running as a domain admin. This is a nasty solution and we don't intend on using this permanently, but we needed to get the package out.
Are you seeing any of the following:
Entries in PDApp.log:
[FATAL] | | ASU | DeploymentManager | DeploymentManager | | | 2900 | The Bootstrapper Process is (5).Stopping the installation process.
[FATAL] | | ASU | DeploymentManager | DeploymentManager | | | 2900 | The return code from the Adobe Installer Process is (33).Stopping the uninstallation process.
[WARN] | | ASU | DeploymentManager | DeploymentManager | | | 2900 | Failed to find the pdb database.
[WARN] | | ASU | DeploymentManager | DeploymentManager | | | 2900 | Failed to get the local payload database handle.
Event Log:
Faulting application name: Set-up.dat, version: 2.9.1.474, time stamp: 0x54e11f94
Faulting module name: Set-up.dat, version: 2.9.1.474, time stamp: 0x54e11f94
Exception code: 0xc0000005
Fault offset: 0x000d7c52
Faulting process id: 0xb40
Faulting application start time: 0x01d072a073861622
Faulting application path: \\server.name.path\Adobe CC\FullPackage\Build\ASU\Set-up.dat
Faulting module path: \\server.name.path\Adobe CC\FullPackage\Build\ASU\Set-up.dat
Report Id: c86d9216-de93-11e4-8284-782bcb99e284
Faulting package full name:
Faulting package-relative application ID:
Installer Log
Indicates it can't find the Media_db. We noticed that the folder C:\Program Files (x86)\Common Files\Adobe\caps doesn't get created on the machines were the install fails, so error message is correct in that there isn't a Media_db.db. Sysinterals Process Monitor seems to show that the setup tried to create the folder/files but they don't actually get created. Copying a Media_db into the folder from another machine seems to allow the installation to almost finish, but unsurprisingly you end up with problems later on.

SCCM 2012 SP1 errors when downloading updates

Currently using SCCM 2012 SP1 with CU2 and I am having some update download issue with Automatic Deployment Rules.
The Environment is:
Server 2008 R2
SCCM 2012 SP1 CU2 (Upgraded from SCCM 2012 CU2)
I created an Automatic Deployment Rule for Adobe Flash. Since I was having the same issue with Adobe Reader, when I published via SCUP to WSUS I chose not to sign the updates.
After publishing to WSUS I then sync SCCM, I see the updates and then in the ADR I had it download the updates and I see this error:
Authentication of file C:\Windows\TEMP\CABDEC5.tmp failed, error 0x800b0004 Software Updates Patch Downloader 8/15/2013 6:49:43 PM 3712 (0x0E80)
ERROR: DownloadContentFiles() failed with hr=0x80073633 Software Updates Patch Downloader 8/15/2013 6:49:43 PM 6876 (0x1ADC)
Failed to download the update from internet. Error = 13875 SMS_RULE_ENGINE 8/15/2013 6:49:43 PM 6876 (0x1ADC)
Failed to download ContentID 16845337 for UpdateID 16841530. Error code = 13875 SMS_RULE_ENGINE 8/15/2013 6:49:43 PM 6876 (0x1ADC)
Now the funny thing is if I go to the update itself within update group that Flash is a member I can right click it and choose download and the error doesn't occur.
I observed that the UNC path for ADR Adobe flash, when the rule is ran, is populated with folders that have a name something like 44738297895427890.1 or 423154325378u867234789.1. I have come to realize that those are failed downloads. So for the
heck of it I then right clicked the update itself and chose download and it downloaded without issue. Now I'm guessing that when I chose to download directly from the update maybe the system is getting the update from adobe and not from wherever the rule was
trying to get it from. I then see the .1 removed from the directory name and there are updates within them.
Just for clarity here are the steps I go through from SCUP to Syncing...
Log in to WSUS server
Run SCUP as administrator
Get notified there are updates from Adobe and let SCUP download updates
Find the updates the specify the following publishing options
Full Content
Sign all software updates with a new publishing certificate .... (Is this necessary by the way?)
Then click Next
After that's done I then go to SCCM Manager Console and go to Software Updates and right click to Synchronize them.
After that's done then I run the ADR for Adobe Flash and when it goes to download the updates that's when the error occurs.
What am I missing?
Also, while I wait for help I just recently added the WSUS SCUP certificate to the SCCM server to see if by chance that fixes stuff. If it does then I'll post the results of adding the certificate to the SCCM server.
One other thing, is there a way to delete updates? When I was having this issue in the past, I went in to SCUP I marked the updates as expired and then deleted the updates. Went to SCCM and synchronized the updates and they went from not expired to expired
then I waited, maybe 30 days or so before I could add the updates back in.
Thanks for the help!

Yes, I know this is an old post, but I’m trying to clean them up. Did you solve this problem, if so what was the solution?
Have you seen the note at the bottom of this page about this error?
http://technet.microsoft.com/en-us/library/bb932193.aspx
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

SCCM 2012 R2 - Management Point deployment to untrusted domain

Hi all,
we've got two domains in our environment which have no trust relationship. I have sccm 2012 r2 installed on a Windows 2012 R2 server in the larger domain
and have just installed a DP and MP on a Windows 2008 R2 server in the second, smaller domain. The Management Point installed ok according to mpmsi.log but the problem i'm having is that the mpcontrol.log is now repeatedly throwing up the following message:
Call to HttpSendRequestSync failed for port 80 with status code 500, text:Internal Server Error
On the dp/mp server in the smaller domain i can browse to http://sccm-dp1/ ok. I can also browse to http://sccm-dp1/sms_mp/.sms_aut?MPCert ok. I cannot
browse to http://sccm-dp1/sms_mp/.sms_aut?MPList (receive a HTTP 500 error).
In additon to this, every now and again the MP tries to connect to the SQL DB in the other domain. This fails with the following errors:
MPStart(): RegisterWithWINS() returned 0x0
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04 1924 (0x0784)
CMPControlManager::PublishInDNS: DnsReplaceRecordsInSet() failed with status 9002.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04 1924 (0x0784)
MPStart(): PublishInDNS() returned 0x0
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04 1924 (0x0784)
EnableBranchCache(): configuration has not been changed.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04
1924 (0x0784)
MPStart(): EnableBranchCache() returned 0x0
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04 1924 (0x0784)
Successfully Registered for IP Address Change notifications.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04
1924 (0x0784)
MPStart(): RegisterForIPAddressChangeNotification() returned 0x0
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04
1924 (0x0784)
Attempting to register the SQL connection type for the configured SQL database.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04
1924 (0x0784)
Registered connection type for SQL Server 'xxxxxxxxx' and database 'xxxx\xxx_xxx'.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04 1924 (0x0784)
MPStart(): RegisterSqlDatabaseConnectionType() returned 0x0
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04
1924 (0x0784)
Checking the current CLR Enabled configuration setting for the configured SQL Server hosting the database.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04 1924 (0x0784)
Getting the CLR Enabled value from the configured SQL database.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04
1924 (0x0784)
Attempting to connect to the configured SQL database.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04
1924 (0x0784)
Impersonating using the SQL connection account; user name is now 'xxxxxxxxx'.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04
1924 (0x0784)
*** [08001][10060][Microsoft][SQL Server Native Client 11.0]TCP Provider: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to
respond.        SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
*** [HYT00][0][Microsoft][SQL Server Native Client 11.0]Login timeout expired
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
*** [08001][10060][Microsoft][SQL Server Native Client 11.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL
Server is configured to allow remote connections. For more information see SQL Server Books Online.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
*** Failed to connect to the SQL Server, connection type: MP_CONTROL_ACCESS.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
Failed to get connection to the configured SQL database.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
Failed to connect to the configured SQL database.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
Reverting back from using the SQL connection account.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
Failed to get the current CLR Enabled configuration setting for the configured SQL Server hosting the database.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
MPStart(): CheckSqlDatabaseClrEnabled() returned 0x800720d9
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
Waiting up to 300 seconds for the SMS Agent Host service to be running.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
Stopped waiting for the SMS Agent Host service to be running; Result = 0x0.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
MPStart(): WaitOnSmsAgentHostRunning() returned 0x0
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
MPStart(): CreateThread() succeeded with id 0x2fc.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10 1924 (0x0784)
SMS_MP_CONTROL_MANAGER successfully STARTED.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10 1924 (0x0784)
Can anyone provide any suggestions as to where i should begin troubleshooting this issue? When i deployed the MP to the smaller domain i ensured it
had a Management Point Connection Account which could access the SQL DB in the larger domain. I'm wondering if the two error messages i'm receiving are related or whether i have two separate issues here?
Thanks for the help!

Hi Paul,
thanks for taking the time to help. I registered asp.net v4 with IIS as per your suggestion, unfortunately it hasn't made much difference and i'm still seeing the "Call
to HttpSendRequestSync failed for port 80 with status code 500, text:Internal Server Error"
message repeating in mpcontrol.log. Have you got any further suggestions of things
to try? Seems like an error message i really need to fix!
As far as the MP to SQL issue goes, the network team assured me the connection is allowed
but i might get them to double check this just in case.
Thanks

SCCM 2012 SP1 - Offline Servicing failure - Failed to find or access the update binaries to be applied on the image

Hi there
Trying to patch a new Windows 7 SP1 image within SCCM 2012 SP1, but it's failing.
I've searched for information on the failure messages I am seeing, but although there is a LOT of information online concerning Offline Servicing failures, I can't find anything on the errors I am seeing.
I've tried injecting a single update, five updates and ten updates, no difference, same messages.
We have McAfee Access Protection disabled, as we know Offline Servicing simply won't work if this is running.
In the console, in Schedule Update Status for the image I am trying to update, the following message is shown:
"Failed to find or access the update binaries to be applied on the image."
That sounds as if the process can't find the actual .cab file for any update I've tried to inject, but I don't know why it wouldn't be able to do that, we have Software Updates configured and the .cab files are on the same server.
When I looked at the OfflineServicingMgr.log file, I see the following entries:
Processing image at index 1        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:52:49        8272 (0x2050)
Mounting image at index 1. Image file='D:\ConfigMgr_OfflineImageServicing\PackageID\W7_Image.wim', MountDirectory='D:\ConfigMgr_OfflineImageServicing\PackageID\ImageMountDir', ImageFileType='WIM', Mode='ReadWrite'        SMS_OFFLINE_SERVICING_MANAGER
14/06/2014 14:52:49        8272 (0x2050)
Image OS information : MajorVersionMS = 6, MinorVersionMS = 1, MajorVersionLS = 7601, MinorVersionLS = 17514        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:53:31
8272 (0x2050)
Failed to find properties of file 4        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:53:31        8272 (0x2050)
UnMounting Image (Commit Changes = 0) ...        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:53:31        8272 (0x2050)
Completed processing image package PackageID. Status = Failed        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:54:04        8272 (0x2050)
Updated history for image package PackageID in the database        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:54:04        8272 (0x2050)
Schedule processing failed        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:54:04        8272 (0x2050)
Processing completed for Schedule with ID 16777237        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:54:04        8272 (0x2050)
STATMSG: ID=7910 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCMServer.domain SITE=Site_Code PID=8560 TID=8272 GMTDATE=Sat Jun 14 13:54:04.964 2014 ISTR0="16777237" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0        SMS_OFFLINE_SERVICING_MANAGER
14/06/2014 14:54:04        8272 (0x2050)
Schedule processing thread stopped        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:54:05        8272 (0x2050)
I'm not sure what file "Failed to find properties of file 4" is referring to, whether dism.exe, an update or the image itself, but immediately after this message appears the image is unmounted. After that this message shows:
"Completed processing image package PackageID. Status = Failed"
As I say, there's a lot of information available re Offline Servicing but I haven't found anything with these particular messages.
If anyone has encountered this before, I'd appreciate any information you have.
Regards,
John.

Hi,
I think file named 'NO_SMS_ON_DRIVE.SMS’ might be causing this issue. If this file is present in logical drives, then please give it a shot one more time after deleting this file from the logical drives.
Due to this file, it might be preventing 'smsexec' service to skip the drive when looking for content. So worth a try!
After deleting this file, you also need to restart 'smsexec' service to reflect the changes. You can also verify from below registry value & ensure that all of your logical drives (specially where SCCMContentLib directory resides) should be listed
over there
'HKLM\Software\Microsoft\SMS\DP\ContentLibUsableDrives'
Hope this will help!
Cheers | Navdeep Sidhu

SCCM 2012 - Project 2010 Standard deployment failed with error 1603

Hi everyone,
I’m in the progress to roll out a software deployment via SCCM 2012, it’s to remove the current Project 2010 Professional we installed and reinstall the Standard version. We got a task sequence for the job, which is Reboot>Un-install Project 2010 Pro>Reboot>Install
Project 2010 Std.
The Un-installation process uses this command: setup.exe /uninstall PrjPro /config "PrjPro.WW\uninstall.xml"
The Installation process uses this command: setup.exe /adminfile project_silent_install.MSP
But the deployment result is quite random, some of the PCs would succeed without any issue, some of them with fail at the installation process with 1708/1603 error. As far as I know we use standard Win 7 64bits SOE across the environment, so everyone should
have same system baseline.
I reviewed some of the failed Project 2010 Standard installation logs as it shows the following:
Executing chained package: PrjStdWW
05/09/2014 20:16:14 Installing chained package: PrjStdWW
PERF: TickCount=530512 Name=Verify MSI local install source Description=Begin function
OSE is detected as a registered service. Service binary is reported at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
OSE service binary is detected at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
File at \\SCCM2012\SMSPKGE$\PC100139\PrjStd.WW\ose.exe has version: 14.0.4730.1010
File at C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE has version: 14.0.4730.1010
Running OSE version 14.0.4730.1010
OSE is detected as a registered service. Service binary is reported at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
OSE service binary is detected at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
File at \\SCCM2012\SMSPKGE$\PC100139\PrjStd.WW\ose.exe has version: 14.0.4730.1010
File at C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE has version: 14.0.4730.1010
Running OSE version 14.0.4730.1010
LIS: wait for package "{90140000-003A-0000-0000-0000000FF1CE}" to complete caching
LIS: package "{90140000-003A-0000-0000-0000000FF1CE}" caching completed
PERF: TickCount=530528 Name=Completed verify local install source Description=End function
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Use Shell UI transform : LIS\{90140000-0115-0409-0000-0000000FF1CE}\ShellUI.MST
Current transform is at path: LIS\{90140000-0115-0409-0000-0000000FF1CE}\ShellUI.MST
OSE is detected as a registered service. Service binary is reported at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
OSE service binary is detected at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
File at \\SCCM2012\SMSPKGE$\PC100139\PrjStd.WW\ose.exe has version: 14.0.4730.1010
File at C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE has version: 14.0.4730.1010
Running OSE version 14.0.4730.1010
Using transform at path: C:\MSOCache\All Users\{90140000-0115-0409-0000-0000000FF1CE}-C\ShellUI.MST
Catalyst Package Install...
Package: PrjStdWW
File: C:\MSOCache\All Users\{90140000-003A-0000-0000-0000000FF1CE}-C\PrjStdWW.msi
Command Line: PATCH="\\SCCM2012\SMSPKGE$\PC100139\project_silent_install.MSP" ADDLOCAL=C.35347883.0E64.45B4.88A0.1881DE05E259,OSpp_Core,Project_PIA,SetupExeArpEntry,Office10Fix1,ProductFiles,InternationalSupportFiles_JPN,AceFiles,IMNFiles,OfficeIntlRDC,AceOdbc,OArt_DocTheme,OSetupController,WISPFiles,TCDRegistration,SetLanguageFiles,TCWorks7Files,ClviewFiles,VBAFiles,OfficeAppSupport,TextConverters,ProductNonBootFiles,dummy_Office_PIA,CAGOffice10,VSCommonPIAHidden,WebDiscussFiles,CAGCat10,CAGCat10Clips,MsoInstalledPackagesScoped,WxpFiles,SetupControllerFiles,Forms_PIA,dummy_MSCOMCTL_PIA,AlwaysInstalled,Gimme_OnDemandData,AceRepl,OISFiles,OfficeOLESupport,OfficeMSProof6,CAGFiles,InternationalSupportFiles_ArialUni,OSpp,Ace_PIA,GraphicsFiltersFile,WebDriveFiles,PROJECTFiles,ProductFiles_B2TR,SetupXmlFiles,OfficePostBoot,DocumentImagingUtils,VSTOCLR35,CAGCategoryFiles,ProjectCommon,VSTO,ProofingParent,MsoCommonShellHandler,OfficeDigitalSFiles,CARegistryFeature,OfficeCoreRDC,SetupExeAddRegistry,NonC2R_ProductFiles,MSSOAP3,TranslationCore,CAGOffice10Clips REMOVE=WISPHidden ARPENTRY_NOMODIFY="#0" ARPENTRY_MODIFYPATH="""C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\setup.exe"" /modify PRJSTD /dll OSETUP.DLL" INSTALLLOCATION="C:\Program Files (x86)\Microsoft Office\" SLD_OEMPIDKEY="0" ARPENTRY_NOELEVATEONMODIFY="#0" SETUP_REBOOT="never" COMPANYNAME=" " ARPENTRY_SKUCOMPONENTS="[~]C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\Office.en-us\setup.xml[~]C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\Proofing.en-us\setup.xml[~]C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\Project.en-us\setup.xml[~]C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\Office64.en-us\setup.xml[~]C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\PRJSTD\setup.xml[~]" ARPENTRY_HELPLINK="" ARPENTRY_DISPLAYICON="C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\OSETUP.DLL,1" ARPENTRY_DISPLAYNAME="Microsoft Project Standard 2010" ACCEPTEDEULA="1" ARPENTRY_DISPLAYVERSION="14.0.4763.1000" BRANDING_XML="C:\Windows\TEMP\Setup00001048\BRANDING.XML" SLD_SUPPORTSBYPASS="0" SLD_ACID="5DC7BF61-5EC9-4996-9CCB-DF806A2D0EFE" SLD_TRIALTYPE="0" ARPENTRY_PACKAGEREFS="[~]OfficeMUISet.en-us[~]OfficeMUI.en-us[~]Proofing.en-us[~]Proof.en-us[~]Proof.es-es[~]Office64MUISet.en-us[~]PrjStdWW[~]Office64WW[~]Office64MUI.en-us[~]ProjectMUI.en-us[~]Proof.fr-fr[~]" SLD_DPID="#xF804000004000000380032003500300033002D00300030003000390038002D003000300031002D003000300030003000310030002D00300033002D0031003000330033002D0037003600300031002E0030003000300030002D0031003200390032003000310034000000000000000000000000000000000000000000000000000000000000000000350064006300370062006600360031002D0035006500630039002D0034003900390036002D0039006300630062002D00640066003800300036006100320064003000650066006500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000500072006F006A0065006300740053007400640056004C00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000A09E4657B64703B2F32E339838F004006FE4EEC0394DE6AB2D77DCABCBC8F1C3B8B617EF54ACB52805F38EE560D0B738230977F4AB92430B37CBF02B49DB7636DCF15CE7E175CCF354E009C7A02432315800310036002D0030003800300035003100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000056006F006C0075006D0065003A00470056004C004B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000006C0074004B004D00530000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000" REMOVESAMEVERSION="" SLD_LICENSETYPE="6" SETUPEXEINSTALLUICULTURE="en-US" ARPENTRY_SHELLUITRANSFORMLANGUAGE="en-US" USERNAME=" " ARPENTRY_CONTACT="" ARPENTRY_HELPTELEPHONE="" ARPENTRY_PRODUCTCODES="[~]{90140000-00B4-0409-0000-0000000FF1CE}[~]{90140000-002C-0409-0000-0000000FF1CE}[~]{90140000-003A-0000-0000-0000000FF1CE}[~]{90140000-002A-0000-1000-0000000FF1CE}[~]{90140000-001F-0C0A-0000-0000000FF1CE}[~]{90140000-001F-0409-0000-0000000FF1CE}[~]{90140000-001F-040C-0000-0000000FF1CE}[~]{90140000-0115-0409-0000-0000000FF1CE}[~]{90140000-006E-0409-0000-0000000FF1CE}[~]{90140000-002A-0409-1000-0000000FF1CE}[~]{90140000-0116-0409-1000-0000000FF1CE}[~]" ARPENTRY_INSTALLLOCATION="C:\Program Files (x86)\Microsoft Office\" SETUPEXE_DOARPWRITE="1" ACIDS="11B39439-6B93-4642-9570-F2EB81BE2238;5DC7BF61-5EC9-4996-9CCB-DF806A2D0EFE;B6E9FAE1-1A0E-4C61-99D0-4AF068915378" ARPENTRY_SPPSKUID="[~]5DC7BF61-5EC9-4996-9CCB-DF806A2D0EFE[~]" ARPENTRY_NOREMOVE="#0" SLD_PKU="0" SLD_PID="82503-001-0000106-49615" LICTYPE="ltKMS" ARPENTRY_UNINSTALLSTRING="""C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\setup.exe"" /uninstall PRJSTD /dll OSETUP.DLL" ARPENTRY_NOREPAIR="#1" ARPENTRY_URLUPDATEINFO="" ARPENTRY_URLINFOABOUT="" REMOVEPREVIOUS="" ARPENTRY_CACHELOCATION="C:\MSOCache\All Users" REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\" ARPSYSTEMCOMPONENT=1 TRANSFORMS="C:\MSOCache\All Users\{90140000-0115-0409-0000-0000000FF1CE}-C\ShellUI.MST" ALLUSERS="1"
PERF: TickCount=530543 Name=MsiPackage::Install Description=Calling OMsiInstaller::InstallProduct for package file "C:\MSOCache\All Users\{90140000-003A-0000-0000-0000000FF1CE}-C\PrjStdWW.msi"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Error: Failed to install product: C:\MSOCache\All Users\{90140000-003A-0000-0000-0000000FF1CE}-C\PrjStdWW.msi ErrorCode: 1603(0x643).
Log level changed from: Standard to: Verbose
Rolling back chain
05/09/2014 20:18:47 Rolling back package: PrjStdWW
There appears to be no rollback work to do for package: PrjStdWW path: C:\MSOCache\All Users\{90140000-003A-0000-0000-0000000FF1CE}-C\PrjStdWW.msi
05/09/2014 20:18:47 Rolling back package: Office64WW
Package Office64WW was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Office64WW
File: C:\MSOCache\All Users\{90140000-003A-0000-0000-0000000FF1CE}-C\Office64WW.msi
Command Line: ADDLOCAL=AcePiaReg64,VSTO64,WordXmlEditVerb64,ExcelXmlEditVerb64,GrooveShellIntegration64,Project64Files,OSpp64_Core,ExcelPiaReg64,GraphPiaReg64,FormsPiaReg64,SmartTagPiaReg64,PPTXmlEditVerb64,MsoInstalledPackagesScoped,OfficeExample64bitFilesA,WAC_XmlEditVerb64SPD,SetupXmlFiles,WordPiaReg64,Outlook64Files,AlwaysInstalled64,VBEPiaReg64,VisioPiaReg64,Outlook64SearchShellReg,OneNote64Files,SetupControllerFiles,ProjectPiaReg64,SearchFilters64Files,OutlookPiaReg64,Gimme_OnDemandData,Visio64ShapeSearch,WAC_PIARegSPD64,ProductNonBootFiles64,XDocsPiaReg64,PublisherPiaReg64,OneNotePIAReg64,ProductFiles64,OfficeExample64bitFilesB,OfficePiaReg64,Visio64Files,TCDRegistration64,OSpp64,XDOCSFiles64,XDocsXmlEditVerb64,MsoCommonShellHandler64bit,AccessPiaReg64,PowerPointPiaReg64 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Office64WW ProductCode:{90140000-002A-0000-1000-0000000FF1CE}
05/09/2014 20:18:56 Rolling back package: ProjectMUI.en-us
Package ProjectMUI.en-us was installed in the chain... uninstalling as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Install Rollback (uninstall)...
Package: ProjectMUI.en-us
Product Code: {90140000-00B4-0409-0000-0000000FF1CE}
Command Line: REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back install of package: ProjectMUI.en-us path:C:\MSOCache\All Users\{90140000-00B4-0409-0000-0000000FF1CE}-C\ProjectMUI.msi
05/09/2014 20:19:00 Rolling back package: Proofing.en-us
Package Proofing.en-us was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Proofing.en-us
File: C:\MSOCache\All Users\{90140000-002C-0409-0000-0000000FF1CE}-C\Proofing.msi
Command Line: ADDLOCAL=Gimme_OnDemandData,SetupXmlFiles,SetupControllerFiles,MsoInstalledPackagesScopedIntl_1033 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Proofing.en-us ProductCode:{90140000-002C-0409-0000-0000000FF1CE}
05/09/2014 20:19:04 Rolling back package: Proof.en-us
Package Proof.en-us was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Proof.en-us
File: C:\MSOCache\All Users\{90140000-002C-0409-0000-0000000FF1CE}-C\Proof.en\Proof.msi
Command Line: ADDLOCAL=FindAllWordFormsFiles_1033,Gimme_OnDemandData,SpellingAndGrammarFiles_1033,ThesaurusFiles_1033,MsoInstalledPackagesScopedIntl_1033,HyphenationFiles_1033,OCR_1033,SetupControllerFiles,SetupXmlFiles REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Proof.en-us ProductCode:{90140000-001F-0409-0000-0000000FF1CE}
05/09/2014 20:19:05 Rolling back package: Proof.fr-fr
Package Proof.fr-fr was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Proof.fr-fr
File: C:\MSOCache\All Users\{90140000-002C-0409-0000-0000000FF1CE}-C\Proof.fr\Proof.msi
Command Line: ADDLOCAL=MsoInstalledPackagesScopedIntl_1036,Gimme_OnDemandData,SpellingAndGrammarFiles_1036,SetupControllerFiles,FindAllWordFormsFiles_1036,TranslationFiles_1036,ThesaurusFiles_1036,HyphenationFiles_1036,SetupXmlFiles,OCR_1036 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Proof.fr-fr ProductCode:{90140000-001F-040C-0000-0000000FF1CE}
05/09/2014 20:19:11 Rolling back package: Proof.es-es
Package Proof.es-es was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Proof.es-es
File: C:\MSOCache\All Users\{90140000-002C-0409-0000-0000000FF1CE}-C\Proof.es\Proof.msi
Command Line: ADDLOCAL=Gimme_OnDemandData,SpellingAndGrammarFiles_3082,OCR_3082,FindAllWordFormsFiles_3082,HyphenationFiles_3082,ThesaurusFiles_3082,MsoInstalledPackagesScopedIntl_3082,SetupControllerFiles,SetupXmlFiles,TranslationFiles_3082 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Proof.es-es ProductCode:{90140000-001F-0C0A-0000-0000000FF1CE}
05/09/2014 20:19:12 Rolling back package: Office64MUISet.en-us
Package Office64MUISet.en-us was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Office64MUISet.en-us
File: C:\MSOCache\All Users\{90140000-0116-0409-1000-0000000FF1CE}-C\Office64MUISet.msi
Command Line: ADDLOCAL=Gimme_OnDemandData,SetupXmlFiles,SetupControllerFiles,MsoInstalledPackagesScopedIntl_1033 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Office64MUISet.en-us ProductCode:{90140000-0116-0409-1000-0000000FF1CE}
05/09/2014 20:19:19 Rolling back package: Office64MUI.en-us
Package Office64MUI.en-us was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Office64MUI.en-us
File: C:\MSOCache\All Users\{90140000-0116-0409-1000-0000000FF1CE}-C\Office64MUI.msi
Command Line: ADDLOCAL=OfficeExample64bitFilesBIntl_1033,OfficeExample64bitFilesAIntl_1033,Gimme_OnDemandData,Outlook64SearchShellRegIntl_1033,ProductFilesIntl64_1033,MsoInstalledPackagesScopedIntl_1033,OneNoteToLinkedNotesIEAddin64Intl_1033,GrooveFiles64Intl_1033,SetupControllerFiles,SetupXmlFiles REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Office64MUI.en-us ProductCode:{90140000-002A-0409-1000-0000000FF1CE}
05/09/2014 20:19:20 Rolling back package: OfficeMUISet.en-us
Package OfficeMUISet.en-us was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: OfficeMUISet.en-us
File: C:\MSOCache\All Users\{90140000-0115-0409-0000-0000000FF1CE}-C\OfficeMUISet.msi
Command Line: ADDLOCAL=Gimme_OnDemandData,SetupXmlFiles,SetupControllerFiles,MsoInstalledPackagesScopedIntl_1033 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: OfficeMUISet.en-us ProductCode:{90140000-0115-0409-0000-0000000FF1CE}
05/09/2014 20:19:20 Rolling back package: OfficeMUI.en-us
Package OfficeMUI.en-us was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: OfficeMUI.en-us
File: C:\MSOCache\All Users\{90140000-0115-0409-0000-0000000FF1CE}-C\OfficeMUI.msi
Command Line: ADDLOCAL=MetricConverterIntl_1033,AlwaysInstalledIntl_1033,MSTagPluginStockFilesIntl_1033,WebDiscussFilesIntl_1033,GraphicsFiltersPNGFilesIntl_1033,EquationEditorFilesIntl_1033,GraphicsFiltersEPSFilesIntl_1033,MSTagPluginNamesFilesIntl_1033,TCWP5FilesIntl_1033,CAGOffice10Intl_1033,OISFilesIntl_1033,WxpFilesIntl_1033,XDOCSEditorFilesIntl_1033,CAGFilesIntl_1033,WISPHiddenIntl_1033,CAGCat10Intl_1033,SetLanguageFilesIntl_1033,OSetupControllerIntl_1033,MsoInstalledPackagesScopedIntl_1033,TCRecoverFilesIntl_1033,SetupControllerFiles,ClviewFilesIntl_1033,GraphHelpFilesIntl_1033,ProductNonBootFilesIntl_1033,MSTagPluginPlacesFiles_1033,VisioPreviewerIntl_1033,ProductFilesIntl_1033,AceReplIntl_1033,GraphicsFiltersCGMFilesIntl_1033,GraphicsFiltersWPGFilesIntl_1033,Gimme_OnDemandData,TCWP6FilesIntl_1033,GraphicsFiltersGIFFilesIntl_1033,GRAPHFilesIntl_1033,MSTagPluginDateFilesIntl_1033,WebDriveFilesIntl_1033,LOBiFilesIntl_1033,LISTFilesIntl_1033,UICaptionsCompanionIntl_1033,SetupXmlFiles,AceFilesIntl_1033,TOOLSFilesIntl_1033,MSSOAP3Intl_1033,VBAHelpFilesIntl_1033,GraphicsFiltersPICTFilesIntl_1033,OfficeDigitalSFilesIntl_1033,VBAFilesIntl_1033,GraphicsFiltersJPEGFilesIntl_1033,QueryFilesIntl_1033,SetLanguageHelpFilesIntl_1033 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: OfficeMUI.en-us ProductCode:{90140000-006E-0409-0000-0000000FF1CE}
Error attaching to OSE, error 0x00000000
Stopping running ose
LIS: start uncaching for download "{90140000-002C-0409-0000-0000000FF1CE}-C"
LIS: finished uncaching for download "{90140000-002C-0409-0000-0000000FF1CE}-C"
LIS: start uncaching for download "{90140000-003A-0000-0000-0000000FF1CE}-C"
LIS: finished uncaching for download "{90140000-003A-0000-0000-0000000FF1CE}-C"
LIS: start uncaching for download "{90140000-00B4-0409-0000-0000000FF1CE}-C"
LIS: finished uncaching for download "{90140000-00B4-0409-0000-0000000FF1CE}-C"
LIS: start uncaching for download "{90140000-0115-0409-0000-0000000FF1CE}-C"
LIS: finished uncaching for download "{90140000-0115-0409-0000-0000000FF1CE}-C"
LIS: start uncaching for download "{90140000-0116-0409-1000-0000000FF1CE}-C"
LIS: finished uncaching for download "{90140000-0116-0409-1000-0000000FF1CE}-C"
Error attaching to OSE, error 0x00000000
Stopping running ose
SystemRestore : Attempting to cancelling System-Restore-Point for Product [Microsoft Project Standard 2010] (with RestorePointType [0, Installed]).
SystemRestore : Successfully cancelled System-Restore-Point for Product [Microsoft Project Standard 2010] (with RestorePointType [0, Installed]).
Not showing completion dialog because it was not requested.
Catalyst execution finished: 05/09/2014 20:19:25. Return code: 1603.
PERF: TickCount=722128 Name=RunSetup Description=End function
Can onyone enlighten me what's went wrong, and why did I get this inconsitent installation behaviour?
Thank you very much!!!

1603 means there is a fatal error during installation process.
Take a look at the article below. It may help on finding cause.
Hi Juke,
I did do fair a bit of Googling before I started the post. I have increased the logging level on one of the machines failed on the installation. Apparently Project installation log doesn't throw the "return value 3", I think it's pointing to a particular
updating item, anyone knows what is it?
Microsoft Office Project Standard 2010 - Update '{35347883-0E64-45B4-88A0-1881DE05E259}' could not be installed.
The following is the detailed installation log.
MSI (s) (8C:B4) [20:31:33:122]: Executing op: SetTargetFolder()
MSI (s) (8C:B4) [20:31:33:122]: Executing op: FontRegister(Title=Arial Unicode MS (TrueType),File=ARIALUNI.TTF)
MSI (s) (8C:B4) [20:31:33:122]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\Fonts
MSI (s) (8C:B4) [20:31:33:122]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=0)
MSI (s) (8C:B4) [20:31:33:122]: Error in rollback skipped. Return: 5
MSI (s) (8C:B4) [20:31:33:746]: Entering MsiProvideAssembly. AssemblyName: Policy.12.0.Microsoft.Office.Interop.MSProject,version="14.0.0.0000000",processorArchitecture="MSIL",publicKeyToken="71E9BCE111E9429C",fileVersion="14.0.4751.1000",culture="neutral", AppContext: , InstallMode: -4
MSI (s) (8C:B4) [20:31:33:746]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (8C:B4) [20:31:33:777]: MsiProvideAssembly is returning: 1607
MSI (s) (8C:B4) [20:31:33:777]: Entering MsiProvideAssembly. AssemblyName: Policy.11.0.Microsoft.Office.Interop.MSProject,version="14.0.0.0000000",processorArchitecture="MSIL",publicKeyToken="71E9BCE111E9429C",fileVersion="14.0.4751.1000",culture="neutral", AppContext: , InstallMode: -4
MSI (s) (8C:B4) [20:31:33:777]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (8C:B4) [20:31:33:808]: MsiProvideAssembly is returning: 1607
MSI (s) (8C:B4) [20:31:33:808]: Entering MsiProvideAssembly. AssemblyName: Microsoft.Office.Interop.MSProject,version="14.0.0.0000000",processorArchitecture="MSIL",publicKeyToken="71E9BCE111E9429C",fileVersion="14.0.4751.1000",culture="neutral", AppContext: , InstallMode: -4
MSI (s) (8C:B4) [20:31:33:808]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (8C:B4) [20:31:33:840]: MsiProvideAssembly is returning: 1607
MSI (s) (8C:B4) [20:31:33:840]: Note: 1: 2318 2:
MSI (s) (8C:B4) [20:31:33:840]: No System Restore sequence number for this installation.
MSI (s) (8C:B4) [20:31:33:840]: Unlocking Server
MSI (s) (8C:B4) [20:31:33:980]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.
MSI (s) (8C:B4) [20:31:33:980]: Transforming table InstallExecuteSequence.
MSI (s) (8C:B4) [20:31:33:980]: Transforming table InstallExecuteSequence.
MSI (s) (8C:B4) [20:31:33:980]: Transforming table InstallExecuteSequence.
MSI (s) (8C:B4) [20:31:33:980]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (8C:B4) [20:31:34:011]: Product: Microsoft Office Project Standard 2010 - Update '{35347883-0E64-45B4-88A0-1881DE05E259}' could not be installed. Error code 1603. Additional information is available in the log file C:\WINDOWS\TEMP\MSI1f79e.LOG.
MSI (s) (8C:B4) [20:31:34:011]: Windows Installer installed an update. Product Name: Microsoft Office Project Standard 2010. Product Version: 14.0.4763.1000. Product Language: 0. Manufacturer: Microsoft Corporation. Update Name: {35347883-0E64-45B4-88A0-1881DE05E259}. Installation success or error status: 1603.
MSI (s) (8C:B4) [20:31:34:011]: Note: 1: 1708
MSI (s) (8C:B4) [20:31:34:011]: Product: Microsoft Office Project Standard 2010 -- Installation operation failed.
MSI (s) (8C:B4) [20:31:34:011]: Windows Installer installed the product. Product Name: Microsoft Office Project Standard 2010. Product Version: 14.0.4763.1000. Product Language: 0. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.
MSI (s) (8C:B4) [20:31:34:011]: Attempting to delete file C:\WINDOWS\Installer\5a202cf.msp
MSI (s) (8C:B4) [20:31:34:011]: Unable to delete the file. LastError = 32
MSI (s) (8C:B4) [20:31:34:011]: Attempting to delete file C:\WINDOWS\Installer\5a202d0.mst
MSI (s) (8C:B4) [20:31:34:011]: Unable to delete the file. LastError = 32
MSI (s) (8C:B4) [20:31:34:011]: Deferring clean up of packages/files, if any exist
MSI (s) (8C:B4) [20:31:34:011]: Attempting to delete file C:\WINDOWS\Installer\5a202cf.msp
MSI (s) (8C:B4) [20:31:34:011]: Attempting to delete file C:\WINDOWS\Installer\5a202d0.mst
MSI (s) (8C:B4) [20:31:34:011]: MainEngineThread is returning 1603
MSI (s) (8C:24) [20:31:34:011]: No System Restore sequence number for this installation.
MSI (s) (8C:24) [20:31:34:011]: User policy value 'DisableRollback' is 0
MSI (s) (8C:24) [20:31:34:011]: Machine policy value 'DisableRollback' is 0
MSI (s) (8C:24) [20:31:34:011]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (8C:24) [20:31:34:011]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (8C:24) [20:31:34:011]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (8C:24) [20:31:34:027]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (8C:24) [20:31:34:027]: Restoring environment variables
MSI (s) (8C:24) [20:31:34:027]: Destroying RemoteAPI object.
MSI (s) (8C:48) [20:31:34:027]: Custom Action Manager thread ending.
MSI (c) (F4:1C) [20:31:34:027]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (F4:1C) [20:31:34:027]: MainEngineThread is returning 1603
=== Verbose logging stopped: 7/05/2014 20:31:34 ===

Windows 8.1 laptop computer not showing in SCCM 2012 devices collection

Hi,
I am trying to do a POC on license management from SCCM 2012. I have configures a SCCM 2012 server and intune subscription also. I have Android, iOS and desktop apps uploaded (.msi). when I enrolled android and ios devices its shows up in SCCM,
devices collection but do not show in Intune.
my company portal is nicely coming up on android and iOS tabs. on the other hand company portal showing only Web apps, on a win8.1/7 laptop.
When I tried to enroll 2 windows 8.1/ 7 laptop (intel x86), they donot show up in SCCM. clients of intune manually installed, endpoint protection of SCCM installed also on both boxes.
I tried updating membership in SCCM for both know and unknown type, many time and also triggered Deployment of some desktop app, to the win 8.1 laptops. the desktops are showing in Intune All devices -> all computers nicely. But
not in SCCM2012.
what did I missed, I tried to add all the logical roles. below is some details what shows up in Intune:
indranil

If you installed the Intune agents on the Win 8.1 and Win 7 systems, then they will never show up in ConfigMgr.
There are basically two parts of Intune -- a Mobile Device Management piece and a Windows management piece. The Intune connector in ConfigMgr takes over the MDM piece and nothing more. When ConfigMgr takes over this MDM piece, as Torsten said, all MDM devices
enrolled show up in ConfigMgr and not Intune because that's now controlled by ConfigMgr. The Windows management piece remains unchanged and separate though and so those systems will be directly managed by Intune only or ConfigMgr only.
So you have three options there:
- Install the ConfigMgr agent and managed using COnfigMgr
- Install the Intune agent and manage using Intune
- Enroll the systems using OMA-DM which manages them as if they were devices. This means so you don't get SCEP or Windows Updates or most of the other ConfigMgr functionality. This is only valid for Win 8.1 though.
Jason | http://blog.configmgrftw.com

Windows 8.1 Mobile Device Management and SCCM 2012 R2 - 'Turn on' option missing

I am trying to test a virtual desktop with SCCM 2012 R2 integrated with Intune. There is no Configuration Manager client on the workstation, the Intune subscription is configured and enabled for Windows enrolment, AD is synchronizing with Intune, DNS has
the enrolment record added and resolves, the user can logon to Intune from the client using Internet Explorer and the client has had the registry key added with the DiscoveryService configured to manage.microsoft.com. The problem is that on
the 8.1 workstation in Workplace Settings the only option is 'Join' and the 'Turn-on' option is missing. How do I get it to appear?

Yes I am using an activated version of 8.1 Enterprise, it is in a workgroup and I am logged in as a member of the local Administrator's group but not Administrator. I even joined the domain again and then removed it. Still there is only the 'Join'
option and no 'Turn on' option. This is driving me nuts.

Sccm 2012 r2 connector stops synchronizing at 11percent

Similar Messages

Maybe you are looking for