Kashif Nizam Qureshi


Leave a comment

Site Collection Feature Activation Failed

I tried activating feature from site collection feature GUI, but threw an error. Just like a normal SP guy, I took shovel and starting digging into SP error logs. At first it was pointing to very unrelated items as given below.

Failed on try1 to load XML document at path ‘C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\Template\Features\NintexLiveAdminLinks\feature.xml': System.IO.DirectoryNotFoundException: Could not find a part of the path ‘C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\Template\Features\NintexLiveAdminLinks\feature.xml’.

I kept on digging harding :P deep in its core and found another stupid error saying

Getting Error Message for Exception System.Security.SecurityException: Access denied.

After googling for the solution, came to know to use powershell. I used the following comand

Enable-SPFeature “DHA EPM 2013 GRP Job” -url “http://server:123″

The Feature is not a Farm Level Feature and is not found in a Site level defined by the Url.

Without banging my head here and there, I went to feature hive “c:/prog/common/micro/web/15/feature…” and found that feature name is different as “DHA EPM 2013_Feature1″. This could be because I named it sometime back and somehow it kept this in itself. I correct the name in the command and it worked.


Leave a comment

Adding Resource Calendar Exceptions Programmatically

 

 

ResourceDataSet rds = _resourceClient.ReadResource(new Guid(resGuid));

// be sure that the resource is checked out !

if (rds.CalendarExceptions != null)
{
for (int i = 0; i < rds.CalendarExceptions.Rows.Count; i++)
{
// check row data…

// delete row if necessary
rds.CalendarExceptions.Rows[i].Delete();
break;
}
// don´t use GetChanges() method on the dataset !
_resourceClient.UpdateResources(resourceDataSet, false, false);
}

// Read resource data again
rds = _resourceClient.ReadResource(new Guid(resGuid));

// create new datarow
ResourceDataSet.CalendarExceptionsRow exceptionsRow = rds.CalendarExceptions.NewCalendarExceptionsRow();

// set necessary data for the new exception row here
//exceptionsRow.Start
//exceptionsRow.Finish
//exceptionsRow.Name
//exceptionsRow.RES_UID
//…

// update the resource again
_resourceClient.UpdateResources(resourceDataSet, false, false);


// don´t forget to check in the resource


Leave a comment

Project Server 2013 Sending GeneralQueueJobFailed Error Emails

You receive the following email.

Solution: Simply release some memory from server :) Mine was taking 7+ out of 8 GB (Recommended is at least 16 GB)

 

Subject: Your queue job PreparePSProjectPermissionSynchronization failed. Please contact your administrator for assistance

 

Your PreparePSProjectPermissionSynchronization job failed. Its current state is FailedNotBlocking. It was 0% complete. It entered the queue at 06/02/2014 09:24:39.

 

To get more information about the job failure, please go to Project Web App. Select Personal Settings from the left menu. Then select My Queued Jobs.

 

The errors returned from the queue are as follows:

Error ID: 26000

 

Detailed error below – send it to the administrator for more detailed troubleshooting.

 

<?xml version=”1.0″ encoding=”utf-16″?>

<errinfo>

<general>

<class name=”Queue”>

<error id=”26000″ name=”GeneralQueueJobFailed” uid=”a5295a3b-16ea-e311-93f4-3440b5c8d286″ JobUID=”5e7d692f-16ea-e311-93f4-3440b5c8d286″ ComputerName=”f7e42ffb-822b-4c26-89d7-3887749c7b49″ GroupType=”PreparePSProjectPermissionSynchronization” MessageType=”PreparePSProjectPermissionSynchronizationMessage” MessageId=”1″ Stage=”” CorrelationUID=”62d3969c-70df-e085-c7b4-902232ca1280″ />

</class>

</general>

</errinfo>

 

You can do the following:

1. Try troubleshooting using the error IDs, error XML.

2. Contact administrator with your jobID (5e7d692f-16ea-e311-93f4-3440b5c8d286) and error XML.

 

To turn off these notifications, go to PWA Settings, and then click Manage My Alerts and Reminders.

 

From this page, you can clear the check box for those notifications you no longer want to receive.

 

Microsoft Project Server


Leave a comment

Project Server 2013 SP1 Error – Derived method ‘RequiresWebPartClientScript’

Installing Project Server 2013 SP1, you welcome yourself to hell! :P

The server went down with the following error.

“Derived method ‘RequiresWebPartClientScript’ in type ‘Microsoft.Office.Project.PWA.WebParts.PWAPart’ from assembly ‘Microsoft.Office.Project.Server.PWA, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c’ cannot reduce access.”

I was wondering why this PS SP1 is such in small size, where as earlier CUs were over a GB. What I beleive it does not contain anything for SharePoint and that would have caused the issue. So I went for SharePoint 2013 SP1, an another hell! :P well it worked after couple of hours of update :)

Follow

Get every new post delivered to your Inbox.