> > I created a site with the MidCom site template as the template. It will > let > > me initialize either the staging or the live, but not both, I can do > either > > one, but then the other will fail to initialize. > > > > Here is what it spits at me. Any suggestions? > > > > Trying to initialize MidCOM site data correctly > > > > midcom_site root topic not found > > > > Failed to create midcom_site root topic, reason Name exists > > > > midcom_site AIS topic not found > > > > Failed to create midcom_site AIS topic, reason Name exists > > Module Status Details > > Root topic FAIL Topic midcom_site root topic not found > > Root topic component FAIL Parameter midcom_site root topic component > > not found > > AIS topic FAIL Topic midcom_site AIS topic not found > > AIS topic components FAIL Parameter midcom_site AIS topic component > > not found > > Localization topic FAIL > > Localization topic component FAIL > > You shoudl only initilize staging one as MidCOM operates on GUID and GUID > are repliactede between DBs, so when you initialized staging MidCOM it got > replicated to live after running replication script. > Well that is what I thought, but it didn't, I initialized staging, but live still shows un-initialized. Is there someway to force a reload of the live?
Right now 8001 is showing up as initialized, but 80 doesn't. I just dropped the live db and reimported and published the approvals. I'm not sure what else to do. Miles --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
