Developer's Paradise

ASP.NET MVC - Sport Facility Booking system

2021-09-15T16:03:00.001-07:00

The project relies on some external service providers. Thus accessing them via their API requires authentication. An API Key need to be supplied in order to achieve the full functional capacity of the app. Please fill in the sections in the appsettings.json with your personal keys. The application will still work if not supplied with valid API keys but with limited functionality. Email sending will be disabled and adding rooms will be impossible without images uploaded to Cloudinary. An admin account is seeded with login credentials Admin for username and AdminPass for password

https://github.com/vivekthangaswamy/SportsFacilityManager

Mobile apps using Xamarin + Azure

2018-03-07T16:25:00.000-08:00

Microsoft has released a wonderful detailed "Mobile app using Xamarin + Azure" poster which covers all details and services for developers and designers.

2018-03-07T16:20:00.000-08:00

How do I access the All People group/page in a SharePoint 2013/2010 site collection?

In Microsoft Office SharePoint 2007, you could remove the user from the All People group and re-add them. This option is no longer available in SharePoint 2010/2013. SharePoint 2010/2013 removed the page from navigation, but you can still access the All People page by appending the following to the root URL of the site collection.

SharePoint 2013
/_layouts/15/people.aspx?MembershipGroupId=0

SharePoint 2010
/_layouts/people.aspx?MembershipGroupId=0&FilterField1=ContentType&FilterValue1=Person

U-SQL Local execution error in Visual Studio

2017-10-03T21:26:00.000-07:00

Severity Code Description Project File Line Suppression State
Error E_STORE_USER_FILENOTFOUND: File not found or access denied: C:\Users\...\AppData\Local\USQLDataRoot\SearchLog.tsv.
Description:
Unable to obtain information about this file.
Resolution:
Ensure the file with exact casing exists (paths are case-sensitive) and the account has read permission to the file. USQLApplication1 C:\Users\...\Documents\Visual Studio 2017\Projects\USQLApplication1\USQLApplication1\Script.usql 10

This is caused due to 2 reason

1- Run your visual studio as Administrator can solve it.

2- Download the SearchLog.tsv or your data file from your Data Lake Store and place in the DataRoot directory.

Hope this helps.

Microsoft.EntityFrameworkCore.Database.Connection[200004]

2017-08-24T18:42:00.000-07:00

Microsoft.EntityFrameworkCore.Database.Connection[200004]
An error occurred using the connection to database 'DBAPIContext-4266f07e-a498-4ab6-9c86-792af5b78354' on server '(localdb)\mssqllocaldb'.
System.Data.SqlClient.SqlException (0x80131904): Cannot open database "DBAPIContext-4266f07e-a498-4ab6-9c86-792af5b78354" requested by the login. The login failed.
Login failed for user 'user.ID'.

---------------------------
Microsoft Visual Studio
---------------------------
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible.
Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 50 - Local Database Runtime error occurred.
Specified LocalDB instance name is invalid.

)
---------------------------
OK

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

Solution:

The following 2 steps solved issue for me.

1- One run the following command in command window

2- Then run PM> Update-Database in Package manager in your visual studio project.

Then you can check the DB by try connecting via Management Studio.

nuget configuration is invalid.

2017-08-17T17:00:00.001-07:00

---------------------------
Microsoft Visual Studio
---------------------------
"Project" nuget configuration is invalid.

---------------------------
OK
---------------------------

When you try to add the reference, via Manage Nuget Packages. You may get this above error message.

The solution is simple. Close the Visual Studio and open it again. This works most of the time.

Windows Server AppFabric: installation error , While installing SharePoint prerequisite installer

2016-07-06T18:49:00.000-07:00

