Showing posts with label SharePoint Server 2010. Show all posts
Showing posts with label SharePoint Server 2010. Show all posts

Thursday, March 28, 2013

Site Collection Codes


Parameter value
Description
GLOBAL#0
Global template
STS#0
Team Site
STS#1
Blank Site
STS#2
Document Workspace
MPS#0
Basic Meeting Workspace
MPS#1
Blank Meeting Workspace
MPS#2
Decision Meeting Workspace
MPS#3
Social Meeting Workspace
MPS#4
Multipage Meeting Workspace
CENTRALADMIN#0
Central Admin Site
WIKI#0
Wiki Site
BLOG#0
Blog
SGS#0
Group Work Site
TENANTADMIN#0
Tenant Admin Site
ACCSRV#0
Access Services Site
ACCSRV#1
Assets Web Database
ACCSRV#3
Charitable Contributions Web Database
ACCSRV#4
Contacts Web Database
ACCSRV#6
Issues Web Database
ACCSRV#5
Projects Web Database
BDR#0
Document Center
OFFILE#0
(obsolete) Records Center
OFFILE#1
Records Center
OSRV#0
Shared Services Administration Site
PPSMASite#0
PerformancePoint
BICenterSite#0
Business Intelligence Center
PWA#0
Project Web App Site
PWS#0
Microsoft Project Site
SPS#0
SharePoint Portal Server Site
SPSPERS#0
SharePoint Portal Server Personal Space
SPSMSITE#0
Personalization Site
SPSTOC#0
Contents area Template
SPSTOPIC#0
Topic area template
SPSNEWS#0
News Site
CMSPUBLISHING#0
Publishing Site
BLANKINTERNET#0
Publishing Site
BLANKINTERNET#1
Press Releases Site
BLANKINTERNET#2
Publishing Site with Workflow
SPSNHOME#0
News Site
SPSSITES#0
Site Directory
SPSCOMMU#0
Community area template
SPSREPORTCENTER#0
Report Center
SPSPORTAL#0
Collaboration Portal
SRCHCEN#0
Enterprise Search Center
PROFILES#0
Profiles
BLANKINTERNETCONT
Publishing Portal
SPSMSITEHOST#0
My Site Host
ENTERWIKI#0
Enterprise Wiki
SRCHCENTERLITE#0
Basic Search Center
SRCHCENTERLITE#1
Basic Search Center
SRCHCENTERFAST#0
FAST Search Center
visprus#0
Visio Process Repository

Thursday, February 21, 2013

Code blocks are not allowed in this file SharePoint 2010



Hello Everybody,
Today I worked on one critical issue which belongs to our development environment. We have migrated one web application from production environment to development for testing purpose. Migration has been successful but we were facing an exception while browsing the web application.

Error Message:
An error occurred during the processing.
Code blocks are not allowed
Troubleshoot issues with Microsoft SharePoint Foundation.

Server Configuration:
·         2 SharePoint Servers
·         SQL server 2008 R 2
·         Windows Server 2008 R2
·         SharePoint Version: SP2010

Troubleshooting done:
1.    Tried accessing the system pages i.e. settings.aspx, viewlsts.aspx etc. every system was opening fine without any issues. So the issue is with the home page only…
2.    Tried accessing the web part maintenance page, it opened without any issues. We closed the webparts which are present on the home page-just to make sure that there is no problem with the existing webparts. Checked the home page again but same issue.
3.    Tried changing the master page as were able to open the system pages (by appending _layouts/changesitemasterpage.aspx). We changed to different one as we are using custom master page. Checked the results again but same problem.
4.    Opened the site in SharePoint Designer 2010 and checked the status of master page as well as the home page. It was fine and without customization too.

Note: if you see any of these pages in customizable state then I would suggest you to take the backup and try ‘reset to site definition” option.

Obviously, next question will arise- what exactly it will do? Yes, it will reset your page to default state. It means you will lose your customizations. But issue will be resolved and you can customize the page again as per your requirements.

5.    Checked the windows application as well as SP logs (Location: \14\Logs). I would suggest you to analyze these logs before continuing your troubleshooting.

What is my observation\Understanding?
·         Code blocks are only processed for custom pages deployed in the root virtual directory of a site if the code it considered safe.
·         This code is considered safe only if the page is served directly from the file system. As soon as it becomes unghosted for any reason, the code is no longer considered safe and the error shown in the symptom occurs.

Resolution:
As our production web application was working without any issues so I compared the web.config of both the applications. Analyze the code line by line with the production web.config and that’s it. I found the one which was missing in the web.config that belongs to my development web application.

Note: I would suggest you to take a proper backup before making any changes in the web.config file.

What I did? What kind of entries I added in the web.config file?

Here we go:-
In you web.config, you need to search the tag name as “<PageParserPaths>”
Once you find that then make the following  entry:
<PageParserPaths>
    <PageParserPath VirtualPath="/apps/*" CompilationMode="Always"
              AllowServerSideScript="true" IncludeSubFolders="true" />
</PageParserPaths>
After adding this entry then IISRESET is mandatory.

Tried accessing the site and the issue has been resolved.

Happy SharePoint once again…

If you have any queries/questions regarding the above mentioned information then please let me know, Thank you.

Users cannot see the checked out files in the folder/ library

I Came across a Issue today wherein the user opened a ticket for the below issue Issue : Users cannot see the checked out files in the fo...