Speed Up Sharepoint

I found this at the SBS Diva's site - thank you!!!

Sharepoint slow to load when first opening it up? Tweak it!
You can speed up the launching of the Companyweb site by changing the IIS
Application Pool.

Go to IIS Manager
Open the Application Pools
Right click on the DefaultAppPool and go to properties
Go to the Performance Tab
Uncheck the top box - shutdown worker processes after being idle.

http://www.sbslinks.com/AppPool.htm

Event ID: 1000 Sharepoint Services

Via:

http://support.microsoft.com/kb/840685

SYMPTOMS

When you restart a computer that is running Microsoft Windows Small Business Server 2003, the following event error message may be logged to the application event log:

Type: Error
Source: Windows SharePoint Services 2.0
Category: None
Event ID: 1000
Description:
#50070: Unable to connect to the database STS_Config on SBS\SharePoint. Check the database connection information and make sure that the database server is running.

Although the error message is logged to the application event log, you can successfully connect to and work in your Microsoft Windows SharePoint Services Web site.

CAUSE

This issue may occur when the SharePoint Timer Service tries to contact the configuration database when the computer starts or shuts down. By default, the configuration database in Windows SharePoint Services is named STS_config.

RESOLUTION

The error message that is mentioned in the "Symptoms" section does not affect the functionality of Windows SharePoint Services or of Windows Small Business Server 2003. If you can connect to the Windows SharePoint Services Web site successfully, you can safely ignore this error message.

WORKAROUND

To work around this issue, add the DependOnService registry entry to the following registry subkey on the server, and then set the DependOnService registry entry to MSSQL$SHAREPOINT:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SPTimer

To do this, follow these steps.

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

1.	Click Start, and then click Run.
2.	In the Open box, type regedit, and then click OK.
3.	Locate, and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SPTimer
4.	On the Edit menu, point to New, and then click String Value.
5.	Type DependOnService, and then press ENTER
6.	On the Edit menu, click Modify.
7.	In the Value data box, type MSSQL$SHAREPOINT, and then click OK.
8.	Quit Registry Editor.

sharepoint error

Event Type: Error
Event Source: Windows SharePoint Services 2.0
Event Category: None
Event ID: 1000
Date: 7/18/2006
Time: 1:43:02 AM
User: N/A
Computer: MYSERVER
Description:
#50070: Unable to connect to the database STS_adina_1 on MYSERVER\SharePoint. Check the database connection information and make sure that the database server is running.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Googling...

Found: http://support.microsoft.com/?kbid=900498&FR=1

RESOLUTION

To resolve this issue, synchronize the Windows SharePoint Services Timer Service together with the new user account information. To do this, follow these steps:

1. Start Windows SharePoint Services Central Administration.
2. On the Windows SharePoint Services Central Administration page, click Configure virtual server for central administration under Server Configuration.
3. On the Configure Administrative Virtual Server page, click Use an existing application pool, click the existing application pool that you are already using, and then click OK.

WSUS problem

Event Type: Error
Event Source: Windows Server Update Services
Event Category: Database
Event ID: 421
Date: 7/18/2006
Time: 10:15:55 AM
User: N/A
Computer: MYSERVER
Description:
Connection to database failed. Reason=Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
General network error. Check your network documentation.. Connection string: Data Source=MYSERVER\WSUS;Initial Catalog=SUSDB;Connection Timeout=60;Application Name=WSUS SQL Connection;Trusted_Connection=Yes;Pooling='true'; Max Pool Size = 100

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I'm Googling this....

Found http://wsus.editme.com/ContentFileDownloadFailedAccessDeniedNoHTTP
and http://msmvps.com/blogs/athif/archive/2006/04/18/91472.aspx
and http://blogs.msdn.com/astebner/archive/2005/11/23/496503.aspx

All refer to a hidden setting on the SonicWall firefall (I have a SOHO3):

Enable HTTP 1.1 Range Requests from FIREWALL

If you have a SonicWALL device on your network then, you can use the following steps to resolve this issue:

1. Navigate to http:///diag.html from a computer on your network (by default this URL will be http://192.168.168.168/diag.html).
2. Enable the setting to allow HTTP byte range requests in the gateway anti-virus filtering process.
3. Reboot the SonicWALL firewall device .
4. Attempt to download again.

