Search This Blog

Loading...

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.

Tuesday, April 12, 2016

The version of the report server database is either in a format that is not valid, or it cannot be read

If you choose to do an in place upgrade of SQL 2012 to SQL 2014, you might see this error when trying to access the report server:

The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is '163'. The expected version is '162'. (rsInvalidReportServerDatabase).

image

As part of a hotfix for SQL 2012 SP2 CU5, a change was made which resulted in a new ReportServer database version. Since this fix was made after the SQL2014 release, if your SQL2012 SP2 server is on CU5 or later, then it will have a higher database version than what SQL2014 RTM expects.

SQL 2014 SP1 has the same problem.

So if you see this problem upgrade to the latest CU level for SQL 2014 RTM or SQL 2014 SP1, and the problem will be fixed.

http://blogs.msdn.com/b/sql_server_team/archive/2015/03/20/upgrading-to-sql-2014-report-server-version-mismatch.aspx

While having this problem your SCCM console will just not display any reports (blank – no items found), so you will have to go to the  report server homepage URL to verify if this is your problem (as shown in the top):

image

Monday, April 4, 2016

Exchange 2013 and 2016 Schema versions

After an Exchange 2016/2013 installation and Active Directory schema change, several properties are updated to show that everything are as expected.

You can use the information in the following to make sure these properties have the right values.

Exchange Version

msExchProductId

rangeUpper

objectVersion (Microsoft Exchange System Objects)

objectVersion (Organization container)

Exchange 2013 RTM

15.00.0516.032

15137

13236

15449

Exchange 2013 CU1

15.00.0620.029

15254

13236

15614

Exchange 2013 CU2

15.00.0712.024

15281

13236

15688

Exchange 2013 CU3

15.00.0775.038

15283

13236

15763

Exchange 2013 SP1

15.00.0847.032

15292

13236

15844

Exchange 2013 CU5

15.00.0913.022

15300

13236

15870

Exchange 2013 CU6

15.00.0995.029

15303

13236

15965

Exchange 2013 CU7

15.00.1044.025

15312

13236

15965

Exchange 2013 CU8

15.00.1076.009

15312

13236

15965

Exchange 2013 CU9

15.00.1104.005

15312

13236

15965

Exchange 2013 CU10

15.00.1130.007

15312

13236

16130

Exchange 2013 CU11

15.00.1156.006

15312

13236

16130

Exchange 2016 Preview

15.01.0225.017

15317

13236

16041

Exchange 2016

15.01.0225.042

15317

13236

16210

Use an elevated powershell console to get the your values:

rangeUpper

Get-ADObject -Identity "CN=ms-Exch-Schema-Version-Pt,CN=schema,CN=configuration,DC=YourDomain,DC=YourDomainSuffix" -properties rangeUpper | select rangeUpper | format-List

image

msExchProductId

Get-ADObject -Identity "CN=YourExchangeOrganisation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=YourDomain,DC=YourDomainSuffix" -properties msExchProductId | select msExchProductId | Format-List

image

objectVersion (attribute on Organization container in Configuration Naming Context)

Get-ADObject -Identity "CN=YourExchangeOrganisation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=YourDomain,DC=YourDomainSuffix" -properties objectVersion | select objectVersion | Format-List

image

objectVersion (attribute on Microsoft Exchange System Objects container in Domain Naming Context)

Get-ADObject -Identity "CN=Microsoft Exchange System Objects,DC=YourDomain,DC=YourDomainSuffix" -properties objectVersion | select objectVersion | Format-List

image

Unsure about your Exchange Organization name?

Use the Exchange management Shell:

get-organizationconfig | select name,DistinguishedName | Format-list

image

For older versions and use of adsiedit.msc see http://larslohmann.blogspot.dk/2012/07/exchange-schema-version.html