MSDN > 論壇首頁 > Microsoft Visual Studio Team Foundation Server 2010 Beta 2 > TFS Default Configuration Wizard - [ Reporting ] TF255275
發問發問
 

已答覆TFS Default Configuration Wizard - [ Reporting ] TF255275

  • Saturday, 23 May, 2009 15:44Larouex BB King Jordan 使用者勳章使用者勳章使用者勳章使用者勳章使用者勳章
     
    I am trying to get the last configuration details in running the TFS Default Configuration Wizard.

    I am getting this error...

    [ Reporting ] TF255275: The following Web service for SQL Server Reporting Services could not be accessed: http://dads-r2-vs10/ReportServer/ReportService2005.asmx

    I have tested that I can access this URL from IE and that IE-ES is off and intranet settings are enabled.

    I am installing on WS2K8-R2 (Build 7100) and I have SQL Server 2008 SP1 installed.

    Here are my results...

    Error [ Reporting ] TF255275: The following Web service for SQL Server Reporting Services could not be accessed: http://dads-r2-vs10/ReportServer/ReportService2005.asmx.

    Warning [ Project Collection ] TF255331: The existence of the following folder on the report server could not be verified: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing.. A network problem might have prevented communication, the report server might be offline, or your account might not have permissions on the report server. The team project collection could not be created. To complete this wizard, you must specify the option not to create a collection. As an alternative, you can close this wizard, correct the problem, and then restart the wizard.

    I don't see the "following folder on the report server could not be verified" as indicated in error.

    Larouex BB King Jordan

解答

  • Monday, 25 May, 2009 10:09MartinHock 使用者勳章使用者勳章使用者勳章使用者勳章使用者勳章
     已答覆
    Hi Larouex ,

    I had the same problem. Though with custom configuration
    The cause is a Problem with the Reporting Service configuration.

    I was able to solve it as follows :

    1. try too create a new Reporting database from Reporting Services configuration Manager.

    2. If you get an error there search for Repo*.mdf and Repo*.ldf

    3. Delete those

    4. Create new Database

    5. Rerun TFS COnfiguration wizard

    HTH


    Martin

