We recently did a site-recovery to Windows Server 2012 as we had to move off of Windows Server 2008. So the infrastructure is functioning well, but the SRS is not getting installed as a role properly.  Maybe I should set up our process and explain where we are with it in case any of this makes a difference.

Started with a Primary, a SQL server (and SRS), and a DP (with an MP).  These were all on Windows Server 2008 R2.  There are other roles, but these are the ones that might make the difference.

We built 3 new Windows Server 2012 R2 Standard servers.  The process was to backup with SCCM backup, shut down Primary and SQL servers (moved reporting DB first to new server), rename 2 of the new servers to OLD primary and SQL server names, and run site recovery.  This left our DP\MP alone, but we just moved the roles to the 3rd server rather than rename and go through that process.

So now we have all servers on 2012, and all roles are functioning properly.  When I try to add the SRS, I get an "Error" when trying to verify the database.  I am not sure where to even look for logs.  I can't seem to find any entry in a Primary server log showing the attempted connection, and nothing appears to be on the SQL server yet.  Where should I be looking for more information?

Also, I can get to the link from a workstation, but once I click on a report I get an error.  Of course I don't have that error handy because this computer is located in a different country and the local contacts have revoked my permissions.  Trying to get that back but wanted to get a question out to troubleshoot from the server if possible. 

I can open a ticket with Microsoft, but would prefer figure it out myself.  I will have to do this again in another site and want to understand how it works.  Any help is appreciated.

Thanks!

Hi,

>>When I try to add the SRS, I get an "Error" when trying to verify the database. 

Do you mean that you got error when adding a reporting service point? What is the error?

>> I can't seem to find any entry in a Primary server log showing the attempted connection

What is the log you checked?

We were able to figure this out.  The error showing was just that...."Error".  So that wasn't helpful.  However if we hovered over the ! (exclamation point) we saw a named pipes error.  We had to put the port for the SQL box that we are using after the name of the server.  We didn't have to do that in the past, so I don't know if it is a change somewhere on our end that I wasn't made aware of, or if Windows Server 2012 or SQL 2014 causes this.  In any case, it is working now

• Marked as answer by brishr 20 hours 21 minutes ago