How to identify the template used to create a site..

hi Friends

I use to wonder in case solution (WSP files) when deployed on the server globally

If the solution are available the sites are also made using those solution . Now I had a Question in my mind that how could I find which templates are bening applied on the site .In case site are moved i.e server is backup is restored over a new server , Creation on new configuration database , Solution are removed etc

At last we end up in getting message

"Page not found' or "Internet Explorer could complete this request " or " Unkown Error"

I created a Aspx file usign the code snipet given below

Code Snippet [ before every tag, '--' is added, you need to remove the hyphens]

==========================================================

<--script type="text/javascript" <--%@ Assembly Name="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"%>
<--%@ Page Language="C#" MasterPageFile="~/_layouts/application.master" Inherits="Microsoft.SharePoint.WebControls.LayoutsPageBase" %>
<--%@ Import Namespace="Microsoft.SharePoint" %>

<--script runat="server">
protected override void OnLoad(EventArgs e){
SPSecurity.RunWithElevatedPrivileges(delegate()
{
using (SPWeb thisWeb = this.Web)
{
lblWebTempalte.Text = thisWeb.WebTemplate;
lblWebTemplateID.Text = thisWeb.WebTemplateId.ToString();
}
});
}
<--/script>
<--asp:Content ID="Main" runat="server" contentplaceholderid="PlaceHolderMain" >

Web Template: <--asp:Label ID="lblWebTempalte" runat="server" />

Web Template ID: <--asp:Label ID="lblWebTemplateID" runat="server" />
<--/asp:Content>

<--asp:Content ID="PageTitle" runat="server" contentplaceholderid="PlaceHolderPageTitle" >
Site Template Information
<--/asp:Content>

<--asp:Content ID="PageTitleInTitleArea" runat="server" contentplaceholderid="PlaceHolderPageTitleInTitleArea" >
Site Template Information
<--/asp:Content>

<--/script>
===========================================================

Web Template: ----->Web Template ID:

============= ================

ABSENCE ----> Absencevacationschedule ----> 75811

PROJMULTI ---->Budgetingtrackingmultipleprojects ----> 75819

BT ----> Bugdatabase ----> 75801

CALLCENTER ---->Callcenter ---->75812

PROJCHANGE ---->Changerequest ----> 75818

COMPROC ---->Complianceprocesssupport ---->75813

DR ---->Documentlibraryreview ---->75803

EVENTPLAN ----> Eventplanning ---->75814

EXREPORTS ---->expensereimbursementapproval ----> 75815

HELPDESK ---->HELPDESK ---->75816

IT ---->InventoryTracking ---->75804

ITTEAM ---->ITTeamWorkspace ---->75817

JRIM ---->JobRequisition ---->75805

KB ---->KnowledgeBase ---->75806

LL ---->LendingLibrary ---->75807

PATM ---->PhysicalAssetTracking ---->75808

PROJSING ---->ProjectTrackingWorkspace ----> 75820

RER ---->RoomEquipmentReservations ---->75809

ST ---->SalesLeadPipeline ---->75810

List of Out of the box MOSS 2007 Template ID Information

========================================================

NAme ---->Web Template: ----> Web Template ID:

============= ================

GLOBAL ---->Global template" ----> 0

STS ---->Team Site,Blank Site,Document Workspace ----> 1

MPS ---->Basic Meeting Workspace ----> 2

MPS ---->Blank Meeting Workspace ---->2

MPS ---->Decision Meeting Workspace ---->2

MPS ---->Social Meeting Workspace 2

MPS ---->Multipage Meeting Workspace 2

CENTRALADMIN ---->Central Admin Site ----> 3

WIKI ---->Wiki Site ---->4

BDR ---->Document Center ----> 7

BLOG ---->Blog ---->9

SPS ---->SharePoint Portal Server Site ---->20

SPSPERS ---->SharePoint Portal Server Personal Space ---->21

SPSMSITE ---->Personalization Site ---->22

SPSTOC ---->Contents area Template ----> 30

SPSTOPIC ---->Topic area template ---->31

SPSNEWS ---->News area template ---->32

SPSNHOME ---->News Home template ---->33

