Showing posts with label upgrade. Show all posts
Showing posts with label upgrade. Show all posts

Thursday, March 22, 2012

"Your upgrade is blocked"

I am getting the following error message when I tried installing the 2005 Developer Edition from the MSDN kit. I previously installed the 2005 Express Edition, and it worked just fine, so I thought that the install failed as it was at a lower version than the Express Edition. I uninstalled the SQLExpress Edition, however, when I try to install SQL Server 2005 again, I get the following message:

Name: Microsoft SQL Server 2005 Tools

Reason: Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.

Build version check:

Your upgrade is blocked because the existing component is a later version than the version you are trying to upgrade to. To modify an existing SQL Server component, go to Add or Remove Programs in Control Panel, select the component you would like to modify, and then click Change/Remove.

Name: Microsoft SQL Server 2005 Tools

Reason: Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.

Build version check:

Your upgrade is blocked because the existing component is a later version than the version you are trying to upgrade to. To modify an existing SQL Server component, go to Add or Remove Programs in Control Panel, select the component you would like to modify, and then click Change/Remove.

I have also installed Visual Studio NET, and I wonder if some component in the Studio app is holding back the SQL Server install. I have uninstalled all SQL components several times already, and I keep on getting this message.

Gregory

Gregory

Gregory, when you go to Add/Remove Programs, do you see any SQL 2005 installation info there? If so, what versions does the report say?

Also, what version of SQL Server Express did you install? RTM or SP1?

Thanks,
Samuel Lester (MSFT)

sql

Tuesday, March 20, 2012

"Upgrade" from 2000 to 2005, version still says 8.0.2039

I just installed 2005 and accepted all the defaults to upgrade the default instance of 2000 as prompted. However, when I open the SQL Server Mgnt Studio, my server shows 8.0.2039 as the version which is 2000, and I can't restore a backup from another 2005 server, because it gives an error message like it still thinks its 2000. The whole installation process went fine including sp1. I looked in Services to see if there was more than one instance of SQL Server, and there isn't. Also, all my database files are still in the old 2000 (mssql\data) directory. Any ideas, solutions? Thanks.

Michael

I have the same problem. It's like the upgrade didn't totally happen. The new Management studio is installed, but the 2005 specific progs don't work. Like the surface area configure program errors when started since it can't find any 2005 servers installed.

|||

Here's the response that I received from someone else on another forum that was kind enough to reply and it also worked. I simply stopped the 2000 service, and reinstalled. You would think that the installer would do this for you, but oh well. HTH

Before you update to 2005, you have to stop the 2000 version. If you don’t, the code to start 2005 is not installed and the code for starting and stopping 2000 will remain on the server. Thus 2000 will always be started and not 2005. Hope this helps.

Try stopping 2000 and reinstalling 2005.

|||

That's correct, since files are always in use, you need to restart the services for both versions to get the full upgrade to work.

Thanks,
Sam Lester (MSFT)

|||

So to be clear...

I don't have to uninstall either version now. All I have to do is stop all of the current SQL services that are running. Then re-insert the 2005 disc, and it will re-upgrade over itself? ( I don't want a new instace installed, I literally wanted the upgrade so that only one version would be on the machine )

Is there a way to do this without putting the disc back in? i.e. Are all of the files present since I tried to upgrade the first time. So now, I could just stop the services and use some other method to get it to reinstall all new files and services over itself? Or do I have to physically reinsert the disc to follow normal steps?

|||I did not uninstall anything. I just stopped the 2000 service, then reinserted the CD and reinstalled 2005 exactly as I did before, with the intent of upgrading (i.e. replacing) 2000. After completion, I may have had to start the MSSQLServer service manually and set to automatic, can't remember, but after that everything was just fine, and there only appears to be one instance/service (2005).|||Thanks much...I am clear now. I will try this tonight. Since I am about to do this...did you have any surprises or "gotchas" that you can warn me about? Anything that worked before then didn't work after? Also, did you do any timing studies to verify if the 2005 is faster than the 2000? I have heard that the BULK INSERTS are speed improved, but have not seen any benchmarks or other data on speed increases. Just wondering if you noticed some benefits and/or have data on the improvements. Thanks again for the help, glad you were still watching this thread even though you already got the answer elsewhere.|||

There seems to be a hitch. I stopped all of the SQL services. Pop in the disc, begin the install process.

