07-28-05 07:48 AM
Hi Ramzi,
check out my FAQ:
http://download.microsoft.com/downl...>
MCMS+2002+-+(complete)+FAQ.htm#DD159085-1AFB-4244-AE6D-D0A1C0E9E274
Cheers,
Stefan
--
This posting is provided "AS IS" with no warranties, and confers no rights
New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
----------------------
"Ramzi" <Ramzi@discussions.microsoft.com> wrote in message
news:30A6E1D1-F2D6-44CE-AF92-82BBBFB794DC@microsoft.com...
> we have been exporting SDOs with no problems for the past 3 months and
> with
> no issues.
>
> For some reason, we started to get this error message in Site Manager when
> attempting to export the SDO package.
>
> Error: 0
> Description: The remote server returned an error: (500)
> Internal Server Error.
> Severity: 5
> Source: System
> Debug info: N/A
> Extra info: N/A
> Client Source: CExProgress::ProcessPackage
> Recommended Action: N/A
>
>
> I tried the follwoing steps to no avail; did not resolve the problem..What
> do you recommend?
>
> 500 server errors are internal processing errors. Try the following
> troubleshooting suggestions:
>
> 1. Ensure that there is no web.config or global.asax file in the
> root
> of your Web site as this can cause such issues.
>
> Which .NET framework version do you use? If it is 1.1 ensure that
>
> <pages smartNavigation="false" validateRequest="false" />
> is included in your web.config. If you receive the error using one of your
> templates check the web.config in your template project. If you receive
> the
> error using Site Manager or Authoring Connector, check the web.config in
> the
> /MCMS directory.
>
> If it is .NET framework 1.0 ensure that the 'validateRequest' entry is NOT
> in the web.config.
>
> 2. Check whether there is a global.asax or a web.config in the root
> of
> your Web site. If one of these files exists, remove or rename it and test
> to
> see if the problem is gone. An error in one of these files can cause these
> kind of problems.
>
> 3. Check the event log for errors. Often an event log entry is
> written
> when a 500 error is reported
>
> 4. If this is a multiproc machine and/or hyperthreading is enabled
> and
> .NET framework 1.1 is installed then the following hotfix is required:
> 821157.
> Update: this fix is now also included in Microsoft .NET framework 1.1
> Service Pack 1 (Windows Server 2003 version, Windows 2000 version)
>
> 5. Run a virus scanner as a virus can cause such an errors.
>
> 6. If the problem happens in SiteManager try to access the following
> URL in a browser to see if an error occurs:
> http://localhost/NR/System/ClientUI/login.asp
>
> If the problem happens during Site Deployment in SiteManager try to access
> the following URL in a browser to see if an error occurs:
> http://localhost/mcms/sitedeployment/cmsxmlstub.aspx
>
> 7. If neither of these help, try the request from a machine which is
> not the MCMS server machine and ensure that
>
> <customErrors mode="Off" />
> is set in your web.config. See above about how to determine which
> web.config
> to use. Now use Network Monitor to take a trace to see the complete error
> response sent by MCMS.
>
>
> --
> MCSD.NET
[ Post a follow-up to this message ]
| 