SPSSITES ---->Site Directory area template ----> 34

SPSCOMMU ---->Community area template ---->36

SPSREPORTCENTER ----> Report Center Site" ---->38

CMSPUBLISHING ---->Publishing and Team Collaboration Site ----> 39

OSRV ----> Shared Services Administration Site ----> 40

SPSPORTAL ---->Corporate Intranet Site ---->47

SRCHCEN ---->Search Center ---->50

PROFILES ---->Profiles ----> 51

BLANKINTERNETCONTAINER ---->Internet Presence Web Site ---->52

BLANKINTERNET ---->Publishing Site ---->53

BLANKINTERNET ---->Press Releases Site ---->53

BLANKINTERNET ---->Publishing Site ---->53

SPSMSITEHOST ----> My Site Host ---->54

SRCHCENTERLITE ----> Search Center Lite ---->90

PWA ---->Project Web Access Site ----> 6221

PWS ----> Project Workspace ---->6215

OFFILE ----> Records Repository ----> 1483

OFFILE---->Records Repository ---->14483

To find out how many Solutions are deployed on the server we can achieve by

Central administration > operation> solution management

We would be finding the List of WSP file or Cab files installed

To find the solution from the Configuration database to you configuration database (Eg Wss_config)

Go to the databases open the table Dbo.objects .you would be finding the List of Solution in inside the tables

Note:- Above Steps would be senario Specfic .before doing any step Its advisable to take a full farm back and Sql back up to be on safe side

Full farm Backup (GUI)

hi Friends
Recently I faced a issue related to Full farm backup .When I use to take a Full farm backup we use to get error
"object (database name) failed in event OnBackup. for more information, see the error log located in the backup directory. sqlException: BACKUP DATABASE is terminating abnormally.

Digging more in to the issue we came accross many settings. but the one thats solved the problem was a registry entry
We added the registry key “SessTimeout” at the location HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters.
We gave the value as 360 for SessTimeout

Here is the article you can check
http://support.microsoft.com/default.aspx?scid=kb;EN-US;102981

Schedule Automatic WSS3.0 Backups

Back up a farm by using the Stsadm command-line tool (Windows SharePoint Services 3.0)
http://technet.microsoft.com/en-us/library/cc288541.aspx

Back up a farm by using SQL Server Tools (Windows SharePoint Services 3.0)
http://technet.microsoft.com/en-us/library/cc288402.aspx

How to schedule a database backup operation by using SQL Server Management Studio in SQL Server 2005
http://support.microsoft.com/?kbid=930615

Restore a farm after a configuration database problem (Windows SharePoint Services)
http://technet.microsoft.com/en-us/library/cc512814.aspx

MOSS/WSS3.0 DISASTER RECOVERY STEPS

From File system backup following:
1.C:\inetpub\wwwroot
2.C:\windows\assembly
3.C:\windows\system32\drivers\etc\hosts file
4.C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\
5.C:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\
6.C:\Program Files\Microsoft Office Servers\12.0 (Not Applicable in WSS3.0)
(If you are using any custom locations instead of above default locations please backup them.)

From Registry Editor backup following:
1. 1.HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Secure
2.HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0

Back Up IIS Metabase (IIS 6.0) using following steps:
To create a non-portable backup (password not required)
1.
In IIS Manager, right-click the local computer, click All Tasks, and click Backup/Restore Configuration.
2.
Click Create Backup.
3.
In the Configuration backup name box, type a name for the backup file.
4.
Click OK, and then click Close.
The IIS metabase is created in the systemroot\system32\inetsrv\MetaBack folder.

Back up Central Administration Configured Settings:
1. In Central Administration,
2. Here is the following links that need to be documented(screenshot) to have a
backup of your configuration

a. Operations
i. Outgoing e-mail settings
ii. Incoming e-mail settings
iii. Approve/reject distribution groups
iv. Master site directory settings
v. Alternate access mappings
vi. Solution Management
vii. Services on Server (for each server)

