Comments on: en: Crashing SQL Server 2005 Upgrade Advisor error

By: Sikots

Sikots — Mon, 03 May 2010 14:29:53 +0000

Confirmed…
God damn Microsoft! Just wasted 4 hours before I found this article! Thanks stug for the cure for this cancer

By: Deb

Deb — Wed, 24 Mar 2010 19:58:14 +0000

I was getting an error referring to my password not being strong enough – an Upgrade Advisor Returned -1 error – which when I sent the link referred to a “weak” password problem. It wasn’t the password that was the problem – it was the .NET 3.5. I unstalled all .net software, had the install package reinstall 2.0 and then it worked just fine.
Thanks!

By: JM Wozniak

JM Wozniak — Tue, 16 Mar 2010 17:44:05 +0000

I alos had to copy the files on level up and then the application worked just fine…thanks all.

By: Pete The Van

Pete The Van — Thu, 18 Feb 2010 14:14:18 +0000

@stug says: (August 27, 2009 at 11:04 am) Reply and @Mark

This fixed my problem – many thanks guys.

By: Mark

Mark — Mon, 12 Oct 2009 20:43:01 +0000

Messing with the Microsoft.NET versions did not help me at all, but copying the BPAClient.dll file up one directory did. I had to copy that file from C:\Program Files\Microsoft SQL Server 2005 Upgrade Advisor\BPA\bin to C:\Program Files\Microsoft SQL Server 2005 Upgrade Advisor\BPA and the BPAcmd.exe error went away and the analysis ran with no problems. Thanks!

By: Tony

Tony — Tue, 22 Sep 2009 11:10:26 +0000

Thank you, thank you, thank you! Microsoft, eh?

By: stug

stug — Thu, 27 Aug 2009 10:04:21 +0000

Hi,

asked Microsoft for any solution and got THE SOLUTION! If you run the Advisor in a Microsoft.NET 3.5 enviroment.

The file: BPAClient.dll is called in “C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\BPA”
but setup copied it to “C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\BPA\Bin”.
Copy that file to the first filesystem link. If that doesnt work, copy the content of the whole folder to the other.

PS: It’s a Microsoft bug. So the support call was for free

By: Abdul

Abdul — Wed, 26 Aug 2009 15:13:28 +0000

Thank you so much, I have spent all day banging my head against a wall trying to figure out why I could not upgrade my MSDE2000 instance to SQL Server 2005 Express!

Upgrade Advisor didn’t mind the original installation of NET Framework being installed on the server, but it didn’t like Framework 3.5 SP1 on there at all.

Microsoft can be stupid sometimes, can’t they

By: GP_Pro

GP_Pro — Tue, 16 Jun 2009 05:07:41 +0000

UN-F-ING BELIEVABLE! Hours wasted scouring for an answer that should have been CLEAR in MSFT documentation and/or help files. Why can’t they get their aps to play nicely with one another?

Thank you SO MUCH for this post….I may get to bed before mid-night after all!

Some days being an independant consultant isn’t all it’s cracked up to be….this was one of those days!

By: Steve

Steve — Thu, 02 Apr 2009 12:39:18 +0000

Brilliant.

Just a point to note. I had to remove the .Net framework 2.0 completely and let the SQL Installer re-install it for this to work. Presumably becuase the framwork 2.0 had been updated by windows update.