Developers who are working with Correspondence Management solution would have encountered these errors when working with author and publish instances (see the screen grab of error below).
These errors will be seen when Author and Publish instances of Correspondence Management solution are run on same machine and if one tries to work with both author and publish instances in two different tabs of same browser. This is quite common on a development system but not on production systems.
These errors can be avoided in different ways
1) Instead of accessing author and publish with same name or IP in browser’s address bar , One can use an IP address for one instance and FQDN for another instance i.e
http://fqdn:author-port/cm/manageassets.html (for author)
http://ipaddress:publish-port/cm/manageassets.html (for publish)
2) One can use two different browsers , one for accessing author instance and another for publish instance
3) Make two entries in hosts file with same IP address but different names , i.e if one’s client machine’s IP address is xx.xx.xxx.xxx one can add following entries in the hosts file of client machine from where the author and publish CM instances are accessed via browser and access the author and publish instances with their names provided in hosts file
e.g entries in hosts file (If the system is Win XP the hosts file will be under %SystemRoot%\system32\drivers\etc\ folder )
Once the above entries are made in hosts file one can access the author and publish instances as below