b. Application Management
i. Define managed paths
ii. Web Application outgoing e-mail settings
iii. Web application general settings
iv. Content Databases
v. Web Application list
vi. Records center
vii. Manage form templates
viii. Configure InfoPath Forms Services
ix. Manage data connection files
x. Manage the Web service proxy
xi. Create or configure this farm’s shared services
xii. Grant or configure shared services between farms
xiii. Configure session state
xiv. Security for Web Part pages
xv. Self-service site management
xvi. User permissions for Web application
xvii. Policy for Web application
xviii. Authentication providers
xix. Manage Search service
xx. Workflow settings

c. Shared Services Administration (Not Applicable in WSS3.0)
i. In each SSP, document the following
1. User profiles and properties
2. Profile services policies
3. My Site settings
4. Trusted My Site host locations
5. Published links to Office client applications
6. Personalization site links
7. Personalization services permissions
8. Search settings
9. Search usage reports
10. Edit Excel Services settings
11. Trusted file locations
12. Trusted data connection libraries
13. Trusted data providers
14. User-defined function assemblies
15. Audiences
16. Usage Reporting
17. Import application definition
18. View applications
19. View entities
20. Business Data Catalog permissions
21. Edit profile page template

3. Next we will need to have you take a backup using the Central Administration site
a. In the Operations tab, click on Perform a Backup
b. Check the box next to Farm, click on Continue to Backup Options
c. Be sure that Full is selected
d. Enter in a share for the backup to be placed in that folder
i. Note: The MOSS service account needs full control for the Share, as well as
the NTFS permissions.
e. Click OK
i. It will take a few minutes before the backup is started.

Full Farm Backup using command prompt:
stsadm -o backup -directory -backupmethod full

To backup individual site collections:
Open a command prompt
Cd “C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN”
stsadm -o backup -url -filename -overwrite

Backup all SharePoint Databases from SQL Server Management Studio:
1. Configuration database (Configuration database name can be found from Central admin>Operations>Topology and Services>Servers in Farm)
2. Content Databases (We can find the association of the web application and Content database from Central administration>Application Management>Content Database>On right hand side we need to select drop down list>change web application & we need to select a web application for which the Content database will be listed below.)
3. WSS_Search Database (WSS Search database name can be found from Central admin>Operations>Topology and Services>Services on server>Click on Windows SharePoint Services Search>Search Database>Database Name)
4. Shared Services DB Databases (Not Applicable in WSS3.0)
5. Shared Services SEARCH Databases (Not Applicable in WSS3.0)
6. Any other databases related to Product integrated with SharePoint (For example: SQL Reporting Services, Project Server etc)

4.Disconnecting from existing Configuration Database & creating a new Configuration Database:
This will cause loss of following:
1. Central admin configured settings (Need to be reentered from screenshots taken earlier)
2. Any solutions deployed in farm (Need to read & redeploy)
3. 3rd party web parts or templates (Need to reinstall)
4. Integration with other products (Need to reconfigure)

5. After the backup finishes successfully, run SharePoint Products and Technologies Configuration from each server(one at a time)
a. Click next; click Yes
b. Select Disconnect from this server farm; click Next

6. Creating a new configuration database;
run the SharePoint Products and
Technologies Configuration from the server that will be hosting Central
Administration.
a. Click Next; Click Yes
b. Select No, I want to create a new server farm
c. Type in Database server
d. Make sure the Database name is unique(This will be the name of your
configuration database)
e. Enter in your username and password
f. Click next
g. Specify a port(optional)
h. Click Next; Click Next

7. Connect other servers up to the farm; run SharePoint Products and Technologies Configuration from the other servers one at a time
a. Click Next; click Yes
b. Make sure Yes, I want to connect to an existing server farm is selected; click
Next
c. Enter in the database server name; Click Retrieve Database Names
d. Select the database that you just created for Database name
e. Type in the password for the service account
f. Click Next 3 times

8. Start the services in the Central Administration -> Operations -> Services on server
a. Start the services that were documented in the previous steps for each server
b. Make sure the services are in the Started status, not Starting

9. Restoring from backup; Central Administration -> Operations -> Restore from backup
a. Specify the location of the backup; click OK
b. Select the backup that was taken in the previous steps; Click Continue the
Restore Process
c. Check the box next to Farm; Click Continue the Restore Process
d. Select New Configuration
i. NOTE: DO NOT USE SAME CONFIGURATION
e. Complete the forms with the correct information about database names/servers
and service account usernames/passwords
f. Click OK
i. The Restore process will take a few minutes to start.

