Ask a questionAsk a question
 

AnswerTfsVersionControl Hourly Job is failing after TFS 2010 Beta 2 Upgrade

  • Tuesday, October 27, 2009 11:20 PMJoe Koolipurackal Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hello,

    We upgraded from TFS 2008 SP1 to TFS 2010 Beta 2.  Since then, I'm noticing failure log messages in SQL Server:
    [298] SQLServer Error: 4060, Cannot open database "TfsVersionControl" requested by the login. The login failed. [SQLSTATE 42000]

    Apparently, SQL Server Agent is configured to run an hourly job "TfsVersionControl Hourly Job" that runs "EXEC prc_UpdateStatistics @modificationThreshold = 1000000".  It is apparently pointing to the TfsVersionControl database, which no longer exists after the 2010 Beta 2 upgrade (since everything's now in TFS_DefaultCollection).

    How can I resolve this?  Is this just an artifact of something not going perfectly with the TFS upgrade?  Should I disable the job, or should I point it to another database?

    Best regards,
    Joe

Answers

  • Wednesday, October 28, 2009 3:28 PMCraig Harry - Microsoft Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    We have moved away from using SQL Jobs and we execute all of our scheduled work using the TFS Job Agent. During upgrade we attempt to delete the 2005/2008 SQL jobs. There are a number of reasons they may fail from ownership to teh agent not running. There should have been a warning in the upgrade log that stated we couldnt remove them and you can remove them if you wish. Since we now execute these procedures and tasks ourselves please delete the jobs and the errors should go away.
    Craig

All Replies

  • Wednesday, October 28, 2009 3:28 PMCraig Harry - Microsoft Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    We have moved away from using SQL Jobs and we execute all of our scheduled work using the TFS Job Agent. During upgrade we attempt to delete the 2005/2008 SQL jobs. There are a number of reasons they may fail from ownership to teh agent not running. There should have been a warning in the upgrade log that stated we couldnt remove them and you can remove them if you wish. Since we now execute these procedures and tasks ourselves please delete the jobs and the errors should go away.
    Craig
  • Wednesday, October 28, 2009 8:15 PMChandru R - MSFTMSFTUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Joe - would it be possible to post the upgrade log which shows why the deletion failed, we are trying to gather more information on why the delete job failed.
    Chandru R - MSFT
  • Tuesday, November 03, 2009 5:51 PMJoe Koolipurackal Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Craig and Chandru, thanks for the response and assistance.

    I have disabled the job, so that should solve it for now.

    Chandru - regarding the log, I'll be happy to provide it to you.  I'm seeing two in "C:\Program Files\Microsoft Team Foundation Server 2010\Microsoft Team Foundation Server 2010 Beta 2 - ENU\Logs":
    dd_install_tfs_stdserver_100.txt / About 1/2 MB
    dd_VSMsiLog466D.txt / About 6 MB

    Are those the logs that could be useful to you?  Is there another log file somewhere that could help?  Let me know and I'll get them to you.

    Is there an email address I can send them to?

    Best regards,
    Joe