Thanks Joe, you are right. The issue solved by giving privilege to the administrator through SQL Server Surface Area Configuration.