Search This Blog

Loading...

Thursday, May 19, 2016

Task Sequence error code (0x80070002)

You might se this error when deploying Windows from a SCCM 1511 task Sequence:

Task Sequence: xxx has failed with the error code (0x80070002)

image

If we take a closer look at the smsts.log file, you will in this specific case find the message No credential information in environment.

image

The reason will probably be that no Network Access Account has been defined, go to Administration, Overview, Site Configuration, Sites, in the top select Configure Site Components and Software Distribution.

image

Select the tab Network Access Account, an enter a account to use when access network locations.

image

See more information about this account here https://technet.microsoft.com/en-us/library/hh427337.aspx (search for Network Access Account)

Also see this post http://larslohmann.blogspot.dk/2016/01/task-sequence-error-code-0x80070002.html for another possible solution for the same error.

Monday, May 9, 2016

Citrix Receiver for Windows 4.4.1000.16 (CU1)

Citrix has released a new version of Citrix Receiver for Windows, new version is 4.4.1000.16 (CU1)

image

You will find ADMX/ADML files in the installation folder (C:\Program Files (x86)\Citrix\ICA Client\Configuration) or here https://www.citrix.com/downloads/citrix-receiver/windows/receiver-for-windows-latest.html

image

Download installation file :

https://www.citrix.com/downloads/citrix-receiver/windows/receiver-for-windows-latest.html

Changes is this version and documentation:

http://docs.citrix.com/en-us/receiver/windows/4-4.html

Thursday, April 28, 2016

Windows 10 and Office 2013

When deploying Windows 10 and Office 2013 with SCCM (here 1602) you might see that the update progress stops and the task sequence hangs.

image

If you take a closer look at the WUAHandler.log you will also notice that the installation progress has stopped.

image

Opening the event viewer will reveal that updates are actually still being installed.

image

Right now one workaround is to wait for all updates to be installed.

This is when you no longer see updates being installed in the Event Viewer and the Windows Update service change status to stopping.

Now the task sequence will hang for real.

image

Find the process ID for the Windows Update Service and terminate the process.

sc queryex wuauserv | find "PID"

taskkille /PID <ID from sc queryex> /F

image

This will of course change the status to not running.

image

The SMS Agent Host  will now change status to Stopping.

image

Stop this process as well:

sc queryex ccmexec | find "PID"

taskkille /PID <ID from sc queryex> /F

image

The task sequence should now continue:

image

Not pretty but ………..

Wednesday, April 20, 2016

Failed to load expression host assembly. Details: Could not load file or assembly 'SrsResources

If you choose to do an in place upgrade of SQL 2012 to SQL 2014 on your SCCM server, you might see this error when trying to run a report:

Failed to load expression host assembly. Details: Could not load file or assembly 'SrsResources, Culture=neutral' or one of its dependencies. The system cannot find the file specified"

image

And in Details:

image

The best way around this error is to remove the Reporting services point and add it again after it has been removed.

But if this is in a lab, here is a quick (and dirty) workaround:

Open the old Report Server BIN folder and copy srsresources.dll and the SCCMErrorResource (folder structure) default location will be C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer\bin when upgrading from SQL 2012.

image

And paste the file and folders to the new Report Server BIN folder as shown here:

Default location will be C:\Program Files\Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\ReportServer\bin when upgrading to SQL 2014.

image

Now locate the file rssrvpolicy.config. Default location will be C:\Program Files\Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\ReportServer for your new SQL 2014 Reporting server.

image

Edit the file and change the URL for srsresources.dll to the new location (just search for srsresources.dll to find the place to change)

Change from:

              <IMembershipCondition class="UrlMembershipCondition" version="1" Url="C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer\bin\srsresources.dll" />

Change it to:

              <IMembershipCondition class="UrlMembershipCondition" version="1" Url="C:\Program Files\Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\ReportServer\bin\srsresources.dll" />

 

Save it and after a short wait period, try running a report again to test if its working as expected.