Category:: Problems faced during SharePoint 2007 installation
1) Install IIS --> Configure ur server wizard
2) install .net 2.0
3) install .net 3.0 framework.
After this installation, ASP.NET v2.0.50727 should appear in inetmgr/internet manager. Well the problem happens when it doesn't appear in web server extensions.
One solution is to remove .NET Framework 3.0 SP1 and .NET Framework 2.0 SP1 then download the .NET Framework 2.0 and 3.0.
After installing .NET Framework 2.0 the ASP.NET v2.0.40727 will show up.
well the shortcut is:
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727> or C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727> for 64 bit
Type aspnet_regiis.exe – i
ASP.NET will register itself and show up in Web Service Extensions!
Thursday, November 6, 2008
Tuesday, August 19, 2008
How to upgrade sites built on custom site definitions not available in MOSS?
How to upgrade Sites built on custom site definitions not available in MOSS?
Category: Common Problems faced during Upgrade from SPS2003 to MOSS2007
Problem/ Scenario: We are doing Gradual Upgrade approach for upgrading SPS 2003 to SharePoint 2007. The upgrade fails in between as the sites are made out of custom site definition which is not available in sharepoint 2007.
Cause: For the upgrade,custom site definition has to be there at the source as well as the destination. Upgrade fails if it is not there. In our case, our sites were built on 'STSCLIENTITSITES' custom site definition which was not present in MOSS. So the upgrade fails.
Solution:
Make a copy of the site definitiona from which the custom site definition was made. Rename it to 'STSCLIENTITSITES' or the custom site definition name. The template ID in the definition should match the template ID in STSCLIENTITSITES.
Now run the gradual upgrade.
Category: Common Problems faced during Upgrade from SPS2003 to MOSS2007
Problem/ Scenario: We are doing Gradual Upgrade approach for upgrading SPS 2003 to SharePoint 2007. The upgrade fails in between as the sites are made out of custom site definition which is not available in sharepoint 2007.
Cause: For the upgrade,custom site definition has to be there at the source as well as the destination. Upgrade fails if it is not there. In our case, our sites were built on 'STSCLIENTITSITES' custom site definition which was not present in MOSS. So the upgrade fails.
Solution:
Make a copy of the site definitiona from which the custom site definition was made. Rename it to 'STSCLIENTITSITES' or the custom site definition name. The template ID in the definition should match the template ID in STSCLIENTITSITES.
Now run the gradual upgrade.
Tuesday, July 22, 2008
How to detect, repair and delete Orphan objects in SharePoint?
Category: Common Problems faced during Upgrade from SPS2003 to MOSS2007
Problem:
How to detect Orphan objects? How to remove or delete Orphans from the system?
Scenario:
We are doing Gradual upgrade approach for upgrading SPS 2003 to SharePoint 2007. During the root site upgrade, it failed saying that there are orphans in the sites.
Solution:
What is an Orphan Site?
An Orphaned Site is where SharePoint only has partial information and not a complete set of data for a given site collection in your Windows SharePoint Services or SharePoint Portal Server content databases or configuration databases. The site may in fact still be viewable via the browser, but you may notice that many things are broken. 99% of the cases I have seen though, the orphaned site is just unavailable.
How to detect Orphan Site?
To detect orphaned items, use the Stsadm command:
stsadm -o databaserepair -url http:// -databasename
This would return a XML with the orphan sites (if they exist) details as mentioned below:
Refer to ‘http://technet.microsoft.com/en-us/library/cc263282(TechNet.10).aspx’ for details on this stsadm command.
How to delete or remove orphan site?
To delete orphaned items, use the following stsadm command:
stsadm -o databaserepair -url http:// -databasename -deletecorruption
This command repairs corruption in the content database but sometimes it can’t remove corruption in the configuration database.
Here Spsadm tool comes into picture. Spsadm cleans up orphaned items in the configuration database in Sharepoint server 2003.
spsadm repairorphans http://Server1
Refer to ‘http://support.microsoft.com/kb/918742’ for more details on this command.
How to handle the worst kind of Orphan sites?
It happened to us in one of our upgrade phases. Our gradual upgrade was failing due to an Orphan site. We tried to repair the corrupted site using stsadm –databaserepair but it didn’t help. So I turned to SPSADM. That also didn’t help. The orphan site was not even getting deleted from the frontend.
So the only option was to somehow delete the site from the database. THOUGH THIS IS NOT A RECOMMENDED MICROSOFT APPROACH, we were left with only this option.
1) Find out the Site ID of the orphan site. You will get this from the orphan XML.
Check its entry in Webs table.
select * from webs where id = 'A7A18BB5-A483-4979-8038-0DA388CBC3E0'
For deleting an orphan site or web from the database, you have to delete its entry from webgroupmembership, webmembers & webs table, as shown below:
delete from webgroupmembership where webid= ‘A7A18BB5-A483-4979-8038-0DA388CBC3E0'
delete from webmembers where webid= ‘A7A18BB5-A483-4979-8038-0DA388CBC3E0'
delete from webs where id = 'A7A18BB5-A483-4979-8038-0DA388CBC3E0'
2) In our case, we had three orphan lists as well. You can see the lists in the xml (Output of stsadm –databaserepair command)
For deleting an orphan list from the database, delete its entry from Userdata, docs & aptb_lists sharepoint tables.
delete from aptb_lists where tp_id = '4202479A-706D-4416-ADCB-35410EAA7672' (corrupted List)
delete from aptb_lists where tp_id = 'B2A38B61-CC99-4528-A6B4-365019BB5B03' (corrupted List)
delete from aptb_lists where tp_id = 'FD65BF5F-D120-4A41-A2AB-63A6BA60C45' (corrupted List)
Similarly check for the list id entry in Docs & userdata and delete those entries from it.
***Either Stsadm -databaserepair or spsadm -repairorphans or deleting from database should solve the ORPHANED object problem for you.
Problem:
How to detect Orphan objects? How to remove or delete Orphans from the system?
Scenario:
We are doing Gradual upgrade approach for upgrading SPS 2003 to SharePoint 2007. During the root site upgrade, it failed saying that there are orphans in the sites.
Solution:
What is an Orphan Site?
An Orphaned Site is where SharePoint only has partial information and not a complete set of data for a given site collection in your Windows SharePoint Services or SharePoint Portal Server content databases or configuration databases. The site may in fact still be viewable via the browser, but you may notice that many things are broken. 99% of the cases I have seen though, the orphaned site is just unavailable.
How to detect Orphan Site?
To detect orphaned items, use the Stsadm
stsadm -o databaserepair -url http://
This would return a XML with the orphan sites (if they exist) details as mentioned below:
Refer to ‘http://technet.microsoft.com/en-us/library/cc263282(TechNet.10).aspx’ for details on this stsadm command.
How to delete or remove orphan site?
To delete orphaned items, use the following stsadm command:
stsadm -o databaserepair -url http://
This command repairs corruption in the content database but sometimes it can’t remove corruption in the configuration database.
Here Spsadm tool comes into picture. Spsadm
spsadm repairorphans http://Server1
Refer to ‘http://support.microsoft.com/kb/918742’ for more details on this command.
How to handle the worst kind of Orphan sites?
It happened to us in one of our upgrade phases. Our gradual upgrade was failing due to an Orphan site. We tried to repair the corrupted site using stsadm –databaserepair but it didn’t help. So I turned to SPSADM
So the only option was to somehow delete the site from the database. THOUGH THIS IS NOT A RECOMMENDED MICROSOFT APPROACH, we were left with only this option.
1) Find out the Site ID of the orphan site. You will get this from the orphan XML.
Check its entry in Webs table.
select * from webs where id = 'A7A18BB5-A483-4979-8038-0DA388CBC3E0'
For deleting an orphan site or web from the database, you have to delete its entry from webgroupmembership, webmembers & webs table, as shown below:
delete from webgroupmembership where webid= ‘A7A18BB5-A483-4979-8038-0DA388CBC3E0'
delete from webmembers where webid= ‘A7A18BB5-A483-4979-8038-0DA388CBC3E0'
delete from webs where id = 'A7A18BB5-A483-4979-8038-0DA388CBC3E0'
2) In our case, we had three orphan lists as well. You can see the lists in the xml (Output of stsadm –databaserepair command)
For deleting an orphan list from the database, delete its entry from Userdata, docs & aptb_lists sharepoint tables.
delete from aptb_lists where tp_id = '4202479A-706D-4416-ADCB-35410EAA7672' (corrupted List)
delete from aptb_lists where tp_id = 'B2A38B61-CC99-4528-A6B4-365019BB5B03' (corrupted List)
delete from aptb_lists where tp_id = 'FD65BF5F-D120-4A41-A2AB-63A6BA60C45' (corrupted List)
Similarly check for the list id entry in Docs & userdata and delete those entries from it.
***Either Stsadm -databaserepair or spsadm -repairorphans or deleting from database should solve the ORPHANED object problem for you.
Tuesday, July 15, 2008
How to update link between Recurring meeting workspace and the outlook meeting after SPS 2003 upgrade to MOSS 2007
Category: Common SPS2003 to MOSS upgrades issues:
Problem: When you migrate/ upgrade Recurring meetings, the data in the meeting workspace get migrated properly but the links between outlook calendar and the meeting workspace gets broken.
Scenario: This is a known issue with SharePoint upgrade. When you upgrade SharePoint, recurring meeting link with outlook gets broken. There is no way to directly update the link. The data in the recurring meeting workspace will be migrated. Also you would be able to see the old meeting in the outlook calendar but when you open the meeting, it will no longer be connected to the sharepoint meeting workspace. And it won’t allow you to even update the link.
Solution / Workaround: There is a Microsoft tool for exchange server which exposes the raw data of Outlook. Using this tool, you can again establish link with the migrated recurring meeting workspace.
Below are the steps on how to use this tool:
Step 1) Go To http://www.microsoft.com/downloads/details.aspx?FamilyID=55FDFFD7-1878-4637-9808-1E21ABB3AE37&displaylang=endownloads/details.aspx?FamilyID=55FDFFD7-1878-4637-9808-1E21ABB3AE37&displaylang=en
Click on ‘Download ‘and follow the setup. It will extract MFCMAPI files as shown in the figure 1
Figure 1
Step 2) Close your Outlook in case it is Open
Step 3) Click on ‘mfcmapi.exe’ à it will open up a window as shown in figure 2
Figure 2
Step 4) Click on OK on that window à Click on Session from the Menu à Click on ‘Logon and Display Store Table’ as shown in Figure 3
Figure 3
Step 5) Profile Name will automatically come as ‘Outlook’ à Click on OK
In the upper table, double click on “Mailbox -” to open up a new window as shown in Figure 4
Figure 4
Step 6) On the tree in the left navigation menu, double click on ‘select Root – Mailbox à IPM_SUBTREE à Calendar’ as shown in the figure above. It will open up the calendar in new window as shown in the figure 5. Select the recurring meeting you want to relink.
Figure 5
Step 7) In the lower table, double click on the URL in the Value column as shown in the figure 6 and 7 below.
Figure 6
Figure 7
Step 7) Change the URL of the workspace here and click on OK à Exit the window
Step 8) Open your recurring meeting. It has been linked to the new site URL of Step 7
Step 9) Note: the link on the outlook meeting will not change. Please delete the existing link and paste the new link into the outlook meeting body.
After doing this, the recurring meeting will be linked again! :-)
Problem: When you migrate/ upgrade Recurring meetings, the data in the meeting workspace get migrated properly but the links between outlook calendar and the meeting workspace gets broken.
Scenario: This is a known issue with SharePoint upgrade. When you upgrade SharePoint, recurring meeting link with outlook gets broken. There is no way to directly update the link. The data in the recurring meeting workspace will be migrated. Also you would be able to see the old meeting in the outlook calendar but when you open the meeting, it will no longer be connected to the sharepoint meeting workspace. And it won’t allow you to even update the link.
Solution / Workaround: There is a Microsoft tool for exchange server which exposes the raw data of Outlook. Using this tool, you can again establish link with the migrated recurring meeting workspace.
Below are the steps on how to use this tool:
Step 1) Go To http://www.microsoft.com/downloads/details.aspx?FamilyID=55FDFFD7-1878-4637-9808-1E21ABB3AE37&displaylang=endownloads/details.aspx?FamilyID=55FDFFD7-1878-4637-9808-1E21ABB3AE37&displaylang=en
Click on ‘Download ‘and follow the setup. It will extract MFCMAPI files as shown in the figure 1
Figure 1
Step 2) Close your Outlook in case it is Open
Step 3) Click on ‘mfcmapi.exe’ à it will open up a window as shown in figure 2
Figure 2
Step 4) Click on OK on that window à Click on Session from the Menu à Click on ‘Logon and Display Store Table’ as shown in Figure 3
Figure 3
Step 5) Profile Name will automatically come as ‘Outlook’ à Click on OK
In the upper table, double click on “Mailbox -
Figure 4
Step 6) On the tree in the left navigation menu, double click on ‘select Root – Mailbox à IPM_SUBTREE à Calendar’ as shown in the figure above. It will open up the calendar in new window as shown in the figure 5. Select the recurring meeting you want to relink.
Figure 5
Step 7) In the lower table, double click on the URL in the Value column as shown in the figure 6 and 7 below.
Figure 6
Figure 7
Step 7) Change the URL of the workspace here and click on OK à Exit the window
Step 8) Open your recurring meeting. It has been linked to the new site URL of Step 7
Step 9) Note: the link on the outlook meeting will not change. Please delete the existing link and paste the new link into the outlook meeting body.
After doing this, the recurring meeting will be linked again! :-)
Saturday, February 2, 2008
How to move upgraded SPS sites under one site collection in MOSS - sharing single Content Database?
Category: Common Problems faced during Upgrade from SPS2003 to MOSS2007
Problem:
How to migrate 2 or more site collections from SPS to MOSS – under one site collection and wherein the migrated site collections should share the same content DB?
Scenario:
In SPS 2003, there is only one content database and in MOSS we want a separate content database for each site collection.
HR and IT are two site collections in SPS.
http://SPSprod/sites/IT & http://SPSprod/sites/HR
In MOSS, we want to migrate this under one site collection CORP i.e. http://MOSSprod/CORP/IT & http://MOSSprod/CORP/HR. Our aim is to get one content database for CORP. HR and IT will reside under CORP and will share the same Content database.
For getting data specific to HR and IT only from SPS2003 database, we used STSADM
STSADM.exe –o backup http://SPSprod/sites/IT -filename backup_IT.bak
STSADM.exe –o backup http://SPSprod/sites/HR -filename backup_HR.bak
Solution:
Create the site collection ‘CORP’ under web application ‘MOSSprod’. As MOSSprod already has one more site collection, we needed to create a separate content DB for CORP. For that I followed the below steps:
1) Go to MOSS Central Administration à Go to Application Management à Click on Content Databases under SharePoint web application management à Click on MOSSprod’s content DB and ‘Manage Content database settings’ page appears. Make MOSSprod’s content DB OFFLINE.
2) Create a new content database and put 15000 or any larger no in Maximum number of Sites column. Make sure the sum between “Current number of Sites” and “Maximum number of Sites” is the largest in the Content database you want to use before you run the stsadm – restore command.
3) Create site collection ‘CORP’ under MOSSprod web application. In our case, we did it through STSADM. We restored the migrated sites from SPS2003 to MOSSprod such that all sites under CORP use one content DB.
Stsadm.exe –o restore http://MOSSprod/CORP/ -filename backup_IT.bak
Stsadm.exe –o restore http://MOSSprod/CORP/ -filename backup_HR.bak
As the MOSSprod original content DB is offline, system sees the new content DB which is available and restores the data there.
Problem:
How to migrate 2 or more site collections from SPS to MOSS – under one site collection and wherein the migrated site collections should share the same content DB?
Scenario:
In SPS 2003, there is only one content database and in MOSS we want a separate content database for each site collection.
HR and IT are two site collections in SPS.
http://SPSprod/sites/IT & http://SPSprod/sites/HR
In MOSS, we want to migrate this under one site collection CORP i.e. http://MOSSprod/CORP/IT & http://MOSSprod/CORP/HR. Our aim is to get one content database for CORP. HR and IT will reside under CORP and will share the same Content database.
For getting data specific to HR and IT only from SPS2003 database, we used STSADM
STSADM.exe –o backup http://SPSprod/sites/IT -filename backup_IT.bak
STSADM.exe –o backup http://SPSprod/sites/HR -filename backup_HR.bak
Solution:
Create the site collection ‘CORP’ under web application ‘MOSSprod’. As MOSSprod already has one more site collection, we needed to create a separate content DB for CORP. For that I followed the below steps:
1) Go to MOSS Central Administration à Go to Application Management à Click on Content Databases under SharePoint web application management à Click on MOSSprod’s content DB and ‘Manage Content database settings’ page appears. Make MOSSprod’s content DB OFFLINE.
2) Create a new content database and put 15000 or any larger no in Maximum number of Sites column. Make sure the sum between “Current number of Sites” and “Maximum number of Sites” is the largest in the Content database you want to use before you run the stsadm – restore command.
3) Create site collection ‘CORP’ under MOSSprod web application. In our case, we did it through STSADM. We restored the migrated sites from SPS2003 to MOSSprod such that all sites under CORP use one content DB.
Stsadm.exe –o restore http://MOSSprod/CORP/ -filename backup_IT.bak
Stsadm.exe –o restore http://MOSSprod/CORP/ -filename backup_HR.bak
As the MOSSprod original content DB is offline, system sees the new content DB which is available and restores the data there.
Subscribe to:
Posts (Atom)