Missing something on newly built server?

Missing something on newly built server? (Full Version)

All Forums >> [Web Development] >> Server Issues

Message

fhenkel -> Missing something on newly built server? (6/16/2006 20:09:51)
Well I built a new server 2003 on a new machine but I'm missing something. When trying to access any of the sites, using intranet address, I am getting "This Virtual Directory does not allow contents to be listed.". I mus be something I missed in the setup. Items installed are Server2003, SQL 2005 Express, SharePoint 2.0, Framework 2.0, XML 6.0, IIS 6.0 and FP Extensions 2002. The one sharepoint site comes up fine, it is with the FP extensions 2002 sites this happens?

rdouglass -> RE: Missing something on newly built server? (6/19/2006 9:22:24)
Check your default pages and be sure you have a default page in each directory. Index.htm, default.asp, etc. Also, check to see if you can browse to a specific page. If not, check the permissions on any directories to be sure the IUSR_machinename account has at least Read priv's. That give you any leads?

fhenkel -> RE: Missing something on newly built server? (6/19/2006 10:37:49)
Yep, that was the only problem. As I was working on it I noticed that I had not had anything in those directories, duh! I created each site on the new server and then published each site, from the old server, to the new server and then changed the server name to the old servers name. I then demoted the DC (old server) and promoted the new server. It all came up fine. A tip for those who may use the free MailEnable Standard Server software for their mail server, install the free MailEnable standard on the new server and don't setup anything except the default Postoffice. Then simply copy the whole MailEnable directory from the old server and overwrite the MailEnable directory on the new server. This copies all the mail as well as all the accounts, mailbox's and passwords to the new server and it is up and running. There is still one item which I have to resolve and that is that the SharePoint Services 2.0 did not "take" the server name rename. The SQL 2005 Express took it fine and renamed the SQL server automatically but I'm getting an error because SahrePoint is still looking for the "old" server name database. Any idea how I might change the STS_servername to the new one? I have done a "Repair" of the SahrePoint and it goes through fine but doesn't change this. I'm a bit leary of removing SharePoint and re-installing but that may have to be.

Page: [1]

Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

0.046875