You will also need to rename the physical folder under the Program Files\ASI\iMIS15\Net folder that contains the default.aspx page for the website, and fix the URL for the website's Home navigation item, if you want to change all instances of the name; I had forgotten about that one.

Eric Means
System Architect, ASI

I have renamed the site in Site Designer>Manage websites (in properties), renamed the content folder, app_theme folder and changed the master page name.  However, in Content Designer, when I change the name I get an error stating the name must be unique within the containing parent.  When I try to publish from Site Designer, it acts like it is publishing, but when I look at the Publishing Server Detail, I don't see where it is submitted, completed or errored.  There is nothing in the error log.  Site designer still shows the old URL in the status section under Manage Websites.

Make sure the content folder name is actually unique within its parent folder (you may need to check if there is a Recycled version in the Recycle Bin and Purge it if so).

Also, make sure you've performed the manual folder move (on the webserver) and fixed the Home nav item's URL.

You will not see any results in the Pub Server Detail when publishing via Site Designer; Site Designer and Content Designer use different publishing processes (Pub Servers only handle Content publishing).

Eric Means
System Architect, ASI

I don't have a recycle in this version of iMIS (15.1.2).  I used to see it under Organize, but it seems to no longer be there. 

I have renamed all instances of the old folder name on the web server with the new name.  I am not sure what you mean by "fixed the Home nav item's URL". 

Ahh.  I see.

Duhhh.  Do I feel stupid.  There is the recycle bin!  Sorry.

OK, I think I have this figured out and am now republishing.  I do see a duplicate folder name I need to blow out and then try to update the content folder name again and  republish one more time.  I do see, however, that the old name still exists in the url.  The url is http://www.my.org/imis15/newsitename/home/oldsitename/default.aspx?...  Where is it still getting that oldsitename?

That's the physical folder name (if you look on the webserver, under Program Files\ASI\iMIS15\Net) that contains the Default.aspx file for the website. You need to rename it to the new name, and then update the URL for the Home navigation item for the website, then republish that nav item.

Eric Means
System Architect, ASI

Thanks for the help, Eric, but I think that is the part I am still not getting.  The folder has been renamed.  The old folder no longer exists in the NET folder.  Where do I update the URL for the Home Navigation item? 

Found it.  Sorry.

Hi Eric.  One problem solved, to make way for another.

we are trying to deploy our customers site.  The site was origianally developed under http://imis.abc-hq.com/imis15/wcm.  They want to use a different site for the actual public facing site.  That site will be http://www.abc.org.  Both sites are physically on the same server.  We set up a hosts file entry for the url on this server since the old site is being hosted elsewhere and will be switched after we get these issues resolved. 

I followed the docs for setting this up - specifically pages 62 thru 71 of the WCM manual, including the section on hosting as an IIS website instead of an IIS application.   I copied the contents of the NET folder into the root of the web (d:\inetpubs\vhosts\abc.org\httpdocs).   Installed a second publishing service and added that service to th Publishing Servers in WCM, etc.  Both have different codes and are using different ports, etc.  I even ran the ACL commands that normally get run when setting up multi-sites even though not specified in the docs.  I checked and changed permissions ont he folder as required to match the permissions of the original folder, etc.  The new site will not come up.  I get this error:

Server Error in Application "ABC.ORG"

Internet Information Services 7.0

Error Summary

HTTP Error 500.21 - Internal Server Error

Handler "Plesk_Handler_053326038" has a bad module "ManagedPipelineHandler" in its module list

Detailed Error Information

Most likely causes:

ASP.NET is not installed or incompletely installed.

A configuration typographical error occured. Unfavourable pre-condition evaluation exists.

Publishing on both publishing servers are giving an error "the remote server returned an error:(500) Internal Server Error.  Location:  System.Net.HttpWebRequest.GetResponse. 

Any ideas?  Does this have anything to do with the <system.webserver> element?

I've never seen that error before, and I don't know what Plesk_Handler is at all.

Make sure that app pool is configured to run using the .NET 2.0 runtime with the Classic Pipleline (which will ignore the system.webserver element entirely) and is set to a 32-bit application. If it's already configured that way, you may want to try running an "aspnet_regiis.exe -ir" to ensure ASP.NET is correctly installed.

Eric Means
System Architect, ASI

Yeah, we tried that and ASP.NET seems to be installed OK.   Plesk is a third party tool used to set up web sites and it sets up the default handler mappings for the sites.  When I just try entering http://www.abc.org/default.aspx I get a slightly different error:

Server Error in Application "DEFAULT WEB SITE"

Internet Information Services 7.0

Error Summary

HTTP Error 500.21 - Internal Server Error

Handler "PageHandlerFactory-Integrated" has a bad module "ManagedPipelineHandler" in its module list

Detailed Error Information

Most likely causes:

ASP.NET is not installed or incompletely installed.

A configuration typographical error occured.

Unfavourable pre-condition evaluation exists.

Which is confusing since I am not trying to hit the "default web site"......

Are you sure it's running the Classic Pipeline for that application pool? I'm concerned that it says it's using the Integrated page handler factory there, although again I've got no experience of this error at all.

Eric Means
System Architect, ASI

The www.abc.org site is set to Classic, yes.  The default website is not.  if I change the default website to classic I get a 404 error. But I am not trying to hit the default website which is a different IP address. 

Unfortuantely I don't have a lot of experience with Plesk either.  I have been in contact with the support group for the server and they spent all day yesterday looking at it and came to the conclusion that it was an application problem. 

Based on the "Default Web Site" thing, it sounds  like maybe the host header isn't getting properly configured; the fact that changing the default web site's pipeline mode changes the result seems like confirmation of that.

Eric Means
System Architect, ASI

Hmmmm.... I just noticed something.  The site name is abc.org.  It is on an ip address ending in 117.  The server name is vms.abc.org.  Could that be the conflict?  Could that be why the abc.org url keeps trying to resolve back to the default website?