However, this does not help me, since my SonicWall doesn't run Gateway AV.

The other suggested workaround is:

Set BitsDownloadPriorityForeground=1 using osql.exe on WSUS SQL instance.

1. net stop WSUSservice
2. CD "%ProgramFiles%\Update Services\tools\osql"
3. osql.exe -S -E -b -n -Q "USE SUSDB update tbConfigurationC set BitsDownloadPriorityForeground=1"
4. net start WSUSservice

Notes

• When you run the above command-line, you will get the output as - "(1 row affected)".
• The osql utility can be found under the "%ProgramFiles%\Update Services\Tools\osql" folder.
• Provide the servername with the -S parameter. [Replace

However, someone commented on this blog:

http://wsus.editme.com/ContentFileDownloadFailedAccessDeniedNoHTTP

to add these domains to the Allowed List when using SonicWall's CFS:

enter the following URL's in the Allowed domains http://windowsupdate.microsoft.com http://*.windowsupdate.microsoft.com https://*.windowsupdate.microsoft.com http://*.update.microsoft.com https://*.update.microsoft.com http://*.windowsupdate.com http://download.windowsupdate.com http://download.microsoft.com http://*.download.windowsupdate.com http://wustat.windows.com http://ntservicepack.microsoft.com

I did that, so let's see if it helps......

WSUS error

Source	Event ID	Last Occurrence	Total Occurrences
Windows Server Update Services	421	7/5/2006 1:08 AM	8 *
Connection to database failed. Reason=Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.. Connection string: Data Source=MYSERVER\WSUS;Initial Catalog=SUSDB;Connection Timeout=60;Application Name=WSUS SQL Connection;Trusted_Connection=Yes;Pooling='true'; Max Pool Size = 100

Hmmm...

Things to check:

1. SQLAgent$WSUS running under LocalAdmin account - check

2. Check membership of the WSUS Administrators security group; I had no members in there...how did that happen? I added domain admins and domain controllers. (According to this: http://forums.techarena.in/archive/index.php/t-233723.html, a front-end domain controller needs to have a computer account in the WSUS administrators group.)

Exchange Mailbox Manager Policy

My server: SBS 2003 running Exchange 2003 sp1

Even though my Mailbox Manager policy was running, I was getting emails that said:

Mailboxes processed: 0
Messages moved: 0
Size of moved messages: 0.00 KB
Deleted messages: 0
Size of deleted messages: 0.00 KB

I googled this problem, but didn't find anything that helped me. In fact, the documenation on Mailbox Manager is somewhat lacking. In the Google Groups, a lot of people had posed the question, but never got a response. I had my Mailbox Manager Policy move things to the "System Cleanup" folder, which is supposed to appear in the Folder List in the Outlook client, but it was not showing, so I knew something wasn't working right.

Here's how I got the Mailbox Manager working:

1. In SBS 2003's Server Management console, expand First Organization Exchange, Recipients, Recipient Policies.

2. Right-click on Mailbox Manager Policy

3. The problem I had was that I had never set up the filter on the General tab, so nothing was displayed in that filter rules box. To set up the filter, I clicked "Modify" and on the pop-up box that displayed, I un-checked everything but "Users With Exchange Mailboxes," since that was the only item that I wanted Mailbox Manager to process. (Your needs may vary).

4. Then click on the Mailbox Manager Policy (Settings) box. I clicked the drop-down box under "When Processing a Mailbox", and chose "Move to System Cleanup folders" because I want the messages stored there instead of just deleting them.

5. Check the checkboxes of the folders you want managed and set the age limit (days). click "OK"

6. close this window so you're back in the Server Management console. Right-click on the Mailbox Manager Policy and click "Apply this policy now."

7. To run the Mailbox Manager policy manually (which I did to test), right-click on your server (First Organization, Servers, ServerName) and choose "Start Mailbox Management Process."

8. The mailbox management process will begin. When completed, you (the admin, will receive an email message stating that the process is completed. Also, all users will receive an email message about what was cleaned and where the deleted messages were moved to (the System Cleanup folder).

9. To configure this policy to run on a regular basis, right-click your server, choose Properties, then click the Mailbox Management tab. Here you can configure the times for this policy to run. It's best to have it run after-hours, as it does require some system resources.