Report Builder error -> Application installation did not succeed on SQL 2005 Reporting Services

Hi all,

First off, I am just getting exposed to SQL 2005 Reporting Services, so this is all new to me.  I am doing server administration for a group and they use this tool.  They are having what appears to be some permissions problems with it, so I was asked to install the necessary tools and try to test out the Report Builder.  When I installed the tools in SQL Enterprise 2005 and rebooted, I still can't run the Report builder.  When i click on the link, this is the message I get in a pop-up:

Title: Cannot Start Application
Message: Application installation did not succeed.  Cannot locate application files on the server.  Contact the application vendor or your administrator for assistance.

Here is the detailed message:

      Windows                   : 5.1.2600.131072 (Win32NT)
      Common Language Runtime       : 2.0.50727.42
      System.Deployment.dll             : 2.0.50727.42 (RTM.050727-4200)
      mscorwks.dll                   : 2.0.50727.42 (RTM.050727-4200)
      dfdll.dll                   : 2.0.50727.42 (RTM.050727-4200)
      dfshim.dll                   : 2.0.50727.42 (RTM.050727-4200)

      Deployment url                  :

      Below is a summary of the errors, details of these errors are listed later in the log.
      * Activation of resulted in exception. Following failure messages were detected:
            + Downloading did not succeed.
            + The remote server returned an error: (403) Forbidden.

      No transaction error was detected.

      There were no warnings during this operation.

      * [4/6/2006 9:09:00 AM] : Activation of has started.

      Following errors were detected during this operation.
      * [4/6/2006 9:09:00 AM] System.Deployment.Application.DeploymentDownloadException (Unknown subtype)
            - Downloading did not succeed.
            - Source: System.Deployment
            - Stack trace:
                  at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
                  at System.Deployment.Application.SystemNetDownloader.DownloadAllFiles()
                  at System.Deployment.Application.FileDownloader.Download(SubscriptionState subState)
                  at System.Deployment.Application.DownloadManager.DownloadManifestAsRawFile(Uri& sourceUri, String targetPath, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
                  at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirectBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
                  at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options)
                  at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut)
                  at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
            --- Inner Exception ---
            - The remote server returned an error: (403) Forbidden.
            - Source: System
            - Stack trace:
                  at System.Net.HttpWebRequest.GetResponse()
                  at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)

      No transaction information is available.

Any help you can offer would be greatly appreciated!

LVL 13
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

masterbakerAuthor Commented:
Ok, so I got this working.  Using the fully qualified domain name for the server did not work.  However, when I just used the short name (http://qa-reports/.....) it worked.  So it was just an access problem as the FQDN did not allow Windows authentication to work properly.  Oh well!  I'm just glad it works.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.