Uprgade SQL 2000 > SQL 2005

jibbajabba

I am lost on this one. I must say that I am not a DB as I always tried to avoid SQL etc.

Now a customer asked us to upgrade one of his SQL 2000 box .. the Upgrade Advisor fires up the following error :

http://images2host.co.uk/images/119_Capture.png

I create an image from the system to try it anyway .. you never know .. anyway, I also get this error when attempting the upgrade :

http://images2host.co.uk/images/436_Capture1.png

When I do choose a different data location, I get the following error :

http://images2host.co.uk/images/799_Capture2.png

I am really lost here

JDMurray

You'll find far more expertise on this sort of problem in the SQL Server MSDN forum at http://social.msdn.microsoft.com/Forums/en-US/category/sqlserver/

brad-

try
SQL Server Forums

jibbajabba

Ok, I posted on both .. Lets just hope

If not I will call Microsoft tomorrow - we are Gold Partner so we get free tickets anyway ...
Don't remember, but don't you get some free support with MSDN / Technet as well ?

jibbajabba

How fcuking random. I think I found it and post the solution here as reference.

I was getting nowhere.
The problem was that the Upgrade Advisor always threw and error at the SQL Server part,
without specifying what the error is and the damn logfile just referred to itself to check for more details (which is already rubbish).
I figured due to the fact that they don’t use DTS packages, the errors that the advisors throws could be ignored, yet it didn’t go any further.

At the same time the upgrade itself failed with “-1” which was at the point where it runs the advisor also in the background (and “-1” is clearly fail).

Anyway, I found out that you can enable Debugging in the registry:

http://images2host.co.uk/images/658_Capture1.png

Then I run it again :

http://images2host.co.uk/images/801_Capture.png

So it errors out at the .NET part ..

Mmmm... So the server had every latest .NET Framework version on the planet installed and as a hunch,
I removed every single .NET Framework install and downloaded the Version 2 without Servicepack.

And oh look :

http://images2host.co.uk/images/974_Capture3.png

Now how random is that ....

JDMurray

There was a glitch in your .NET Framework installation that the uninstallation or reinstallation removed or corrected. That is a rare thing to have happen.

jibbajabba

JDMurray wrote: »

There was a glitch in your .NET Framework installation that the uninstallation or reinstallation removed or corrected. That is a rare thing to have happen.

It is not even over yet

Trying to install SP3 since yesterday without any joy ... man I hate that ..

jibbajabba

Fixed the upgrade issue as well ...

Random #2 : The Remote Registry service has to be enabled during the upgrade and service pack install (which we always disable).

Makes sense, no ? It doesn't ? Well you got me ....

Megadeth4168

Gomjaba wrote: »

Fixed the upgrade issue as well ...

Random #2 : The Remote Registry service has to be enabled during the upgrade and service pack install (which we always disable).

Makes sense, no ? It doesn't ? Well you got me ....

You would be surprised at what you need the Remote Registry service enabled for.

I wrote a script some time back that utilized the Netsh command to changed client IP addresses. Apparently, without the Remote Registry Service that just doesn't work.

jibbajabba

Megadeth4168 wrote: »

You would be surprised at what you need the Remote Registry service enabled for.

I wrote a script some time back that utilized the Netsh command to changed client IP addresses. Apparently, without the Remote Registry Service that just doesn't work.

Just annoying that you simply don't get an error stating that it needs xyz in order to work.
The real pain now is that this particular server has about 300 websites on it which have now all revert back to .NET 1.1

jibbajabba

Just an update for future reference (as I am sure I am not the only one upgrading SQL 2000 to SQL 2005).

There is one more option to avoid removing .NET framework, which is once you started the upgrade and you are at the first ‘NEXT’ go to

C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\BPA

And create a folder called

‘BPAClient’

Copy BPAClient.dll (from the sibling bin directory) into this directory.

And guess what, setup runs through just fine ...

JDMurray

Gomjaba wrote: »

The real pain now is that this particular server has about 300 websites on it which have now all revert back to .NET 1.1

I would seriously consider trying to find another solution than reverting back to .NET 1.1. .NET 2.0 greatly improved the security and security features of the .NET framework. For this reason alone I strongly advice never using .NET 1.x again--or having it installed on any Windows machine.

And the Remote Registry Service contains a lot of miscellaneous, ancillary functionality that is used by a lot of other programs. In other words, it not just for accessing the Windows Registry remotely.

jibbajabba

JDMurray wrote: »

I would seriously consider trying to find another solution than reverting back to .NET 1.1. .NET 2.0 greatly improved the security and security features of the .NET framework. For this reason alone I strongly advice never using .NET 1.x again--or having it installed on any Windows machine.

Oh what I meant was I had to uninstall every .NET version just for the upgrade. After the upgrade we of course installed .NET 2.x and 3.x again but I had to change every IIS site back to the necessary .NET version.

I found another solution, which is SOOOO RANDOM :

Once you started the upgrade of SQL 2005 and you are at the first ‘NEXT’ go to

C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\BPA

And create a folder called

‘BPAClient’

Copy BPAClient.dll (from the sibling bin directory) into this directory.

This way, you don't need to remove / reinstall .NET

Fook knows why that is .. what these painful 5 days taught me is that SQL is one route I am NOT going ...

JDMurray

It sounds like the installer can't find the BPAClient.dll file in its original location. That's a problem with the installer program, not with SQL Server itself. Make sure you are upgrading using the latest release of SQL Server 2005. You might be using an eariler release of SQL2005 with known bugs that have been fixed.

dynamik

Gomjaba wrote: »

Fook knows why that is .. what these painful 5 days taught me is that SQL is one route I am NOT going ...

Sounds like a problem with the installer more than SQL Server in general. I don't know if I'd base my career direction on that

jibbajabba

JDMurray wrote: »

It sounds like the installer can't find the BPAClient.dll file in its original location. That's a problem with the installer program, not with SQL Server itself. Make sure you are upgrading using the latest release of SQL Server 2005. You might be using an eariler release of SQL2005 with known bugs that have been fixed.

You cannot get any SPLA media with SP slipstreamed

dynamik wrote: »

Sounds like a problem with the installer more than SQL Server in general. I don't know if I'd base my career direction on that

Well, I was never REALLY interested into SQL stuff .. That just proved my point LOL