Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2008 Forums
 Analysis Server and Reporting Services (2008)
 Why No URL Access At All???!

Author  Topic 

mikebird
Aged Yak Warrior

529 Posts

Posted - 2009-09-30 : 09:09:29
What's wrong when the Web Service and Report Manager URLs don't work? They are exactly the same.

The setup is shown as automatically http://user/ReportServername_db_name

http://homeuser/ReportServer_AUG2009

Simply trying http://HOMEUSER/reports fails to work, or
http://HOMEUSER/Reports/Pages/Folder.aspx

All addresses fail

The SSRS service is running fine, checked in both SQL Server Configuration and in Reporting Services Configuration. Service started

Server: HOMEUSER\AUG2009
DB: ReportServer
InstanceID: MSRS10.AUG2009

My version is Developer Edition, 2008

When I look at the rsreportservices.config file for my instance, the <URL root> tab is completely empty, where the name for the address should be. I had an Enterprise demo instance working for a while. Perhaps this has clouded the SSRS auto setup? How can I get a working address in there?


I think maybe I don't have a component for providing the local web service? It's all on the local machine, by the way... What's the service I need? I've looked through all of 'em. I made sure I got Windows XP Pro with that

Latest response to URL failure is thus:


Server Error in '/ReportServer_AUG2009' Application.

Provider type not defined. (0x80090017)

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Runtime.InteropServices.COMException: Provider type not defined. (0x80090017)

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[COMException (0x80090017): Provider type not defined. (0x80090017)]
System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) +0
System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) +43
System.Reflection.Assembly.InternalGetSatelliteAssembly(CultureInfo culture, Version version, Boolean throwOnFileNotFound) +215
System.Resources.ResourceManager.GetSatelliteAssembly(CultureInfo lookForCulture) +79
System.Resources.ResourceManager.InternalGetResourceSet(CultureInfo culture, Boolean createIfNotExists, Boolean tryParents) +299
System.Resources.ResourceManager.GetString(String name, CultureInfo culture) +74
Microsoft.ReportingServices.Diagnostics.Utilities.Keys.GetString(String key) +21
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException..ctor(Exception innerException, String additionalTraceMessage) +23
Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.WriteErrorResponse(Int32 code, String shortHttpDescription, Exception exception, Boolean errorResponseAsXml) +67
Microsoft.ReportingServices.WebServer.Global.WriteServerError(Exception e) +44
Microsoft.ReportingServices.WebServer.Global.Application_AuthenticateRequest(Object sender, EventArgs e) +187
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +68
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75

Version Information: Microsoft .NET Framework Version:2.0.50727.3082; ASP.NET Version:2.0.50727.3082
   

- Advertisement -