First snafu...

The installer knows that my current install, 2005 Workgroup with SP1, is newer than the version I have on the disc, so it blocks the install. A small report window appears saying I can avoid this problem by installing from the command line and using the SKUUPGRADE=1 parameter. So, I open "Run..." from the start button. I run "F:\Setup.exe SKUUPGRADE=1" The installer begins, but...

Second snafu...

I eventually get to the part where I select the services to install. I choose all services and select the "All components will be installed" option for all of them. I tell it "default instance". Then the installer tells me that it can't continue since all of the components are already installed. Forced to exit.

Am I doing something wrong? Is there a way to just re-install without these problems?

|||

Hi Sam:

Thanks for trying to help...but, your response is not clear, you first say "That's correct" which makes me think that you agree with the info that came from the previous post, the one that says to stop SQL 2000 services and re-install 2005. But, then your post goes on to say "restart both services for both versions", which is not the same as stopping SQL 2000 then reinstalling 2005. Which is it?

Also, if you read my other posts in this thread, the "stop 2000 services and re-install 2005" does not work. The installer will not allow a "re-install" since it sees that 2005 is already installed...furthermore, when using the SKUUPGRADE=1 which is supposed to skip this problem, the installer stops since all of the programs are already installed.

Please help...I am still stuck in the same spot and not sure how to proceed. I suppose I could just uninstall all of the 2005 programs then try all this again...but I was hoping that there was an easier and less time consuming solution.

Thanks in advance.

|||

Sorry for not having a more direct answer, but can you read through this forum thread regarding SQL 2000 and 2005 on the same box and see if it applies to your situation?

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=397541&SiteID=1

Thanks,
Sam Lester (MSFT)

|||

Sorry Sam, this doesn't seem to be the problem I am having. The problem I am having is explained in all of the previous posts in this thread. A SQL 2005 upgrade from SQL 2000 appears to have worked, but it didn't. The version number still shows 8.00.2039 and the SQL 2005 Tools say that there is no 2005 instance on the machine. The other posts here explained how to fix this, but the fix doesn't work since the installer program sees the previous SQL 2005 install on the machine, it won't allow another install to cover over it.

But, since I read the other forum, now I am worried about trying to uninstall SQL 2005 and try again.

Please help if you have any other ideas or point me in the right direction for other resources that may know what to do.

Thanks

|||I am also having the very same problems to the "T". It is also causing a new installation of Reporting Services from properly initializing on the server. It complains about a version problem.

It would seem the next logical step would be to somehow get the databases converted, but outside of doing an upgrade from the SQL Server 2005 setup disk, I cannot find any good documentation on how to do this.

Any help with this problem would be greatly appreciated. I am at wits end.

Friday, February 24, 2012

"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe" finished and retu

Hello,

We are running Windows Server 2003 SP 1 and trying to upgrade SQL 2000 SP 4 to SQL 2005 using the command line.

The process finishes in under ten minutes. Summary.txt file we have this information:

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup_<ServerName>_SQL.log
Last Action : ValidateUpgrade
Error String : The installer has encountered an unexpected error. The error code is 2259. Database: Table(s) Update failed
Error Number : 2259

In the log file named SQLSetup_ServerName_Core.log I found the following:

Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run:
"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe" finished and returned: 1627
Aborting queue processing as nested installer has completed
Message pump returning: 1627

After receiving this info, I can navigate to the setup.bat for the SQL 2005 upgrade and complete the upgrade without error. We are planning on 500 of these, so manual updates is a very ugly concept.

I'd appreciate any and all ideas on where to go from here.

Most Sincerely.

Could you search inside the *_SQL.log for the string mentioned in summary.txt:

"The installer has encountered an unexpected error. The error code is 2259. Database: Table(s) Update failed"

When you find the string, could you copy the lines above and below so we could see the context around the error? Hopefully you could include all the logging statements associated with the ValidateUpgrade action. It should start with a line like this:

<Func Name='ValidateUpgrade'>

Thanks!

|||

Dear R.Green,

I appreciate your help. The results of your request follows. Please let me know if I can help in any other way.

Thanks,

Bill

