There is a system running in win NT with DB SQL server 7.0, and now want to upgrade DB SQL server 7.0 to 2005 and run at window server 2003.
I want to konw that is there any impact to the system at DB part ? all the original script can be run normal when DB upgraded to 2005?
I have a SQL Server 2005 evaluation that has already been installed and setup on a server. I believe it originally had a 180 day eval. There have been numerous databases and users added as well as maintenance plan created...
The eval was put on the machine as an interim solution while waiting for paper work and order processiing things to happen. All the paperwork and ordering... have been completed and I now have the real SQL Server 2005 Standard Edition license key ....
I am very new to SQL Server and need to determine ...
1. Can I update the eval copy to become permanently licensed?
2. Would I want to upgrade the eval to permanent? Will I lose any capabilities by keeping the current eval setup?
If it is reasonable to keep the eval setup
3. How do I go about entering the license key to make it permanent?
If it is necessary to install the new Standard Edition...
4. How do I install it while maintaining the already defined databases, data, users, maintenance plan...
Thanks in advance for any and all help.
Chris
I am trying to upgrade SQL Server Express 2005 Report Server to SQL 2005 Standard and it fails with the following error:
SQL Server Setup did not have the administrator permissions required to copy a file: C:Program FilesMicrosoft SQL ServerMSSQL.8Reporting ServicesReportServer
ssrvpolicy.config. To continue, verify that the file exists, and either grant administrator permissions to the account currently running Setup or log in with an administrator account. Then run SQL Server Setup again.
After I click OK on the message, this whole path where the upgrade is bieng installed dissapears C:Program FilesMicrosoft SQL ServerMSSQL.8Reporting Services. The error is a bit missleading because the file that it is trying to copy rssrvpolicy.config does appear in that upgrade folder so I am not sure why it would try to copy a file that has already been copied.
I was able to upgrade the Database Engine instance fine but can't upgrade Reporting Services due to that error. I have verified that the account that ran the setup had the administrator permissions. Your prompt reply to my question would be greatly appreciatted.
How do I upgrade Sql Server 2005 Express to SP2 if I also have SQL Server 2005 Enterprise SP2 already on the same box? I installed Sql Server 2005 Enterprise first, then applied SP2, then installed Visual Studio 2008 (which installed SQL Server 2005 Express).
When I try to upgrade Sql Server 2005 Express to SP2 using the special Express edition of SP2, I get an error message that says "None of the selected features can be installed". I end up having to cancel the install of SP2.
I'm left with SQL Server 2005 at level 9.0.3054 and SQL Server 2005 Express at 9.0.3042. How can I bring SQL Server Express 2005 to the same level as SQL Server 2005 Entperprise?
if i upgrade from sql server 2005 expressto sql server 2005 enterprise can i do it ?
am i need to uninstall 2005 express before ?
Hi
I am trying to upgrade SQL Server 2005 Express to SQL Server 2005 Enterprise Edition.
(As a Preparation to install SQLServer2005 Service Pack 2 (CTP))
I tried to upgrade a particular Instance (OFFICESERVERS, which was based on SQL Server 2005 Express ).
During the upgrade I get a message saying that ...
.....Your upgrade is blocked because of edition upgrade rules.....
All other components I selected for Installation are propertly installed (Analysis, Reporting)
The setup log contains the following detail information:
---- Context -----------------------------------------------
Setting status of unmanaged components and removing unmanaged resources
Error Code: 29543
MSI (s) (DC!C8) [13:57:26:265]: Product: Microsoft SQL Server 2005 -- Error 29543. 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.
Edition check:
Your upgrade is blocked because of edition upgrade rules. For more information about edition upgrades, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
Error 29543. 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.
Edition check:
Your upgrade is blocked because of edition upgrade rules. For more information about edition upgrades, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: ValidateUpgrade
PerfTime Start: ValidateUpgrade : Fri Dec 29 13:57:26 2006
<Func Name='ValidateUpgrade'>
<Func Name='updateFeatureSellection'>
Error Code: 0x80077367 (29543)
Windows Error Text: Source File Name: sqlcaupgradeproduct.cpp
Compiler Timestamp: Mon Sep 19 01:07:45 2005
Function Name: sqls::UpgradeProduct::CanUpgrade
Source Line Number: 142
---- Context -----------------------------------------------
I also tried to explicitly upgrade the OFFICESERVERS instance by executing Setup from the command shell:
start /wait setup.exe ADDLOCAL=SQL_Engine INSTANCENAME=OFFICESERVERS UPGRADE=SQL_Engine SKUU
PGRADE=1 /qb
The result is the same, i.e.... Your upgrade is blocked because of edition upgrade rules...
Does anybody know about this problem?
Some more information about the system:
W2K3 R2 Enterprise Edition
WSS3.0
MOSS2007
previously installed SQL Server 2005 Express Edition (Version 9.00.2047.00)
Kinde regards
Andreas
Hi,
We are performing a SQL 2005 SP1 upgrade from SQL 2000 on our Windows 2003 SP1 Standard Edition.
When we run the upgrade, we got a error "Upgrade Advisor Return -1" as a pop-up window.
When we run the Upgrade Advisor separately, we get this error :
===================================
Common Language Runtime detected an invalid program.
===================================
Common Language Runtime detected an invalid program. (System.Xml)
------------------------------
Program Location:
at System.Xml.Schema.SchemaInfo..ctor()
at System.Xml.Schema.XmlSchemaSet..ctor(XmlNameTable nameTable)
at System.Xml.XmlReaderSettings.get_Schemas()
at Microsoft.SqlServer.UpgradeAdvisor.ReportViewer.UAReportController.LoadAndValidateDataFile()
at Microsoft.SqlServer.UpgradeAdvisor.ReportViewer.UAReport.ValidateDataFile()
at Microsoft.SqlServer.UpgradeAdvisor.ReportViewer.UAIssueReport.Refresh()
at Microsoft.SqlServer.UpgradeAdvisor.ReportPanel.OpenReport(String reportFile)
We are in a lost for solutions. We do hope to hear from anyone asap...
Greatly appreciated for any kind assistance.
Thanks.
Hi,
We are running a test upgrade form sql 2000 standard edition 32 bit to sql 2005 developer edition 32bit. Followed through all the steps and specified the account(SA priveleges and currently used by the 2000 version) and is the local admin on the box for the services and the setup seemed to move fine, except for when it got to the point of installing database services - This is the error message that I got:
MSSQLServer could not be started. Verify you have sufficient priveleges to start system services. The was no choice but to hit cancel and then the set up progressed with a final message of 'SEtup failed'.
Here is a portion of the error log:
Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
Database Mirroring Transport is disabled in the endpoint configuration.
Starting up database 'master'.
Converting database 'master' from version 589 to the current version 611.
Database 'master' running the upgrade step from version 589 to version 590.
Error: 946, Severity: 14, State: 1.
Cannot open database 'master' version 589. Upgrade the database to the latest version.
System Task Aggregate global counters produced an error that was not handled. Major: 9, Minor: 46, Severity:14, State:1
Error: 928, Severity: 20, State: 1.
During upgrade, database raised exception 15151, severity 16, state 1, address 01C4C50B. Use the exception number to determine the cause.
Error: 15151, Severity: 16, State: 1.
Cannot find the endpoint 'TSQL Local Machine', because it does not exist or you do not have permission.
Any help would be greatly appreciated
Thanks KR
hi All .
I use Micorosft SQL 2005 upgrade advisor to upgrade from sql 2000 to sql 2005, but I got problem .
here is my problem .
On my machine I have Sql 2000 Developer without server pack, and Sql server 20045 express edition .
Please help me to overcome this problem .
Many thanks in advance .
regards,
QuachNguyen
Hi,
I have a problem about upgrading SQL server. We were using sql server 2005 express. Then we removed it and install sql server 2005 enterprise edition.
But now we cant start our services (those written by us .NET c#) We get some errors like
"Login failed for user 'NT AUTHORITYSYSTEM'. [CLIENT: <local machine>] "
What is the problem?
Thanks...
I'm running SQL 2005 on a Windows 2000 server. I would like to upgrade the OS to Windows 2003 server. Is there a whitepaper with all the required steps listed?
Thanks,
Dave
Hi All,
Is there a way to print out reports of the errors and warnings created by the
SQL Server 2005 upgrade advisor?
I am currently using sql server 2000 and I have just installed sql server 2005 in a separate box that will be used as the production server so I will be upgrading to the new database server soon.
I was reading the upgrade options for this situation and one option is to detach the 2000 database, copy the mdf and log files to the new server and attach it to mssql 2005. Another option is to recreate the tables, views, etc. and export/import the data to the new server.
I would like to ask what the best option is for this situation because I am not sure what the advantages and disadvantages of just detaching/attaching and recreating the database in sql server 2005. If I just detach/attach the database, will there be any disadvantage in the performance because the database files were created in 2000 and is functioning because of backward compatibility in 2005? Would it be better to recreate the database in 2005 and import the data from 2000 so that the database would be running in a way that is designed for 2005?
I am not really sure of the differences of these upgrade options so any ideas would be greatly appreciated.
Thanks in Advance
-Voltaire
We have an extensive stress test for our OLTP application.that runs slower after upgrading to SQL Server 2005.
We have done the following:
- applied SP1 and SP2
- updated statistics (sp_updatestats)
- recompiled all stored procedures
Some behavior we notice in Perfmon over the course of the 1-hour test is:
- Average CPU Utilization is up from 22% to 32% and we're trying to figure out why
- Compilations per second are up from 200 to 250
- Recompilations per second are down from 5 to 1 (which is good).
- Memory utilization is identical.
- We see exagerated spikes in response times. The general performance
seems pretty good - but there are periodic spikes that hurt our averages.
- I examined perfmon for waits and nothing jumped out.
- A small handful of application workflows are much slower, while most are roughly identical.
I realize there could be a zillion different causes. But if anyone has experience upgrading a large OLTP solution which uses a mixture of dynamic SQL and stored procedures to SS2005 - and tuning the upgraded database - please offer any suggestions.
Our current plan includes (a) running the Best Practices analyzer which already uncovered a trace flag we may want to use since we're running on an 8-way, (b) rebuilding indexes, and (c) examine a SQL Trace this time around too since it appears the slowness is isolated to certain application workflows.
Please offer any suggestions that have worked for your team.
Thanks so much!
Mike
PS I will post all the things we end up doing in the end once we get performance equal or better - hopefully the latter!!!
Team,
Got a question about one of the results on the upgrade advisor report.
When to Fix: Before
Description: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
Object: SVCACCTREQ
It is looking like some type of permission problem but I cannot find anything about this specific issue.
I am running the advisor from my local machine, on which I am a local administrator, against a remote server where I am just a typical user.
Is this an error that would be corrected if I were to run the upgrade advisor logged into the server as a local administrator? I'm trying to determine whether there is anything that needs to be done with this issue.
Thanks.
Richard
Hello, I have sql server 2000 personal edition on my PC and I have just got a 2005 DVD. I tried to install it but it is not working. I don't know how to manage my databases. As if there is no graphical managemnt tool. The 2005 is also Personal edition.
I reinstalled the sql 2000, and now I'm trying t upgrade to sql 2005, but still don't know how to do that.
Please someone help me!!!!!!!!!!
Probably this question has been asked hundreds of times and yet netsearch has not generated satisfactory enough answer, at least, to me.And OK, let's assume your organization has more than 200 employees,just one measure to indicate that it's not small and data processingneeds are quite extensive (for both OLTP and OLAP).We've heard so much about concurrency support, stability andperformance. Are there any real persuasive paper out there to talkabout it? Now, let me also put it in another perspective, say, you'rea Microsoft sql server sales guy or gal for that matter for newaccounts. What you got?Thanks.
View 5 Replies View RelatedMy instance of SQL Server Developer stopped working after upgrade of OS from Vista to XP. I have also installed SP1 & SP2. Still it is not working. The message that I get when I start SQL Server Management Studio is "The application cannot start."
View 7 Replies View RelatedHow can I upgrade Sql Express SP1 to SQL Server 2005 Standard ?
I've inherited 6 sql server 2000 boxes. I've upgrade 3 with no trouble. now I have one that gives the message :
"your upgrade is blocked because of cross-language compatibility rules.
For more information about cross-language support, see the version..."
all servers are 2003, sp2. All SQL is Enterprise edition, default language is "english". even the collation order is
the same. why the cross language message? Any help would be good else I'll be forced to rebuild the DB and load application again. ugly!!
dave
Getting error upgrading from SP1 to SP2:
SQL Server Database ServicesConfiguring Components:
The installed has encountered an unexpected error. The error code is 2259. Database: Table(s) update failed
Attached is the section of the SQL setup log where the error occurs:
MSI (s) (70!C4) [10:50:00:107]: PROPERTY CHANGE: Deleting SQLACCOUNT property. Its current value is 'NT AUTHORITYNETWORK SERVICE'.
<Func Name='updateFeatureSellection'>
Attempt to start service when it is already running
SQL service MSSQL$SQLEXPRESS started successfully waiting for SQL service to accept client connections
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.
<Func Name='SqlComponentUpgrade'>
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='111'>
<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='ProcessScriptTable'>
<Func Name='GetFileTargetPath'>
MSI (s) (70!C4) [10:50:00:417]: Note: 1: 2259 2: 3: 4:
<Func Name='GetFileTargetPath'>
Error Code: 0x8007065b (1627)
Windows Error Text: Function failed during execution.
Source File Name: darlibviewinstaller.cpp
Compiler Timestamp: Wed Jun 14 16:19:22 2006
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) (70!C4) [10:52:33:376]: 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 : Mon Mar 12 10:52:33 2007
<Func Name='ValidateUpgrade'>
<Func Name='updateFeatureSellection'>
<Func Name='SqlComponentUpgrade'>
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='111'>
<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='ProcessScriptTable'>
<Func Name='GetFileTargetPath'>
MSI (s) (70!C4) [10:52:33:506]: Note: 1: 2205 2: 3: _sqlSqlUpgradeInstallSequence
MSI (s) (70!C4) [10:52:33:506]: Note: 1: 2228 2: 3: _sqlSqlUpgradeInstallSequence 4: CREATE TABLE `_sqlSqlUpgradeInstallSequence` (`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) (70!C4) [10:52:33:506]: Note: 1: 2262 2: _sqlSqlUpgradeInstallSequence 3: -2147287038
<Func Name='GetFileTargetPath'>
MSI (s) (70!C4) [10:52:33:516]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '310719000'. Its new value: '325719000'.
MSI (s) (70!C4) [10:52:33:516]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '325719000'. Its new value: '325759000'.
MSI (s) (70!C4) [10:52:33:516]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '325759000'. Its new value: '325769000'.
MSI (s) (70!C4) [10:52:33:516]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '325769000'. Its new value: '395769000'.
MSI (s) (70!C4) [10:52:33:526]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '395769000'. Its new value: '576338000'.
MSI (s) (70!C4) [10:52:33:526]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '576338000'. Its new value: '591338000'.
MSI (s) (70!C4) [10:52:33:526]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '591338000'. Its new value: '621338000'.
MSI (s) (70!C4) [10:52:33:526]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '621338000'. Its new value: '621438000'.
Couldn't find SQL Agent service SQLAgent$SQLEXPRESS. Skipping service stop
Thanks for your help in advance,
Marty
I have multiple development SQL Servers running Enterprise edition that I want to upgrade for application testing before upgrading our production system. All of the servers meet the hardware and software requirements for SQL Server 2005 Enterprise edition. However, when I try to install to use the SQL Server 2005 Evaluation Edition to upgrade the servers in place, I get the blocked upgrade message:
Name: Microsoft SQL Server 2000
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.
Edition check:
Your upgrade is blocked because of edition upgrade rules. For more information about edition upgrades, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
Can the Evaluation Edition be used to upgrade these servers or do you need the full blown version?
thanks
I have downloaded SQLServer2005SP2-KB921896-x86-ENU.exe and attempted to update to SP2 with no success.
SQL Server 2005 Developers Edition is installed on my computer as part of a Visual Studio 2005 installation.
When I try to run this package under my admin account, I get through the Feature Selection (selecting everything) to Authentication.
When I press the Test button or the Next button, I get "Your account information could not be verified. Press Ok to return to Authentication Mode screen to determine the reason for failure. For setup to verify your credentials the services must be startable, connectable, and you must be a SQL Server administrator."
The Authentication screen shows "Database Services, MSSQLSERVER, Windows, domainusername, Service Failed to Start"
I am a novice SQL Server user, Clearly I am floundering! Any observations, advice, or suggestions would be greatly appreciated.
Hi
I am trying to upgrade an existing SQL Server 2000(SP3) instance to 2005.
In the installation process it showed me an existing component SQL Server 2000. But when I select the checkbox and hit the next button to upgrade the Database Engine I get an error
"Microsft SQL Server 2005 Error 1603. The setup has encountered an unexpected error while NextUpgradeDialog."
I am logged in as Administrator and have full permission.
Any help is appreciated.
Following is the Log File
Microsoft SQL Server 2005 Setup beginning at Tue Oct 09 11:30:49 2007
Process ID : 2940
E:Serverssetup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2007/9/9 11:30:48
Complete: LoadResourcesAction at: 2007/9/9 11:30:48, returned true
Running: ParseBootstrapOptionsAction at: 2007/9/9 11:30:48
Loaded DLL:E:Serversxmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2007/9/9 11:30:49, returned true
Running: ValidateWinNTAction at: 2007/9/9 11:30:49
Complete: ValidateWinNTAction at: 2007/9/9 11:30:49, returned true
Running: ValidateMinOSAction at: 2007/9/9 11:30:49
Complete: ValidateMinOSAction at: 2007/9/9 11:30:49, returned true
Running: PerformSCCAction at: 2007/9/9 11:30:49
Complete: PerformSCCAction at: 2007/9/9 11:30:49, returned true
Running: ActivateLoggingAction at: 2007/9/9 11:30:49
Complete: ActivateLoggingAction at: 2007/9/9 11:30:49, returned true
Delay load of action "DetectPatchedBootstrapAction" returned nothing. No action will occur as a result.
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__2940" returned false.
Running: PerformSCCAction2 at: 2007/9/9 11:30:49
Loaded DLL:C:WINDOWSsystem32msi.dll Version:3.1.4000.4042
Loaded DLL:C:WINDOWSsystem32msi.dll Version:3.1.4000.4042
Complete: PerformSCCAction2 at: 2007/9/9 11:30:50, returned true
Running: PerformDotNetCheck at: 2007/9/9 11:30:50
Complete: PerformDotNetCheck at: 2007/9/9 11:30:50, returned true
Running: ComponentUpdateAction at: 2007/9/9 11:30:50
Complete: ComponentUpdateAction at: 2007/9/9 11:31:44, returned true
Running: DetectLocalBootstrapAction at: 2007/9/9 11:31:44
Complete: DetectLocalBootstrapAction at: 2007/9/9 11:31:44, returned true
Running: LaunchLocalBootstrapAction at: 2007/9/9 11:31:44
Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run:
"C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe" finished and returned: 1603
Aborting queue processing as nested installer has completed
Message pump returning: 1603
Thanks
Reddy
Hi all,
My question might be a little bit unusual, but is it possible to upgrade SQL 2005 Express (the free version of SQL) to SQL 2000 Server without any loss of functionality?
Where do I have to pay attention to when doing this?
Thanks in advance!
MMQ
Hi All,
Currently we use SQL 2K SP4 and snapshot replication with a Central Publisher with Remote Distributor toplogy.
I am looking to upgrade or migrate our SQL servers to SQL 2005 and was wondering what is the best way to do this for our replicated architecture?
Is the best way to run the SQL 2005 Upgrade on all 3 servers (publisher, distributor, subscriber) and should it automatically upgrade the servers including the replication components? Is there anything i should consider/watch out for when doing the upgrade and it involves replication (namely snapshot replication)?
Thanks in advance.
I have SQL Server 2005 installed on a machine that was recently upgraded to SP2 (build 3042). The server never had the replication feature installed on it. I attempt to add replication to it and I get an error because (I think) I am installing from the initial version media (CD-ROM, build 1399) and the setup appears to want an MSI file for SP2. Any help is appreciated.
I followed the exact procedures in online help How to: Change Components in an Existing Instance of SQL Server 2005 (Setup), but after I get the Ready to Update page, I get the error box:
An installation package for the product Microsoft SQL Server 2005 cannot be found. Try the installation again using a valid copy of the installation package €˜SqlRun_SQL.msi€™.
Here is a partial output of the SQLSetupxxxx_ComputerName_Core.log file:
Action 17:44:25: ResolveSource.
Action start 17:44:25: ResolveSource.
MSI (c) (E4!D4) [17:44:25:200]: Resolving source.
MSI (c) (E4!D4) [17:44:25:200]: User policy value 'SearchOrder' is 'nmu'
MSI (c) (E4!D4) [17:44:25:200]: User policy value 'DisableMedia' is 0
MSI (c) (E4!D4) [17:44:25:200]: Machine policy value 'AllowLockdownMedia' is 0
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Media enabled only if package is safe.
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Looking for sourcelist for product {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Adding {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}; to potential sourcelist list (pcode;disk;relpath).
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Now checking product {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Media is enabled for product.
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Processing net source list.
MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1402 2: UNKNOWNNet 3: 2
MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1706 2: -2147483647 3: SqlRun_SQL.msi
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Processing media source list.
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Trying media source H:ServersSetup.
MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 2203 2: H:ServersSetupSqlRun_SQL.msi 3: -2147287037
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1706 2: -2147483647 3: SqlRun_SQL.msi
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Processing URL source list.
MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1402 2: UNKNOWNURL 3: 2
MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1706 2: -2147483647 3: SqlRun_SQL.msi
MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1706 2: 3: SqlRun_SQL.msi
MSI (c) (E4:7C) [17:44:25:200]: User policy value 'SearchOrder' is 'nmu'
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Media enabled only if package is safe.
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Prompting user for a valid source.
MSI (c) (E4:7C) [17:44:25:200]: Machine policy value 'DisableBrowse' is 0
MSI (c) (E4:7C) [17:44:25:200]: Machine policy value 'AllowLockdownBrowse' is 0
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Browsing is enabled.
MSI (c) (E4:7C) [17:44:25:200]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Now checking product {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Media is enabled for product.
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Processing net source list.
MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1402 2: UNKNOWNNet 3: 2
MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1706 2: -2147483647 3: SqlRun_SQL.msi
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Processing media source list.
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Trying media source SQLSTDSEL;.
MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1706 2: 3: SqlRun_SQL.msi
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Processing URL source list.
MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1402 2: UNKNOWNURL 3: 2
MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1706 2: -2147483647 3: SqlRun_SQL.msi
MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1706 2: 3: SqlRun_SQL.msi
MSI (c) (E4:7C) [17:44:44:388]: SOURCEMGMT: Trying source H:SetupSqlRun_SQL.msi.
MSI (c) (E4:7C) [17:44:44:388]: Cloaking enabled.
MSI (c) (E4:7C) [17:44:44:388]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (E4:7C) [17:44:44:403]: SOURCEMGMT: Resolved source to: 'H:Setup'
MSI (c) (E4!D4) [17:44:44:403]: SOURCEMGMT: Now checking product {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}
MSI (c) (E4!D4) [17:44:44:403]: SOURCEMGMT: Media is enabled for product.
MSI (c) (E4!D4) [17:44:44:403]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (c) (E4!D4) [17:44:44:403]: Note: 1: 1706 2: 3: SqlRun_SQL.msi
MSI (c) (E4!D4) [17:44:44:403]: SOURCEMGMT: Failed to resolve source
MSI (c) (E4!D4) [17:44:44:419]: Transforming table Error.
MSI (c) (E4!D4) [17:44:44:419]: Note: 1: 2262 2: Error 3: -2147287038
MSI (c) (E4!D4) [17:44:44:435]: Transforming table Error.
MSI (c) (E4!D4) [17:44:44:435]: Transforming table Error.
MSI (c) (E4!D4) [17:44:44:435]: Note: 1: 2262 2: Error 3: -2147287038
MSI (c) (E4!D4) [17:44:44:435]: Transforming table Error.
MSI (c) (E4!D4) [17:44:44:435]: Note: 1: 2262 2: Error 3: -2147287038
MSI (c) (E4!D4) [17:44:44:435]: Transforming table Error.
MSI (c) (E4!D4) [17:44:44:435]: Note: 1: 2262 2: Error 3: -2147287038
MSI (c) (E4:7C) [17:44:44:435]: Transforming table Binary.
MSI (c) (E4:7C) [17:44:44:435]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (c) (E4:7C) [17:44:44:450]: Transforming table Binary.
MSI (c) (E4:7C) [17:44:44:450]: Transforming table Binary.
MSI (c) (E4:7C) [17:44:44:450]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (c) (E4:7C) [17:44:44:450]: Transforming table Binary.
MSI (c) (E4:7C) [17:44:44:450]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (c) (E4:7C) [17:44:44:450]: Transforming table Binary.
MSI (c) (E4:7C) [17:44:44:450]: Note: 1: 2262 2: Binary 3: -2147287038
Error 1706. An installation package for the product Microsoft SQL Server 2005 cannot be found. Try the installation again using a valid copy of the installation package 'SqlRun_SQL.msi'.
MSI (c) (E4!D4) [17:45:02:731]: Transforming table Error.
MSI (c) (E4!D4) [17:45:02:731]: Note: 1: 2262 2: Error 3: -2147287038
MSI (c) (E4!D4) [17:45:02:747]: Transforming table Error.
MSI (c) (E4!D4) [17:45:02:747]: Transforming table Error.
MSI (c) (E4!D4) [17:45:02:747]: Note: 1: 2262 2: Error 3: -2147287038
MSI (c) (E4!D4) [17:45:02:747]: Transforming table Error.
MSI (c) (E4!D4) [17:45:02:747]: Note: 1: 2262 2: Error 3: -2147287038
MSI (c) (E4!D4) [17:45:02:747]: Transforming table Error.
MSI (c) (E4!D4) [17:45:02:747]: Note: 1: 2262 2: Error 3: -2147287038
MSI (c) (E4!D4) [17:45:02:747]: Product: Microsoft SQL Server 2005 -- Error 1706. An installation package for the product Microsoft SQL Server 2005 cannot be found. Try the installation again using a valid copy of the installation package 'SqlRun_SQL.msi'.
Action ended 17:45:02: ResolveSource. Return value 3.
<EndFunc Name='ResolveInstallMediaPath' Return='1602' GetLastError='0'>
<EndFunc Name='BackToBootstrap' Return='1602' GetLastError='0'>
PerfTime Stop: BackToBootstrap : Fri Mar 21 17:45:02 2008
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='1602' GetLastError='0'>
Action ended 17:45:03: BackToBootstrap.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 2.
MSI (c) (E4:98) [17:45:03:013]: Doing action: UserExit
Action 17:45:03: UserExit.
Action start 17:45:03: UserExit.
MSI (c) (E4:98) [17:45:03:013]: Transforming table CustomAction.
MSI (c) (E4:98) [17:45:03:013]: Note: 1: 2262 2: CustomAction 3: -2147287038
MSI (c) (E4:98) [17:45:03:028]: Transforming table CustomAction.
MSI (c) (E4:98) [17:45:03:044]: Transforming table CustomAction.
MSI (c) (E4:98) [17:45:03:044]: Note: 1: 2262 2: CustomAction 3: -2147287038
MSI (c) (E4:98) [17:45:03:044]: Transforming table CustomAction.
MSI (c) (E4:98) [17:45:03:044]: Note: 1: 2262 2: CustomAction 3: -2147287038
MSI (c) (E4:98) [17:45:03:044]: Transforming table CustomAction.
MSI (c) (E4:98) [17:45:03:044]: Note: 1: 2262 2: CustomAction 3: -2147287038
MSI (c) (E4:7C) [17:45:03:044]: Transforming table Binary.
MSI (c) (E4:7C) [17:45:03:044]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (c) (E4:7C) [17:45:03:059]: Transforming table Binary.
MSI (c) (E4:7C) [17:45:03:059]: Transforming table Binary.
MSI (c) (E4:7C) [17:45:03:059]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (c) (E4:7C) [17:45:03:059]: Transforming table Binary.
MSI (c) (E4:7C) [17:45:03:059]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (c) (E4:7C) [17:45:03:059]: Transforming table Binary.
MSI (c) (E4:7C) [17:45:03:059]: Note: 1: 2262 2: Binary 3: -2147287038
Action 17:45:03: UserExit. Dialog created
Action ended 17:45:04: UserExit. Return value 2.
Action ended 17:45:04: INSTALL. Return value 2.
MSI (c) (E4:98) [17:45:04:622]: Destroying RemoteAPI object.
MSI (c) (E4:64) [17:45:04:637]: Custom Action Manager thread ending.
Property(C): ProductCode = {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}
Property(C): ProductLanguage = 1033
Property(C): Manufacturer = Microsoft Corporation
Property(C): ProductVersion = 9.2.3042.00
Property(C): MEDIAPACKAGEPATH = Setup
Property(C): ALLUSERS = 1
Property(C): NULLGUID = {00000000-0000-0000-0000-000000000000}
Property(C): ASPNetVersion = 2.0.50727
Property(C): ARPHELPLINK = http://go.microsoft.com/fwlink/?LinkId=52152
Property(C): ARPPRODUCTICON = ARPIcon.ico
Property(C): ARPNOREPAIR = 1
Property(C): ARPSYSTEMCOMPONENT = 1
I would like to upgrade a production active/passive SQL Server 2000 cluster to SQL Server 2005.
I've read all of the documentation I could find, and doing an in-place upgrade seems to be the way to go. (Despite the fact it scares the hell out of me.
But throughout all the documentation, I've yet to see some simple and fairly important questions answered.
How does the process of upgrading SQL Server work when you're dealing with a cluster?
Do you upgrade one machine then the other? If so, do you upgrade the active node first, or the passive node?
What happens if you're forced to failover from one instance to the other before you've had a chance to upgrade both to 2005? In other words, you failover from 2005 to 2000. Would that even work?
What happens if your upgrades fails for some reason? Is it easy to rollback the installation? If not, will reinstalling SQL Server 2000 cause any issues? Will it remember the previous configuration and simply fix the broken install?
Any help/insight would be greatly appreciated.
I'm currently upgrading from Access to Sql Server, and I have a broken query that I cannot find a fix for.
The original query:
SELECT DISTINCT DownloadedNames.*FROM DownloadedSkims INNER JOIN (DownloadedNames INNER JOIN DownloadedInfo ON DownloadedNames.DNID = DownloadedInfo.DIDnID) ON DownloadedSkims.DM_ID = DownloadedInfo.DI_DM_IDWHERE DM_ID=23 AND (dWeek BETWEEN '6/26/2006' AND '9/18/2006')ORDER BY DIID, dWeek
I get the error "Msg 145, Level 15, State 1, Line 2
ORDER BY items must appear in the select list if SELECT DISTINCT is specified" when I test the query.
If anyone knows what changes I can make to the query, you'd really be helping me out.
Chris
Hi
We want to upgrade the Clustered SQL Server 2000 in our production environment to SQL Server 2005 (Clustered).
Are there any complexities we need to take care of?
Do we need a downtime during the period when the SQL server is being upgraded?
Thanks
Priyanka
I tried creating an alias to the server to get it to connect to analyze the server but it will not recognize the SQL 2000 server as a valid server to analyze. I can use the alias to connect in EM or SSMS. Any ideas? The server is not clustered and is at SP4. I've connected to several others in my environment but this one is causing me grief!
Thanks,
Linda
I upgraded my SQL 2005 Workgroup 2005 to SP2 and subsequently could not get the SQL Server service running. Turns out this was a problem because I had created separate folders for my data and log files. The distmdl.mdf and mssqlsystemresource.mdf files were in my data folder and distmdl.ldf and mssqlsystemresource.ldf were in my log folder. During SP2 upgrade a new distmdl.ldf and mssqlsystemresource.ldf were created in my data folder. I deleted the distmdl.ldf and mssqlsystemresource.ldf files in my log folder and then moved the newly created ones in my data folder into the log folder and all is well now.
Just a heads up!
--Greg
I have upgraded a server with 4 CPU's 1.7 Dual Core AMD opteron.
Running with 16 GB RAM, on windows server 2003 enterprize edition.
and my server has really slowed down ?
An i missing something need urgent help