Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

SharePoint 2003 Databases

  Asked By: Alisha    Date: Apr 18    Category: Sharepoint    Views: 1048

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

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

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

I am also getting W3CTRS Event ID 2001: It has taken too long to
W3SVC counters, the stale counters are being used instead
Windows SharePoint Server Event ID 1000: Faulting application
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
is the size of these files. I assume that in both cases the larger
the "correct" ones. CGSC1_SITE.mdf is 403Gb CGSC1_SITE_log.--LDF is
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
name and are existing in the same exact directory. How can that
be? And
that my culprit?



9 Answers Found

Answer #1    Answered By: Trevor Davis     Answered On: Apr 18

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

Answer #2    Answered By: Vinay Thakur     Answered On: Apr 18

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: Shayla Mcbride     Answered On: Apr 18

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
Finally I brought back up my web site.

The system still lags and hangs. I am still getting the Windows
Server Event ID 1000 Faulting application w3wp.exe, version
stamp 42435be1, faulting module tquery.dll, version 11.0.5704.0,
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 #4    Answered By: Jarvis Rowe     Answered On: Apr 18

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 #5    Answered By: Selena Glenn     Answered On: Apr 18

I have not recycled the application pools. Does Windows do that
automagically on reboot? And honestly I have no idea of where or how to dispose of all SPWeb and SPSite objects.

Portal users we have all domain users with Read Access and honestly I can
not answer how many people that is. At a rough guess I would say around

As far as outgrowing our servers....the Web Site and Database both are IBM
X345 Series with Duel P4 3.2 processors and 4Gb of memory and tons of disk
space. So honestly I do not think that we are outgrowing our current
configuration. Here in the next few weeks we will be migrating to a new
VMware ESX solution.

Answer #6    Answered By: Christian Waters     Answered On: Apr 18

When you reboot it recycles the app poool. However, what I am
saying is you stated it takes a little while for your installation
to crash. Therefore, to test if a recycle of the application pool
is going to fix your problem: Next time the site becomes
unresponsive log on to the front end web server and open up IIS
through administrative tools. Then right click the application pool
that your sharepoint  installation is using and choose the recycle
option. If this fixes the problem your exceeding the amount of
connections you have alllowed in your app pool settings.

Are you or do you have any developers that are writing web parts for
you sharepoint installation? IF so they need to go through ALL of
there code and add .dispose() after all SPSite, SPWeb, SQL Data
Readers, and make sure all sql connections are closed. If not they
will grow and grow until you crash your application pool

As for knowing how many users you have. Are you using portal server
or just WSS? From a licensing standpoint you realy need to know how
many users are connecting to your portal because each one needs a
portal client access license or your in violation of microsofts
licensing agreement. IF you are using shared services you can go to
your profile database (access it from the bottom of the site
settings page) and it will tell you the number of profiles. Also if
all AD users have access to sharepoint then how many users are in
your SP installation?

AS for VM ware. Sharepoint is a IO intensive program that is making
constant querys to the SQL database. I don't know about your
installation but we have found that VM is not a viable solution for

Answer #7    Answered By: Virendar Bahudur     Answered On: Apr 18

Now what seems to have fixed my problem was removing the following Widows






I applied these updates last Monday before the issue arose. I am currently
researching to see if these security updates have been know to cause any
system latency. However I am still getting the error message. Am I looking
at a serous database corruption possibly?

We are not building any custom web parts. We have purchased Corusworks

Answer #8    Answered By: Alisha Itagi     Answered On: Apr 18

How is your experience with the VMware ESX virtual server solution?
We are thinking to go that way and would like to know about it.

Answer #9    Answered By: Elisabeth Walsh     Answered On: Apr 18

For our v2 environment we found that virtualized web servers seemed to work
okay, but virtualized SQL servers were unacceptably slow. This was WSS v2
running on ESX 2.5. We just use them for test or restore environments these

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