The server-packages of October 2009 Cumulative Update for Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0 are ready for download. October 2009 Cumulative Updates introduce more rules on Pre-Upgrade Checker, which can help customers to prepare the upgrade of their SharePoint farm to SharePoint 2010
Download Information
Windows SharePoint Services 3.0 October 2009 cumulative update package
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=974989
Office SharePoint Server 2007 October 2009 cumulative update package
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=974988
A Share Point of View
Showing posts with label SharePoint - Administration. Show all posts
Showing posts with label SharePoint - Administration. Show all posts
Thursday, November 12, 2009
Friday, September 4, 2009
Announcing the Fourth Release of the Microsoft SharePoint Administration Toolkit
The fourth version of the Microsoft SharePoint Administration Toolkit is available for download! This toolkit services both Microsoft Office SharePoint Server 2007 and Windows SharePoint Services v3.0.
For installation instructions, see
WSS: Installing the SharePoint Administration Toolkit (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc508987.aspx)
Installing the SharePoint Administration Toolkit (Office SharePoint Server) (http://technet.microsoft.com/en-us/library/cc508849.aspx)
For more detailed information about the SharePoint Administration Toolkit, see following documentation on TechNet:
SharePoint Administration Toolkit (Office SharePoint Server) (http://technet.microsoft.com/library/cc508851.aspx)
SharePoint Administration Toolkit (Windows SharePoint Services) (http://technet.microsoft.com/en-us/library/cc508986.aspx)
The download links for the SharePoint Administration Toolkit v4.0
x64: http://www.microsoft.com/downloads/details.aspx?FamilyID=665e98ea-5318-486d-aba2-2bfe46254357 (http://go.microsoft.com/fwlink/?LinkID=142035)
x86: http://www.microsoft.com/downloads/details.aspx?FamilyID=cd2d09a7-1159-4d40-be1c-8efab1345381 (http://go.microsoft.com/fwlink/?LinkId=141504)
Monday, August 31, 2009
Office Service Packs – more and more
| Office Client Products | ||
| The 2007 Microsoft Office Suite Service Pack 2 | Download | 953195 |
| Microsoft Office Language Pack 2007 Service Pack 2 | Download | 953195 |
| Microsoft Office Project 2007 Service Pack 2 | Download | 953326 |
| Microsoft Office Project Language Pack 2007 Service Pack 2 | Download | 953326 |
| Microsoft Office SharePoint Designer 2007 Service Pack 2 | Download | 953292 |
| Microsoft Office SharePoint Designer Language Pack 2007 Service Pack 2 | Download | 953292 |
| Microsoft Office Visio 2007 Service Pack 2 | Download | 953327 |
| Microsoft Office Visio Language Pack 2007 Service Pack 2 | Download | 953327 |
| Microsoft Office Proofing Tools 2007 Service Pack 2 | Download | 953328 |
| Microsoft Office Access Runtime and Data Connectivity Components 2007 Service Pack 2 | Download | 957262 |
| Calendar Printing Assistant for Microsoft Office Outlook 2007 Service Pack 2 | Download | 953329 |
| Microsoft Office Compatibility Pack Service Pack 2 | Download | 953331 |
| Excel Viewer 2007 Service Pack 2 | Download | 953336 |
| PowerPoint Viewer 2007 Service Pack 2 | Download | 953332 |
| Visio Viewer 2007 Service Pack 2 | Download | 953335 |
| Microsoft Office Language Interface Pack 2007 Service Pack 2 | Download | 953339 |
| Microsoft Service Pack Uninstall Tool for the 2007 Microsoft Office Suite | Download | 954914 |
| Office server products | ||
| The 2007 Microsoft Office servers Service Pack 2 | Download | 953334 |
| The 2007 Microsoft Office servers Service Pack 2, 64-bit edition | Download | 953334 |
| The 2007 Microsoft Office servers Language Pack Service Pack 2 | Download | 953334 |
| The 2007 Microsoft Office servers Language Pack Service Pack 2, 64-bit edition | Download | 953334 |
| Windows SharePoint Services 3.0 products | ||
| Windows SharePoint Services 3.0 Service Pack 2 | Download | 953338 |
| Windows SharePoint Services 3.0 Service Pack 2, 64-bit edition | Download | 953338 |
| Windows SharePoint Services 3.0 Language Pack Service Pack 2 | Download | 953338 |
| Windows SharePoint Services 3.0 Language Pack Service Pack 2, 64-bit edition | Download | 953338 |
| Windows SharePoint Services 3.0 with Service Pack 2 | Download | |
| Windows SharePoint Services 3.0 x64 with Service Pack 2 | Download |
Tuesday, June 16, 2009
Installing SharePoint on Windows Server 2008 R2
With Windows Server 2008 R2 available as a release candidate, you may have tried installing MOSS on it already without success and received an error similar to this: "The program is blocked due to compatibility issues".
SharePoint SP2 enables compatibility with Server 2008 R2, so first you've got to make a slipstream install -- then you can install without any problem.
The steps for making a slipstreamed installation of MOSS are pretty simple.
For more details, follow the technet article:
http://technet.microsoft.com/en-us/library/cc261890.aspx
Once you have your slipstream image ready, you'll need to enable a few roles on your Server 2008 R2 box.
SharePoint SP2 enables compatibility with Server 2008 R2, so first you've got to make a slipstream install -- then you can install without any problem.
The steps for making a slipstreamed installation of MOSS are pretty simple.
- Download a MOSS image, and extract it (or copy the contents) to a folder.
- Download WSS and MOSS SP2 patches
- Run each patch with /extract:<\mymossimage>\Updates
- Delete Wsssetup.dll from the updates folder.
- Keep in mind that if you have the combined x86/64 MOSS ISO, your updates folder will be in \x64\Updates or \x86\Updates.
For more details, follow the technet article:
http://technet.microsoft.com/en-us/library/cc261890.aspx
Once you have your slipstream image ready, you'll need to enable a few roles on your Server 2008 R2 box.
Friday, June 12, 2009
SharePoint 2007 Outgoing E-mail Troubleshooting Tips
Tip #1
Talk to your networking/mail team and get the SMTP server address and port
Tip #2
Go to the index server and open a command prompt and use the basic old school dos command “telnet”.
telnet smtp.server.com 25
(Typically SMTP operates over port 25, but your company may be different.)
What will happen with this command is one of two things:
If it opens up and basically looks like a blank screen, that means that the SharePoint server can talk to the SMTP server fine.
If it tells you something along the lines of “connect failed”, you know that your SharePoint server can’t talk to the SMTP server. What you should then do is talk to your networking team and make sure that your SMTP server allows connections from your SharePoint server. Once that is done, retest your telnet command.
Tip #3
If your networking team says that you have the server correct, port correct and that there is no reason your server can’t connect to the SMTP, then check your SharePoint server and see if its running any antivirus. The past few clients have been running McAFee antivirus. In its Access Prevention Task, "Prevent mass mailing worms from sending mail" has been enabled and that was blocking the server from connecting to the SMTP server over port 25. As soon as I disabled that I was able to telnet in without issues and then I was able to send email from SharePoint without issue.
I am not sure about the other antivirus vendors but I am sure they have something similar, so check the settings to see if they block port 25.
Tip #4
Check to make sure that Windows Firewall is not blocking port 25, if it is, make sure that you add 25 as an exception.
Talk to your networking/mail team and get the SMTP server address and port
Tip #2
Go to the index server and open a command prompt and use the basic old school dos command “telnet”.
telnet smtp.server.com 25
(Typically SMTP operates over port 25, but your company may be different.)
What will happen with this command is one of two things:
If it opens up and basically looks like a blank screen, that means that the SharePoint server can talk to the SMTP server fine.
If it tells you something along the lines of “connect failed”, you know that your SharePoint server can’t talk to the SMTP server. What you should then do is talk to your networking team and make sure that your SMTP server allows connections from your SharePoint server. Once that is done, retest your telnet command.
Tip #3
If your networking team says that you have the server correct, port correct and that there is no reason your server can’t connect to the SMTP, then check your SharePoint server and see if its running any antivirus. The past few clients have been running McAFee antivirus. In its Access Prevention Task, "Prevent mass mailing worms from sending mail" has been enabled and that was blocking the server from connecting to the SMTP server over port 25. As soon as I disabled that I was able to telnet in without issues and then I was able to send email from SharePoint without issue.
I am not sure about the other antivirus vendors but I am sure they have something similar, so check the settings to see if they block port 25.
Tip #4
Check to make sure that Windows Firewall is not blocking port 25, if it is, make sure that you add 25 as an exception.
Sunday, May 17, 2009
How to move a SharePoint Content Database
Here are step by step instructions for moving your MOSS content database to a new server, followed by the things to watch out for.
You have two initial options, doing a backup and restore within MOSS to move the data, or doing it at the SQL/STSADM level. I prefer the latter, as it isn't nearly as inclined to fail and leaves you with more flexibility.
1) Find the content Database,
These are listed under Central Admin->Application Management->Site Collection List
2) Backup the content database,
You could alternatively detach it, and copy it. Just doing a backup in SQL Server Management studio is easier.
3) Restore content database to new server
Copy the BAK file to new server. Create an empty DB in Management Studio, restore from backup, you may need to change an option in the "options" tab of the restore dialog to get it to work. (Overwrite db).
4) Create Web App on new Server
Central Admin->Application Management->Create or extend Web App->Create New Web App.
5) Associate restored DB with new Web App
Central Admin->Application Management->
SharePoint Web Application Management->Content Databases->
Remove Content Database from your new web app.
Now use STSADM to add restored DB to this web app
c:\program files\common files\microsoft shared\web server extentions\12\bin on new server is where you can find the STSADM.
run this command from there.
stsadm -o addcontentdb -url http://yourwebapp:port -databasename yourcontentdb -databaseserver yoursqlserver
6) Run ISSRESET from command prompt
Important :
You have two initial options, doing a backup and restore within MOSS to move the data, or doing it at the SQL/STSADM level. I prefer the latter, as it isn't nearly as inclined to fail and leaves you with more flexibility.
1) Find the content Database,
These are listed under Central Admin->Application Management->Site Collection List
2) Backup the content database,
You could alternatively detach it, and copy it. Just doing a backup in SQL Server Management studio is easier.
3) Restore content database to new server
Copy the BAK file to new server. Create an empty DB in Management Studio, restore from backup, you may need to change an option in the "options" tab of the restore dialog to get it to work. (Overwrite db).
4) Create Web App on new Server
Central Admin->Application Management->Create or extend Web App->Create New Web App.
5) Associate restored DB with new Web App
Central Admin->Application Management->
SharePoint Web Application Management->Content Databases->
Remove Content Database from your new web app.
Now use STSADM to add restored DB to this web app
c:\program files\common files\microsoft shared\web server extentions\12\bin on new server is where you can find the STSADM.
run this command from there.
stsadm -o addcontentdb -url http://yourwebapp:port -databasename yourcontentdb -databaseserver yoursqlserver
6) Run ISSRESET from command prompt
Important :
- Make sure your running the same service pack level on both source and destination sharepoint if possible.
- Make sure you install all webparts, solutions, features, etc on new server before you restore the content database, so that it can find all the features it's looking for
- Make sure you copy any files that may be living in the file system that you need, sometimes people have css/javascript here. (This refers to files in the hive)
- Leave your old site and contentDB intact until you get the backup running on the new server, this way your ok if there is a problem
- DON'T try this with your config database! It won't work
Saturday, May 16, 2009
Configure SharePoint list to receive incoming emails from external senders
I found the following post and it was very helpful
https://exchange.readyexchange.net/support/kb/default.asp?id=1558
https://exchange.readyexchange.net/support/kb/default.asp?id=1558
Subscribe to:
Posts (Atom)