Re: Sharepoint Database falling over event 1000

Tech-Archive recommends: Fix windows errors by optimizing your registry

Colin,

Based on the error you received in the mssql$sharepoint\log\errorlog it looks like something else has it open.. Did you reboot the server? or restart just the mssql$sharepoint service?

The osql command I provided earlier you should be able to simply copy paste it into a command prompt to run it.. Another way of doing it would be to do the following from a command prompt on the server

osql -E -S %computername%\sharepoint 
select name, filename from sysdatabases
go
exit

Basically, we need to verify that is the correct path to the database.. and that it exists.. and then possibly use a utility to show the open handles to that file if the database is still in use after a reboot.

Yes, the logical database name as far as WMSDE/SQL is concerned is sts_siva01_1, but the physical file name is
D:\Data\MSDEDatabases\SharePoint\STS_SIVA01_1.mdf
There should also be a D:\Data\MSDEDatabases\SharePoint\STS_SIVA01_1.ldf (by default) which is the log file for that database.


--

Hope that helps,
David Copeland
Microsoft Small Business Server Support

This posting is provided "AS IS" with no warranties, and confers no rights.


SBS Newsgroups:

SBS v4.x: microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs




"Colin Coleman" <colin@xxxxxxxxxxx> wrote in message news:uuOv8CmqFHA.3424@xxxxxxxxxxxxxxxxxxxxxxx
Checked the McAfee Antvirus, It Has Now Been Excluded from Scanning the Parent Folder and All Sub Folders,
Restarted Sharepoint Services,
Restarted Sharepoint Timer

Opened Companyweb......Crash still same single line showing

and the Application log still adds
Event 1000, Category None, Type Error, User N/A Source Windows Sharepoint Service
#50070: Unable to connect to the datbase STS_siva01_1 on
SIVA01\sharepoint. Check the database connection information and make
sure that the database server is running.

Could the database Be Corrupt?
How Can i check it ?
Is the Database D:\Data\MSDEDatabases\SharePoint\STS_SIVA01_1.mdf. ?
What is the correct text for osql -E -S %computername%\sharepoint -Q "select name, filename from sysdatabases" ?

Best Regards

Colin




"Default User" <anonymous@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:ucApyulqFHA.240@xxxxxxxxxxxxxxxxxxxxxxx 
Colin,

Based on

2005-08-25 21:12:30.07 spid55 udopen: Operating system error 32(The
process cannot access the file because it is being used by another process.)
during the creation/opening of physical device
D:\Data\MSDEDatabases\SharePoint\STS_SIVA01_1.mdf.
2005-08-25 21:12:30.09 spid55 FCB::Open failed: Could not open device
D:\Data\MSDEDatabases\SharePoint\STS_SIVA01_1.mdf for virtual device number
(VDN) 1.

It looks like something else already has that file open (at least when the SharePoint instance attempted to start). You might try simply restarting the MSSQL$SharePoint service (make sure no one is using Companyweb or any WSS site on the server first) and then check the log to see if you still get the same error.
If you do, then at that point you could try rebooting the server to see if it is about to open it then..

Do you have any AV software that may be scanning that directory? Open File Agent type software?


--

Hope that helps,
David Copeland
Microsoft Small Business Server Support

This posting is provided "AS IS" with no warranties, and confers no rights.


SBS Newsgroups:

SBS v4.x: microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs



"Colin Coleman" <colin@xxxxxxxxxxx> wrote in message news:eskjQClqFHA.3180@xxxxxxxxxxxxxxxxxxxxxxx 
Hi David,

Thanks for the reply, i have looked into the log files and have copied the most recent one, if this helps diagnose what has happened.
THE LOGFILE

2005-08-25 20:56:56.40 server Microsoft SQL Server 2000 - 8.00.884 (Intel X86)
Nov 29 2003 20:52:47
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine (Windows) on Windows NT 5.2 (Build 3790: )

