Discussion:
PowerDesigner Portal - installs but I can't get it to run.
(too old to reply)
Nate Hoy
2012-09-28 11:50:12 UTC
Permalink
I have a new PowerDesigner 16.1 install on 64-bit Windows Server 2008 R2 running against a repository located on a remote SQL Server database. All components of PowerDesigner are running perfectly, but I cannot for the life of me get the portal to start.

The only errors I see in cmrserver.log are:

ERROR main 2012/09/28 07:25:02 EDT com.sybase.cmr.infra.server.license.LicenseUtils.getLicenseFilePath(LicenseUtils.java:140) License file powerdesigner.server.lic does not exist in the CMR_HOME
ERROR main 2012/09/28 07:25:02 EDT com.sybase.cmr.infra.server.license.LicenseManager.initLicenseService(LicenseManager.java:104) License validation service can not be started. License library or configuration file can not be found under CMR_HOME.

CMR_HOME is set to my Portal's installation directory. That directory contains a "license" folder that has a "lib" folder with some zip files in it (sylapi 2.2.0.7.zip and sylapi 2.2.0.8fc.zip). and a couple of DLLs (sylapij and sylapij_MT). It also has a locale directory with .lcu files for English and French.

I've tried the "vanilla" 16.1 portal as well as installing the 16.1 ESD6 fixpack. Same result.

The symptoms from the client side are:
1. If I intentionally mess up my connection to the Repository, I see the signon screen in the web browser, and when trying to log in I get a message that the repository cannot be accessed.

2. If I get the Repository connection correct during setup, the browser sits on "waiting for http://servername:3030/cmr..." (where servername is my actual server name, of course) until it gives up. I cannot find any logs on the server side associated with any attempts from the client to connect.

Sybase professional services is stumped, and I've already dumped a lot of money in professional services time trying to fix this to no avail.

What am I doing wrong, please??

Thanks in advance for any advice anyone can offer!
Nate Hoy
2012-09-28 11:54:37 UTC
Permalink
Post by Nate Hoy
I have a new PowerDesigner 16.1 install on 64-bit Windows Server 2008 R2 running against a repository located on a remote SQL Server database. All components of PowerDesigner are running perfectly, but I cannot for the life of me get the portal to start.
ERROR main 2012/09/28 07:25:02 EDT com.sybase.cmr.infra.server.license.LicenseUtils.getLicenseFilePath(LicenseUtils.java:140) License file powerdesigner.server.lic does not exist in the CMR_HOME
ERROR main 2012/09/28 07:25:02 EDT com.sybase.cmr.infra.server.license.LicenseManager.initLicenseService(LicenseManager.java:104) License validation service can not be started. License library or configuration file can not be found under CMR_HOME.
CMR_HOME is set to my Portal's installation directory. That directory contains a "license" folder that has a "lib" folder with some zip files in it (sylapi 2.2.0.7.zip and sylapi 2.2.0.8fc.zip). and a couple of DLLs (sylapij and sylapij_MT). It also has a locale directory with .lcu files for English and French.
I've tried the "vanilla" 16.1 portal as well as installing the 16.1 ESD6 fixpack. Same result.
1. If I intentionally mess up my connection to the Repository, I see the signon screen in the web browser, and when trying to log in I get a message that the repository cannot be accessed.
2. If I get the Repository connection correct during setup, the browser sits on "waiting for http://servername:3030/cmr..." (where servername is my actual server name, of course) until it gives up. I cannot find any logs on the server side associated with any attempts from the client to connect.
Sybase professional services is stumped, and I've already dumped a lot of money in professional services time trying to fix this to no avail.
What am I doing wrong, please??
Thanks in advance for any advice anyone can offer!
Oh, yes. I should probably also note that I am not attempting to install the "Composer" version of Portal, just the basic "Powerdesigner Portal", that I installed the Tomcat 6 that comes with it, and that I have also tried the "Trial" option on the install to see if that gets past whatever this license problem is and it made no difference.
Loading...