Archive for August, 2009
Setting the Maximum Memory Usage on the Sharepoint Database
Posted by: | CommentsOur earlier post referred to setting the maximum memory usage for the SBSMonitoring database, but it is not the only default database that can use a large amount of RAM. The Sharepoint database for the companyweb interface can also get a bit out of control at times. Here are the steps to limit the maximum amount of RAM used:
- On the SBS 2008 server, open the Start menu and select All Programs.
- Select Microsoft SQL Server 2005.
- Right-Click on SQL Server Management Studio Express and select Run As Administrator. If you don’t run the tool as Administrator, the remaining steps will not work.
- Enter the following for the datbase name:
\\.\pipe\mssql$microsoft##ssee\sql\query - Click Connect.
- When the Object Explorer window opens, right-click on the top item (\\.\pipe\mssql$microsoft##ssee\sql\query) and select Properties.
- Click on the Memory page in the left-hand column.
- Change the Maximum Server Memory value to something a little more reasonable. The minimum RAM is set to 128, so the maximum cannot be set lower than that. You may need to tweak this value to ensure proper performance out of the Sharepoint database.
- Click OK and the database memory usage will be adjusted.
- Close SQL Server Management Studio Express when finished.
Want to see this in action? Check out our screencast of the process!
So who wrote this blog and what do they do for a living anyway?
We’re Third Tier. We provide advanced Third Tier support for IT Professionals.
Get Support 
Blog 
Twitter 
Facebook 
LinkedINSetting the Maximum Memory Usage on SBSMonitoring
Posted by: | CommentsSusan Bradley had an often-referenced post on how to adjust the maximum memory usage of the SBSMonitoring MSDE instance in SBS 2003. Surprise, the SBSMonitoring database in SBS 2008 can also grow exceedingly large if not kept in check. The memory limits for the SBSMonitoring database can be adjusted in the SQL 2005 Management Studio Express on an SBS 2008 server. Here are the steps to do that:
- On the SBS 2008 server, open the Start menu and select All Programs.
- Select Microsoft SQL Server 2005.
- Right-Click on SQL Server Management Studio Express and select Run As Administrator. If you don’t run the tool as Administrator, the remaining steps will not work.
- Select the database from the drop-down list, or enter it as servername\SBSMONITORING, then click Connect.
- When the Object Explorer window opens, right-click on the top item (servername\SBSMONITORING) and select Properties.
- Click on the Memory page in the left-hand column.
- Change the Maximum Server Memory value to something a little more reasonable (100 has been bantered around as a reasonable value, but you may need to adjust depending on the server performance).
- Click OK and the database memory usage will be adjusted.
- Close SQL Server Management Studio Express when finished.
Want to see this in action? Check out our screencast of the process!
So who wrote this blog and what do they do for a living anyway?
We’re Third Tier. We provide advanced Third Tier support for IT Professionals.
Get Support Blog Twitter Facebook LinkedINMore Fun with SBS 2008 and Sharepoint Updates
Posted by: | CommentsAnyone who has been dealing with SBS 2008 for the last couple of months knows that there have been issues with recent Sharepoint and SBS 2008 updates:
Companyweb Inaccessible After Sharepoint 3.0 Service Pack 2
Files in Companyweb are Opening Read-Only After SBS 2008 UR2
Sharepoint Service 3 Search event errors after an SBS 2008 Update Rollup
Event 2436 for Sharepoint Services 3 Search
Bottom line, it’s not been an easy road. Fortunately, the SBS team have done a good job of documenting the issues as they come up. Unfortunately, not everything has been caught yet. As I found out this week.
I’ve had two new SBS 2008 deployments in the last two months. One a migration (won’t go there), and the other a clean install. Ironically, the clean install is the one that’s caused me the most grief. The initial install went smoothly, and we’ve been keeping up to date with all the updates. Based on the information above, we knew to install the Sharepoint 3 SP2 before installing SBS 2008 UR2, and flipped the database off of Read Only.
Yesterday, I went to create a new security group. I launched the Add Group Wizard from the SBS 2008 console and was immediately greeted with:
“Windows SBS 2008 Add Group Wizard has stopped working”
The first wizard screen never even launched. Of course, I started digging through the addgroup.log file in C:\Program Files\Windows Small Business Server\Logs, and found the following after hunting for several minutes:
An exception of type 'Type: System.Data.SqlClient.SqlException, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' has occurred. Message: Access to table dbo.Versions is blocked because the signature is not valid.
In the stack dump that followed, many of the references were to Sharepoint. “Ah ha!” I thought. “The Add Group Wizard also does some things in Sharepoint!” and I went off to look at Sharepoint. Sure enough, companyweb wouldn’t come up. So, I went back to Companyweb Inaccessible After Sharepoint 3.0 Service Pack 2 and went through those steps again. I verified that the database was not read-only, then I went through and followed the steps to re-run the setup wizard from the command line. Uh, oh, got errors. Fortunately, the psconfig command had me look at the PSCDiagnostics log in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS. Unfortunately, those logs didn’t really tell me anything useful. What I found was this:
08/17/2009 17:12:59 1 ERR One or more configuration tasks has failed to execute
08/17/2009 17:12:59 1 INF Entering function TaskDriver.Stop
08/17/2009 17:12:59 1 INF Entering function StringResourceManager.GetResourceString
08/17/2009 17:12:59 1 INF Resource id to be retrieved is PostSetupConfigurationFailedEventLog for language English (United States)
08/17/2009 17:12:59 1 INF Resource retrieved id PostSetupConfigurationFailedEventLog is Configuration of SharePoint Products and Technologies failed. Configuration must be performed in order for this product to operate properly. To diagnose the problem, review the extended error information located at {0}, fix the problem, and run this configuration wizard again.
08/17/2009 17:12:59 1 INF Leaving function StringResourceManager.GetResourceString
08/17/2009 17:12:59 1 ERR Configuration of SharePoint Products and Technologies failed. Configuration must be performed in order for this product to operate properly. To diagnose the problem, review the extended error information located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\PSCDiagnostics_8_17_2009_17_7_9_507_298886299.log, fix the problem, and run this configuration wizard again.
I actually found a reference to the solution in the comments in the Companyweb Inaccessible After Sharepoint 3.0 Service Pack 2 post. Not directly, but one of the comments mentions that an account name was changed after the initial setup. I haven’t renamed any accounts, but I was reminded that I was running the psconfig command under a different account than had been used to initially install the Sharepoint SP2 update. I logged out of that account and logged back in with the account that was used to install the update, and the psconfig command completed successfully.
Woo hoo! Got it working! Only, http://companyweb and the Sharepoint Central Administration 3.0 sites still would not come up. I once again connected to the database via SQL Management Studio (reminder: run that with elevated permissions or you’ll never authenticate successfully) and verified that it was not read only. And the services were running. I checked the web site configuration in IIS and found the issue – all of the web sites had stopped. That’s when I remembered getting all the alerts overnight about the World Wide Web Publishing Service and the TS Gateway service being stopped. I had started them again first thing this morning and promptly forgot about them. Sure enough, when I checked again, they were both stopped (not surprised that the TS Gateway service stopped since it’s dependent upon the WWW Publishing service). I started both services and both companyweb and Sharepoint Central Administration were back online.
And I was able to finally add the one security group I needed to get added.
Takeaways from this process that aren’t documented in the SBS blog posts:
- If the Sharepoint SP2 update doesn’t take the first time and you need to run the psconfig command manually to complete the install, make sure you are running the command from the same user account that was used to attempt to install SP2 in the first place.
- Note that the psconfig command stops the World Wide Web Publishing Service (and TS Gateway) and does NOT restart them automatically.
Adding IPv6 to DNS
Posted by: | CommentsThis weekend I noticed that NSLOOKUP on my SBS 2008 server is no longer able to return the local DNS server name. Maybe it’s just semantics because otherwise NSLOOKUP seems to work fine, just was bothering me. Having noticed that it is using the IPv6 address for NSLOOKUP resolution I knew right away what the problem was – there’s no IPv6 information in my DNS. Specifically NSLOOKUP uses the PTR record.
Here’s how to resolve that problem:
At this point we’re just using a LinkLocal IP address. All LinkLocal addresses start with the prefix fe80:: Which in ipv4 speak is like the 169.254…addressing. It doesn’t go anywhere, it is just for internal use.
- Create an IPv.6 AAAA host record in the .local zone
2. Create an IPv.6 reverse lookup zone for fe80::/64
3. Create a ptr record for the IPv6 address of the server. To do this use the browse option in the new PTR record window
Now NSLookup will know the name of the local DNS server.
—
So who wrote this blog and what do they do for a living anyway?
We’re Third Tier. We provide advanced Third Tier support for IT Professionals.
Get Support Blog Twitter Facebook LinkedIN
Entourage for Exchange Web Services Released
Posted by: | CommentsToday, Microsoft released an update to the Office 2008 suite that allows Entourage (the Exchange e-mail client) to connect to Exchange 2007 servers using Exchange Web Services instead of WebDAV. This update provides improvements in the calendar interface and allows Entourage to sync tasks, notes, and categories with Exchange server. While Entourage still lags terribly behind Outlook 2001 for Mac in terms of feature compatability with Exchange server, this update provides a much-awaited set of improvements for the Mac e-mail client.
Entourage 2008 Web Services edition requires Office 2008 with the 12.2.1 update installed. Unfortunately, Microsoft does not make the updates for Office for Mac cumulative, so if you install Office 2008 from the original media, you must first install Office 2008 SP1, then Office 2008 SP2, then the 12.2.1 Update before you will be able to install Entourage Web Services Edition. All of these downloads are available at the Mactopia download site, http://www.microsoft.com/mac/downloads.
Detailed information about how Entourage Web Services works and tips for how to upgrade to Entourage Web Services can be found at the Microsoft Mac IT Pros site, http://www.microsoft.com/mac/itpros/default.mspx.
Calyptix and Third Tier Partner to Support IT Professionals
Posted by: | CommentsAugust 12, 2009 – CHARLOTTE, NC & DETROIT, MI – Internet security firm, Calyptix Security, has partnered with Third Tier, a leading provider of remote support services for IT professionals and business owners. By combining efforts, the two companies offer IT professionals the broad spectrum of resources and expertise they need to deliver IT services at the highest level.
IT professionals can leverage the Calyptix-Third Tier relationship to offer services that will distinguish them in their marketplace and cement their customer relationships. This partnership creates access through a single platform to extensive expertise on Microsoft technologies, UNIX, networking and security matters.
Third Tier will work with Calyptix resellers as an operational resource as resellers integrate the AccessEnforcerTM into client networks with Microsoft’s Small Business Server, Essential Business Server and other solutions. Calyptix and Third Tier will also work together to provide enhanced services and troubleshooting tools to address specific needs of small and medium businesses (SMBs).
“I have worked closely with this partnership to deploy EBS with the AccessEnforcer and it was extremely helpful,” noted Wendy Frank of Accell, Inc., a Microsoft certified partner operating in the suburbs of Philadelphia. “Timely and affordable access to subject matter experts saves us time and money and ensures the best result for our clients.”
The AccessEnforcer all-in-one security appliance is purpose built for SMBs with all the necessary network security features needed to address today’s changing threat landscape with an affordable and easy to use solution. AccessEnforcer leverages the value of Microsoft’s Small Business Server 2008, which requires a separate perimeter firewall solution such as AccessEnforcer, with seamless integration with Microsoft’s Active Directory and reporting right out of the box.
“We’re excited about this partnership and the opportunity it presents to deliver a solution purpose built for small and medium businesses and the IT professionals they depend on,” comments Amy Babinchak, Managing Partner, Third Tier. “By combining our focus on the needs of small businesses, we are helping IT professionals deliver timely and affordable solutions to their customers.”
Third Tier provides remote support services for IT Professionals that serve the SMB market with immediate access to subject matter experts. This approach provides IT professionals a more efficient alternative to traditional vendor support. Third Tier consists of experts focused on SMB technologies such as Microsoft’s Small Business Server and counts Eriq Neale author of Windows Small Business Server 2008 Unleashed, among its members. Third Tier is also thoroughly trained in the operation and integration of the AccessEnforcer product line with other leading SMB solutions.
“This partnership provides a very powerful platform for our resellers to serve and grow their customer base,” comments Ben Yarbrough CEO of Calyptix. “By tapping Third Tier, our resellers can differentiate themselves by aligning with industry leading experts and services resources.”
ABOUT THIRD TIER
Third Tier provides remote support services for IT Professionals, consultants and business owners. Third Tier’s consultant staff includes expertise in a wide range of technologies including: Exchange, SQL, Sharepoint, Virtualization, DNS, Active Directory, DNS, Macintosh, AccessEnforcer, ISA, SBS, EBS and general networking. Partners Eriq Neale and Amy Babinchak have combined experience that makes Third Tier one of the most experienced SMB solution services and solutions providers in the industry. For more information about Third Tier, please visit www.thirdtier.net.
ABOUT CALYPTIX SECURITY
Calyptix manufactures and sells AccessEnforcer, an all-in-one security appliance tailored to work with Microsoft’s Small Business Server (SBS) 2008. AccessEnforcer provides comprehensive integrated network security and control of users, groups and devices from a single interface in a plug & play format that is simple to deploy, activate and maintain. AccessEnforcer is available through nearly 200 authorized resellers nationwide. For more information about Calyptix, please visit www.calyptix.com.
| Calyptix Contact: | Third Tier Contact: | |
| Ben Yarbrough, CEO | Amy Babinchak, Managing Partner | |
| 704.971.8989, byarbrough@calyptix.com | amy@thirdtier.net |
####
—
So who wrote this blog and what do they do for a living anyway?
We’re Third Tier. We provide advanced Third Tier support for IT Professionals.
Get Support Blog Twitter Facebook LinkedIN
Avoiding Trouble with Windows Updates
Posted by: | CommentsDo you ever wonder why there are so many sporadic one-off problems with Windows Update? Someone runs a .Net update and it breaks a lot of things, even though thousands of other admins have run that same patch without problems?
I think I might have an inkling why.
How many times have you been checking on a server right before lunch and saw an optimization you could easily make, made the change and then saw that the server wanted a reboot? It wasn’t that critical a change, and you can’t restart the system during business hours, so you add a task to your list to restart the server that evening. Or do you? Did you ever actually get around to it?
Maybe you download a patch for a known issue and then it calls for a reboot, and you decide that you might as well run some other updates before the reboot to get your downtime’s worth.
Both of these situations are much more likely to result in failed Windows Updates, since there are unresolved .dll, file and registry changes underway.
The best practice is to restart a server BEFORE you run Windows Update or any significant patches. You would do this in order to ensure that there are no subsystems that can’t be patched properly due to their already holding their breath for a reboot. So a good Windows Update procedure would involve at least two server restarts: one before the updates are run, and another after.
The truth is, if your servers run for 30+ days between reboots, it’s fairly common for them to begin to accumulate some of these “pending reboot” situations, and if you don’t resolve those before doing any serious patching, you may end up with unpredictable results.
—
So who wrote this blog and what do they do for a living anyway?
We’re Third Tier. We provide advanced Third Tier support for IT Professionals.
Get Support Blog Twitter Facebook LinkedIN
