Ah, I see. Well if setspn said it updated the object in AD when you ran the command I would not worry too much about entries in the SQL log;...

I had hoped to have a series of configuration files for unattended installs (e.g. base 2014 RTM install, slipstream install of service packs and cumulative updates, and patch of service...

Try doing it without the configuration file. Something like:

<SQLServer2014SP1> /IACCEPTSQLSERVERLICENCETERMS=True /ACTION=PATCH /QS /ALLINSTANCES

Where <SQLServer2014SP1> is the SQL Server 2014 service pack.

Just so I am clear: are you trying to patch...

This is not the command you are trying to run to register the SPN is...

It could be a problem with your configuration file. For going from SQL Server 2014 RTM to SP1 the ACTION should be PATCH. You have UPGRADE. That is for upgrading...

On your Test SSRS instance what database instance did you specify in Reporting Services Configuration Manager? It sounds like you specified the default db instance instead of the Test db...

I think Phil Parkin already provided the easiest answer.

Different Options for Query Results in SQL Server Management Studio[/url]

Since you are getting a lot of blank rows it seems like results are present but not being displayed. If I had to guess it is because there are logic...

Hi there,

The database server is rebooting at various times automatically after a windows update. Our admin people are telling me this is ok and that sql is doing a clean...

What happens when you go through the RS Configuration Manager and try re-setting up the connection to the RS databases (choosing an existing database)?

Two things to note about this:

- Has the connection string the application uses to connect to the database changed to support mirroring? If not the application will not automatically redirect...

I think the witness has to...

Just to be clear: are the SSRS server and the Database Server hosting the ReportServer databases on the same machine? If not I would verify connectivity to the instance hosting...

First I would check the Application log to see if it has any entries of value as to why SQL Server would not start. If that does not lead to...

Note though that with Database Mirroring of you want automatic failover you need a third SQL Server to act as a witness.