1) Windows Server AppFabric: installation error
------
2) Warning : Call to OpenService(...,SERVICE_START | SERVICE_QUERY_STATUS | SERVICE_STOP | SERVICE_PAUSE_CONTINUE) function to get handle to the service failed (0X424=1060)
Warning : [In HRESULT format] (0X80070424=-2147023836)
AppFabric caching service is not installed.
-------
3)
---------------------------
Unsupported 16-Bit Application
---------------------------
The program or feature "\??\C:\Users\ANZ~1.DEV\AppData\Local\Temp\AppA0E1.tmp.exe" cannot start or run due to incompatibity with 64-bit versions of Windows. Please contact the software vendor to ask if a 64-bit Windows compatible version is available.
---------------------------
OK
---------------------------

SOLUTION:

1) uninstall the AppFabric and let the SharePoint prerequisite installer do the installation for you.
a) Make sure Windows Update server running.
b) Uninstall AppFabric completely if there is any installed.

2) Append the following path to PSModulePath entry in the environment variables – %SYSTEMROOT%\System32\WindowsPowerShell\v1.0

Go to My Computer, right-click Properties
On the System’ page, click Advanced System Settings on the left-side pane.
If you receive a UAC prompt, click on Yes to launch the System Properties dialog box
From the Advanced tab, click Environment Variables
Within the System Variables section in the lower half, select PSModulePath and click on Edit (or double-click PSModulePath‘)
Append the following path to PSModulePath entry in the environment variables

%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\

Ensure that the PSModulePath entry looks like this:

C:\Windows\system32\WindowsPowerShell\v1.0\Modules\;c:\Program Files\AppFabric 1.1 for Windows Server\PowershellModules

And also verify in your server if any download block happening by any of your firewall or antivirus etc.

Ref Screen Captures:

These services better to be enabled, which helps in error free installation.

Windows could not start the SharePoint 2010 Administration service on Local Computer.

2016-04-07T21:06:00.003-07:00

---------------------------
Services
---------------------------
Windows could not start the SharePoint 2010 Administration service on Local Computer.

Error 1053: The service did not respond to the start or control request in a timely fashion.

---------------------------
OK
---------------------------

---

SOLUTION:

Change the Group Policy settings. To do this, follow these steps:

Under the Computer Configuration node in the Local Group Policy Editor, double-click Policies.
Double-click Windows Settings, double-click Security Settings, and then double-click Public Key Policies.
In the details pane, double-click Certificate Path Validation Settings.
Click the Network Retrieval tab, click to select the Define these policy settings check box, and then click to clear the Automatically update certificates in the Microsoft Root Certificate Program (recommended) check box.
Click OK, and then close the Local Group Policy Editor.

I think this is the beginning of... IoT

2016-03-03T16:43:00.001-08:00

Its been a while, seriously getting into some new platform of development. IoT is buzzword ringing around me for a while now.

I always had love towards Microsoft platforms. When Windows 10 started show casing IoT platform based development, my interest got more into it.

Back in 2015 Microsoft Conducted a Code It Light It

Unable to run through well.

Now after Windows 10 IoT launch, I am diving into it again. let's hope the platform will be interesting to explore.

I am started fresh and starting from here http://ms-iot.github.io/content/en-US/AdafruitMakerKit.htm

The License Agreement file, "C:\WINDOWS\system32\FPdotLicense.dat" does not exist.

2016-02-14T15:28:00.001-08:00

---------------------------
License Agreement Not Found
---------------------------
The License Agreement file, "C:\WINDOWS\system32\FPdotLicense.dat" does not exist. Please install this file to continue.
---------------------------
OK
---------------------------

Cause:
When you build the old solution in New Visual Studio 2015, you may get the above error message.

Solution:
The following folder path needs write permission for C:\WINDOWS\system32\ while building the solution. Its a license scheme for windows.

.NET Framework 3.5 feature + Specify an alternate source path

2015-12-14T17:02:00.001-08:00

.NET Framework 3.5 feature + Specify an alternate source path error for SharePoint prerequisite installation error.

Try to install the following Windows update and it may fix your issues.

https://support.microsoft.com/en-us/kb/3002547