Function=SAPasswordPolicyCheck
Skipping Action: SAPasswordPolicyCheck (Condition is false)
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (A4:94) [11:38:44:323]: Doing action: ValidateUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2
Action ended 11:38:44: SAPasswordPolicyCheck.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 1.
MSI (s) (A4:2C) [11:38:44:339]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI11F.tmp, Entrypoint: ValidateUpgrade
Action start 11:38:44: ValidateUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2.
<Func Name='LaunchFunction'>
Function=ValidateUpgrade
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: ValidateUpgrade
PerfTime Start: ValidateUpgrade : Tue Nov 14 11:38:44 2006
<Func Name='ValidateUpgrade'>
<Func Name='updateFeatureSellection'>
<Func Name='SqlComponentUpgrade'>
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
<Func Name='ProcessHeaderTable'>
<Func Name='ProcessScriptTable'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='ProcessScriptTable'>
<Func Name='GetFileTargetPath'>
MSI (s) (A4!B0) [11:38:44:464]: Note: 1: 2205 2: 3: _sqlSqlUpgradeSequence
MSI (s) (A4!B0) [11:38:44:464]: Note: 1: 2228 2: 3: _sqlSqlUpgradeSequence 4: CREATE TABLE `_sqlSqlUpgradeSequence` (`Action` CHAR(255) NOT NULL, `Sequence` INT NOT NULL, `Param` CHAR(0), `Retryable` INT NOT NULL, `Fatal` INT NOT NULL PRIMARY KEY `Action`, `Sequence`)
MSI (s) (A4!B0) [11:38:44:464]: Note: 1: 2262 2: _sqlSqlUpgradeSequence 3: -2147287038
MSI (s) (A4!B0) [11:38:44:480]: PROPERTY CHANGE: Adding Sql_sqlSqlUpgradeSequence property. Its value is '15000000'.
MSI (s) (A4!B0) [11:38:44:480]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeSequence property. Its current value is '15000000'. Its new value: '30000000'.
MSI (s) (A4!B0) [11:38:44:480]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeSequence property. Its current value is '30000000'. Its new value: '30040000'.
MSI (s) (A4!B0) [11:38:44:480]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeSequence property. Its current value is '30040000'. Its new value: '30050000'.
MSI (s) (A4!B0) [11:38:44:480]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeSequence property. Its current value is '30050000'. Its new value: '30150000'.
MSI (s) (A4!B0) [11:38:44:480]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeSequence property. Its current value is '30150000'. Its new value: '100150000'.
MSI (s) (A4!B0) [11:38:44:480]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeSequence property. Its current value is '100150000'. Its new value: '230871400'.
MSI (s) (A4!B0) [11:38:44:480]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeSequence property. Its current value is '230871400'. Its new value: '245871400'.
MSI (s) (A4!B0) [11:38:44:480]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeSequence property. Its current value is '245871400'. Its new value: '275871400'.
MSI (s) (A4!B0) [11:38:44:480]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeSequence property. Its current value is '275871400'. Its new value: '275971400'.
<Func Name='GetFileTargetPath'>
<EndFunc Name='SqlComponentUpgrade' Return='0' GetLastError='0'>
Added FTE to SqlUpgrade property
Added REPL to SqlUpgrade property
<Func Name='updateFeatureSellection'>
MSI (s) (A4!B0) [11:38:44:636]: skipping installation of assembly component: {7F618CB9-9BCE-4C1E-9E33-59E8A564E456} since the assembly already exists
To perform upgrade setting feature SQL_Replication to be indtalled locally.
To perform upgrade setting feature SQL_FullText to be indtalled locally.
Running:
CollectInstallCases
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 44.44


Complete:
CollectInstallCases
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 44.44
, returned
true


Running:
DefineFeatureActionRules
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 44.44


Complete:
DefineFeatureActionRules
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 44.44
, returned
true


Running:
DefineInstallActionRules
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 44.44


Complete:
DefineInstallActionRules
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 45.45
, returned
true


Running:
AddInstallCaseActions
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 45.45


Complete:
AddInstallCaseActions
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 45.45
, returned
true


Loaded DLL:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\sqlboot.dll
Version:
2005.90.1399.0


Action "
languageUpgrade_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
" will be skipped due to the
following restrictions:


Condition "differentLanguage_with_1033_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.

Loaded DLL:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\sqlboot.dll
Version:
2005.90.1399.0


Action "
maintenance_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
" will be skipped due to the
following restrictions:


Condition "sameVersion_as_9.0.139906_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.

