windows-broken-mini

Error – Directory “FeatureDirectoryName” associated with feature ‘GUID1’ in the solution is used by feature ‘GUID2’ installed in the farm.

The solution cannot be deployed. Directory “FeatureDirectoryName” associated with feature ‘GUID1’ in the solution is used by feature ‘GUID2’ installed in the farm. All features must have unique directories to avoid overwriting files. I’ve ran into this error three times now. It happens when you create two projects with the same name. This error can happen when you have two solutions with the same name, one of the solutions has…

windows-broken-mini

SharePoint 2013, The timer job for this operation has been created, but it will fail because the administrative service for this server is not enabled.

The timer job for this operation has been created, but it will fail because the administrative service for this server is not enabled. If the timer job is scheduled to run at a later time, you can run the jobs all at once using stsadm.exe -o execadmsvcjobs. To avoid this problem in the future, enable the Microsoft SharePoint Foundation administrative service, or run your operation through the STSADM.exe command line…

InitializeControl

The name ‘InitializeControl’ does not exist in the current context

I’ve ran into this error several times now. The name ‘InitializeControl’ does not exist in the current context There have been several suggestions on how to fix this, some blogs say to create a new Visual Web Part in the Template folder and copy it back into the Web Part Project and a myriad of other mumbo jumbo. I discovered the cause of the problem by reading a connect.microsoft submission,…