Sage CRM

Along with upgrading our Sage 100 from 4.5 to 2013, I moved Sage CRM to the new VM (Windows 2008 R2 instead of 2003 with Crystal 2011 instead of Crystal 11.5.) After upgrading to 7.1 SP2, the Tomcat dashboards work if you run CRM on the server, but I get the ""The dashboard has experienced a problem"" again. Turned off the firewall on the server and it did not resolve the problem. Any ideas?

Could be a DNS issue. @PeterWolf helped me with this once on the forum a few months ago, but I don't recall what it was right off hand.

Found the post: https://90minds-com.socialcast.com/messages/14139417?ref=stream

Thanks @AaronClark. That pointed me in the right direction, but the situation is a little different. Since the server is in my house, and Comcast rules say you can't run a web server on a home connection, I have IIS bound to another port besides 80, and have the router forward that port to that VM. I did not set that up on this VM until after I installed CRM. The IIS part of CRM works on either port, but the Tomcat stuff only works on port 80. Does anyone know where the configuration file for the handoff from IIS to Tomcat is?

The CRM to Tomcat should be internal, but I hate messing with ports on CRM no matter what. Instead of changing the port on IIS, why not do a port trigger to convert traffic on port XYZ to port 80 on your internal network?

Well, now I have the reverse of your issue - the dashboards work on the internal IP but not from the external URL...

So, what happens if you use the external address (a la http://pmstudmuffin.dyndns.org/CRM/) inside the network? Does it resolve correctly, or does it give you the ""Dashboard has experienced a problem""?

Internal IP works, external url gives ""Dashboard has experienced a problem"" from inside the network and from outside

So, what's probably happening is that CRM (internally) and externally can't resolve the name. Put an entry in the hosts file of your server for the fqdn, and point it to the IP of the server.

Go to 7.1 sp2