From: Sent and receive mail SBS2008 on
When we works on the SQL server itself with the SQL Server Manager, we
receive regular the following error message:

attemted to read or write protected memory. this is often an indication that
other memory is corrupt.

Google find the following for me, http://support.microsoft.com/kb/926421/,
but this update is for a 32 bit environment.

Do one of you know a solution for me, or tell me where I can find the 64bits
hotfix?

From: Uri Dimant on
What is the version of SQL Server you are working on?
Memory? OS?



"Sent and receive mail SBS2008"
<SentandreceivemailSBS2008(a)discussions.microsoft.com> wrote in message
news:FD787012-274E-495D-BE9E-8CDD9232728E(a)microsoft.com...
> When we works on the SQL server itself with the SQL Server Manager, we
> receive regular the following error message:
>
> attemted to read or write protected memory. this is often an indication
> that
> other memory is corrupt.
>
> Google find the following for me, http://support.microsoft.com/kb/926421/,
> but this update is for a 32 bit environment.
>
> Do one of you know a solution for me, or tell me where I can find the
> 64bits
> hotfix?
>


From: Sent and receive mail SBS2008 on
Our server is running as a VM in a ESX host as a Windows 2003 server with SP2
4GB Ram
SQL2005 with SP3

"Uri Dimant" wrote:

> What is the version of SQL Server you are working on?
> Memory? OS?
>
>
>
> "Sent and receive mail SBS2008"
> <SentandreceivemailSBS2008(a)discussions.microsoft.com> wrote in message
> news:FD787012-274E-495D-BE9E-8CDD9232728E(a)microsoft.com...
> > When we works on the SQL server itself with the SQL Server Manager, we
> > receive regular the following error message:
> >
> > attemted to read or write protected memory. this is often an indication
> > that
> > other memory is corrupt.
> >
> > Google find the following for me, http://support.microsoft.com/kb/926421/,
> > but this update is for a 32 bit environment.
> >
> > Do one of you know a solution for me, or tell me where I can find the
> > 64bits
> > hotfix?
> >
>
>
> .
>