Posted by tommysegoro
No Comments »
Hi guys,
I’ve been able to upgrade MOSS 2007 to Sharepoint 2010. I’ve tried both in-place upgrade and attaching content database.
The in-place upgrade failed twice so I’ve given up however attaching content database succeeded! I think this will be the way to go.
For more details please go to http://sp2010journal.blogspot.com.
Cheers,
Tommy
Posted by tommysegoro
No Comments »
CompleteSharepoint.NET is a content management system written on top of Windows Sharepoint Services 3.0.
It’s now Sharepoint 2010 compatible and proven. NOTE: Use this for new installation only. Do NOT attempt to upgrade your MOSS 2007/WSS 3.0 to SP 2010 just yet.
See here: http://sp2010journal.blogspot.com/2010/02/completesharepointnet-is-sp2010.html
Posted by tommysegoro
No Comments »
Hi everyone, I’ve played around with SP 2010 BETA and VS 2010 BETA for quiet some time now. Just in case you’re interested, please check http://sp2010journal.blogspot.com for my findings.
Cheers,
Tommy
INTRODUCTION
You’ve broken permission inheritance on a particular site in the hope that you can secure that site only to your GMs and Managers. You broke the permission inheritance, remove ALL users and groups and then re-add only GMs and Managers group. A GM tried to access the site and he get Access Denied message although he has been added to the GMs group.
RESOLUTION
It seems that there is a bug with Sharepoint whereby if you follow these process:
1. Break inheritance
2. Remove ALL permissions
3. Only re-add the required ones
Sharepoint will give you Access Denied message whatsoever unless you’re a Site Collection Admin.
To overcome it:
1. Re-inherit the permissions
2. Only take out permissions that you don’t want to be there (ie. don’t remove everything and re-add but instead just leave the ones you want to have access to the site). In this case, only leave GMs and Managers group in there.
Hope this helps,
Tommy
Hi everyone,
I have started a new blog dedicated for my experience using SharePoint 2010 on http://sp2010journal.blogspot.com/.
I will still though writing my experience about WSS 3.0 and MOSS 2007 here.
If you have time please visit my blog and hopefully it will give you a lot of information regarding SP 2010. At the time of writing this article, that blog is still pretty much empty.
Cheers,
Tommy
Posted by tommysegoro
No Comments »
INTRODUCTION
I had this error when I tried to publish an InfoPath template to Sharepoint or when I tried to fill in an InfoPath form and submit it.
RESOLUTION
I resolved it by making the content DB offline, DELETE the whole web-application, RE-CREATE it and re-attach the content DB.
I think it has something to do with the corrupted Sharepoint IIS website. Somehow office client can’t recognize it as a valid Sharepoint website although if I go to the browser and type in the URL manually (eg. http://intranet), it renders as a proper Sharepoint site without any error.
Hope this helps,
Tommy
Posted by tommysegoro
No Comments »
INTRODUCTION
I had this experience before where Sharepoint Designer Workflows suddenly decide to stop sending email.
RESOLUTION
This resolution sounds simple but it in fact fixes it. Thanks to my colleague Tim Allingham who actually found the solution.
Go to Workflow Tasks list of the site where the lists that have the Sharepoint Designer Workflow resides, then go to Settings -> Advanced Settings.
Under E-Mail Notification,set “No” on Send e-mail when ownership is assigned. Click OK.
After that, go back again to this setting page and now set to “Yes” and click OK.
This seems reset the Sharepoint Designer email and fixed the problem.
If this still doesn’t work, it may due to the timer job crashing/corrupted. To fix it, stop Windows Sharepoint Timer service then go to C:\Documents and Settings\All Users\Application Data\Microsoft\Sharepoint\Config\<GUID>. Delete the files within the <GUID> folder, then re-enable the Windows Sharepoint Timer service again. This will reset the Sharepoint Config DB cache and will fix the timer job.
Hope this helps,
Tommy
INTRODUCTION
Sharepoint VNext 2010 is coming up so I have to make sure that CompleteSharepoint.NET – the content management system built on top of WSS 3.0 (http://www.completesharepoint.net) – is compatible.
So I run stsadm -o preupgradecheck and below is the results:
Luckily CS.NET is vNext 2010 compatible! WOOHOO! Please note though that I ran this on a Windows Server 2008 x64 bit environment. Sharepoint vNext 2010 only works on a x64 bit environment and to be precise, it can only run on IIS version 7 onwards. Windows Server 2003 will not be supported.
Your SQL Server has to be x64 bit as well. It has to be SQL 2005 onwards.
Below is the results from the HTML report:
==
| Information Only : Supported upgrade types |
The current farm supports the following upgrade types:
|
There are other text in the report which I haven't included in this article but the main thing is, I didn't get any error message in the report. Some of the elements (such as custom field types) won't be upgraded automatically (ie. need to be upgraded manually).
==
Therefore, if you have used CompleteSharepoint.NET for your client website you'll be able to upgrade to the next version of Sharepoint when it arrives.
I'll keep you posted about the upgrade process.
Cheers and please stay tuned,
Tommy
INTRODUCTION
Hi everyone, a client has been using CompleteSharepoint.NET as their website framework.
If you're interested, please go to http://www.attadalechiropractic.com. They're chiropractor based in Attadale, Western Australia.
The features of the website are:
- Random quote generated from a Sharepoint list
- Custom navigation controls
- The use of CompleteSharepoint.NET custom sitemap provider
If you're interested in using CompleteSharepoint.NET for your personal and clients' website, please go to http://www.completesharepoint.net.
Some other websites that have been using CS.NET:
- http://www.bmuu.com.au
- http://www.tommyfrancesca.com
- http://www.completesharepoint.net
Cheers,
Tommy
Posted by tommysegoro
No Comments »
INTRODUCTION
The client I'm currently working has the following farm configuration:
- 1 WFE
- 1 Central Admin + Indexing
- 1 DB
They have both Test and Prod environments configured with the same number of servers.
After a while, the client starts to find out that although User Profile Import service is running successfully nightly and the data is updated correctly from AD, but somehow the WSS Profile Page is not updated with the latest AD data. There is someone whose job title is updated in AD and it hasn't been replicated in WSS Profile Page although this person's My Site page and search results page are already updated with the correct data. This problem happens in both Test and Prod.
After a day worth of investigation I found out that the secure certificate for Office Server Web Services web site needs updating.
Below are some of the warnings in Event Viewer:
==
Microsoft.Office.Server.UserProfiles.UserProfileException: Failed to obtain crawl status. —> System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. —> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.
==
WHAT DOES IT CAUSE?
With MOSS there are two profile "area" that needs to be updated, MOSS Profile and WSS Profile page.
My Sites and search results page are displaying information from MOSS Profile Page but Contact Details web-part and People And Groups -> All People display information from WSS Profile Page.
Because of this issue, the WSS Profile Page is not updated and causing Contact Details web-part to display incorrect (old) information about someone's profile.
HOW DO YOU SOLVE IT?
After reading some blogs about the error, I finally came up with a solution:
1. Use SelfSSL to update Office Server Web Services web site. Run the following command:
selfssl /S:<site ID of Office Web Services – mine is 951338967> /V:999999
2. Perform full User Profile import in SSP
3. Run stsadm -o sync -deleteolddatabases 0 –> This is to remove the failed-to-sync database information (don't worry it's safe. It's not deleting the actual content database or anything like that)
3. Run stsadm -o sync -sweeptiming m:2 -synctiming m:3 –> This is to sync the WSS Profile Page every 2 minutes, we'll change this later to every day or every 12 hours once we've known that we've solved the problem.
4. Wait for 2-3 minutes.
5. Open Event Viewer and you shouldn't see any more of the above warnings.
6. Go to Central Admin -> Operations -> Timer Job Status -> Profile Synchronization and Quick Profile Synchronization, they will run successfully.
7. DONE, run stsadm -o sync -sweeptiming h:12 -synctiming h:12 –> To set the WSS Profile Update every 12 hours.
That's it.
Hope this helps,
Tommy
Microsoft.Office.Server.UserProfiles.UserProfileException: Failed to obtain crawl status. —> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. —> System.IO.IOException: Authentication failed because the remote party has closed the transport stream.