SharePoint 2010 Error: domain/my Cannot be found

So, this morning i was trying to access my personal site and my profile pages in our new SharePoint farm. But what i got was the HTML 404 The Page Cannot be Found.
After spent hours looking for the solution of this issue, finally found the way to figure this out! Yippi!

1st step---
Log on to your Central Administration > Application Management > Create Site Collection

2nd step---
Point to Web Site Address and click on the link Define Managed Paths.

3rd step---
Add a new path

1. my, choose the type Explicit inclusion, Add Path

2. my/personal, choose the type Wildcard inclusion, Add Path

3rd step---
Go back to Create Site Collection page.

Put the Title and Description : My Sites

Web Site Address : http://your_domain/my/

Template Selection : Enterprise > My Site Host

Then choose the Primary and Secondary Site Collection Administrator, then click OK. Now you have /my site collection.

4th step---
This is optional, just in case if you haven't configured the Self-Service Site Creation. This will let the authenticate user create their own personal page.
Go to Central Administration > Security > General Security > Configure self-service site creation.

Then choose On in the Enable self-service site creation section. Press OK.

Easy, huh? :)

Read more »

SQL Server 2008 R2: Connect to Different Domain and Server Name

Have struggled with this problem almost all day. I couldn't connect to another domain server using SQL Management Studio 2008 R2. Precisely, my other domain server is using Hyper-V and i called the server name as DOMAIN1. In this case i couldn't get access easily by using the server name but what i need is connect using the IP Address of DOMAIN1. In this case i defined the IP address of DOMAIN1 as 192.168.0.11

1st step---
Make sure you can connect to DOMAIN1, add another IP Address. In this case, i am using IP 192.168.0.* so i can connect. For example i defined the IP address of my SQL Server computer as 192.168.0.9

2nd step---
Check the DOMAIN1 firewall, make sure it doesn't block connection from your computer. To set up Firewall, go to Windows Firewall with Advance Security.

Right Click on Windows Firewall with Advance Security and point to Properties > Domain Tab > and Allow inBound connection.

3rd step---
Run Command Prompt:

cd\ <enter>

runas /user:DOMAIN1\admin /netonly "C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\Ssms.exe" <enter>

Enter the password for DOMAIN1\admin then <enter>

wait until SQL Management Studio 2008 R2 open by itself.

4th step---
Once you get the Connect to Server Window. Fill in the Server Name as shown below:
Server type: Database Engine
Server name: 192.168.0.11\InstanceName
Authentication: Windows Authentication
Then click connect button.

Hope it works. Mine is working very well, now i can connect to my Hyper-V SQL Server. :) Good luck!

Read more »

SharePoint 2010: Specify the Default Database Server

If you have look at my posts before this, this post is connected to Migrating SharePoint 2010 Databases from SQL Server 2008 Express Edition to SQL Server 2008 R2 Enterprise Edition. After detach and attach all MOSS 2010 databases from SQL Server Express, now we have  to go back to SharePoint Central Administration. 

1st step---

Log on to your Central Administration as farm administrator.

2nd step---

In the SharePoint 2010 Central Administration Page go to Application Management > Databases > Specify the default database server.

3rd step---

In the default database server page, fill in the Domain\SHAREPOINT_DB_Instance of the SQL Server Instance that you'd like to be as the default.

And if on that Instance you are using SQL Authentication, then you have to fill in the Username and Password, instead leave it blank if you're using Windows Authentication.

Sometimes you may get an error message if there's an issue with the permission for NT AUTHORITY/NETWORK SERVICE group like shown below:

Login failed for user 'NT AUTHORITY\NETWORK SERVICE'

This happens when you're using Windows Authentication, and means you will need to grant permission for NT AUTHORITY/NETWORK SERVICE. Below are some steps that i did to grant permission for NT AUTHORITY/NETWORK SERVICE group.

1st step---

Open SQL Management Studio and then connect to the Database Instance. After you are connected, right click on the Database Instance and point to New Query, because we are going to use Transact-SQL to grant the permission.

2nd step---

Execute the script below:

sp_grantlogin 'NT AUTHORITY\NETWORK SERVICE'

After that you will need to go back to the SharePoint Central Administration, and redo the 2nd step---  and 3rd step--- up above. You will not find any error anymore. :)

Read more »