Can't create a Service Desk Project

Stefan Panic

Hi

Whenever I try to create a Service Desk Project, it fails with the following error-message: "Hmm... we couldn't create your project due to an unknown error. Try refreshing the page to start again."

The atlassian-jira.log showes following error: 

/rest/project-templates/1.0/templates [c.a.p.r.c.error.jersey.ThrowableExceptionMapper] Uncaught exceptio$
java.lang.RuntimeException: An error occurred while notifying that a project was created
        at com.atlassian.jira.bc.project.DefaultProjectService.notifyHandlersOfProjectCreated(DefaultProjectService.java:397)
        at com.atlassian.jira.bc.project.DefaultProjectService.createProjectInternal(DefaultProjectService.java:379)
        at com.atlassian.jira.bc.project.DefaultProjectService.createProject(DefaultProjectService.java:349)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

The suggested resolutions didn't help much. Did someone here experience something similiard to this with Service Desk? 

 

Thanks

 

 

somethingblue

Hi Stefan,

What solutions have you tried at this point and does this happen on all projects or only Service Desk projects?

There is an article titled Couldn't create your project due to an unknown error. Try refreshing the page to start again that may be of assistance if you have not seen it already.  The article describes the cause as follows:

Due to there are NPE on the permission scheme, where a reference on the permission scheme is missing. This can be confirmed with the SQL query:

select * from schemepermissions where perm_type = 'user' and (perm_parameter in (select user_key from app_user where lower_user_name not in (select lower_user_name from cwd_user)) or perm_parameter not in (select user_key from app_user));

If you do see missing permissions please follow the steps in Couldn't create your project due to an unknown error. Try refreshing the page to start again.

If that does not work, the next step would be to turn up the logging for Service Desk and provide the debug logs.

Cheers,

Branden