Jazz server not starting after DOORNEXTGEN beta3 install
Hello,
I have tried to install DOORS NEXT GEN beta 3 on a Windows 2008 Server 64 bits. The installation succeeds without any problem but when I click on the shortcut to start DOORS Server, I see a cmd box appearing and then disappearing directly and the Server is not started.
Anyone can help ?
Thanks
Mokhtar
I have tried to install DOORS NEXT GEN beta 3 on a Windows 2008 Server 64 bits. The installation succeeds without any problem but when I click on the shortcut to start DOORS Server, I see a cmd box appearing and then disappearing directly and the Server is not started.
Anyone can help ?
Thanks
Mokhtar
Accepted answer
This behaviour can occur if there is not enough memory on the machine - reference the section titled Memory on the Getting Started Guide for Beta3. Let us know if this doesn't solve your problem and we can get on of our server team to help you out.
3 other answers
In which location did you install the server?
If it is "C:/Program Files/IBM" then you will need administrator privileges to start the server. From the start menu you can right click and "Run as administrator"
If it is "C:/Program Files/IBM" then you will need administrator privileges to start the server. From the start menu you can right click and "Run as administrator"
To check what was wrong, I opened a command box as administrator.
I moved to C:\Program Files\IBM\DOORSNGS\Server directory.
When I run server.startup.bat I get the following message :
Files\IBM\DOORSNGS\server\tomcat"" was unexpected at this time.
I moved to C:\Program Files\IBM\DOORSNGS\Server directory.
When I run server.startup.bat I get the following message :
Files\IBM\DOORSNGS\server\tomcat"" was unexpected at this time.
Comments
Sorry I am not sure what to suggest. I hope somebody else in the community might have an answer.
I just installed a new version today, and ran the DNG server from Start Menu -> IBM Collaborative Lifecycle Management -> Start the Jazz Team Server with administrator privileges.
It brings up a cmd window which goes away after starting a 2nd command window it is this 2nd window that contains the server. If this 2nd cmd window is not appearing the only thing I can think of is the installation was incomplete or their is a privilege problem in starting this 2nd cmd window. But not sure why.