in cmd prompt try to enable.

open cmd window as Administrator and run the following command.

DISM /Online /Enable-Feature /FeatureName:NetFx3 /All

If still fails, try installing Powershell enable powershell and than add this feature. It will work.

Search for this error Code Error: 0x800f0906 and will give relavent steps to fix the issue.

.NET Framework 3.5 feature + Specify an alternate source path

2015-12-14T17:02:00.000-08:00

.NET Framework 3.5 feature + Specify an alternate source path error for SharePoint prerequisite installation error.

DISM /Online /Enable-Feature /FeatureName:NetFx3 /All

If still fails, try installing Powershell enable powershell and than add this feature. It will work.

Search for this error Code Error: 0x800f0906 and will give relavent steps to fix the issue.

Embrassing screen sharing interview : SharePoint

2015-05-07T05:06:00.001-07:00

First time in 10 years I am attending new format of interview. Sharing your computer screen and writing code as per interviewer request.

For me to be frank, interviewer was really a good guy, Nicely spoken most understanding. But I am very nervous about exams right from childhood :)

This interview format is too much for me :) My interviewer was asked me to do very simple stuff write a c# code using SharePoint object model to set values in Choice field. Damn, I know the 5 lines of code. I don't know what happened at that time by I am totally blank :( It was so embarrassing for me and I cannot deliver what he asked. I don't know how to prove I am so much better than this. :(

This blog, I am writing after 1 hr of the interview. The code blow is the what is expected. Hope the code will compile I guess.

//get choice field instance

SPFieldChoice LeaveReason = (SPFieldChoice)myList.Fields["Reason"];

//set field format type

LeaveReason.EditFormat = SPChoiceFormatType.Dropdown;

//set the choice strings

LeaveReason.Choices.Add("Sick");
LeaveReason.Choices.Add("Long Service");
LeaveReason.Choices.Add("Casual");

//update the field

LeaveReason.Update();

//update list

myList.Update();

I am still cannot understand why I am this bad in interviews.

Service Token Failure In SharePoint 2013 Farm

2015-04-19T19:55:00.003-07:00

Service Token Failure

--

cls
  # This command loads the Microsoft.SharePoint.PowerShell DLL.

# This DLL is required if you are using Windows PowerShell.
  [string]$Snapin="Microsoft.SharePoint.PowerShell"

if ((Get-PSSnapin $Snapin -ErrorAction SilentlyContinue) -eq $null)

{
Write-Host "Loading Snapin: $Snapin";

Add-PSSnapin $Snapin

}
else
  {
Write-Host "Snapin already loaded: $Snapin";

}
$h = Get-SPServiceHostconfig

$h.Provision()

$services = Get-SPServiceApplication

foreach ($service in $services) { $service.provision();

write-host $service.name}

STSADM Cmds for Cancel and redeploy Farm Solution

2015-03-09T18:33:00.003-07:00

STSADM Cmds for Cancel and redeploy Farm Solution

C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\BIN>
stsadm -o execadmsvcjobs

stsadm -o enumdeployments

stsadm -o canceldeployment -id

stsadm -o deletesolution -name .wsp -override

Start Central Administration Via PowerShell

2015-03-09T17:47:00.002-07:00

Start the Central Administration via PowerShell

To list the Central Admin list in Farm

Get-SPServiceInstance | Where-Object {$_.TypeName –eq ‘Central Administration’}

following code will start the Central Admin if its not started, if its started and online already it will show you a warning message.

cls
# This command loads the Microsoft.SharePoint.PowerShell DLL.
# This DLL is required if you are using Windows PowerShell.
[string]$Snapin="Microsoft.SharePoint.PowerShell"
if ((Get-PSSnapin $Snapin -ErrorAction SilentlyContinue) -eq $null)
{
Write-Host "Loading Snapin: $Snapin";
Add-PSSnapin $Snapin
}
else
{
Write-Host "Snapin already loaded: $Snapin";
}

