Sandbox Issue - Can't create sandbox
![](http://jazz.net/_images/myphoto/d555a0383adde211148106d6a4615203.jpg)
I just tried to create sandbox projects on both instances and for both I got an error which indicated I should retry the operation (meaning the projects weren't created). When retrying the operation though, I got a message indicated only one project is allowed per user, so I ended up with no sandbox at all.
How can we correct this?
One answer
![](http://jazz.net/_images/myphoto/d555a0383adde211148106d6a4615203.jpg)
Hi Taly -- sorry to hear that you're having trouble creating projects in our cloud trial environment. What is the name of the project that you were trying to create and what is your jazz id?
Comments
![](http://jazz.net/_images/myphoto/d555a0383adde211148106d6a4615203.jpg)
Hi Miran.
I use jazz id "htaly" and attempted to created the projects with the default suggested name "htaly's Project"
![](http://jazz.net/_images/myphoto/99bef4babf1a0e11accd888fe5b2b2d6.jpg)
Thanks Taly. I've let our operations team know. Hope to have an answer for your soon.
![](http://jazz.net/_images/myphoto/d555a0383adde211148106d6a4615203.jpg)
@mbadzak - have you heard back?
![](http://jazz.net/_images/myphoto/99bef4babf1a0e11accd888fe5b2b2d6.jpg)
Hi Taly -- Everything looks fine with your account. Do you know which sandbox (which url) you were using to create a project? Also, can you please take a screenshot of the issue you're seeing and attach it here?
![](http://jazz.net/_images/myphoto/d555a0383adde211148106d6a4615203.jpg)
I'm getting the same error on all 3 urls
Attached the error screenshots for each instance.
Even though the error message is the same ("project name already in use"), the behavior is a little bit different in each instance. Also note that I get the error no matter what name I set for my project.
Sandbox 02
Sandbox 03
Sandbox 04
![](http://jazz.net/_images/myphoto/99bef4babf1a0e11accd888fe5b2b2d6.jpg)
Hi Taly -- unfortunately we're experiencing a bit of difficulty with all of our cloud trials. We're working hard to resolve the issue.
showing 5 of 6
show 1 more comments