A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More.
AI OnAI Off
Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Vote:
I get the exception:
Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
when installing RC1 or RC2 on a virtual Win 2k3 server with a SQL 2000.
The exception occurs as the installation process is "installing config file /web.config".
Any ideas?
Jun 01, 2007 16:13
Did you have any previous SDK version of EPiServer CMS installed on that virtual PC?
If so - uninstall that and try the Manager again - might help.
#16160
Jun 02, 2007 17:59
There are no previous SDK versions of EPiServer CMS installed on the virtual server.
#16161
Jun 04, 2007 9:50
This exception is thrown by the CLR to prevent buffer overflow. Some stack trace information, or method which throws this exception would be helpful when debugging.
Generally this exception involves the usage of /unsafe code I am not sure if EPiServer uses any unsafe code, but if so it can be a bug, otherwise it's probably a bad parameter to the framework somewhere.
#16162
Jun 13, 2007 13:39
Please try this.
http://support.microsoft.com/default.aspx/kb/923028
Do post back if this worked or not.
#16163
Dec 10, 2007 6:49
While attempting what outlined in the post by Sidharth Ranka the hotfix installer threw up a message saying that the "component in question" was no longer installed. So it did not work.
Anyone else have a solution for this problem?
Oct 23, 2008 14:50
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