Loaded DLL:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\sqlboot.dll
Version:
2005.90.1399.0


Action "
skuUpgrade_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
" will be skipped due to the
following restrictions:


Condition "NOT_sameSKU_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.

Loaded DLL:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\sqlboot.dll
Version:
2005.90.1399.0


Action "
virtualization_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
" will be skipped due to the
following restrictions:


Condition "virtualization_NotSupported_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.

Action "
warningPatchLevel_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
" will be skipped due to the
following restrictions:


Condition "diffInstancePatchLevel_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.

Action "
warningSPLevel_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
" will be skipped due to the
following restrictions:


Condition "diffInstanceSPLevel_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.

Action "
warningUpgrade_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
" will be skipped due to the
following restrictions:


Condition "warningUpgrade_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.

Running:
versionUpgrade_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 45.45


Complete:
versionUpgrade_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 45.45
, returned
true


Running:
AddFeatureCase_versionUpgrade_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 45.45


Complete:
AddFeatureCase_versionUpgrade_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 45.45
, returned
true


Running:
FeaturePhaseAction
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 45.45


Complete:
FeaturePhaseAction
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 45.45
, returned
true


Action "
add_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER_SQL_Engine
" will be skipped due to the
following restrictions:


Condition "noFeatureConflict_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER_SQL_Engine" returned false.
Condition "NOT_featureInstalled_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER_SQL_Engine" returned false.
Condition "installActionAvailable_maintenance_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER_SQL_Engine" returned false.

Action "
remove_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER_SQL_Engine
" will be skipped due to the
following restrictions:


MSI (s) (A4!B0) [11:38:45:839]: PROPERTY CHANGE: Deleting AGTACCOUNT property. Its current value is 'CEDNetLive\Roamer'.
MSI (s) (A4!B0) [11:38:45:839]: PROPERTY CHANGE: Deleting AGTPASSWORD property. Its current value is '**********'.
Condition "installActionAvailable_maintenance_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER_SQL_Engine" returned false.

Attempt to start service when it is already running
SQL service MSSQLSERVER started successfully waiting for SQL service to accept client connections
Loaded DLL:
C:\WINDOWS\system32\Odbc32.dll
Version:
3.526.1830.0


SQL_SUCCESS_WITH_INFO (1) in OdbcConnection::connect
sqlstate=01000, level=-1, state=-1, native_error=5701, msg=[Microsoft][SQL Native Client][SQL Server]Changed database context to 'master'.
sqlstate=01000, level=-1, state=-1, native_error=5703, msg=[Microsoft][SQL Native Client][SQL Server]Changed language setting to us_english.

Executing External Command
Message type: Progress
10
Message type: Component
Database Engine
Message type: Status
Checking for SQL Connectivity...
Message type: Status
Starting analysis...
Message type: Status
Analyzing 1%
Message type: Status
Analyzing 5%
Message type: Status
Analyzing 15%
Message type: Status
Analyzing 16%
Message type: Status
Analyzing 17%
Message type: Status
Analyzing 18%
Message type: Status
Analyzing 20%
Message type: Status
Analyzing 21%
Message type: Status
Analyzing 30%
Message type: Status
Analyzing 33%
Message type: Status
Analyzing 34%
Message type: Status
Analyzing 35%
Message type: Status
Analyzing 38%
Message type: Status
Analyzing 50%
Message type: Status
Analyzing 51%
Message type: Status
Analyzing 55%
Message type: Status
Analyzing 66%
Message type: Status
Analyzing 67%
Message type: Status
Analyzing 68%
Message type: Status
Analyzing 71%
Message type: Status
Analyzing 83%
Message type: Status
Analyzing 84%
Message type: Status
Analyzing 85%
Message type: Status
Analyzing 88%
Message type: Status
Analyzing 90%
Message type: Status
Analyzing 100%
Message type: Status
Creating report
Message type: Status
Creating report
Message type: Progress
Info 100.100
<Func Name='SqlComponentUpgrade'>
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
<Func Name='ProcessHeaderTable'>
<Func Name='ProcessScriptTable'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='ProcessScriptTable'>
<Func Name='GetFileTargetPath'>
MSI (s) (A4!B0) [11:39:18:558]: Note: 1: 2259 2: 3: 4:
<Func Name='GetFileTargetPath'>
Error Code: 0x8007065b (1627)
Windows Error Text: Function failed during execution.
Source File Name: darlib\viewinstaller.cpp
Compiler Timestamp: Mon Jun 13 14:19:43 2005
Function Name: sqls::ViewInstaller::modify
Source Line Number: 137

