OpenEMM Technical Support Forum

Problem solved by enabling DNS doctoring in firewall. Thanks for all the help.

No I did not remove the 8080. I just replaced the URL by http://localhost:8080. However I tried with http://localhost (without the 8080) and that did work too. I am having a new problem though. When I try to save the "Content" for a mailing, the system takes a long time to do the save, and...

Solved the issue.

For some reason the firewall does not like the cms.ccr.url property being set up as FQDN.

I changed it back to http://localhost:8080 and it worked.

Both classic and CM templates fail.

I have not been able to create a single template or edit the templates that come with the empty database (en_template, created by eMM-Xpress, mailinglist). The error I detailed results from clicking on the "New Template" link under "Templates"

Hi, I am having exactly the same problem. I installed OpenEMM 6.2 on a Red Hat Linux 64 bit server. Everything works except for the Templates and CMS. When I click on New Template the system just hangs. The log shows the following error message: 2011-04-04 12:57:28,041: ERROR [resin-tcp-connection-*...

The problem was caused by Sun Java JDK not being properly installed. I uninstralled Sun Java JDK and reinstalled it again and the problem was solved.

Hi,

I have successfully installed OpenEMM 6.2 on a Linux Server. I would like to password protect the OpenEMM directory where files such as logon.jp. I have tried adding .htaccess and .htpasswd files to the /openemm/webapps/core directory but this did not work.

Any help will be appreciated.

Hi, I installed OpenEMM 6.2 (from the tarball) on a RedHat Linux server today. I was able to run the start script, but I was not able to access the login console by typing: http://www.mysite.com:8080 The browser returns a "Unable to connect" message. I am using SendMail and I installed Jav...