We are receiving this error while trying to create a page in a subsite that was restored to a Site Collection.
"Data at the root level is invalid. Line 1, position 1.
Troubleshoot issues with Windows SharePoint Services. "
Seems that when you restore a sub site to a site collection there are many issues that occur. We only came across 2 of them. But after reading this post below we are actually encountering others. http://stsadm.blogspot.com/2007/09/convert-sub-site-to-site-collection.html
Thanks to this post we have fixed our Site Collection.
I have deployed this solution to our environment. Then I ran the command:
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN>stsadm -o gl-repairsitecollectionimportedfromsubsite -sourceurl http://apps/sites/testsc -targeturl http://apps/sites/sdlc
Site Collection is now fixed.
Friday, August 29, 2008
Thursday, August 14, 2008
Move ULS Logs off of your C drive.
Log Files are finally moved off of the C drive. This is configured through Central Administration so it affects every server in your farm. If the drive doesn't exist on the server the log files will not be written.
So what I did was create a folder called SPLogFiles on the D drive of all servers in the farm. Once this was completed I modified the Diagnostic Logging settings in Central Administration under the Operations Tab.
So what I did was create a folder called SPLogFiles on the D drive of all servers in the farm. Once this was completed I modified the Diagnostic Logging settings in Central Administration under the Operations Tab.
Monday, July 21, 2008
Navigation Error: Page being updated by another user.
After restoring a site collection to a new managed path I keep getting an error when trying to modify the navigation that states: Pages is being updated by another user. After googling I came across a post stating corrupted navigation headings. This is how I resolved: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1691577&SiteID=1
To reset corrupted headings, you have to :
- remove all the lists under corrupted heading
- remove corrupted heading
- From the list settings, add a removed list to the quick launch (This regenerate a non corrupted heading)
To reset corrupted headings, you have to :
- remove all the lists under corrupted heading
- remove corrupted heading
- From the list settings, add a removed list to the quick launch (This regenerate a non corrupted heading)
Thursday, July 17, 2008
Storage Space Allocation
Storage Space Allocation is available throughout site collections when site collection quotas are turned on. You can view the size of document libaries by default. If you close Show Only you can select lists and documents. Very nice feature. Easy to keep track of exactly what is taking up the most space.
Wednesday, July 16, 2008
Calendar View Webpart (Today view)
By default you can't add a webpart to display only today's calendar entries. I had to create a new view and modify the webpart on the home page to display only the newly created view.
Go to your calendar settings and create a new column called Begin Date. Add the formula =[Start Time] and select Date and Time for data type returned from this formula and click ok.
Create a new view called Today. Under Filter settings select Show items when the following is true: Column Begin Date, select is equal to, and type [Today].
Click ok.
Add or modify the existing calendar webpart on your home page. Select Today as the selected view.
Go to your calendar settings and create a new column called Begin Date. Add the formula =[Start Time] and select Date and Time for data type returned from this formula and click ok.
Create a new view called Today. Under Filter settings select Show items when the following is true: Column Begin Date, select is equal to, and type [Today].
Click ok.
Add or modify the existing calendar webpart on your home page. Select Today as the selected view.
Friday, July 11, 2008
Backup Farm
I have just finally completed the remainder of my backup tasks.
We are backing up:
IIS Metabase - (running on windows scheduler daily)
Backup IIS once before production and every time there is an IIS change or new WEB App created on ALL WFE’s
Syntax
iisback[.vbs] /backup [/b BackupName] [/v {Integer NEXT_VERSION HIGHEST_VERSION}] [/overwrite] [/e EncryptingPassword] [/s Computer [/u [Domain\]User [/p Password]]]
batch file to run is located at C:\WINDOWS\system32\inetsrv\MetaBack\BACKUP_IIS_METABASE.bat
Creates 2 files in:
C:\WINDOWS\system32\inetsrv\MetaBack\WeeklyBackup.MD0 (0 increments for each save)
C:\WINDOWS\system32\inetsrv\MetaBack\WeeklyBackup.SC0 (0 increments for each save)
IIS Configuration – (running on windows scheduler weekly)
Go to IIS, Right Click Local Computer – Choose All tasks – Backup/Restore Configuration – Create Backup
C:\WINDOWS\system32\inetsrv\MetaBack\IIS Configuration Backup 083107.MD0
NOTE: This backup method provides a way to restore only your IIS settings, not your content files. This backup method does not work if you reinstall your operating system. Backup files cannot be used to restore an IIS configuration on other computers that are running Windows 2000
MOSS – Index Server (full farm)
Full Farm Backup – GUI - Central Admin – Operations – Perform a backup. Backup location S:\FullFarmBackup (needs to have farm service account and sql service account sharing rights)
Batch file created to run on Window Scheduler every Saturday at 9:00PM. - S:\FullFarmBackup (FullFarmDiff) This is a full farm backup using the differential flag. This will only backup changes. You must first have a full farm backup before using the differential flag
Site Collection – Each Site Collection has been backed up to d:\moss_backup. The batch file is located in d:\moss_backup and has been added to the job scheduler to run every Saturday evening at 8:35pm. This works great but once your site collections get really big they will take a long time. Also if you are running this on a server that users are accessing it can hurt performance. We have this running on our Index server which users are not accessing.
I will add also that currently the SSP is very important. This is being backed up by the Central Administration site. I am working on creating a script to have this backed up by the windows scheduler also.
Database backups are done nightly
We are backing up:
IIS Metabase - (running on windows scheduler daily)
Backup IIS once before production and every time there is an IIS change or new WEB App created on ALL WFE’s
Syntax
iisback[.vbs] /backup [/b BackupName] [/v {Integer NEXT_VERSION HIGHEST_VERSION}] [/overwrite] [/e EncryptingPassword] [/s Computer [/u [Domain\]User [/p Password]]]
batch file to run is located at C:\WINDOWS\system32\inetsrv\MetaBack\BACKUP_IIS_METABASE.bat
Creates 2 files in:
C:\WINDOWS\system32\inetsrv\MetaBack\WeeklyBackup.MD0 (0 increments for each save)
C:\WINDOWS\system32\inetsrv\MetaBack\WeeklyBackup.SC0 (0 increments for each save)
IIS Configuration – (running on windows scheduler weekly)
Go to IIS, Right Click Local Computer – Choose All tasks – Backup/Restore Configuration – Create Backup
C:\WINDOWS\system32\inetsrv\MetaBack\IIS Configuration Backup 083107.MD0
NOTE: This backup method provides a way to restore only your IIS settings, not your content files. This backup method does not work if you reinstall your operating system. Backup files cannot be used to restore an IIS configuration on other computers that are running Windows 2000
MOSS – Index Server (full farm)
Full Farm Backup – GUI - Central Admin – Operations – Perform a backup. Backup location S:\FullFarmBackup (needs to have farm service account and sql service account sharing rights)
Batch file created to run on Window Scheduler every Saturday at 9:00PM. - S:\FullFarmBackup (FullFarmDiff) This is a full farm backup using the differential flag. This will only backup changes. You must first have a full farm backup before using the differential flag
Site Collection – Each Site Collection has been backed up to d:\moss_backup. The batch file is located in d:\moss_backup and has been added to the job scheduler to run every Saturday evening at 8:35pm. This works great but once your site collections get really big they will take a long time. Also if you are running this on a server that users are accessing it can hurt performance. We have this running on our Index server which users are not accessing.
I will add also that currently the SSP is very important. This is being backed up by the Central Administration site. I am working on creating a script to have this backed up by the windows scheduler also.
Database backups are done nightly
Microsoft Forefront For Sharepoint
I just finished configuring Forefront for Sharepoint.
This is a very useful users guide:
http://download.microsoft.com/download/A/A/1/AA13E922-FFA3-4EB1-BA3D-D177AB058746/SP_Users_Guide.doc
My next step is to test out the Management Console. We have 6 WFE's in our prd farm so it would make life easier to make configuration changes in 1 place. So far we are only using virus protection. Looking forward to using the file filters.
One thing I like about forefront is it catches files that are excluded by Sharepoint. It will actually look at the header of the file. So a user can't change a .mov extention to a .txt file and upload it to their mysite.
I have done a little testing on this and it works perfectly. I do not like the fact that if a file gets captured it displays a message as if the file has a virus. I do remember at Tech-Ed 08 someone stated in a session that this will be addressed in the next version. Due to this we are not using the file filter option because we don't want users to get confused.
This is a very useful users guide:
http://download.microsoft.com/download/A/A/1/AA13E922-FFA3-4EB1-BA3D-D177AB058746/SP_Users_Guide.doc
My next step is to test out the Management Console. We have 6 WFE's in our prd farm so it would make life easier to make configuration changes in 1 place. So far we are only using virus protection. Looking forward to using the file filters.
One thing I like about forefront is it catches files that are excluded by Sharepoint. It will actually look at the header of the file. So a user can't change a .mov extention to a .txt file and upload it to their mysite.
I have done a little testing on this and it works perfectly. I do not like the fact that if a file gets captured it displays a message as if the file has a virus. I do remember at Tech-Ed 08 someone stated in a session that this will be addressed in the next version. Due to this we are not using the file filter option because we don't want users to get confused.
Monday, June 16, 2008
HTTP/1.1 404 Connection: close Date: GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET ...
After deleting my My Site in QA I couldn't recreate it. I kept getting "HTTP/1.1 404 Connection: close Date: Thu, 29 Mar 2007 10:31:42 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET ..." error.
How I fixed this was going to the User Profiles and Properties page of the SSP and removed /personal/002733/ from my Personal Site: field. Then I recreated the My Site and it worked.
How I fixed this was going to the User Profiles and Properties page of the SSP and removed /personal/002733/ from my Personal Site: field. Then I recreated the My Site and it worked.
Site Collection Polices - Access denied
When trying to get to Site Collection - Policies I was receiving an access denied error. Double checking the portal sites everything was fine. Went to Authentication Providers under Application Management within the Central Administration and enabled client integration for the My Site web app and no more access denied errors.
Site Aggregator webpart not working correctly
Adding a site to a Site Aggregator webpart displays "Page not found" The primary problem is that by default the Site Aggregator adds “/_layouts/MyInfo.aspx"
I fixed this within my My Site by going to “Modify Shared Web Part” from the drop down arrow in the top right corner of the web part. This takes you into Edit Mode and gives you some settings for the Site Aggregator. Navigate to “URL” and you’ll see a field titled “URL to append to site” which is set to “/_layouts/MyInfo.aspx” by default. I deleted this text and now my site aggregator web part works correctly.
I fixed this within my My Site by going to “Modify Shared Web Part” from the drop down arrow in the top right corner of the web part. This takes you into Edit Mode and gives you some settings for the Site Aggregator. Navigate to “URL” and you’ll see a field titled “URL to append to site” which is set to “/_layouts/MyInfo.aspx” by default. I deleted this text and now my site aggregator web part works correctly.
While adding to your My Links from the Portal or HR portal and error would popup stating 409 Conflict error. I modified the Alternate Access Mappings to point to http for the default and https for Intranet. This seemed to resolve the issue.
Thanks to one of my Colleague for this one. Discussing with him helped me research why it worked from the Groups site and not from the others
Thanks to one of my Colleague for this one. Discussing with him helped me research why it worked from the Groups site and not from the others
Changing My Site theme error
When trying to change my theme within my Mysite, I received an error.
What happened was we added blocked file types to our MySite webapp. We used the same list that is being used for Outlook. One of the file types was inf. The themes file is a .inf file. So once we removed we could now change/modify our themes.
What happened was we added blocked file types to our MySite webapp. We used the same list that is being used for Outlook. One of the file types was inf. The themes file is a .inf file. So once we removed we could now change/modify our themes.
Restore a site from test to prd
When restoring a site to another environment you need to first create a site with the same template the site was originally created it.
Once you have a site created you can use stsadm -o import
-url http://url -filename c:\Location of File
When importing a site that has the publishing feature enabled at the SC level you must first activate the feature and then do the import.
If not you will see an error stating "Warning: The Office SharePoint Server Publishing Infrastructure feature must be activated at the site collection level before the Publishing feature can be activated.Progress: Importing Feature PublishingWeb"
Once you have a site created you can use stsadm -o import
-url http://url -filename c:\Location of File
When importing a site that has the publishing feature enabled at the SC level you must first activate the feature and then do the import.
If not you will see an error stating "Warning: The Office SharePoint Server Publishing Infrastructure feature must be activated at the site collection level before the Publishing feature can be activated.Progress: Importing Feature PublishingWeb"
Friday, May 2, 2008
WSS SP1 and MOSS SP1
Just applied WSS and MOSS SP1. So far no major issues. There was one issue when you clicked on a users profile from the Search results page. It was pointing to mysite.server.com:80/ and throwing a page not found. I added a server name mapping so that the index address was http://mysite.server and the search results address https://mysite.server and that seemed to resolve the issue.
Thursday, March 20, 2008
MOSS 2007 MySite: This Site search not working
When searching on your own Mysite search results were always unsuccessful.
First I verified that the search account had full read rights to the mysite web app.
Next verified all IIS settings were correct.
Lastly after speaking to Microsoft for a few hours with no suggestions, I decided to add the crawler account to Personalization Services Permissions. I gave the crawler all rights and the crawl worked.
Well I wasn't fully satisfied with this approach because technically the search account doesn't need a mysite. So I went back to my Policy for Web Application settings. Deleted the crawler and added back. This seemed to work. I deleted the crawler account from the Personalization Services Permissions. Seems it wasn't able to crawl so no results were being searched.
First I verified that the search account had full read rights to the mysite web app.
Next verified all IIS settings were correct.
Lastly after speaking to Microsoft for a few hours with no suggestions, I decided to add the crawler account to Personalization Services Permissions. I gave the crawler all rights and the crawl worked.
Well I wasn't fully satisfied with this approach because technically the search account doesn't need a mysite. So I went back to my Policy for Web Application settings. Deleted the crawler and added back. This seemed to work. I deleted the crawler account from the Personalization Services Permissions. Seems it wasn't able to crawl so no results were being searched.
Subscribe to:
Posts (Atom)
