Resolution for Metadata Folder Property Change Error

  • Updated

If a change to metadata folder properties causes the below error, here are some steps you can use to help diagnose/resolve the issue.
Could not connect to http://localhost:8732/Ektron.ASM.EktronServices/CmsHelperService.svc. TCP error code 10061: No connection could be made because the target machine actively refused it

This error is telling us there is a communication issue on the server and it is likely for one of the below reasons.

1) One possible cause is an issue with security certificates. In version 8.02 the security certificates(same certificates used in eSync) can play a role in the Ektron Windows Service's basic interactions with the workarea. One of those areas is metadata folder properties. To identify if certificates are the cause, please do the following.:

In the Windows Services applet, stop and start the Ektron Windows Service(EWS). It is recommended that you do not do this during a sync or if you are using eCommerce it should be done during a slow period. Now check your L2 logs in your Windows Event Viewer logs(Services and Applications > Ektron L2). If you see nothing logged, change your DebugEnabled value in EWS config file(C:\Program Files (x86)\Ektron\EktronWindowsService30\Ektron.ASM.EktronServices30.exe.config) to one, then stop and start the service again. If you get a message other than the service successfully it's a safe bet that you'll need to regenerate security certificates. Because you don't want to effect existing sync relationships(if present), you should generate security certificates without discarding existing certs(box to discard should be unchecked).

Run this utility as an admin to generate those certs.
'C:\Program Files (x86)\Ektron\CMS400v80\Utilities\SOFTWARE\SecurityConfigurator'

The utility will automatically start and stop the EWS so you can immediately check the logs. If it is still not starting successfully, please call support.

Once it's starting successfully, identify if the issue is still occurring.

2) Another cause could be a communication issue on the server. Make sure that 'localhost' is added to your host file on the server.
Line in host file:

Confirm that you can successfully ping localhost while on the server.

Next, stop and start the EWS and re-evaluate the issue.

If you're still seeing the issue, please call support.

This issue is analogous to many other EWS issues but results may vary depending on your site and CMS version. If you run into issues implementing these steps or have additional questions, please contact support.