- Context --


Setting status of unmanaged components and removing unmanaged resources
Failed to modify installer view
1: 2259 2: 3: 4:

Error Code: 1627
MSI (s) (A4!B0) [11:39:18:745]: Product: Microsoft SQL Server 2005 -- Error 2259. The installer has encountered an unexpected error. The error code is 2259. Database: Table(s) Update failed

Error 2259. The installer has encountered an unexpected error. The error code is 2259. Database: Table(s) Update failed
<Failure Type='Fatal' Error='1627'>
<EndFunc Name='LaunchFunction' Return='1627' GetLastError='0'>
Action ended 11:39:18: ValidateUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3.
Action ended 11:39:18: INSTALL. Return value 3.
Property(S): ProductCode = {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}
Property(S): ProductLanguage = 1033
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductVersion = 9.00.1399.06
Property(S): MEDIAPACKAGEPATH = \Setup\

|||

Thank you for the follow up, we are still looking into this internally to see if we have any ideas. I'm wondering how you are installing SQL Server 2005. Is it from removable media, a network location, or from the hard drive? Did the media come from a download or was it burned from ISO?

The error message is strange because it should list the query that was attempted, but it looks to be an empty string. I'm just wondering if there is a possibility that the point of installation has a corrupt MSI database in some way.

|||

Hi,

Thanks for your efforts. We have a volume license agreement with Microsoft. I copied the two CDs we received under that agreement to an IDE drive on the server that is being upgraded. My template.ini file is pointing to that drive. We are running from the hard drive because we will push this upgrade to the field using LanDesk. To say it another way, we are not sending media to our hundred plus sites.

Please let me know if I didn't answer the correct question. (Something I do more and more as I get older.)

Thanks,

Bill

|||

Hi,

Any word on this? I need to keep this moving.

Thanks,

Bill

|||

Hi BaldManDBA

Any resolution? This is also a SQL Server 2005 Express edition issue too

see: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1663937&SiteID=1

Extract of my log:

- Context --


Setting status of unmanaged components and removing unmanaged resources
Failed to modify installer view
1: 2259 2: 3: 4:

Error Code: 1627
MSI (s) (9C!2C) [21:36:21:171]: Product: Microsoft SQL Server 2005 Express Edition -- Error 2259. The installer has encountered an unexpected error. The error code is 2259. Database: Table(s) Update failed

Error 2259. The installer has encountered an unexpected error. The error code is 2259. Database: Table(s) Update failed
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='203'>
Doing Action: ValidateUpgrade
PerfTime Start: ValidateUpgrade : Tue May 29 21:36:21 2007
<Func Name='ValidateUpgrade'>
<Func Name='updateFeatureSellection'>
<Func Name='SqlComponentUpgrade'>
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='203'>
<Func Name='ProcessHeaderTable'>
<Func Name='ProcessScriptTable'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>

In my case, it was simply a case of leave all the defaults during the SS2005 SP2 install, except the instance where (_) default instance had to be ticked instead of a named instance

Please let us know ... (as your solution may be related to all other SQL Server 2005 version/situations)

Alain

|||

Hi,

The server that generated that error was the only one to encounter the error. So, for that one server, we reinstalled SQL Server. All was OK after that. I hope this helps.

Thanks,

BaldManDBA.

"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe" finished and

Hello,

We are running Windows Server 2003 SP 1 and trying to upgrade SQL 2000 SP 4 to SQL 2005 using the command line.

The process finishes in under ten minutes. Summary.txt file we have this information:

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup_<ServerName>_SQL.log
Last Action : ValidateUpgrade
Error String : The installer has encountered an unexpected error. The error code is 2259. Database: Table(s) Update failed
Error Number : 2259

In the log file named SQLSetup_ServerName_Core.log I found the following:

Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run:
"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe" finished and returned: 1627
Aborting queue processing as nested installer has completed
Message pump returning: 1627

After receiving this info, I can navigate to the setup.bat for the SQL 2005 upgrade and complete the upgrade without error. We are planning on 500 of these, so manual updates is a very ugly concept.

