Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

SharePoint 2003 Databases (UNCLASSIFIED)

  Asked By: Aiesha    Date: Dec 20    Category: Sharepoint    Views: 1226

I am running SharePoint Portal 2003 with 1 web server and a separate
database server. We had to reboot both servers after applying some security
patches. After the reboot the portal sites became unresponsive and were
giving us errors with a link to go to the web part maintenance page which
honestly did nothing to fix the issue. Also some of our other sites that
contains massive document libraries are extremely slow to load while other
sites come up just fine.

In the event viewer there are all sorts of errors. To begin with I am

Windows SharePoint Server Event ID 1000 Unable to connect to the database
CGSC1_SITE (which is running by the way)

I am also getting W3CTRS Event ID 2001: It has taken too long to refresh the
W3SVC counters, the stale counters are being used instead

Windows SharePoint Server Event ID 1000: Faulting application w3wp.exe then
it gives the version..faulting module tquery.dll

Now here is where things are getting even more weird. In my SQL directory I
now have two _SITE log files and .mdf files. They both are showing to be
created at the same time and last modified at the same time. The difference
is the size of these files. I assume that in both cases the larger files are
the "correct" ones. CGSC1_SITE.mdf is 403Gb CGSC1_SITE_log.LDF is 173Gb the
other ones CGSC1_SITE.mdf is a little over 3Gb and finally
CGSC1_SITE_log.LDF is almost 2Gb like I said these files have the same file
name and are existing in the same exact directory. How can that be? And is
that my culprit?



8 Answers Found

Answer #1    Answered By: Gaurav Nemane     Answered On: Dec 20

When rebooting both servers, you have to make sure the database is up
before the web server is up. Try rebooting the web front end one more
time to see if this helps.

Answer #2    Answered By: Marjorie Humphrey     Answered On: Dec 20

You could probably also get away with just doing an IISRESET on the WFE
server. That should kickstart any connections to SQL.

Answer #3    Answered By: Chelsey Watts     Answered On: Dec 20

Now what about the double databases? Do I rename the smaller ones to .bak?
while the web site is rebooting?

Answer #4    Answered By: Vinay Thakur     Answered On: Dec 20

Ok I Physically Shut down the web site and also stopped the Databases and
renamed the second database files. Then rebooted my SQL server and gave it a
few mins to make sure that everything was up and running and connected.
Finally I brought back up my web site.

The system still lags and hangs. I am still getting the Windows SharePoint
Server Event ID 1000 Faulting application w3wp.exe, version 6.0.3790.1830,
stamp 42435be1, faulting module tquery.dll, version 11.0.5704.0, stamp
3f57e562, debug? 0, fault address 0x00080666.

Google showed me that this error was actually coming from IIS but did not
tell me what I can do to fix the issue. Any ideas?

Now the interesting thing is that it goes normal (less than a second to draw
the page) to 10mins at times to load the page. Could this be the result of a
web part that has gone bad?

Answer #5    Answered By: Jonathan Scott     Answered On: Dec 20

When you recylce the application pool does it fix this issue? You
need to make sure that you dispose of all SPWeb and SPSite objects
or your leaving db connections open. How many users are on your
portal? I would definitely start with looking into to closing all
ojbects that give you the .dispose() method. If you are still
getting problems you might have outgrown your server farm depending
on your user base to farm size. Give us some more details onusers
and number of servers.

Answer #6    Answered By: Asia Meyers     Answered On: Dec 20

We had it on our server as well (awhile back). We had to get an
unpublished patch from Microsoft to address this issue.

Answer #7    Answered By: Aditiya Kapale     Answered On: Dec 20

I did contact MS and got the unpublished patch KB900929 and ran that. It did
not fix the issue though. Was this the same patch that solved your issue?

Answer #8    Answered By: Faith Delgado     Answered On: Dec 20

Did you look at the post I made? Answer the questions I posted and
I might be able to help you.

Didn't find what you were looking for? Find more on SharePoint 2003 Databases (UNCLASSIFIED) Or get search suggestion and latest updates.