Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

SQL Server 2008 R2 reporting services - ERROR 1935

Posted on 2012-03-21
5
Medium Priority
?
1,169 Views
Last Modified: 2012-06-08
I keep getting the following error while installing reporting services:

Error 1935. An error occurred during the installation of assembly
'Microsoft.VC90.ATL,version="9.0.21022.8",publicKeyToken="1fc8b3b9a1e18e3b",
processorArchitecture="x86",type="win32". Please refer to Help and Support
for more information. HRESULT: 0x8007054F.

Any thoughts?
0
Comment
Question by:jmvega00
[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
  • 3
  • 2
5 Comments
 
LVL 25

Accepted Solution

by:
TempDBA earned 1500 total points
ID: 37748490
Here is a kb article that explains the problem and fix:-
http://support.microsoft.com/kb/970652
0
 

Author Comment

by:jmvega00
ID: 37748616
That KB refers to a fix for vista based computers. I'm on a Server 2008 R2 system. That kb also refers to "error code 0x80000FFF". My code is HRESULT: 0x8007054F.

Of the registry entries it tries to fix, my system only has one listed in components. I'll try to take it out and try again...however, I don't think this applies to me 100%.
0
 

Author Comment

by:jmvega00
ID: 37749640
Not sure if that helped or if all the other things I did help also. The only key i found in there was:
•HKEY_LOCAL_MACHINE\COMPONENTS\PendingXmlIdentifier

So I deleted it. I also uninstalled any sql components I felt did not need to be in there. I also ran the following command after the uninstall:
fsutil resource setautoreset true c:\
then rebooted and re-ran the sql installer in admin mode (which I have been doing)

This time it worked. I could have been the key; it may have been the uninstall or the cmd command. who knows, but it worked.

Since you are the only person that answered, I'll award you the points. Thank you.
0
 

Author Closing Comment

by:jmvega00
ID: 37749647
Not sure if it fully fixed my issue considering it the kb refrenced applies to a vista machine. None the less, I included this in my host of possible solutions and now I was able to install error free.
0
 
LVL 25

Expert Comment

by:TempDBA
ID: 37750979
Thanks for sharing the steps toward solving the issue.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

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

You might have come across a situation when you have Exchange 2013 server in two different sites (Production and DR). After adding the Database copy in ECP console it displays Database copy status unknown for the DR exchange server. Issue is strange…
A procedure for exporting installed hotfix details of remote computers using powershell
This tutorial will show how to push an installation of Backup Exec to an additional server in both 2012 and 2014 versions of the software. Click on the Backup Exec button in the upper left corner. From here, select Installation and Licensing, then I…
This tutorial will give a an overview on how to deploy remote agents in Backup Exec 2012 to new servers. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as connecting to a remote Back…

705 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