I'd appreciate any and all ideas on where to go from here.

Most Sincerely.

Could you search inside the *_SQL.log for the string mentioned in summary.txt:

"The installer has encountered an unexpected error. The error code is 2259. Database: Table(s) Update failed"

When you find the string, could you copy the lines above and below so we could see the context around the error? Hopefully you could include all the logging statements associated with the ValidateUpgrade action. It should start with a line like this:

<Func Name='ValidateUpgrade'>

Thanks!

|||

Dear R.Green,

I appreciate your help. The results of your request follows. Please let me know if I can help in any other way.

Thanks,

Bill

Function=SAPasswordPolicyCheck
Skipping Action: SAPasswordPolicyCheck (Condition is false)
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (A4:94) [11:38:44:323]: Doing action: ValidateUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2
Action ended 11:38:44: SAPasswordPolicyCheck.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 1.
MSI (s) (A4:2C) [11:38:44:339]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI11F.tmp, Entrypoint: ValidateUpgrade
Action start 11:38:44: ValidateUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2.
<Func Name='LaunchFunction'>
Function=ValidateUpgrade
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: ValidateUpgrade
PerfTime Start: ValidateUpgrade : Tue Nov 14 11:38:44 2006
<Func Name='ValidateUpgrade'>
<Func Name='updateFeatureSellection'>
<Func Name='SqlComponentUpgrade'>
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
<Func Name='ProcessHeaderTable'>
<Func Name='ProcessScriptTable'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='ProcessScriptTable'>
<Func Name='GetFileTargetPath'>
MSI (s) (A4!B0) [11:38:44:464]: Note: 1: 2205 2: 3: _sqlSqlUpgradeSequence
MSI (s) (A4!B0) [11:38:44:464]: Note: 1: 2228 2: 3: _sqlSqlUpgradeSequence 4: CREATE TABLE `_sqlSqlUpgradeSequence` (`Action` CHAR(255) NOT NULL, `Sequence` INT NOT NULL, `Param` CHAR(0), `Retryable` INT NOT NULL, `Fatal` INT NOT NULL PRIMARY KEY `Action`, `Sequence`)
MSI (s) (A4!B0) [11:38:44:464]: Note: 1: 2262 2: _sqlSqlUpgradeSequence 3: -2147287038
MSI (s) (A4!B0) [11:38:44:480]: PROPERTY CHANGE: Adding Sql_sqlSqlUpgradeSequence property. Its value is '15000000'.
MSI (s) (A4!B0) [11:38:44:480]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeSequence property. Its current value is '15000000'. Its new value: '30000000'.
MSI (s) (A4!B0) [11:38:44:480]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeSequence property. Its current value is '30000000'. Its new value: '30040000'.
MSI (s) (A4!B0) [11:38:44:480]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeSequence property. Its current value is '30040000'. Its new value: '30050000'.
MSI (s) (A4!B0) [11:38:44:480]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeSequence property. Its current value is '30050000'. Its new value: '30150000'.
MSI (s) (A4!B0) [11:38:44:480]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeSequence property. Its current value is '30150000'. Its new value: '100150000'.
MSI (s) (A4!B0) [11:38:44:480]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeSequence property. Its current value is '100150000'. Its new value: '230871400'.
MSI (s) (A4!B0) [11:38:44:480]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeSequence property. Its current value is '230871400'. Its new value: '245871400'.
MSI (s) (A4!B0) [11:38:44:480]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeSequence property. Its current value is '245871400'. Its new value: '275871400'.
MSI (s) (A4!B0) [11:38:44:480]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeSequence property. Its current value is '275871400'. Its new value: '275971400'.
<Func Name='GetFileTargetPath'>
<EndFunc Name='SqlComponentUpgrade' Return='0' GetLastError='0'>
Added FTE to SqlUpgrade property
Added REPL to SqlUpgrade property
<Func Name='updateFeatureSellection'>
MSI (s) (A4!B0) [11:38:44:636]: skipping installation of assembly component: {7F618CB9-9BCE-4C1E-9E33-59E8A564E456} since the assembly already exists
To perform upgrade setting feature SQL_Replication to be indtalled locally.
To perform upgrade setting feature SQL_FullText to be indtalled locally.
Running:
CollectInstallCases
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 44.44


Complete:
CollectInstallCases
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 44.44
, returned
true


