none
Can't access Project Server Queue Page RRS feed

  • Question

  • Enviroment:

    server 2008

    Project server 2007

     

    When I follow the Manage Queue button I just get an error page with the following message:

    Object reference not set to an instance of an object.   at Microsoft.Office.Project.PWA.ApplicationPages.QueueStatusPage.GetBetaValues(JobState[]& SelectedJobStates, QueueMsgType[]& SelectedJobTypes, Guid[]& SelectedProjects)
       at Microsoft.Office.Project.PWA.ApplicationPages.QueueStatusPage.CreateDataSet(XmlGrid JobsGrid)
       at Microsoft.Office.Project.PWA.ApplicationPages.QueueStatusPage.OnLoadComplete(EventArgs e)
       at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

     

    It appears several Projects are stuck in the queue but there is no way for me to do anything about it.  Any help will be appreciated.

    Monday, May 16, 2011 6:16 PM

Answers

All replies

  • How about restarting the Project Server Queue Service from the Server?
    Prasanna Adavi, PMP, MCTS Blog: http://thinkepm.blogspot.com
    Monday, May 16, 2011 7:06 PM
    Moderator
  • Just tried, still can't access the queue page.  I have about 4 projects that are on the server but are not appearing in the project center grid.
    Monday, May 16, 2011 7:40 PM
  • Please try restarting the IIS or boot the servers.

    Thanks,
    Amit Khare 

    Tuesday, May 17, 2011 9:26 AM
  • I did a full reboot of the server, no change.

     

    Thanks both of you for the advice so far.  This problem is rather vexing. 

    Tuesday, May 17, 2011 1:51 PM
  • I think I've seen a similar issue when a query was blocked in SQL.
     
     

    Andrew Lavinsky [MVP] Blog: http://azlav.umtblog.com Twitter: @alavinsky
    Tuesday, May 17, 2011 3:24 PM
    Moderator
  • I will poke around and see if I can find anything.

    It looks like the problem is on the SQL side.  I am getting two errors when I attempt to navigate to the queue page in even viewer.

     

     

    Techinal Details:

    System.Data.SqlClient.SqlException: SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x699c6280; actual: 0x619c6280). It occurred during a read of page (1:707) in database ID 8 at offset 0x00000000586000 in file 'c:\Program Files (x86)\Microsoft Office Servers\12.0\Data\MSSQL.3\MSSQL\DATA\PWA_Archive_12101839_DF03_4BBC_AB22_F7E61B5EC47E.mdf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.

       at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)

       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)

       at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)

       at System.Data.SqlClient.SqlDataReader.HasMoreRows()

       at System.Data.SqlClient.SqlDataReader.ReadInternal(Boolean setTimeout)

       at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal.InitializeColumnTypeData(Dictionary`2& columnTypeMapping)

       at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal..ctor(DAL dal, DataStoreEnum store)

       at Microsoft.Office.Project.Server.DataAccessLayer.DAL.StoreDal..ctor(DAL dal, DataStoreEnum store)

       at Microsoft.Office.Project.Server.DataAccessLayer.DAL.get_Versions()

       at Microsoft.Office.Project.Server.BusinessLayer.Project.ReadProjectList()

       at Microsoft.Office.Project.Server.WebService.Project.ReadProjectList()

     

     

    And

     

    SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x699c6280; actual: 0x619c6280). It occurred during a read of page (1:707) in database ID 8 at offset 0x00000000586000 in file 'c:\Program Files (x86)\Microsoft Office Servers\12.0\Data\MSSQL.3\MSSQL\DATA\PWA_Archive_12101839_DF03_4BBC_AB22_F7E61B5EC47E.mdf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.

     

    I am currently running DBCC CHECKDB to see if that is the problem.

    Tuesday, May 17, 2011 3:33 PM
  • When I run DBCC CHECKDB on the Archive DB I get 

    Msg 8921, Level 16, State 1, Line 1

    Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.

    Msg 824, Level 24, State 2, Line 1

    SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x699c6280; actual: 0x619c6280). It occurred during a read of page (1:707) in database ID 10 at offset 0x00000000586000 in file 'c:\Program Files (x86)\Microsoft Office Servers\12.0\Data\MSSQL.3\MSSQL\DATA\PWA_Archive_12101839_DF03_4BBC_AB22_F7E61B5EC47E.mdf:MSSQL_DBCC10'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.

    Tuesday, May 17, 2011 6:00 PM
  • You might want to open a case with Microsoft for this, if Andrew's suggestion doesn't work.
    Gary Chefetz, MCITP, MCP, MVP msProjectExperts
    Project and Project ServerFAQs
    Project Server Help BLOG
    Wednesday, May 18, 2011 1:50 PM
    Moderator
  • No oy yet, I have submitted the problem with the SQL error over on the SQL boards to see if they can help resolve that.  If that doesn't work then I will open a case.

     

    Thanks for the help guys.

    Wednesday, May 18, 2011 5:55 PM