What we end up with is a message that says "500 Internal Server error" when
we import to the production environment. Sometimes when we re-run the import
step on the sdo file that was exported, we also get that message. In that
case we retry the re-run again. If the error happens again, then an IIS
restart (through My Computer->Manage->Services->IIS Admin) on production
fixes the problem, however, we don't like to have to restart IIS on a
production system, especially during the day, which is when we usually catch
the problem.
I've researched this cryptic error message online, and it seems that there
are a myriad of causes, none of which seem to apply to our situation. Any
thoughts on what is causing this and how we might alleviate it (short of
having a scheduled event run to stop and restart production IIS before the
promote job runs)?
Thanks,
Jerome Grimmer
please have a look here for common reasons:
http://download.microsoft.com/download/4/2/5/4250f79a-c3a1-4003-9272-2404e92bb76a/MCMS+2002+-+(complete)+FAQ.htm#8F855853-100E-400F-A914-AC3A42C2EAD6
If this does not help, I would suggest to open a support case with Microsoft
to investigate this further.
Cheers,
Stefan
"jgrimmer" <nob...@naygun.com> wrote in message
news:0AEDD9F5-3475-46CC...@microsoft.com...