10. If above restore Operation does not work try one of following:

A. For catastrophic restore
stsadm -o restore -directory -restoremethod

B. For site collection restore
stsadm -o restore -url -filename [-hostheaderwebapplicationurl] -overwrite

C. Create new web application & use stsadm -o addcontentdb to attach original content database
stsadm.exe -o addcontentdb -url -databaseserver -databasename

Restoring On the same server:
Since Configuration Database is same & all the files are in place, most of the sites work without problem.
If New Configuration Database is created on same server then follow instructions below

Restoring On new server:
1.Since we need to create a new configuation database & all required files are not present, We need to copy the contents of backed up folders partially or fully to the new server.
2.We also need to redeploy the lost settings mentioned in step 4 above,
3.SSL certificates needs to be assigned again.
4.Host/CNAME records in DNS needs to be updated to point to new Server.

Upload Mulitple Documents - .zip files not visible

Environment :- Only Vista Machines.

Note :- Before making any registry changes, take Reg back up

Resolution :- Delete the follow registry keys and reboot is a MUST
HKEY_CLASSES_ROOT\CLSID\{E88DCCE0-B7B3-11D1-A9F0-00AA0060FA31}
HKEY_CLASSES_ROOT\CLSID\{0CD7A5C0-9F37-11CE-AE65-08002B2E1262}

Files opens as Read Only after Check-out

Note:- Please take precautionary steps before applying the below steps. Backup your registry.

Issue:- Files will open as Read-Only after checking Out a document in SharePoint and trying to Edit it.

Environment:- XP + Office 2003 or Vista + Office 2007

Follow the below steps to resolve the issue.
---------------------------------------------------
1.) Search for oledb32.dll on the workstation and make sure it exists in this location. The default location is c:\program files\common files\system\ole db\oledb32.dll

2) Copy and paste the information below to Notepad and save as a .reg file. This will correct the entries in the Registry that are probably missing.

===========================================================
REGEDIT4
[HKEY_CLASSES_ROOT\CLSID\{FF151822-B0BF-11D1-A80D-000000000000}]@="Microsoft OLE DB Root Binder for Internet Publishing"

[HKEY_CLASSES_ROOT\CLSID\{FF151822-B0BF-11D1-A80D-000000000000}\InprocServer32]@="C:\\Program Files\\Common Files\\system\\ole db\\oledb32.dll""ThreadingModel"="Both"

[HKEY_CLASSES_ROOT\CLSID\{FF151822-B0BF-11D1-A80D-000000000000}\OLE DB Binder]@="Microsoft OLE DB Root Binder"

[HKEY_CLASSES_ROOT\CLSID\{FF151822-B0BF-11D1-A80D-000000000000}\ProgID]@="MSDAURL.Binder.1"

[HKEY_CLASSES_ROOT\CLSID\{FF151822-B0BF-11D1-A80D-000000000000}\VersionIndependentProgID]@="MSDAURL.Binder"

[HKEY_CLASSES_ROOT\MSDAURL.Binder.1]@="Microsoft OLE DB Root Binder for Internet Publishing"

[HKEY_CLASSES_ROOT\MSDAURL.Binder.1\CLSID]@="{FF151822-B0BF-11D1-A80D-000000000000}"

[HKEY_CLASSES_ROOT\MSDAURL.Binder]@="Microsoft OLE DB Root Binder for Internet Publishing"

[HKEY_CLASSES_ROOT\MSDAURL.Binder\CLSID]@="{FF151822-B0BF-11D1-A80D-000000000000}"

[HKEY_CLASSES_ROOT\MSDAURL.Binder\CurVer]@="MSDAURL.Binder.1"

===========================================================

3) From Start->Run, type Regsvr32.exe "[Drive]:\Program Files\Common Files\System\OLE DB\MSDAIPP.DLL"

4) Test and see if the issue is resolved.

Windows SharePoint Services Search (SPSearch) Errors File Not Found / 'start' action failed

