Leaderboard

I Had same issue , I was getting assembly reference issue if try to access reports, I followed below steps and got it fixed. Yes I had bakup pf all my custom reports so that was not an issue for me. 1. Uninstalling the ConfigMgr 2012 Reporting Services Role: 1.a Open the ConfigMgr 2012 Console 1.b Navigate to Administration \ Site Configuration \ Servers and Site System Roles 1.c In the Servers and Site System Roles window on the right side of the screen locate the Server you need to remove the role from and select it 1.d In the lower pane of the window (Site System Roles) scroll down until you see Reporting Services Point 1.e Right click the Reporting Services Point, select Remove Role 1.f In the confirmation window, click Yes 1.g Close or minimize the ConfigMgr 2012 Console 2. Uninstall the SQL Reporting Services: 2.a On Server with the SQL Reporting Services open the Control Panel 2.b Navigate to Programs and Features (Add \ Remove Programs) 2.c In the Uninstall or Change a Program list select Microsoft SQL Server 2012 (64-bit) 2.d Click the Uninstall\Change option at the top of the list 2.e On the SQL Server 2012 Dialog, click Remove 2.f On the Setup Support Rules Dialog, click OK 2.g On the Select Instance Dialog, assure the correct instance is select and click Next 2.h On the Select Features Dialog, place a check mark next to Reporting Services – Native and click Next 2.i On the Removal Rules Dialog, click Next 2.j On the Ready to Remove Dialog, click Remove 2.k On the Complete Dialog, click Close 2.l Perform a reboot 3. Clean up the SQL Reporting Service DBs: 3.a Open the SQL Server Management Studio 3.b On the Connect to Server Dialog, verify connection settings and click Connect 3.c Expand the Databases 3.d If the ReportServer and ReportServerTempDB are still present perform the following, if not close the SQL Server Management Studio and move to step 3.j 3.e Select the ReportServer DB, right click and select Tasks and then Detach 3.f On the Detach Database Dialog, select the Drop check box and then click OK 3.g Select the ReportServerTempDB, right click and select Tasks and then Detach 3.h On the Detach Database Dialog, select the Drop check box and then click OK 3.i Close the SQL Server Management Studio 3.j Open File Explorer and navigate to the folder where you stored the ReportServer and ReportServerTempDB database files and the log files 3.k Delete the actual ReportServer and ReportServerTempDB files and log files 4. Re-Install the SQL Reporting Services: 4.a On Server that you just removed the SQL Reporting Services from open the Control Panel 4.b Navigate to Programs and Features (Add \ Remove Programs) 4.c In the Uninstall or Change a Program list select Microsoft SQL Server 2012 (64-bit) 4.d Click the Uninstall\Change option at the top of the list 4.e On the SQL Server 2012 Dialog, click Add 4.f On the Browse for SQL Server 2012 installation media, locate and select the location of the install media, then click OK 4.g On the Setup Support Rules Dialog, click OK 4.h On the Product Updates Dialog, click Next 4.i On the Setup Support Rules, click Next 4.j On the Installation Type Dialog, select Add features to an existing instance of SQL Server 2012, click Next 4.k On the Feature Selection Dialog, check the Reporting Services – Native, click Next 4.l On the Installation Rules Dialog, click Next 4.m On the Disk Space Requirements Dialog, click Next 4.o On the Server Configuration Dialog, click Next 4.p On the Reporting Services Configuration Dialog select the Install Only radio button, click Next 4.q On the Error Reporting Dialog, click Next 4.r On the Installation Configuration Rules Dialog, click Next 4.s On the Ready to Install Dialog, click Install 4.t On the Complete Dialog, click Close 5. Configure the SQL Reporting Services: 5.a On Server you just re-installed the SQL Reporting Services on open Reporting Services Configuration Connection 5.b On the Reporting Services Configuration Connection, click Connect 5.c Select the Web Service URL, click Apply 5.d Select the Database, click Change Database button 5.e Select Create a new report server database, click Next 5.fClick the Test Connection button, click Next if successful 5.g Click the Next button 5.h Click the Next button 5.i Click the Next button 5.j Click the Finish button 5.k Select the Report Manager URL, click Apply 5.l Click Exit 6. Re-install the ConfigMgr 2012 Reporting Services Role: 6.a Open the ConfigMgr 2012 Console 6.b Navigate to Administration \ Site Configuration \ Servers and Site System Roles 6.c In the Servers and Site System Roles window on the right side of the screen locate the Site Server you removed the Reporting Point Role from and select it 6.d Right click the Server and select Add Site System Roles 6.e On the General Dialog, click Next 6.f On the Proxy Dialog, click Next 6.g On the System Role Selection, place a check next to Reporting Services Point, click Next 6.h On the Add Site System Roles Wizard, click Verify 6.i On the Add Site System Roles Wizard, click Set by User Name, select Existing Account 6.j On the Select Account Dialog, select the account, click OK 6.k On the Add Site System Roles Wizard, click Next 6.l On the completion Dialog, click Close 6.m Wait for roughly 5 minutes 6.n Navigate in the ConfigMgr 2012 Console to Monitoring \ Reporting 6.o Click the Links located in the right pane to assure they work 6.p Navigate in the ConfigMgr 2012 Console to Monitoring \ Reporting \ Reports and verify they are present

What your propose, make sense to do.

What version of ADK & MDT are people using with this ? I can see ADK v1703 looks suitable, but what about the MDT ? MDT v8443 is the newest which came out in November 2016 but it was aligned with Windows 10 1607 and ConfigMgr 1606... Shouldn't we get a new MDT ? Anyone know if there's compatibility issues with the latest ADK+SCCM+MDT version 8443 ? -Rumpole

Up and running again! Thanks to anyweb (and Microsoft) we are now running 1702 and so far everything looks good!

update ! Microsoft's product team knows the issue, and is preparing a mitigation.