所有回覆

  • Monday, 25 May, 2009 10:09MartinHock 使用者勳章使用者勳章使用者勳章使用者勳章使用者勳章
     已答覆
    Hi Larouex ,

    I had the same problem. Though with custom configuration
    The cause is a Problem with the Reporting Service configuration.

    I was able to solve it as follows :

    1. try too create a new Reporting database from Reporting Services configuration Manager.

    2. If you get an error there search for Repo*.mdf and Repo*.ldf

    3. Delete those

    4. Create new Database

    5. Rerun TFS COnfiguration wizard

    HTH


    Martin
  • Monday, 25 May, 2009 16:53Larouex BB King Jordan 使用者勳章使用者勳章使用者勳章使用者勳章使用者勳章
     

    Thanks Martin,

    I took the steps...


    Delete ReportServer Database
    Delete ReportServerTemp Database
    Re-Run Report Server Configuration Wizard and create new databases (noticed that the server name in the configuration was auto-generated and not accurate)
    Re-Run the TFS Configuraiton Wizard


    SUCCESS!!! Thanks for the help

    MS: The BPA for the TFS Configuration wizard would have led me to this right away if the Server name was in the results, I woudl have seen the anomoly.


    Larouex BB King Jordan
  • Tuesday, 26 May, 2009 13:11Jason BarileMSFT, 版主使用者勳章使用者勳章使用者勳章使用者勳章使用者勳章
     提議的解答

    Glad to hear this fixed your problem.  One difference from TFS 2008 is that we no longer will configure Reporting Services for you.  That was a big source of failures, so rather than trying to do it automatically and not getting it right, we allow you to do it yourself and verify RS is working before configuring TFS.

  • Thursday, 11 June, 2009 15:33Ahmad Sheibani 使用者勳章使用者勳章使用者勳章使用者勳章使用者勳章
     
    Hello Jason,

    i ran into the same problem (tf255275) during the custom configuration of TFS. i can access the reporting services url in IE http://sharepoint/reportserver/reportservice2005.asmx. i did delete the report server databases after stoping the service and created a new database integrated with sharepoint.

    P.S: i have installed MOSS 2007 and TFS 2010 on the same machine

    hope you can help me solve this problem

    Cheers
    Ahmad
  • Sunday, 14 June, 2009 2:33SergioE 使用者勳章使用者勳章使用者勳章使用者勳章使用者勳章
     提議的解答
    Error [ Reporting ] TF255275: The following Web service for SQL Server Reporting Services could not be accessed: http://dads-r2-vs10/ReportServer/ReportService2005.asmx.
    Warning [ Project Collection ] TF255331: The existence of the following folder on the report server could not be verified: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing.. A network problem might have prevented communication, the report server might be offline, or your account might not have permissions on the report server. The team project collection could not be created. To complete this wizard, you must specify the option not to create a collection. As an alternative, you can close this wizard, correct the problem, and then restart the wizard.
    Hi, I'm installing the TFS 2010 beta1 in a w2k8r2rc server and ?ve got the same troubles, I'm doing now the solution about deleting and recreating the reports database.

    My post is to tell all of you what I've discovered about the TF255331 warning (this post is the only place on all internet until today wicch has a mention to this key) 
    My discoverys are this:  Mi server was named  Y2k9r2serverRCen because: this year is 2009, it is a server, it is a  RC version and is in english :-D but the trouble with te TFS configurator is that it tryes to use http://Y2k9r2serverRCe/ReportServer/ReportService2005.asmx, but the server's name is Y2k9r2serverRCen. It's  only a char 'n' of difference!! but these do that the TFS configurator doesn't found the server and tells that is a remote machine...

    So, my solution was remove the last n in the server name (I've no time now to digg into the TFS config files to add the 'n' in God know how many places...)
    The server is restarting now and I'll check if this error is solved, but meanwhile I put it here because I think it can be usefull to you.

    [Edited] Yes, the two problems was solved! The configurator les me apply the config now...!

    Best regards
    Sergio E.
    Cancún, Q. Roo, MX
    • 已提議為解答SergioE Sunday, 14 June, 2009 2:51
    •  
  • Monday, 15 June, 2009 14:25TheFrogman 使用者勳章使用者勳章使用者勳章使用者勳章使用者勳章
     

    Thanks a lot!!!
    Works perfect now.

    Thomas

  • Monday, 29 June, 2009 23:50MichaelDBang 使用者勳章使用者勳章使用者勳章使用者勳章使用者勳章
     
    Well I'm in the crapper on this one.  I'm trying to upgrade my 2008 instance, and I'm getting this error, even though I just installed a FRESH instance of SSRS. :(
  • Wednesday, 21 October, 2009 20:22David Cuccia 使用者勳章使用者勳章使用者勳章使用者勳章使用者勳章
     提議的解答
    This helped, thanks! It was actually this post that finally helped me solve the second half of my problem: I'd kept configuring the reporting server in "Sharepoint Integrated Mode". Needs to be in "Native Mode"!
  • Thursday, 22 October, 2009 17:48DaveK67 使用者勳章使用者勳章使用者勳章使用者勳章使用者勳章
     
    This helped, thanks! It was actually this post that finally helped me solve the second half of my problem: I'd kept configuring the reporting server in "Sharepoint Integrated Mode". Needs to be in "Native Mode"!

    I'd just like to add for other searchers that the Native Mode problem is also TF255331 but instead of saying that the report server cannot open a collection... it says that the response was html when it was expecting xml.
  • Friday, 6 November, 2009 18:50Jason BarileMSFT, 版主使用者勳章使用者勳章使用者勳章使用者勳章使用者勳章
     
    I just hit this again during some TFS 2010 testing. The solution for me was to make sure the Reporting Services service was actually running.  Sometimes after a reboot, it's not running and there are no errors in the event log to indicate why.