SharePoint Project Task List will not create Project Site for Enterprise Project Solution (error code 26000) RRS feed

  • Question

  • We are having difficulties setting up our project site and loading a few MS Project schedules to be utilized as Enterprise Projects. The steps taken which have identified our issue are as follows:

    1. From the project center we go to the tools, getting started.
    2. Create a new SharePoint task list
    3. We enter the project name and wait for the que.
    4. When the process is over, the text states that they were unable to create the project site and to return to the project center.
    5. Once in the project center, we see the site. However, if you attempt to go to PWA and then Connected SharePoint Sites, the site is there with no site address available.

    In addition, when we have actually been successful at loading the schedule and making it a Enterprise Project, it will eventually error out when we attempt to open it in Project Pro telling me that I need a different version of the Project Software. I have 2013 already. I believe it asks for 2016...

    This is the error message we get via email when the project site does not create.

    "The errors returned from the queue are as
     Error ID: 26000
    Detailed error below - send it to the administrator for more detailed
    <?xml version="1.0" encoding="utf-16"?>
    <errinfo> <general> <class name="Queue"> <error
    id="26000" name="GeneralQueueJobFailed"
    MessageType="CreateWssSiteMessage" MessageId="1"
    CorrelationUID="381f3e9d-40f9-2000-0a26-f08ca41c69dd" />
    </class> </general> </errinfo>

    You can do the following:
    1. Try troubleshooting using the error IDs, error XML.
    2. Contact administrator with your jobID (9dcb5861-8682-e511-80ee-00155db09012)
    and error XML."

    We have looked at the groups and users in Office 365. There are groups we do not need and that do appear to be a part of an upload that had fields in the wrong place. For example we have a group called "1st Floor". I assume this was a task in a construction schedule. We also have users loaded to the active directory who do not have licenses. This was the other thing I thought may be the issue.

    Any help is greatly appreciated. Thank you for looking!

    Wednesday, November 4, 2015 10:52 PM