PENDING Failed to find an available source location ApplyOperatingSystem

[Job André]

We use SCCM 1511 (with 2 DP's) and reimage our systems once in 2 weeks.
Since couple of months we have this issue on some clients. The Task Sequence runs on about 30 clients at the same time, and about 7 - 10 clients are crashing with this error. Every time there are different clients crashing.
All these clients are on the same switch, on the same VLAN etc.

The Task Sequence is started from within Windows and then reboots to Windows PE.
If we reimage the same clients from PXE-boot it just runs normally without problems.

In smsts.log (attached to this post) i see errors like 'no credential information in environment'. On succesfull clients, i don't see this error.

When i google this problem it is related to the Network Access Account. I have set this account, and I think that if this is the problem I would have problems with all my clients. But as told: only a percentage of my clients have this problem.

 

[Prajwal Desai]

I see multiple errors and mostly the errors are related to network access account. As you have mentioned that you have set the network access account, I would suggest you to check if the password entered is correct. What are the AD groups that this account is the member of ?. Are the boundaries and boundary groups configured and is the DP associated with the boundary group ?.

Unsuccessful in connecting to \\checsccm02.che.local\SMSPKGD$\CHE00035. Invalid username or password. ApplyOperatingSystem 05-06-2016 13:02:35 1904 (0x0770)
Unsuccessful in connecting to or accessing \\checsccm02.che.local\SMSPKGD$\CHE00035\ with default account. ApplyOperatingSystem 05-06-2016 13:02:35 1904 (0x0770)
Failed to access the share \\checsccm02.che.local\SMSPKGD$\CHE00035\ with network access account ApplyOperatingSystem 05-06-2016 13:02:35 1904 (0x0770)
Failed to find an available source location ApplyOperatingSystem 05-06-2016 13:02:35 1904 (0x0770)
Installation of image 1 in package CHE00035 failed to complete..
The system cannot find the file specified. (Error: 80070002; Source: Windows) ApplyOperatingSystem 05-06-2016 13:02:35 1904 (0x0770)

 

[Job André]

The network access account is member of Domain Admins. Boundaries are configured per IP subnet. All bounadaries are togheter in 1 boundary group. The DP is in a boundary, the client systems are in other boundaries. But all in the same Boundary Group.

So if the password is correct, why would other systems (in the same boundary) run the task sequence succesfull? Its only around 30% wich are failling.

I read something about not to have special caracters in the password for the NAA account. Now it has a '.' in it. Is it possible to change the password of the account in AD, then re-enter the account in SCCM and try again?

 

[Prajwal Desai]

Yes, you can do that. I did see that thing in the log file "connect(pszPath, pszAccount, pszPassword, L"", uFlags)"
Reset the password in AD. Under the network access account, add the account and verify the password.
Let me know how it goes..

 

[Job André]

Ok i changed it. I will let you know after this weekend

 

[Prajwal Desai]

cool.. Just update this thread..

 

[Job André]

Ok here is an update. Last weekend a total of 76 clients in batches of 32, 32 and 12 had to be run the task sequence.
20 of them runs without any problems
3 of them didn't run with the above error wich i started this topic about.
53 of them didnt even start the task sequence. I looked around in their logfiles and found this errors in cas.log at about 10 minutes before start of the deployment/maintenance window:

Failed to get DP locations from LS for content CHE00044.2 and location request {99C515BB-9C42-4D01-A0AC-596E0D6A57F5} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE00032.3 and location request {E0098105-BBC8-4983-8C77-79B86C65EE9A} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE00027.4 and location request {06533643-4DCE-4A45-9679-B7D0B3796086} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE0000D.3 and location request {C1256D16-6968-4FD2-B13B-B4AA424371E2} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE00055.2 and location request {057B9389-6852-4880-AA02-CF9C6DA22FF6} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE0004C.2 and location request {AFC88817-4B95-4268-9414-31C87DCE2E30} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE0002D.3 and location request {A6029389-1177-4FCF-898D-61E6C4C69E4D} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE0004F.1 and location request {03724491-A3CE-42B0-B1AC-68D2F42D26B8} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE00041.4 and location request {72B054CD-430E-4F0F-A171-CE875163AAE5} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE00034.3 and location request {082C72A9-66BA-4C87-8AAD-BD20491EEA02} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE00025.5 and location request {1134AB3B-2565-426D-8F1A-A6525F15206E} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE00002.1 and location request {ECC02646-2ECB-4987-8A88-DAA23239164E} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE0000F.2 and location request {237128FA-E5AD-46F3-A797-E83562921DBC} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE00037.3 and location request {FE5F6D5A-0BC2-4A57-A9F2-017152C4B140} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE00035.15 and location request {E674210A-4564-4801-81C9-68AFC426E97A} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE00020.2 and location request {8AA771FE-0A29-4B58-AB14-43215D11C246} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE00024.3 and location request {EF623F00-9956-4D27-BE1D-CB5D2A9F974E} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE00026.2 and location request {1970E81D-093A-45EA-89CA-E7D640170DDB} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE00030.4 and location request {EDF9E958-BD25-4ED0-ACE6-EC1D10A0DA31} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE0001E.3 and location request {2AC1270D-E2C5-4A28-B588-4FAF9B07704D} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE00031.2 and location request {9A217D64-AF07-4975-B597-8C297BAA5363} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE00038.2 and location request {9CCC8606-F9E2-4FD5-8B22-593753D3B420} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE0001F.2 and location request {5EBAE12D-D5D4-4CCB-9129-C3BFD81F2D04} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE00039.3 and location request {99FFA90E-AC86-4115-BCEB-FC3EE67267AE} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE0007C.4 and location request {4691F0B4-24F4-4FA0-9EA3-2885072C96E2} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE0000B.2 and location request {482E29C7-1B01-4645-ABD0-387CB2EC2490} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE0000A.4 and location request {D44AD0EA-7139-4386-BDD5-C1BD04AC0A3B} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE00022.3 and location request {99CF2FCB-519E-4C83-9BD2-EB682141E0FD} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE00033.3 and location request {C291B739-A205-4B9F-A8D9-DCC676EE5C4C} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE00023.5 and location request {531AD1C3-45DC-48E3-A2C8-C14FD626B5EE} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE0000E.2 and location request {7A8E94DA-6744-4ABA-9354-A3600497320C} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
Failed to get DP locations from LS for content CHE0004E.12 and location request {AAD38181-4BF1-4FDF-B1C2-69C06A2EE01E} ContentAccess 18-9-2016 02:49:00 2688 (0x0A80)
===========================================================
In execmgr.log i see:

GetContentLocationFromCas GetState Statefailed execmgr 18-9-2016 03:03:02 3464 (0x0D88)
CTSExecutionRequest::GetMemberProgramLocations - failed to get content locations from CAS 0x80004005 execmgr 18-9-2016 03:03:02 3464 (0x0D88)
===========================================================
In TSAgent.log i see:

GetMemberProgramLocations() failed. code 80004005 TSAgent 18-9-2016 03:03:02 3464 (0x0D88)
Task Sequence Manager could not get active request info. code 80004005 TSAgent 18-9-2016 03:03:02 3464 (0x0D88)
Failed to get the details of the execution request. code 0x80004005 TSAgent 18-9-2016 03:03:02 3464 (0x0D88)
Task Sequence Agent could not get active request info. code 80004005 TSAgent 18-9-2016 03:03:02 3464 (0x0D88)
Error initializing TS environment. Code 0x80004005 TSAgent 18-9-2016 03:03:02 3464 (0x0D88)
Task sequence launcher advertisement failed!. Code 0x80004005 TSAgent 18-9-2016 03:03:02 3464 (0x0D88)
CTSAgent::Execute - Failed to launch Task Sequence manager. TSAgent 18-9-2016 03:03:02 3464 (0x0D88)

 

[Job André]

Ok i found out that maybe above errors has nothing to do with the initial errors about network access account. I think these are related to eralier problems with not finishing the task sequence successfull a couple of weeks ago.
Tonight the task sequence will run again on 20 clients. I will see tomorrow what happened and keep this updated

 

[Job André]

Update: Last night the task sequence deployment had to run on 34 clients.
6 of them didnt start. I think because of the problem i described in post #8. So thats another problem.

The other 28 clients runned without any problems! So far so good. For a definite 'solved' I want to wait till next monday as a large batch of 3 x 32 clients will run.

 

[Job André]

Update: The issue with the network access account is resolved by changing the password.

But the other issue described in post #7 still remains. For these clients the last line in the status message log is at the start time of the deployment:
25-9-2016 5:00:00 Program started for deployment "CHE20046" ("CHE00050" - "*"). Command line: Working directory: C:\WINDOWS\system32\ User context: NT AUTHORITY\SYSTEM

[FONT=Georgia, Times New Roman, Times, serif]And nothing after that.

In TSAgent.log i see:[/FONT]
There are no locations for this program TSAgent 25-9-2016 05:00:01 1164 (0x048C)
[FONT=Georgia, Times New Roman, Times, serif]Task Sequence Manager could not get active request info. code 80004005 TSAgent 25-9-2016 05:00:01 1164 (0x048C)
Failed to get the details of the execution request. code 0x80004005 TSAgent 25-9-2016 05:00:01 1164 (0x048C)
Task Sequence Agent could not get active request info. code 80004005 TSAgent 25-9-2016 05:00:01 1164 (0x048C)
Error initializing TS environment. Code 0x80004005 TSAgent 25-9-2016 05:00:01 1164 (0x048C)
Task sequence launcher advertisement failed!. Code 0x80004005 TSAgent 25-9-2016 05:00:01 1164 (0x048C)
CTSAgent::Execute - Failed to launch Task Sequence manager. TSAgent 25-9-2016 05:00:01 1164 (0x048C)

smsts.log there is nothing in it.

I run 3 batches of 32 clients this weekend. The 1st batch has 1 clients with this issue. The 2nd batch had 2 clients with this issue, but the 3rd batch had 15 clients with this issue.

So can you tell me what the errors in tsagent.log are? [/FONT]

 

[Prajwal Desai]

The errors in TSagent.log file points that you need to check the boundaries. Use IP Address Range as a Site Boundary instead of IP subnet and see if that helps.

 

[Job André]

Ok thanx. I'll let you know if that will help

 

[Job André]

Ok I changed the boudaries and the errors in TSAgent.log are gone, so that problem is solved.

But the other problem (about the Network Access Account) is still there.. Last night 5 clients crashed after formatting as described in my opening post.
The weird thing is, these are in the same group of clients wich run the task sequence succesfull 2 weeks ago. I wrote about it in post #9. But now the failed again because of 'no credential information in environment'.

How could that be possible?