SQL Server 2005 Upgrade Advisor Issues

I am getting set up to upgrade a couple of servers from 2000 to 2005,
so am running Upgrade Advisor. It's running remotely on an XP Pro
client, the servers are Server 2003 running SQL Server 2000, one is
SP3, the other is RTM. Neither server is running .NET 2.0.

The issue is I am getting many "Attempted to read or write protected
memory. This is often an indication that other memory is corrupt."
errors. Has anyone else run into this? Any resolutions?

On Aug 22, 2:49*pm, Chris wrote:
> I am getting set up to upgrade a couple of servers from 2000 to 2005,
> so am running Upgrade Advisor. It's running remotely on an XP Pro
> client, the servers are Server 2003 running SQL Server 2000, one is
> SP3, the other is RTM. Neither server is running .NET 2.0.
>
> The issue is I am getting many "Attempted to read or write protected
> memory. This is often an indication that other memory is corrupt."
> errors. Has anyone else run into this? Any resolutions?

I have gotten a test server set up & run the Upgrade Advisor locally.
I did not see these errors, so it seems to be some connectivity issue
with trying to run remotely. Googling the error message gets a lot of
DotNet development hits, but that isn't too helpful in this case. I do
have it running on an account that has full admin rights on the remote
box--without that it would not even connect, so permissions is
unlikely to be the issue.