Hi all; I've searched the forums and the blogs and found nojoy in resolving our issue. We lost our Centrla and one primary site server last week due to machine and virus issues. We have reinstalled the servers (CS on a W2K3 phys box and PS on W2k8 VM) and I've gotten (with errors resolved and fixed in the meantime) the Central site up to teh SP2 level. SP1 installed OK (although there were minor errors which were fixed and the installation finally went through, with an error installing the MP which was also resolved). Tried to install R2 and got the dreaded "Setup cannot update the database. Make sure the SQL server is on the network and your computer account has sysadmin rights to the database". So, I decided to go ahead and install SP2 (since R2 can be applied either to SP1 or 2) and it installed OK with the exception of installing the MP. I suspect that was due more to the old MP being published to AD and not removed prior to this installlation. I'm OK with that since that doesn't affect functionality needed for the Central site as yet. However, I cannot for the life of me figure out how SP1 and SP2 can install OK and R2 cannot update the DB. The machine account is not only an administrator on the SQL machine, it's also got sysadmin and securityadmin privileges on all databases. The account I'm trying to install with is the same. Unfortunately R2 doesn't seem to be updating teh setup log either since the last entry is date/time stamped with the time Sp2 was installed. Any ideas what to check will be greatly appreciated. The accounts (machine and installation) all are also SPNs on the SQL box which was from the last installation. The server name is the same, so that should not affect the SPN. Same applies to the installation account. THANKS!

R2 has its own setup log. I don't remember exactly where it is but I vaguely remember it being created in the current user's TEMP directory (use %TEMP% to get there).Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Not sure what happened, but this seems to have fixed itself and we were able to install R2 and SP2 without issue.