Running:
DefineFeatureActionRules
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 44.44


Complete:
DefineFeatureActionRules
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 44.44
, returned
true


Running:
DefineInstallActionRules
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 44.44


Complete:
DefineInstallActionRules
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 45.45
, returned
true


Running:
AddInstallCaseActions
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 45.45


Complete:
AddInstallCaseActions
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 45.45
, returned
true


Loaded DLL:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\sqlboot.dll
Version:
2005.90.1399.0


Action "
languageUpgrade_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
" will be skipped due to the
following restrictions:


Condition "differentLanguage_with_1033_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.

Loaded DLL:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\sqlboot.dll
Version:
2005.90.1399.0


Action "
maintenance_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
" will be skipped due to the
following restrictions:


Condition "sameVersion_as_9.0.139906_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.

Loaded DLL:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\sqlboot.dll
Version:
2005.90.1399.0


Action "
skuUpgrade_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
" will be skipped due to the
following restrictions:


Condition "NOT_sameSKU_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.

Loaded DLL:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\sqlboot.dll
Version:
2005.90.1399.0


Action "
virtualization_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
" will be skipped due to the
following restrictions:


Condition "virtualization_NotSupported_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.

Action "
warningPatchLevel_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
" will be skipped due to the
following restrictions:


Condition "diffInstancePatchLevel_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.

Action "
warningSPLevel_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
" will be skipped due to the
following restrictions:


Condition "diffInstanceSPLevel_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.

Action "
warningUpgrade_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
" will be skipped due to the
following restrictions:


Condition "warningUpgrade_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.

Running:
versionUpgrade_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 45.45


Complete:
versionUpgrade_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 45.45
, returned
true


Running:
AddFeatureCase_versionUpgrade_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 45.45


Complete:
AddFeatureCase_versionUpgrade_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 45.45
, returned
true


Running:
FeaturePhaseAction
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 45.45


Complete:
FeaturePhaseAction
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 45.45
, returned
true


Action "
add_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER_SQL_Engine
" will be skipped due to the
following restrictions:


Condition "noFeatureConflict_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER_SQL_Engine" returned false.
Condition "NOT_featureInstalled_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER_SQL_Engine" returned false.
Condition "installActionAvailable_maintenance_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER_SQL_Engine" returned false.

Action "
remove_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER_SQL_Engine
" will be skipped due to the
following restrictions:


MSI (s) (A4!B0) [11:38:45:839]: PROPERTY CHANGE: Deleting AGTACCOUNT property. Its current value is 'CEDNetLive\Roamer'.
MSI (s) (A4!B0) [11:38:45:839]: PROPERTY CHANGE: Deleting AGTPASSWORD property. Its current value is '**********'.
Condition "installActionAvailable_maintenance_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER_SQL_Engine" returned false.

Attempt to start service when it is already running
SQL service MSSQLSERVER started successfully waiting for SQL service to accept client connections
Loaded DLL:
C:\WINDOWS\system32\Odbc32.dll
Version:
3.526.1830.0


SQL_SUCCESS_WITH_INFO (1) in OdbcConnection::connect
sqlstate=01000, level=-1, state=-1, native_error=5701, msg=[Microsoft][SQL Native Client][SQL Server]Changed database context to 'master'.
sqlstate=01000, level=-1, state=-1, native_error=5703, msg=[Microsoft][SQL Native Client][SQL Server]Changed language setting to us_english.

