J
Johnny
We had a problem with our Project server database, in the middle of updating
timesheet, an error came up, "#50070: Unable to connect to the database
STS_servername_1_2064 on SERVERNAME. Check the database connection
information and make sure that the database server is running."
The SQL logs was showing,
2006-05-30 14:24:44.68 spid2 LogWriter: Operating system error 33(The
process cannot access the file because another process has locked a portion
of the file.) encountered.
2006-05-30 14:24:44.71 spid2 Write error during log flush. Shutting down
server
2006-05-30 14:24:44.71 spid2 LogWriter: Operating system error 33(The
process cannot access the file because another process has locked a portion
of the file.) encountered.
2006-05-30 14:24:44.71 spid2 Write error during log flush. Shutting down
server
2006-05-30 14:24:44.71 spid2 LogWriter: Operating system error 33(The
process cannot access the file because another process has locked a portion
of the file.) encountered.
2006-05-30 14:24:44.71 spid2 Write error during log flush. Shutting down
server
2006-05-30 14:24:44.73 spid10 Error: 9001, Severity: 21, State: 4
2006-05-30 14:24:44.73 spid10 The log for database 'ProjectServer' is not
available..
2006-05-30 14:24:44.73 spid51 Error: 9001, Severity: 21, State: 1
2006-05-30 14:24:44.73 spid51 The log for database 'ProjectServer' is not
available..
2006-05-30 14:24:44.89 spid51 Error: 9001, Severity: 21, State: 1
2006-05-30 14:24:44.89 spid51 The log for database 'ProjectServer' is not
available..
2006-05-30 14:24:44.90 spid51 Error: 3314, Severity: 21, State: 4
2006-05-30 14:24:44.90 spid51 Error while undoing logged operation in
database 'ProjectServer'. Error at log record ID (1250:466138:3)..
2006-05-30 14:24:44.92 spid51 Error: 9001, Severity: 21, State: 1
2006-05-30 14:24:44.92 spid51 The log for database 'ProjectServer' is not
available..
2006-05-30 14:24:44.92 spid51 Error: 3314, Severity: 21, State: 4
2006-05-30 14:24:44.92 spid51 Error while undoing logged operation in
database 'ProjectServer'. Error at log record ID (1250:466138:3)..
2006-05-30 14:24:44.92 spid51 Error: 9001, Severity: 21, State: 1
2006-05-30 14:24:44.92 spid51 The log for database 'ProjectServer' is not
available..
2006-05-30 14:24:44.92 spid51 Error: 3314, Severity: 21, State: 5
2006-05-30 14:24:44.92 spid51 Error while undoing logged operation in
database 'ProjectServer'. Error at log record ID (1250:464730:1)..
2006-05-30 14:24:46.06 spid19 Starting up database 'ProjectServer'.
2006-05-30 14:24:52.23 logon Login succeeded for user
'MSProjectServerUser'. Connection: Non-Trusted.
2006-05-30 14:24:54.11 spid19 Analysis of database 'ProjectServer' (9) is
100% complete (approximately 0 more seconds)
2006-05-30 14:24:54.23 spid19 LogMgr::FixupLogTail (): alignBuf
0x30df000, writeSize 0xf000, filePos 0x7c207600
2006-05-30 14:24:54.23 spid19 blankSize 0x1e000, blkOffset 0x71d3b,
fileSeqNo 1250, totBytesWritten 0x0
2006-05-30 14:24:54.23 spid19 fcb status 0x3108142, handle 0x9c, size
6240456 pages
2006-05-30 14:24:54.23 spid19 FixupTail: Operating system error 33(The
process cannot access the file because another process has locked a portion
of the file.) encountered.
2006-05-30 14:24:54.23 spid19 Recovery of database 'ProjectServer' (9) is
0% complete (approximately 19 more seconds) (Phase 2 of 3).
2006-05-30 14:24:55.25 spid19 Recovery of database 'ProjectServer' (9) is
99% complete (approximately 0 more seconds) (Phase 2 of 3).
2006-05-30 14:24:55.25 spid19 1559 transactions rolled forward in
database 'ProjectServer' (9).
2006-05-30 14:24:55.25 spid19 Recovery of database 'ProjectServer' (9) is
99% complete (approximately 0 more seconds) (Phase 3 of 3).
2006-05-30 14:24:55.36 spid2 LogWriter: Operating system error 33(The
process cannot access the file because another process has locked a portion
of the file.) encountered.
2006-05-30 14:24:55.36 spid2 Write error during log flush. Shutting down
server
2006-05-30 14:24:55.36 spid19 Error: 9001, Severity: 21, State: 1
2006-05-30 14:24:55.36 spid19 The log for database 'ProjectServer' is not
available..
2006-05-30 14:24:55.36 spid19 Error: 3314, Severity: 21, State: 3
2006-05-30 14:24:55.36 spid19 Error while undoing logged operation in
database 'ProjectServer'. Error at log record ID (1250:465754:1)..
2006-05-30 14:24:55.39 spid19 Error: 3414, Severity: 21, State: 1
2006-05-30 14:24:55.39 spid19 Database 'ProjectServer' (database ID 9)
could not recover. Contact Technical Support..
After this, no one could access the project web page anymore. we checked the
database with Enterprise Manager, the ProjectServer database had a (Suspect)
after the database name.
We restored that particula database file from the tape, now the project web
access is working, but the link to the sharepoint sites are not working at
all.
When I clicked one of the link, it said..
The documents, risks and issues features in Project Web Access use Windows
SharePoint Services.
A Windows SharePoint Services site needs to be created for your project
before you can share project documents or track project risks and issues.
Site creation takes a few minutes, so if the project was just published, wait
a few minutes and then visit the page again. Otherwise, contact your server
administrator.
Where should I start to troubleshoot this problem and how can I prevent this
to happen again?
Thanks in advance for your help.
Johnny
timesheet, an error came up, "#50070: Unable to connect to the database
STS_servername_1_2064 on SERVERNAME. Check the database connection
information and make sure that the database server is running."
The SQL logs was showing,
2006-05-30 14:24:44.68 spid2 LogWriter: Operating system error 33(The
process cannot access the file because another process has locked a portion
of the file.) encountered.
2006-05-30 14:24:44.71 spid2 Write error during log flush. Shutting down
server
2006-05-30 14:24:44.71 spid2 LogWriter: Operating system error 33(The
process cannot access the file because another process has locked a portion
of the file.) encountered.
2006-05-30 14:24:44.71 spid2 Write error during log flush. Shutting down
server
2006-05-30 14:24:44.71 spid2 LogWriter: Operating system error 33(The
process cannot access the file because another process has locked a portion
of the file.) encountered.
2006-05-30 14:24:44.71 spid2 Write error during log flush. Shutting down
server
2006-05-30 14:24:44.73 spid10 Error: 9001, Severity: 21, State: 4
2006-05-30 14:24:44.73 spid10 The log for database 'ProjectServer' is not
available..
2006-05-30 14:24:44.73 spid51 Error: 9001, Severity: 21, State: 1
2006-05-30 14:24:44.73 spid51 The log for database 'ProjectServer' is not
available..
2006-05-30 14:24:44.89 spid51 Error: 9001, Severity: 21, State: 1
2006-05-30 14:24:44.89 spid51 The log for database 'ProjectServer' is not
available..
2006-05-30 14:24:44.90 spid51 Error: 3314, Severity: 21, State: 4
2006-05-30 14:24:44.90 spid51 Error while undoing logged operation in
database 'ProjectServer'. Error at log record ID (1250:466138:3)..
2006-05-30 14:24:44.92 spid51 Error: 9001, Severity: 21, State: 1
2006-05-30 14:24:44.92 spid51 The log for database 'ProjectServer' is not
available..
2006-05-30 14:24:44.92 spid51 Error: 3314, Severity: 21, State: 4
2006-05-30 14:24:44.92 spid51 Error while undoing logged operation in
database 'ProjectServer'. Error at log record ID (1250:466138:3)..
2006-05-30 14:24:44.92 spid51 Error: 9001, Severity: 21, State: 1
2006-05-30 14:24:44.92 spid51 The log for database 'ProjectServer' is not
available..
2006-05-30 14:24:44.92 spid51 Error: 3314, Severity: 21, State: 5
2006-05-30 14:24:44.92 spid51 Error while undoing logged operation in
database 'ProjectServer'. Error at log record ID (1250:464730:1)..
2006-05-30 14:24:46.06 spid19 Starting up database 'ProjectServer'.
2006-05-30 14:24:52.23 logon Login succeeded for user
'MSProjectServerUser'. Connection: Non-Trusted.
2006-05-30 14:24:54.11 spid19 Analysis of database 'ProjectServer' (9) is
100% complete (approximately 0 more seconds)
2006-05-30 14:24:54.23 spid19 LogMgr::FixupLogTail (): alignBuf
0x30df000, writeSize 0xf000, filePos 0x7c207600
2006-05-30 14:24:54.23 spid19 blankSize 0x1e000, blkOffset 0x71d3b,
fileSeqNo 1250, totBytesWritten 0x0
2006-05-30 14:24:54.23 spid19 fcb status 0x3108142, handle 0x9c, size
6240456 pages
2006-05-30 14:24:54.23 spid19 FixupTail: Operating system error 33(The
process cannot access the file because another process has locked a portion
of the file.) encountered.
2006-05-30 14:24:54.23 spid19 Recovery of database 'ProjectServer' (9) is
0% complete (approximately 19 more seconds) (Phase 2 of 3).
2006-05-30 14:24:55.25 spid19 Recovery of database 'ProjectServer' (9) is
99% complete (approximately 0 more seconds) (Phase 2 of 3).
2006-05-30 14:24:55.25 spid19 1559 transactions rolled forward in
database 'ProjectServer' (9).
2006-05-30 14:24:55.25 spid19 Recovery of database 'ProjectServer' (9) is
99% complete (approximately 0 more seconds) (Phase 3 of 3).
2006-05-30 14:24:55.36 spid2 LogWriter: Operating system error 33(The
process cannot access the file because another process has locked a portion
of the file.) encountered.
2006-05-30 14:24:55.36 spid2 Write error during log flush. Shutting down
server
2006-05-30 14:24:55.36 spid19 Error: 9001, Severity: 21, State: 1
2006-05-30 14:24:55.36 spid19 The log for database 'ProjectServer' is not
available..
2006-05-30 14:24:55.36 spid19 Error: 3314, Severity: 21, State: 3
2006-05-30 14:24:55.36 spid19 Error while undoing logged operation in
database 'ProjectServer'. Error at log record ID (1250:465754:1)..
2006-05-30 14:24:55.39 spid19 Error: 3414, Severity: 21, State: 1
2006-05-30 14:24:55.39 spid19 Database 'ProjectServer' (database ID 9)
could not recover. Contact Technical Support..
After this, no one could access the project web page anymore. we checked the
database with Enterprise Manager, the ProjectServer database had a (Suspect)
after the database name.
We restored that particula database file from the tape, now the project web
access is working, but the link to the sharepoint sites are not working at
all.
When I clicked one of the link, it said..
The documents, risks and issues features in Project Web Access use Windows
SharePoint Services.
A Windows SharePoint Services site needs to be created for your project
before you can share project documents or track project risks and issues.
Site creation takes a few minutes, so if the project was just published, wait
a few minutes and then visit the page again. Otherwise, contact your server
administrator.
Where should I start to troubleshoot this problem and how can I prevent this
to happen again?
Thanks in advance for your help.
Johnny