Disclaimer: Take all possible backups, Since you have decided to troubleshoot on your own we hold no responsibility if anything goes wrong.

Note: After every troubleshooting step run following command
stsadm -o spsearch -action fullcrawlstart
& monitor Eventviewer>Application log for Success or Failures related to Windows SharePoint Services Search Service

On Failures try next step.

1. Open a Command prompt
Browse to C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN

stsadm -o provisionservice -action stop -servicetype "Microsoft.SharePoint.Search.Administration.SPSearchService, Microsoft.SharePoint.Search, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" -servicename "SPSearch"stsadm -o provisionservice -action start -servicetype "Microsoft.SharePoint.Search.Administration.SPSearchService, Microsoft.SharePoint.Search, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" -servicename "SPSearch"

stsadm -o spsearch -action stop

From SQL Server Management Studio backup & remove Old WSS_Search databases

stsadm -o spsearch -action start -farmserviceaccount [Domain\user]-farmservicepassword [Password] -databaseserver [SQL Server\Instance] -databasename [New WSS_Search DatabaseName]
Note: Replace above parameters with proper values

2. Run following from command prompt Before Reboot
net stop sptimerv3
net stop spsearch
sc config sptimerv3 start= disabled
sc config spsearch start= disabled

Run following from command prompt After Reboot
sc config spsearch start= demand
sc config sptimerv3 start= auto
net start sptimerv3
net start spsearch

3. From Windows Explorer go to backup cache.ini file from following location
C:\Documents and Settings\All Users\Application Data\ Microsoft\ SharePoint\ Config\

Change the contents of cache.ini to 1

From command promptnet stop spsearch net start spsearchstsadm -o execadmsvcjobs

4. psconfig -cmd secureresources
attrib -s %windir%\tasks.

Go to Properties of windows\tasks folder and add wss_wpg and wss_admin_wpg groups and give the full control permissions.

5. Repair MOSS from Add/Remove programs
Reboot server
Run PSCONFIG without changing any settings

NOTE: Do not perform following step if you want to use Network Service as SharePoint Service Account on SingleServer Installation with SQL Internal Engine

6. Central Admin>Operations>Servers in Farm
Note down the Configuration Database name

Run PSCONFIG Disconnect from Configuration Database

Run PSCONFIG Reconnect to same Configuration Database disconnected above.

Workflow "Error" System Account An error has occurred after workflow completed MOSS 2007

Problem: If you have a "built in" or custom approval workflow setup for your document library. The workflow runs correctly, however when sometimes you look at the workflow status, you may receive an error after the task has been approved and completed such as, Event Type: Error User ID: System Account Description: An error has occurred in [name of workflow].

Resolution: When you define your workflow, there is a section "Post-completion Workflow Activities", where you can check "Update the approval status (use this workflow to control content approval)". If you check this option, and you do NOT have content approval enabled on the library level, you get the system account error message. If you do not check it, everything works fine.

Reason for occurrences: The account listed in the "User ID" column does not have permission to "something" that is being requested in the workflow code. Workflow usually running as the "system account" within SharePoint and should have access to all the objects within SharePoint. However, the system account may not have access to some resources that are outside of SharePoint and needed by the workflow code. Accessing outside resources is usually done via the .NET worker process account (e.g. NETWORK SERVICE).

Move WSS3.0 databases from one SQL Server to another?

How to move WSS3.0 databases from one SQL Server to another?

Configuration:
WSS3.0 Server
Source SQL Server: Win 2003 Server SP2 SQL Server 2000 + SP4
Destination SQL Server: Win 2003 Server SP2 SQL Server 2000 + SP4

STEP1: BACKUP:

1] On Source SQL Server: Backup SharePoint Content databases.
Open SQL Server Enterprise manger
Right Click a database (For ex: WSS_Content)>All Tasks>Backup Database>Database Complete>Backup to disk>Add>Filename>Provide a path & filename>Ok>Ok
Repeat above procedure for all SharePoint databases however we will not restore all of them.
(Do not restore COnfiguraion & WSS_AdminContent... database on new SQL Server)
How to find name of Content databases:
Central Admin>Application Management>Content databases>Select web application from Right Hand Side Top drop down list
Database name will be displayed

-------------

