Solved

Win2003 SP3, Sql Server 2005 SP2 trying to patch to SP3 with a Report Writer failure.

Posted on 2013-05-13
3
1,002 Views
Last Modified: 2013-05-19
Hello all,

I have a Windows 2003 32-bit SP3 server with SQL Server 2005 Standard SP2.  I am trying to upgrade to SQL Server 2005 SP3.  

When trying to run SQLServer 2005SP3-KB955706-x86-ENU.exe it fails on Reporting Services authentication test...while Database Services authentication is successful.

"Account Information Verification
Your account information could not be verified. ...For setup to verify your credentials the services must be startable, connectable, and you must be a SQL Server administrator"

OK, ok..now I know you're thinking "DUH!"  ..but please bear with me...

I am a hardware/OS person.  My dba 'says' that the local administrator has the rights...to what? Don't as me!

The SQL services are running under the domain\administrator.  The install will let me choose between the local\administrator or an SQL account.  The Database Services authenticate via the local\administrator account.  The Report Writer fails authentication on the local\administrator account as well as the sa account.

The Report Writer (as far as I know..has not been utilized at all)...

Mgmt will not allow for me to uninstall the Report Writer because it may be used in the future.

If the solution is within the SQL... please please please be detailed because I am a hardware/OS person who is going to have to speak SQL DBA to a DBA...

HELP!
0
Comment
Question by:sloverr
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 30

Expert Comment

by:Mike Lazarus
ID: 39165587
0
 
LVL 30

Accepted Solution

by:
Mike Lazarus earned 455 total points
ID: 39165600
Failing that, use a local server admin account and grant that account/group sysadmin access temporary in order to do the service pack.
0
 

Author Closing Comment

by:sloverr
ID: 39178358
Someone had keyed in an incorrect Report Server name.  Fixing that, and changing the service account fixed the issue.  Thanks for pointing me in the right direction, GL.
0

Featured Post

SharePoint Admin?

Enable Your Employees To Focus On The Core With Intuitive Onscreen Guidance That is With You At The Moment of Need.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Never store passwords in plain text or just their hash: it seems a no-brainier, but there are still plenty of people doing that. I present the why and how on this subject, offering my own real life solution that you can implement right away, bringin…
When table data gets too large to manage or queries take too long to execute the solution is often to buy bigger hardware or assign more CPUs and memory resources to the machine to solve the problem. However, the best, cheapest and most effective so…
Via a live example, show how to backup a database, simulate a failure backup the tail of the database transaction log and perform the restore.
Via a live example, show how to set up a backup for SQL Server using a Maintenance Plan and how to schedule the job into SQL Server Agent.

738 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question