2005-08-25 20:56:56.40 server Copyright (C) 1988-2002 Microsoft Corporation.
2005-08-25 20:56:56.40 server All rights reserved.
2005-08-25 20:56:56.40 server Server Process ID is 2424.
2005-08-25 20:56:56.40 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\LOG\ERRORLOG'.
2005-08-25 20:56:56.42 server SQL Server is starting at priority class 'normal'(2 CPUs detected).
2005-08-25 20:56:58.06 server SQL Server configured for thread mode processing.
2005-08-25 20:56:58.06 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2005-08-25 20:56:58.85 spid4 Starting up database 'master'.
2005-08-25 20:56:59.32 spid4 Server name is 'SIVA01\SHAREPOINT'.
2005-08-25 20:56:59.32 spid4 Skipping startup of clean database id 4
2005-08-25 20:56:59.32 spid4 Skipping startup of clean database id 5
2005-08-25 20:56:59.32 spid4 Skipping startup of clean database id 6
2005-08-25 20:56:59.32 spid4 Skipping startup of clean database id 7
2005-08-25 20:56:59.32 spid4 Skipping startup of clean database id 8
2005-08-25 20:56:59.35 server Using 'SSNETLIB.DLL' version '8.0.880'.
2005-08-25 20:56:59.35 spid5 Starting up database 'model'.
2005-08-25 20:56:59.39 server SQL server listening on Shared Memory.
2005-08-25 20:56:59.39 server SQL Server is ready for client connections
2005-08-25 20:56:59.78 spid5 Clearing tempdb database.
2005-08-25 20:57:02.15 spid5 Starting up database 'tempdb'.
2005-08-25 20:57:02.25 spid4 Recovery complete.
2005-08-25 20:57:03.73 spid4 SQL global counter collection task is created.
2005-08-25 20:57:09.40 spid51 Starting up database 'STS_Config'.
2005-08-25 21:00:38.42 spid52 Starting up database 'STS_SIVA01_1'.
2005-08-25 21:12:30.07 spid55 Starting up database 'STS_SIVA01'.
2005-08-25 21:12:30.07 spid53 Starting up database 'STS_OEMSBSCN-3158_1'.
2005-08-25 21:12:30.07 spid55 udopen: Operating system error 32(The process cannot access the file because it is being used by another process.) during the creation/opening of physical device D:\Data\MSDEDatabases\SharePoint\STS_SIVA01_1.mdf.
2005-08-25 21:12:30.09 spid55 FCB::Open failed: Could not open device D:\Data\MSDEDatabases\SharePoint\STS_SIVA01_1.mdf for virtual device number (VDN) 1.
2005-08-25 21:12:30.12 spid56 Starting up database 'msdb'.
2005-08-25 21:12:30.17 backup BACKUP failed to complete the command BACKUP DATABASE [STS_SIVA01] TO VIRTUAL_DEVICE='{E78EA9E3-1F8C-450A-A134-FA1E7902D9B9}6' WITH SNAPSHOT,BUFFERCOUNT=1,BLOCKSIZE=1024
2005-08-25 21:12:31.32 spid51 BackupVirtualDeviceFile::PrepareToFreeze: failure on backup device '{E78EA9E3-1F8C-450A-A134-FA1E7902D9B9}1'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2005-08-25 21:12:31.32 backup BACKUP failed to complete the command BACKUP DATABASE [master] TO VIRTUAL_DEVICE='{E78EA9E3-1F8C-450A-A134-FA1E7902D9B9}1' WITH SNAPSHOT,BUFFERCOUNT=1,BLOCKSIZE=1024
2005-08-25 21:12:31.34 spid52 BackupVirtualDeviceFile::ClearError: failure on backup device '{E78EA9E3-1F8C-450A-A134-FA1E7902D9B9}2'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2005-08-25 21:12:31.34 backup BACKUP failed to complete the command BACKUP DATABASE [model] TO VIRTUAL_DEVICE='{E78EA9E3-1F8C-450A-A134-FA1E7902D9B9}2' WITH SNAPSHOT,BUFFERCOUNT=1,BLOCKSIZE=1024
2005-08-25 21:12:31.36 spid56 BackupMedium::ReportIoError: write failure on backup device '{E78EA9E3-1F8C-450A-A134-FA1E7902D9B9}3'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2005-08-25 21:12:31.36 spid56 Internal I/O request 0x80815C08: Op: Write, pBuffer: 0x03C50400, Size: 1024, Position: 0, UMS: Internal: 0x0, InternalHigh: 0x80811DD0, Offset: 0x80810CA0, OffsetHigh: 0x0, m_buf: 0xFFFFFFFF, m_len: 2147483647, m_actualBytes: 0, m_errcode: 995, BackupFile: {E78EA9E3-1F8C-450A-A134-FA1E7902D9B9}3
2005-08-25 21:12:31.36 backup BACKUP failed to complete the command BACKUP DATABASE [msdb] TO VIRTUAL_DEVICE='{E78EA9E3-1F8C-450A-A134-FA1E7902D9B9}3' WITH SNAPSHOT,BUFFERCOUNT=1,BLOCKSIZE=1024
2005-08-25 21:12:31.39 spid54 BackupMedium::ReportIoError: write failure on backup device '{E78EA9E3-1F8C-450A-A134-FA1E7902D9B9}4'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2005-08-25 21:12:31.39 spid54 Internal I/O request 0x80969BC0: Op: Write, pBuffer: 0x03A90400, Size: 1024, Position: 0, UMS: Internal: 0x80968800, InternalHigh: 0x0, Offset: 0x0, OffsetHigh: 0x809DB400, m_buf: 0x00000000, m_len: 0, m_actualBytes: 0, m_errcode: 995, BackupFile: {E78EA9E3-1F8C-450A-A134-FA1E7902D9B9}4
2005-08-25 21:12:31.39 backup BACKUP failed to complete the command BACKUP DATABASE [STS_Config] TO VIRTUAL_DEVICE='{E78EA9E3-1F8C-450A-A134-FA1E7902D9B9}4' WITH SNAPSHOT,BUFFERCOUNT=1,BLOCKSIZE=1024
2005-08-25 21:12:31.39 spid53 BackupMedium::ReportIoError: write failure on backup device '{E78EA9E3-1F8C-450A-A134-FA1E7902D9B9}5'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2005-08-25 21:12:31.39 spid53 Internal I/O request 0x80A51C80: Op: Write, pBuffer: 0x03D90400, Size: 1024, Position: 0, UMS: Internal: 0x0, InternalHigh: 0x0, Offset: 0x211, OffsetHigh: 0x211, m_buf: 0x00000000, m_len: 0, m_actualBytes: 0, m_errcode: 995, BackupFile: {E78EA9E3-1F8C-450A-A134-FA1E7902D9B9}5
2005-08-25 21:12:31.39 backup BACKUP failed to complete the command BACKUP DATABASE [STS_OEMSBSCN-3158_1] TO VIRTUAL_DEVICE='{E78EA9E3-1F8C-450A-A134-FA1E7902D9B9}5' WITH SNAPSHOT,BUFFERCOUNT=1,BLOCKSIZE=1024
2005-08-26 10:33:37.59 spid4 SQL Server is terminating due to 'stop' request from Service Control Manager.

