[Webinar] Streamline your web hosting managementRegister Today

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 442
  • Last Modified:

Very low free disk resources on system drive (C:) of MOSS 2007 database server


I have a small server farm with two (2) servers: a MOSS Enterprise Edition server and a MS SQL 2005 Standard Edition server, both running Windows Server 2003 Enterprise Edition.

I am in urgent need for help due to the following issue on my production MOSS 2007 database server. Today, I tried to log into my database server which holds the database of our MOSS 2007 Enterprise Edition installation. The server started showing some messages that my profile is corrupt (administrator profile) and a default profile will be used instead. In addition, the GUI of the server is corrupted, and it kept complaining for low disk space. Please note that the database files of my installation are kept on a different drive (network storage).

Actually, I cannot even get a DOS window, etc, so I don't know how to tackle this safely and reliably.

My MOSS 2007 installation is working fine so far, however, I am afraid that if I let this "low resources" situation continue, my database server will crash

So, I am thinking of quisciencing (shutting down gracefully) my MOSS farm, then, shutdown my MOSS 2007 Enterprise Edition Server, then ask the system administrator to shutdown the database server. After both servers are shutdown, I am thinking to power up the database server FIRST, then powerup the MOSS 2007 Enterprise Server and login to the administration database to un-quisce the MOSS farm. I don't know if this is the correct procedure to follow...

Also I cannot understand why there is a disc space issue with the system drive of the database server, since we do NOT store any sharepoint content on this drive, just the Microsoft SQL databases (master, temp, etc).

Can you please help me ???
  • 2
1 Solution
> Actually, I cannot even get a DOS window, etc, so I don't know how to tackle this safely and reliably.

Boot from your installation DVD, go to command prompt and remove (or just backup) some useless data.
Then you can boot normally and identify and resolve the issue. Something is filling your disk and usually you can change the location to the new place. windirstat http://windirstat.info/ can be useful for detecting large files or directories after you boot.
The Issue is related on non backed up Databases, so roll-back datalogs not deleted.

Delete some TMP-Files or "Uninstall Files" of your Windows-Patches. You can find them in windows-direcotry for example C:\Windows

Display any hidden and system files. At the top you can find any directories with "uninstall" information.

Nice Weekend!

devshedAuthor Commented:
Hi all,
We ended up connecting to the database server through another instance of MS SQL Server 2005 Management Studio and shrunk a couple of database log files that were not automatically shrinked due to some unknown reason.

Thank you for the suggentions, though.
This is not you've asked for but great you solved your issue :)

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now