August 13, 2008 at 10:19 pm
I'm running upgrade advisor and am getting the following errors:
"Database Server","PreUpgrade","Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.","FTCATALOGNAMERESTRICTION"
"Database Server","PreUpgrade","Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.","FTCATALOGPATH"
"Database Server","PreUpgrade","Requested registry access is not allowed.","FTMULTIPLEINSTANCES"
"Database Server","PreUpgrade","Requested registry access is not allowed.","WINSOCKPROXY"
"Database Server","PreUpgrade","Requested registry access is not allowed.","NETPROTOCOL"
"Database Server","PreUpgrade","Requested registry access is not allowed.","FTACCTPASS"
How can I eliminate this errors?
I'm running this upgrade advisor on a machine to remotely analyze a sql server cluster. When I tried to connect to the cluster I identified the cluster name "ABC" for the machine and but no instances where displayed. I found if I enter "default" for the instance it connects.
August 14, 2008 at 4:31 am
There are some known issues with SQL2005 upgrade advisor on a cluster, but I think the errors you're seeing are more security based.
Try running as a user with both sysadmin to the SQLServer and windows registry access.
HTH
Adam
August 14, 2008 at 8:45 am
I know my account has SQL Server sysadmin permissions, but I might not have Local Adminstrator rights on the cluster box.
Does anyone know what Upgrade advisor was unable to scan because of these error. I'd like to know so I can assess what didn't get scan so I can determine what code changes it might not have identified.
August 14, 2008 at 9:20 am
I'd imagine it's only trying to read the registry in an attempt to gather information on the environment it's running in. I've seen a few similar posts in an attempt to find an answer for you, but alas no answers. Have you tried running regedit on the cluster just to see if you can read certain registry values with your account?
Might be worth a try to see if this seems like a feasible reason for the errors.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply