No permissions to access site root "Sorry, you don't have access to this page"

If you have had this annoying message on your site

Sorry, you don't have access to this page

and you don't understand why it's happening, try the method below:

You have given read permission to a user on Site Permission and even with full control permission, user still can't access the Site!! keep reading...

You have tryied out every internet solution and nothing was usefull ?
Wait, here is the solution.

1- First go to your root site and list all webparts on it with "?contents=1" at the end of URL.

2- After that check every webpart/list/library permission that says "open on page" to see if it has "unique permission".

3- If you find any webpart/list/library with "unique permission" then "delete unique permission" and you should now login fine with the problematic user ;)

SharePoint 2013 Demonstration free online

Hi folks,

If you need a site to make a demo for a public speaking or just for fun, check out this site. 

It's free!!

Site: https://www.cloudappsportal.com/

I needed a public SharePoint Server just for a quick demonstration in a public speaking and was exactly what i found. Remember that the template allowed is only Team Sites, but it rocks.

Quick setup and you can create unlimited users but only 1 Site Collection.

Enjoy

FTP Server - 530 User cannot log in. - Critical error: Could not connect to server

Problem: When connecting to FTP Server, User can't login.

Firewall is disabled

User created

Note: Even allowing all users error happens

Following error appears:

Status: Connecting to 10.1.163.72:21...

Status: Connection established, waiting for welcome message...

Status: Insecure server, it does not support FTP over TLS.

Command: USER FTPuser

Response: 331 Password required

Command: PASS *********************************

Response: 530 User cannot log in.

Error: Critical error: Could not connect to server

Solution: After trying a lot of things, I found the solution to be simple!!

Just login with the new user to the server machine. After login and Profile is created you can login successfully on FTP. 

Enjoy :)

Sql Server Configuration Manager remote procedure call failed(0x800706be)

Problem: Receiving the following message in SQL Server Configuration Manager:

"SQL Server Configuration Manager remote procedure call failed (0x800706be)"

Solution that WORKED for me: 

Tried a bunch of solutions found online but none worked. So i found myway out.

1. Uninstall all versions of other SQL Versions in Control Panel
2. Register the sqlmgmprovider with this command 

regsvr32 "C:\Program Files\Microsoft SQL Server\100\Shared\sqlmgmprovider.dll"

Infopath Publishing error "The following URL is not valid"

When trying to publish Form the following alert appear "The Following URL is not valid"

Solution: 

After Googling and trying lots of things, I remembered my proxy was turned on at University...

Check if it's active, if so deactivate the proxy server at IE

Internet Options - > Connections - Lan settings - > "Proxy server" - deactivate the check boxes here

Have a great Day ;)

The workbook cannot be opened - Excel File SharePoint

Whether you open a excel file in SharePoint the following message appear "The workbook cannot be opened"

You have to do these 2 steps:

1. Run Powershell commands
1. $w = Get-SPWebApplication -Identity http://portal
2. $w.GrantAccessToProcessIdentity("domain\ServiceAccount")
2. Restart IIS iisreset /noforce

The breapoint will not currently be hit. No symbols have been loaded for this document.

Hi Folks,

One day in the morning I keep getting this error: The breakpoint will not currently be hit. No symbols have been loaded for this document.

I asked for help on a Microsoft College and He simple did "nothing". After 30 minutes it started to work and the only different thing he done was this:
Solution:

1. Go to Menu build -> Configuration Manager
2. In the Active Solution Configuration, select Release (or Debug if you had Release). Close
3. Do a Clean Solution then a Build Solution
4. Switch back to to Debug (or Release if you had Debug).
5. Now if you deploy the error will go away.

Hope it helps for you folks