================

Also I am not sure from your reply what goes into the example osql -E -S %computername%\sharepoint -Q "select name, filename from sysdatabases" Can you see what i need from the error log ?

Thanks for helping us, we are a bit lost on this one

Cheers

Colin




"David Copeland [MSFT]" <davidcop@xxxxxxxxxxxxxxxxxxxx> wrote in message news:eWMK%232jqFHA.364@xxxxxxxxxxxxxxxxxxxxxxx 
Colin,

Based on the error it appears that it is unable to get to your content database (based on the database name of sts_siva01_1)

Couple of things to check..
1) Check in the \program files\microsoft sql server\mssql$sharepoint\log directory for the errorlog. Does it show any problems loading/finding that database?

2) Run the following from a command prompt on the server to see where the instance thinks the database should be.

osql -E -S %computername%\sharepoint -Q "select name, filename from sysdatabases"

--

Hope that helps,
David Copeland
Microsoft Small Business Server Support

This posting is provided "AS IS" with no warranties, and confers no rights.


SBS Newsgroups:

SBS v4.x: microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs

"Colin Coleman" <colin@xxxxxxxxxxx> wrote in message news:urhtWejqFHA.2596@xxxxxxxxxxxxxxxxxxxxxxx
Since running the Windows update on SBS2k3 SP (none) 25th Aug 2005 , we now
find that the http://companyweb has stopped working and get a single line
reporting that the database could not be connected on the client explorer and server.
the messsage is :

Unable to connect to database. Check database connection information and
make sure the database server is running.


I have read many articles regarding the shrepoint timer service and tried
all of the, to no avail, have restrted the Sharepointservice but it still
reports the same error on the server and all clients.

There appears an event 1000 in the application every time anyone logs on to
the web at any client so we have loads of red Gongs in the evnt log now.

The Log Error reads:

#50070: Unable to connect to the datbase STS_siva01_1 on SIVA01\sharepoint. Check the database connection information and make sure that the database server is running.

For more info.......microsoft.....events.asp


Where  should I look next ?

Colin











.

Relevant Pages

  • RE: How do I restore from mdf and ldf files?
    ... Tasks -> Backup Database ... Tasks -> Restore Database ... Windows 2003 Server with Latest Service Pack ... Pre-requisites for Sharepoint Backup and Restore: ...
    (microsoft.public.sharepoint.portalserver)
  • RE: ESENT Logging
    ... SBS server 2003 has a backup job that will ... 145881 How to Use Jetpack.exe to Compact a WINS or DHCP Database ... newsgroups so that they can be resolved in an efficient and timely manner. ...
    (microsoft.public.windows.server.sbs)
  • RE: ESENT Logging
    ... SBS server 2003 has a backup job that will ... 145881 How to Use Jetpack.exe to Compact a WINS or DHCP Database ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • RE: Backups have Shadow Copy Problems
    ... and restarted the server. ... suggested and changed the recovery model to simple on the one database called ... I understand the issue to be: the backup task failed ... You back up data from a volume that contains a Microsoft SQL Server ...
    (microsoft.public.windows.server.sbs)
  • Re: Copying a database between servers
    ... In 2000 you can backup to an UNC path ... or a local drive and the same goes for the restore. ... backup the database and then restore it on the new server. ... >>> one SQL Server 7.0 database with 'select' access to another SQL ...
    (microsoft.public.sqlserver.tools)