Http 404 errors

Http 404 errors

Post by Trevor Gra » Sat, 09 Aug 2003 23:31:20


Hi

Has anyone seen this before?

We have a site that has around 1000 postings based on a single template.
These postings are very similar to one another as they were created from the
same migration script on the development server. As part of the migration
process, we backed up the database and restored it on the production server
using standard SQL procedures.

Interesting thing is: out of the 1000 postings, some of them could be viewed
in published mode, but some returned a Http 404 error.

All postings
+ share the same start and expiry dates
+ have a status of Published and
+ use the same template.

The channel rendering script displays a list of the 1,000 postings correctly
in Published mode. The 404 error occurs only when trying to view the
contents of particular postings.

Any ideas?

Trevor
 
 
 

Http 404 errors

Post by Stefan [MS » Sat, 09 Aug 2003 23:52:53

Hi Trevor,

is this migration from CMS 2001 to CMS 2002?
Have you check the migration log?

Cheers,
Stefan.



the
server
viewed
correctly

 
 
 

Http 404 errors

Post by Stefan [MS » Sun, 10 Aug 2003 01:00:35

Hi Trevor,

yes it is!
And in addition this is the reason why SQL replication can cause data loss.
When SiteDeployment or another server updates content, he sets a flag that
the content has changed and all CMS frontend servers will know that they
have to invalidate their node cache. SQL replication and SQL database
restore bypasses this notification feature.

Cheers,
Stefan.




server.
deploy
Deployment
The




template.
from
 
 
 

Http 404 errors

Post by Clif Peter » Sun, 10 Aug 2003 04:05:28

Trevor,

Out of curiosity, how big of an .SDO file are you talking
about. By using the server side export/import ojects, I'm
able to process a 300Mb SDO file with over 10,000 objects.

This is after the client-side processes failed, even with
the configuration changes detailed in Stefan's site.


restart of the server.
bring everything
reason to not deploy
to use Site
the Site Deployment
another story)
2001 to CMS 2002. The
an existing
message



a single template.
they were created from
part of the
the production
of them could be
1,000 postings
trying to view the
 
 
 

Http 404 errors

Post by Trevor Gra » Sun, 10 Aug 2003 11:58:15

i

It's around 350MB and has objects in the range of 30,000 (of which the 1,000
mentioned earlier were part of them). Export was sucessful (thanks to
Stefan's troubleshooting tips posted in this NG). We were trying to use the
Site Manager Import Dialog to import them on the destination server. We
clicked Browse, located the huge SDO file, clicked Open and then waited and
waited... nothing happened. If the Browse button was clicked again, Site
Manager threw an exception saying "User aborted operation". There's probably
more tweaking involved in getting that dialog box to digest huge SDOs.

MCMS out-of-the box does not seem to have the ability to process large SDOs
without changes to the configuration settings. Even the Preview does not
support anything in excess of 10,000 objects. I'll have to try it again with
the scripts to satisfy my curiousity. Hey, how long did the import process
take for your large SDO?


Trevor

"Clif Peterson" < XXXX@XXXXX.COM > wrote in message
news:034e01c35de0$07c738a0$ XXXX@XXXXX.COM ...


 
 
 

Http 404 errors

Post by Stefan [MS » Sun, 10 Aug 2003 17:55:05

i Trevor,

is this on Windows Server 2003 or on Windows 2000?
Btw. the limitation is most likely not a limitation of CMS but of IIS, IE
and ASPNET timeout values.
These values often have to be adjusted.

Cheers,
Stefan


"Trevor Grant" < XXXX@XXXXX.COM > wrote in message
news: XXXX@XXXXX.COM ...
1,000
the
and
probably
SDOs
with


 
 
 

Http 404 errors

Post by Trevor Gra » Mon, 11 Aug 2003 00:45:09

i Stefan

It's on Windows Server 2000.

Trevor

"Stefan [MSFT]" < XXXX@XXXXX.COM > wrote in message
news: XXXX@XXXXX.COM ...
process