Connecting to SQL 2005 from a client pc

I am getting this message. On the actual server I can pull up the report builder, but from a client on the network when trying to connect to the sql report builder I get this message:

PLATFORM VERSION INFO
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)

SOURCES
Deployment url : http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application

ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application resulted in exception. Following failure messages were detected:
+ Downloading http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application did not succeed.
+ The remote server returned an error: (401) Unauthorized.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [3/16/2006 10:10:28 AM] : Activation of http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application has started.

ERROR DETAILS
Following errors were detected during this operation.
* [3/16/2006 10:10:28 AM] System.Deployment.Application.DeploymentDownloadException (Unknown subtype)
- Downloading http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application 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 ---
System.Net.WebException
- The remote server returned an error: (401) Unauthorized.
- Source: System
- Stack trace:
at System.Net.HttpWebRequest.GetResponse()
at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

Remote connections is enabled and I am connecting as the servers admin. Any suggestions. I think it might be a user thing, but I am not sure. Do I need to add a user to the report builder folder in iss or what.

Thank you for any suggestions



Answer this question

Connecting to SQL 2005 from a client pc

  • Sunny_Lang

    Couple of things about Report Builder -

    1) Report Builder requires the .net framework 2.0 to be installed on the client machine. I think that's the problem you're encountering related to to the .application file.

    2) Report Builder requires a direct connection back to the report server in order to work. That means that you have to expose your report server on the extranet. This has security implications for your deployement - when report server is available on the extranet, so are all the other reports that are on that report server. Also, the report server SOAP API is available on the internet - so application authors can try to have programmatic access to your report server.

    When pursuing this type of deployment you should evaluate your security story for your corporate data. Often what is sufficient is to provide the actual report output to the user through the use of a ReportViewer control in an ASP.Net application - this reduces the amount of data that is accessible from outside your company's firewall.

    Hope that helps,

    -Lukasz



  • bri5

    I have the same problem except Reporting Services is running in SharePoint integration mode, setting anonymous access on the report builder directory doesn't help.

    Any ideas how to fix this problem when running Reporting Services in integrated mode

  • Mickey G

    Have you had any luck with your issue I am having a similar issue and have posted about it, but so far, no response.

    ANY info you might have would be appreciated, thanks!


  • ClydeL

    I think your issue is different than that of the others on this thread. You can get started with security in reporting services here:

    http://msdn2.microsoft.com/en-us/library/ms156014.aspx

    -Lukasz



  • Sam Roth

    We are trying to get the report builder to be accessed from the url and at the time we can, due to the fact that we are allowing the users to access it using the administrator login. At the moment it is not asking for credentials, but we are wanting to add users and allow them access through the users credentials, not the administrators. We are also wanting to allow users to access reports on the server through their credentials and allow certain users access to certain folders on the server. Could you walk us through adding a user and allowing the user access to certain folders on the server and finally the report builder
  • wobblemonster

    Hi Lukasz,
    I have the same issue, however I am trying to execute the report builder from the server itself. If I login as the domain administrator then it works. If I log in as any one else (even users that are part of the Administrators and Domain Admin accounts) then it fails with this error.


    Thoughts



  • Gili

    Have you had any luck with this problem. If so please inform me on your solutions.
  • whs45

    Hi Lukasz,

    What do you mean with 'report builder requires a direct connection back to the report server We are trying to use Report Builder on the internet, but our site is secured using ISA. When we try to launch Report Builder, we get an error 'Cannot retrieve application. Authentication error (401: unauthorised)'.

    Also our site is using certificates, so when trying to start Report Builder, we have to adjust the link to the reportbuilder.application to httpS.

    Any idea's

    ** Bianca


  • StephenCraig

    Have you had any luck with this issue If so, please let me know what you did to figure it out.


  • swo

    I had this same problem and found a good solution here.


  • Siebe Tolsma

    Are your users in the same domain or a trusted domain as your report server Do you use forms authentication for your report server

    -Lukasz



  • Mr_D

    I'm having the same problem, seams like reportbuilder can't connect to host when you try to use it in an EXTRANET, because if you try it in an INTRANET works perfectly.

    I hope someone could help us on this matter. (ASAP)



  • aquatic

    Yes, they can see the button.

    When they click on the Report Builder button a dialog pops up saying that it is Launching Application.

    This is quickly replaced by a dialog titled "Cannot start application" which says:
    "Cannot retrieve application. Authentication error."

    When I click on the details button then I can see the error "The remote server returned an error: (401) Unauthorized."


  • noorafridi

    Your users, are they able to see the report builder button in report manager

    What is the exact error they get when they try to launch report builder

    -Lukasz



  • Connecting to SQL 2005 from a client pc