Executing External Command
Message type: Progress
10
Message type: Component
Database Engine
Message type: Status
Checking for SQL Connectivity...
Message type: Status
Starting analysis...
Message type: Status
Analyzing 1%
Message type: Status
Analyzing 5%
Message type: Status
Analyzing 15%
Message type: Status
Analyzing 16%
Message type: Status
Analyzing 17%
Message type: Status
Analyzing 18%
Message type: Status
Analyzing 20%
Message type: Status
Analyzing 21%
Message type: Status
Analyzing 30%
Message type: Status
Analyzing 33%
Message type: Status
Analyzing 34%
Message type: Status
Analyzing 35%
Message type: Status
Analyzing 38%
Message type: Status
Analyzing 50%
Message type: Status
Analyzing 51%
Message type: Status
Analyzing 55%
Message type: Status
Analyzing 66%
Message type: Status
Analyzing 67%
Message type: Status
Analyzing 68%
Message type: Status
Analyzing 71%
Message type: Status
Analyzing 83%
Message type: Status
Analyzing 84%
Message type: Status
Analyzing 85%
Message type: Status
Analyzing 88%
Message type: Status
Analyzing 90%
Message type: Status
Analyzing 100%
Message type: Status
Creating report
Message type: Status
Creating report
Message type: Progress
Info 100.100
<Func Name='SqlComponentUpgrade'>
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
<Func Name='ProcessHeaderTable'>
<Func Name='ProcessScriptTable'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='ProcessScriptTable'>
<Func Name='GetFileTargetPath'>
MSI (s) (A4!B0) [11:39:18:558]: Note: 1: 2259 2: 3: 4:
<Func Name='GetFileTargetPath'>
Error Code: 0x8007065b (1627)
Windows Error Text: Function failed during execution.
Source File Name: darlib\viewinstaller.cpp
Compiler Timestamp: Mon Jun 13 14:19:43 2005
Function Name: sqls::ViewInstaller::modify
Source Line Number: 137

- Context --


Setting status of unmanaged components and removing unmanaged resources
Failed to modify installer view
1: 2259 2: 3: 4:

Error Code: 1627
MSI (s) (A4!B0) [11:39:18:745]: Product: Microsoft SQL Server 2005 -- Error 2259. The installer has encountered an unexpected error. The error code is 2259. Database: Table(s) Update failed

Error 2259. The installer has encountered an unexpected error. The error code is 2259. Database: Table(s) Update failed
<Failure Type='Fatal' Error='1627'>
<EndFunc Name='LaunchFunction' Return='1627' GetLastError='0'>
Action ended 11:39:18: ValidateUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3.
Action ended 11:39:18: INSTALL. Return value 3.
Property(S): ProductCode = {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}
Property(S): ProductLanguage = 1033
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductVersion = 9.00.1399.06
Property(S): MEDIAPACKAGEPATH = \Setup\

|||

Thank you for the follow up, we are still looking into this internally to see if we have any ideas. I'm wondering how you are installing SQL Server 2005. Is it from removable media, a network location, or from the hard drive? Did the media come from a download or was it burned from ISO?

The error message is strange because it should list the query that was attempted, but it looks to be an empty string. I'm just wondering if there is a possibility that the point of installation has a corrupt MSI database in some way.

|||

Hi,

Thanks for your efforts. We have a volume license agreement with Microsoft. I copied the two CDs we received under that agreement to an IDE drive on the server that is being upgraded. My template.ini file is pointing to that drive. We are running from the hard drive because we will push this upgrade to the field using LanDesk. To say it another way, we are not sending media to our hundred plus sites.

Please let me know if I didn't answer the correct question. (Something I do more and more as I get older.)

Thanks,

Bill

|||

Hi,

Any word on this? I need to keep this moving.

Thanks,

Bill

|||

Hi BaldManDBA

Any resolution? This is also a SQL Server 2005 Express edition issue too

see: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1663937&SiteID=1

Extract of my log:

- Context --


Setting status of unmanaged components and removing unmanaged resources
Failed to modify installer view
1: 2259 2: 3: 4:

Error Code: 1627
MSI (s) (9C!2C) [21:36:21:171]: Product: Microsoft SQL Server 2005 Express Edition -- Error 2259. The installer has encountered an unexpected error. The error code is 2259. Database: Table(s) Update failed

Error 2259. The installer has encountered an unexpected error. The error code is 2259. Database: Table(s) Update failed
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='203'>
Doing Action: ValidateUpgrade
PerfTime Start: ValidateUpgrade : Tue May 29 21:36:21 2007
<Func Name='ValidateUpgrade'>
<Func Name='updateFeatureSellection'>
<Func Name='SqlComponentUpgrade'>
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='203'>
<Func Name='ProcessHeaderTable'>
<Func Name='ProcessScriptTable'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>

In my case, it was simply a case of leave all the defaults during the SS2005 SP2 install, except the instance where (_) default instance had to be ticked instead of a named instance

Please let us know ... (as your solution may be related to all other SQL Server 2005 version/situations)

Alain

|||

Hi,

The server that generated that error was the only one to encounter the error. So, for that one server, we reinstalled SQL Server. All was OK after that. I hope this helps.

Thanks,

BaldManDBA.