2] On SharePoint Server: Take screenshots of all configured setting on Central administration page
For example:
Central Admin>Operations>Global Configuration>Alternate access mappings
Central Admin>Operations>Outgoing email settings
Central admin>Application management>Define managed paths
etc.

--------------

STEP 2: PREPARE DESTINATION SQL SERVER
We must install either same or Better version than Source SQL Server
Open SQL Server Enterprise manger
Security>Logins>Right Click>New Login
Add SharePoint Service Account in Domain\user format
This account must be either Domain admin or Domain user with Local admin rights on SharePoint server.
Security>Logins>Right Click Service Account>Properties>Server Roles Tab
Check Security Administrators & Database Creators
Click Ok

STEP 3: RESTORE CONTENT DATABASE TO DESTINATION SERVER
Copy backup Content database files to Destination SQL Server
Open SQL Server Enterprise manger
Databases>Right Click>All Tasks>Restore database>Restore as Database>Type name of Content Database>From device>Select device>disk>Add>Browse to backup files>Ok>Ok
Similarly restore all Content databases from backup
Security>Logins>Service Account>Database Access Tab>In upper pane select Content database>In lower pane check DB_OWNER checkbox>Click Ok

STEP 4: DISCONNECT FROM SOURCE SQL SERVER
On WSS3.0 Server
Run SharePoint Products and Technologies Configuration (PSCONFIG ) Wizard
-Select Disconnect from this server farm

-We should get configuration successful message.

STEP 5: CONNECT TO DESTINATION SQL SERVER
Run SharePoint Products and Technologies Configuration (PSCONFIG ) Wizard
-Select No, I want to create a new server farm

-Database Server: Give Destination SQL Server name
-Database Name: Type new Config Database Name
-Username: Use same Service account as used in existing old server
-Password: Password for that account

-We should get configuration successful message.
-After PSCONFIG finishes successfully Central admin page will open automatically.

STEP 6: RESTORING SITES FROM DATABASES

3.Create a new web application http://app on port 80 with content database name WSS_Content_TEST

1] Go to V3 Central Administration Page>Application Management>Create or extend Web Application

2] Click on Create a new web application

3] Choose any unused port no

4] Enter Database Server Name and enter Database name as WSS_Content_TEST

7] Wait for operation to complete

8]After application is created create a site collection

9] Fill the details and select Team site template click Ok

11] Browse to test site http://app

12] Check if it is working

To remove dummy_content_db from a web application

1] Click on Content Databases

2] On right hand side select the newly created web application if not already present
3] Click on Database name WSS_Content_TEST


4] Check remove content database checkbox and click OK

To attach restored content database to a new web application:
Open a command prompt and browse to
c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Bin>
Run following command
stsadm -o addcontentdb -url -databaseserver -databasename

Now browse to http://app and check if it is working
Similarly add content databases for other web applications.

STEP 7: POST MIGRATION TASKS

From the screenshots taken earlier we need to reconfigure central admin.
If site was using SSL we need to reapply it & change AAM.
We need to redo any customizations if lost after creating new configuration database.
If 3rd party web parts stop working we need to reinstall them.
Integration with other products needs to be reconfigured.
We need to assign the indexer to the sites from Central Admin>Application Management>Content databases>Select web application from Right Hand Side Top drop down list>Click on Database name>Select Search server from drop down list>Click Ok
Use "stsadm -o spsearch -action fullcrawlstart" to force instant crawling of sites.

NOTE:
=====
Do NOT discard Source SQL Server & Databases until the functionality of New SQL Server & WSS3.0 is tested & confirmed.

There are alternatives to above procedure but are quite tricky. :-)

500 Internal Error

Error:- 500 Internal Error

Description:- This error comes only for subsites and subsite administrators can browse the subsite without any issues. The parent site collection is also browsable without any issues. Only member or visitors of the subsite get the error "500 Internal Error"

Resolution:
1. Go to the subsite settings page by adding /_layouts/settings.aspx at the end.
2. Select Advanced permissions -> Settings -> Permissions Level
3. Click "Edit Permissions level"
4. Click "Inherit Permissions from parent"

Now the subsite should be browsable by all without any issues.