Get-SPServiceInstance | Where-Object {$_.TypeName –eq ‘Central Administration’} | Start-SPServiceInstance

Hope this helps.

'Form' is an ambiguous reference between 'System.Windows.Forms.Form' and 'Microsoft.SharePoint.Client.Form'

2014-07-11T00:35:00.001-07:00

When I try to use the SharePoint 2013 Client Object model in Windows Application I was getting the following error.

"'Form' is an ambiguous reference between 'System.Windows.Forms.Form' and 'Microsoft.SharePoint.Client.Form'"

Reason is there is a conflict between ‘System.Windows.Forms.Form’ and ‘Microsoft.SharePoint.Client.Form’

Solution:
Just after changing the code

To

public partial class MainForm : System.Windows.Forms.Form
    {
        public MainForm()
        {
            InitializeComponent();
        }

From

public partial class MainForm : Form
    {
        public MainForm()
        {
            InitializeComponent();
        }

Problem fixed.

Windows Phone Emulator is unable to create the virtual machine:

2014-06-23T22:43:00.003-07:00

Windows Phone Emulator is unable to create the virtual machine:

Couldn't change Processor of the virtual machine: 'Emulator 8.1 720P 4.7 inch....' failed to modify device 'Processor'. (Virtual machine ID {GUID})

Cannot assign the specified number of processors for virtual machine 'Emulator 8.1 720P 4.7 inch....' is out of range. The range is 1 through 1. (Virtual machine ID GUID)

Solution:

For VMWare, - click on the Edit Virtual Machine Settings and Change the Processor from 1 to more.

Restoration of the configuration database by using the built-in backup and restore functionality is not supported in SharePoint products

2014-05-21T19:56:00.003-07:00

After having a technical discussion with on the client, I came to notice the key aspect of SharePoint Config DB. Thanks SW :)

I never noticed this specific characteristics of Config DB

We do not support restoration of the configuration database in SharePoint products using the built in backup and restore functionality.

If you restore the configuration database, data in the configuration database will not be synchronized with data in other SharePoint databases. If this data is not synchronized, users may experience various random errors.

For example, a Windows SharePoint Services 3.0 content database may contain data about a newer site. If the configuration database does not contain information about this site, the site is orphaned.

http://support.microsoft.com/kb/948725/en-us

happy learning...

Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance

2013-12-01T22:57:00.000-08:00

Event Type:    Error
Event Source:    Office SharePoint Server
Event Category:    Office Server Shared Services
Event ID:    6482
Date:        2/12/2013
Time:        4:39:40 PM
User:        N/A
Computer:    "SERVER NAME"
Description:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (75d4a317-f4ef-4afb-a3c6-c907afccceba).

Reason: Cannot open database "SharedServices_DB" requested by the login. The login failed.
Login failed for user 'CORP\SERVERNAME$'.

Techinal Support Details:
System.Data.SqlClient.SqlException: Cannot open database "SharedServices_DB" requested by the login. The login failed.
Login failed for user 'CORP\SERVERNAME$'.
   at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.SqlClient.SqlConnection.Open()
   at Microsoft.Office.Server.Data.SqlSession.OpenConnection()
   at Microsoft.Office.Server.Data.SqlSession.ExecuteNonQuery(SqlCommand command)
   at Microsoft.Office.Server.Administration.SharedObjectStore.Initialize()
   at Microsoft.Office.Server.Administration.SharedObjectStore.GetObject[T]()
   at Microsoft.Office.Server.Administration.SharedResourceProvider.Microsoft.Office.Server.Administration.ISharedObjectStore.GetObject[T]()
   at Microsoft.Office.Server.Administration.SharedApplicationCollection`1.GetValue(SharedResourceProvider sharedResourceProvider)
   at Microsoft.Office.Server.Administration.SharedApplicationCollection`1.get_Item(SharedResourceProvider sharedResourceProvider)
   at Microsoft.Office.Server.ServerContext.GetApplication[S,T](String name)
   at Microsoft.Office.Server.Search.Administration.SearchContext..ctor(ServerContext serverContext, Boolean cached)
   at Microsoft.Office.Server.Search.Administration.SearchDataAccessServiceInstance.Synchronize(Boolean bCalledFromSSI)
   at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

---
Solution:

Below is the step by step provided by Microsoft in this KB Article for doing this:

Stop the Windows SharePoint Services Timer service (Found in Windows Services)
Navigate to the cache folder
In Windows Server 2008, the configuration cache is in the following location:
Drive:\ProgramData\Microsoft\SharePoint\Config
In Windows Server 2003, the configuration cache is in the following location:
Drive:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config
Locate the folder that has the file "Cache.ini"
(Note: The Application Data folder may be hidden. To view the hidden folder, change the folder options as required)
Back up the Cache.ini file.
Delete all the XML configuration files in the GUID folder. Do this so that you can verify that the GUID folder is replaced by new XML configuration files when the cache is rebuilt.
Note When you empty the configuration cache in the GUID folder, make sure that you do not delete the GUID folder and the Cache.ini file that is located in the GUID folder.
Double-click the Cache.ini file.
On the Edit menu, click Select All. On the Edit menu, click Delete. Type 1, and then click Save on the File menu. On the File menu, click Exit.
Start the Windows SharePoint Services Timer service
Note The file system cache is re-created after you perform this procedure. Make sure that you perform this procedure on all servers in the server farm.
Make sure that the Cache.ini file in the GUID folder now contains its previous value. For example, make sure that the value of the Cache.ini file is not 1.

- See more at: http://www.social-point.com/sharepoint-2010-event-id-6482-application-server-administration-job-failed-for-service-instance-microsoft-office-server-search-administration-searchserviceinstance#sthash.d9rBKjLc.dpuf

Below is the step by step provided by Microsoft in this KB Article for doing this:

    Stop the Windows SharePoint Services Timer service (Found in Windows Services)
    Navigate to the cache folder
    In Windows Server 2008, the configuration cache is in the following location:
    Drive:\ProgramData\Microsoft\SharePoint\Config
    In Windows Server 2003, the configuration cache is in the following location:
    Drive:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config
    Locate the folder that has the file "Cache.ini"
    (Note: The Application Data folder may be hidden. To view the hidden folder, change the folder options as required)
    Back up the Cache.ini file.
    Delete all the XML configuration files in the GUID folder. Do this so that you can verify that the GUID folder is replaced by new XML configuration files when the cache is rebuilt.
    Note When you empty the configuration cache in the GUID folder, make sure that you do not delete the GUID folder and the Cache.ini file that is located in the GUID folder.
    Double-click the Cache.ini file.
    On the Edit menu, click Select All. On the Edit menu, click Delete. Type 1, and then click Save on the File menu. On the File menu, click Exit.
    Start the Windows SharePoint Services Timer service
    Note The file system cache is re-created after you perform this procedure. Make sure that you perform this procedure on all servers in the server farm.

Below is the step by step provided by Microsoft in this KB Article for doing this:

Stop the Windows SharePoint Services Timer service (Found in Windows Services)
Navigate to the cache folder
In Windows Server 2008, the configuration cache is in the following location:
Drive:\ProgramData\Microsoft\SharePoint\Config
In Windows Server 2003, the configuration cache is in the following location:
Drive:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config
Locate the folder that has the file "Cache.ini"
(Note: The Application Data folder may be hidden. To view the hidden folder, change the folder options as required)
Back up the Cache.ini file.
Delete all the XML configuration files in the GUID folder. Do this so that you can verify that the GUID folder is replaced by new XML configuration files when the cache is rebuilt.
Note When you empty the configuration cache in the GUID folder, make sure that you do not delete the GUID folder and the Cache.ini file that is located in the GUID folder.
Double-click the Cache.ini file.
On the Edit menu, click Select All. On the Edit menu, click Delete. Type 1, and then click Save on the File menu. On the File menu, click Exit.
Start the Windows SharePoint Services Timer service
Note The file system cache is re-created after you perform this procedure. Make sure that you perform this procedure on all servers in the server farm.
Make sure that the Cache.ini file in the GUID folder now contains its previous value. For example, make sure that the value of the Cache.ini file is not 1.

Below is the step by step provided by Microsoft in this KB Article for doing this:

Stop the Windows SharePoint Services Timer service (Found in Windows Services)
Navigate to the cache folder
In Windows Server 2008, the configuration cache is in the following location:
Drive:\ProgramData\Microsoft\SharePoint\Config
In Windows Server 2003, the configuration cache is in the following location:
Drive:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config
Locate the folder that has the file "Cache.ini"
(Note: The Application Data folder may be hidden. To view the hidden folder, change the folder options as required)
Back up the Cache.ini file.
Delete all the XML configuration files in the GUID folder. Do this so that you can verify that the GUID folder is replaced by new XML configuration files when the cache is rebuilt.
Note When you empty the configuration cache in the GUID folder, make sure that you do not delete the GUID folder and the Cache.ini file that is located in the GUID folder.
Double-click the Cache.ini file.
On the Edit menu, click Select All. On the Edit menu, click Delete. Type 1, and then click Save on the File menu. On the File menu, click Exit.
Start the Windows SharePoint Services Timer service
Note The file system cache is re-created after you perform this procedure. Make sure that you perform this procedure on all servers in the server farm.
Make sure that the Cache.ini file in the GUID folder now contains its previous value. For example, make sure that the value of the Cache.ini file is not 1.

Insufficient SQL database permissions for user '' in database '' on SQL Server instance ''. Additional error information from SQL Server is included below.

2013-12-01T21:25:00.001-08:00

Event Type:    Error
Event Source:    Windows SharePoint Services 3
Event Category:    Database
Event ID:    5214
Date:        2/12/2013
Time:        2:51:05 PM
User:        N/A
Computer:    SERVERNAME
Description:
Insufficient SQL database permissions for user '' in database 'SharePoint_ConfigDBXX' on SQL Server instance 'SERVERNAME'. Additional error information from SQL Server is included below.

The EXECUTE permission was denied on the object 'proc_getNewObjects', database 'SharePoint_ConfigDBXX', schema 'dbo'.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

----

The procedure to solve the problem follow these steps:

    Open the SQL Management Studio
    Locate the database that presents the problem in my case was 'SharePoint_Config'
    Open the database and then Security> Roles> Database Roles
    In the right part of the window, right-click the role WSS_Content_Application_Pools and click on properties
    Select from the left menu option "Securables"
    By clicking "Add"
    Select "Specific objects" and click "OK"
    Click "Object Types", select "Stored Procedures" and click "OK"
    Add the stored procedures in the error in my case was the proc_GetNewObjects but it is also important to check whether the following stored procedures are added; proc_FetchDocForUpdate, proc_GetWebMetaInfo, proc_UpdateDirtyDocument, proc_UpdateListItem not I be there to add.
    Click Ok to add these stored procedures
    Teams stored procedures that were added and select "Execute" in the column of "Grant"
    Click "Add" once again
    Select "Specific objects" and click "OK"
    Click "Object Types", select "views" and click "OK"
    Check if the view is added UserData otherwise select to add
    Click on ok to add this view
    Teams eye that was added and select "Select" column of "Grant"
    Click on ok to finish.

Once this procedure done mistakes of 5214 should no longer appear in the event viewer of the server.

ref: http://mundomoss.blogspot.com.au/2010/04/sharepoint-error-5214-execute.html

Design Manager feature in SharePoint 2013

2013-11-26T15:57:00.001-08:00

Design Manager is a feature in SharePoint 2013, which will make designer job easier to create a fully customized design while using the web-design tools that we're already conversant with.

Design Manager is a publishing feature that is available in publishing sites in both SharePoint Server 2013 and Office 365. You can also use Design Manager to brand the public-facing website in Office 365. To enable the Design Manager for the SharePoint sites, go to site settings under the Site Collection Feature enable the SharePoint Server Publishing Infrastructure.

Than go to the Site Features section and activate the SharePoint Server Publishing feature.

After activating the features, when click on the Site Settings menu you can the Design Manager has been enable for the designer. Please refer the following screen capture.

With the help of Design Manager, you can create a visual design for your website by using whatever web design tool design prefer, using only HTML and CSS, and then upload that design into SharePoint. Design Manager is the central hub and interface where you manage all aspects of a custom design.

To interact with SharePoint projects in Visual Studio, your system user account must have administrator privileges.

2013-09-30T22:16:00.001-07:00

When I run my Visual Studio 2012/2013 Preview with SharePoint 2013 App the following error shown
"Microsoft Visual Studio

This task requires the application to have elevated permissions.

Why is using the Administrator or other account necessary?
[^] Hide error information
[Restart under different credentials] [Cancel the task and return to Microsoft Visual Studio]

Unable to open the Web site 'http://siteapp:420'. Unable to access the IIS metabase. You do not have sufficient privilege to access IIS web sites on your machine."

When I skipped this message and tried to deploy the solution, I following error message was thrown.

"Error 1 To interact with SharePoint projects in Visual Studio, your system user account must have administrator privileges."

To avoid the above problem, please login to your system or development VM using administrator privileged user not with real Administrator or System Account or localadmin user IDs.

After you logged in with administrator privileged user, hold shift and right click on Visual Studio 2012 and run with other account. Problem Solved.

Hope this helps.

Error occurred in deployment step 'Uninstall app for SharePoint': The local SharePoint server is not available. Check that the server is running and connected to the SharePoint farm.

2013-09-30T20:21:00.001-07:00

After a frustrating search results from internet. I though of looking into my Event Viewers. And I found the following error message.

"SQL database login for 'SharePoint_Config' on instance 'SERVERNAME' failed. Additional error information from SQL Server is included below.
Login failed for user 'CORP\MYID'."

I opened the Microsoft SQL Server 20008 Management Studio and given access to the ID in which I am running my Visual Studio. Now it works. Problem solved.

Hope this helps.

Error occurred in deployment step 'Install app for SharePoint': The System Account cannot perform this action.

2013-09-30T18:24:00.003-07:00

After different suggestion tried from Internet search I found the following 2 options worked for me.

1) Follow the article steps http://www.codeproject.com/Articles/515677/MyplusFirstplusSharepoint-HostedplusAppplusinplus2

and reset your IIS. It will work

2) This is a security feature in the SharePoint 2013 that you cannot deploy an app using System Account. So what is the alternative?

Create another account and give permissions, so that it is NOT the system account.

So I did the following: •Created a new account in AD as “admin1”
•Added “admin1” account into Farm Administrator’s group in Central Admin
•Added “admin1” account as Site Collection administrator to the target developer site
•Added “admin1” account into local administrators group

Ref:

To "Run as different user" using Context Menu

1. Press and hold the Shift key and right click on the program's shortcut or BAT, CMD, EXE, MSC, or MSI file, then click/tap on Run as different user. (See screenshot below)

2. Type in the user name and password of the user account that you want to run this program as. (see screenshot below)
NOTE: If the user account is on a domain, then you would use UserName@Domain or Domain\UserName for the user name instead.

3. If prompted by UAC, then click/tap on Yes.

4. The program will now be running as that user.

5. When done, simply close the program to stop it from running as that user.

Helpful Post ref:
http://www.sevenforums.com/tutorials/419-run-different-user.html
http://blog.mannualag.com/2013/03/07/nuisances-of-starting-developing-apps-for-sharepoint-2013/