I'm went through the necessary steps to create a new web site using WCM. When I click save, I get the following message: Error: no publishing servers defined. I'm not sure where to look to address this.
WCM error message on Save
set up Publishing server
On January 19th, 2010 Sandeep says:
You will have to set up Publishing server in case they did not get set up at time of install.
I had done this which I found on iMIS community.
Log in to the iMIS15 application server and navigate to Content Management > Maintenance > Publishing Servers. Click the "add" link and fill in the required fields, making sure that "Local Publishing Path" is the same as the path you used above and "Local Protected Path" is a path that is not available from IIS on the webserver host (i.e. it should not be under the root of the website), but that the ASP.Net user (NETWORK SERVICE by default) has Full Control permissions for.
Also the site you created without the publishing server will have to be deleted and you will have to create a new site all over again.
You shouldn't have to delete
On January 19th, 2010 Eric Means says:
You shouldn't have to delete the site; you should just be able to reapply the template, I think.
Eric Means
System Architect, ASI
Additional information
On January 19th, 2010 Brad Cady says:
First, I should state that this is a multi-instance installation. I found that in the original installation the publishing service had been created, but not in the one I was working with. So I created it. Now I'm finding that the service won't start, and that the sites I create are not publishing correctly.
You need to edit the
On January 19th, 2010 Eric Means says:
You need to edit the PublishServer.exe.config file for the second instance, and make sure the PublishServerCode is unique for the database it's connecting to and matches the definition in Content Management > Maintenance > Publish servers.
You also need to locate the port used for remoting (by default 15151) in both PublishServer.exe.config and SearchRemoting.config (in the web root directory) and change them to a new number (15152, for example). The publishing service will then start; you may need to recycle the application pool in IIS.
Eric Means
System Architect, ASI
multi-instance installation
On January 19th, 2010 Sandeep says:
I had the multi-instance installation too and that is why I think the WCM site I setup without the Publishing server did not work right even after I published the site after setting the Publishing server.
But when I deleted the WCM site and created a new one after setting the Publishing server, it worked right.
Is this a 15.1 install?
On January 19th, 2010 Henry Huey says:
If so, the 15.1 version of the MI utility (dated 4 Sept 2009 on the Tech Support download area) will create the Publishing service ( as well as the Index catalog). It will find an open TCP port and set the two .config files appropriately. If you have the 15.1 MI utility, and it didn't create the publishing service successfully, please file an SMR so I can take a look.
Interesting - when I check
On January 19th, 2010 Brad Cady says:
Interesting - when I check the protected folder, I don't see an asp.net or Network Service user listed.
Content Management
Content Management > Maintenance > Publishing servers.
If you used the iMIS installer to create your appserver or WCM server, it should have automatically created the needed entries.
Eric Means
System Architect, ASI