Setting up a new server and going to create first project when I get the error. I checked the analyzer but now clear answer. Logs attached
unable to create project.PNG
Community moderators have prevented the ability to post new answers.
Please note our sys admin did the following and I was able to create the project and move forward
I ran this query then it started working
ALTER DATABASE JiraProd SET READ_COMMITTED_SNAPSHOT OFF
Atlassians documentation said to do the opposite in server setup:
https://confluence.atlassian.com/doc/database-setup-for-sql-server-9258.html
ALTER DATABASE <database_name>
SET READ_COMMITTED_SNAPSHOT ON
WITH ROLLBACK IMMEDIATE;
Hi Jen,
here is what I was able to get from the support zip.
JIRA version = 7.1.9
Microsoft SQL Server - 11.00.6020
There are two errors in the log file:
1.
2016-07-28 14:06:26,884 http-nio-8080-exec-24 ERROR jenhamilton 846x1750x1 gr57p4 10.51.171.159 /rest/project-templates/1.0/templates [c.a.jira.project.ProjectCreateRegistrarImpl] The handler with id com.atlassian.greenhopper.project.PermissionSchemeProjectCreateHandlerImpl.ProjectCreateHandler threw an exception while handling a notification about a project being created
org.eclipse.gemini.blueprint.service.importer.ServiceProxyDestroyedException: service proxy has been destroyed
at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceDynamicInterceptor$ServiceLookUpCallback.doWithRetry(ServiceDynamicInterceptor.java:101)
2.
2016-07-28 14:06:28,132 http-nio-8080-exec-24 ERROR jenhamilton 846x1750x1 gr57p4 10.51.171.159 /rest/project-templates/1.0/templates [c.a.p.r.c.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: An error occurred while notifying that a project was created
java.lang.RuntimeException: An error occurred while notifying that a project was created
at com.atlassian.jira.bc.project.DefaultProjectService.notifyHandlersOfProjectCreated(DefaultProjectService.java:396)
this looks suspiciously similar to the issue described in this kb:
If it does not work I would suggest to notify Atlassian support. The errors are deep into their core codebase.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.