Unattended Upgrade Of SQL Server 2005 Express SP1 To SP2 Not Succeeding
Mar 30, 2007
1. Extracted SQL Server 2005 Express Service Pack 1 files to local filesystem.
2. Ran setup.exe from local filesystem.
3. Changed all installation paths to D. Specified data files go to D:Data
3. Set all services to run as Local System.
4. Did not reboot.
5. Extracted SQL Server 2005 Express Service Pack 2 files to local filesystem.
6. Attempted an unattended installation using /settings and a modified template.ini file.
7. Checked C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSummary.txt which did not show any errors.
8. SELECT @@VERSION showed the version number is 9.00.2470.00, which indicates the upgrade was not actually successful.
This is what was in the modified template.ini file:
INSTANCENAME=MSSQLSERVER
INSTALLSQLDIR="D:Program FilesMicrosoft SQL Server"
UPGRADE=SQL_Engine
INSTALLSQLSHAREDDIR="D:Program FilesMicrosoft SQL Server"
ENABLERANU=0
Tried added this, which did not help:
REINSTALLMODE=vomus
Also tried adding this, which did not help, either:
INSTALLSQLDATADIR="D:Data"
What does it take to have a successful unattended upgrade of SQL Server 2005 Express from SP1 to SP2?
View 3 Replies
ADVERTISEMENT
Jan 7, 2008
Hi There
I am doing an unattended upgrade of Sql Express with Advanced Services SP1.
Before the upgrade the services run under domain accounts.
I use the following command :
start /wait setup UPGRADE=SQL_Engine INSTANCENAME=MSSQLSERVER SQLACCOUNT=DOMAINUser SQLPASSWORD=p@ssw0rd ADDLOCAL=Client_Components,SQL_SSMSEE /qn
However after the ugrade the service accounts are running under local system.
Documentation is unclear, i find the following:
; The services for SQL Server and Analysis Server are set auto start. To use the *ACCOUNT settings
; make sure to specify the DOMAIN, e.g. SQLACCOUNT=DOMAINNAMEACCOUNT
; NOTE: When installing SQL_Engine 3 accounts are REQUIRED: SQLACCOUNT, AGTACCOUNT and SQLBROWSERACCOUNT.
; SQLACCOUNT Examples:
; SQLACCOUNT=<domainuser>
; SQLACCOUNT="NT AUTHORITYSYSTEM"
; SQLACCOUNT="NT AUTHORITYNETWORK SERVICE"
; SQLACCOUNT="NT AUTHORITYLOCAL SERVICE"
To my knowledge the <> is not required.
Can someone please help as i cannot get the services accounts to run under a domain user after upgrade.
Thanx
View 1 Replies
View Related
May 2, 2008
Hi,
I have a script that performs an unattended installation of SQL Server and works fine.
However, if I un-install via the control panel all the files are removed apart from the databases that are created by me when SQl server was installed. This is good and ensures data is not deleted.
The files left over are in the following directory:
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLData
and contains:
MyDatabase.mdf
MyDatabase_log.LDF
The problem I have is after performing the re-installtion of SQL server (unattended) I am unable to create a new database with the same name (in this instance called "myDatabase").
The actual files are physically there so this is the reason a new database with the same name cannot be creacted.
Again this is ok again because it ensures I cannot overwrite existing data. However I am unable to re-attach this database to SQl server so I can continue to use it!
The question is:
How do I make this database usable again after an unattended install? Is there a parameter I am missing?
Below are the commands I use that are passed to the installation of SQL Server as command line parameters:
#define SQL_SILENT "-q /passive /norebootchk /qn reboot=ReallySuppress"
#define SQL_USERNAME "username=MyUserName"
#define SQL_COMPANYNAME "companyname=MyCompanyName"
#define SQL_ADDLOCAL "addlocal=ALL"
#define SQL_DISABLENETWORKPROTOCOLS "disablenetworkprotocols=0"
#define SQL_INSTANCENAME "instancename=MSSQLSERVER"
#define SQL_SQLAUTOSTART "SQLAUTOSTART=1"
#define SQL_SECURITYMODE "SECURITYMODE=SQL"
#define SQL_SAPWD "SAPWD=#Password#"
#define SQL_SAVESYSDB "1"
#define SQL_USESYSDB ""
#define SQL_INSTALLSQLDIR ""
#define SQL_INSTALLDATADIR ""
#define SQL_PARAMETERS SQL_SILENT + " " + SQL_USERNAME + " " + SQL_COMPANYNAME + " " + SQL_ADDLOCAL + " " + SQL_DISABLENETWORKPROTOCOLS + " " + SQL_INSTANCENAME + " " + SQL_USESYSDB + " " + SQL_INSTALLSQLDIR + " " + SQL_INSTALLDATADIR + " " + SQL_SAVESYSDB + " " + SQL_SQLAUTOSTART + " " + SQL_SECURITYMODE + " " + SQL_SAPWD
The last four commands I have played around with but for some reason SQL Server service will not start when these are used! (This is a different issue though!).
Any advice would be gratefully accepted.
Thanks
Paul
View 3 Replies
View Related
Jun 23, 2015
I'm trying to do an unattended upgrade of 2014 RTM to 2014 SP1.
It's my first attempt at an upgrade configuration file, and its failing with missing registry entry for database engine service and replication service.
Error in summary.txt is:
The registry key SOFTWAREMicrosoftMicrosoft SQL ServerMSSQL12.MSSQLSERVER2495Setup is missing
That's a valid error, as the registry only has an entry for:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL ServerMSSQL12.MSSQLSERVERSetup
Am I missing something obvious here, or how can this be resolved?
View 9 Replies
View Related
Jul 6, 2006
Hi there,
I am trying to create an un-attended SQL 2005 Express install. I have successfully made my own template.ini file to install SQL the way I like but I cannot find a way to make it install with the "Ad hox remote queries" option enabled.
Is there anyway to do this? I can't seem to find any switches in the INI file to allow this.
Thanks
Joseph Beckett
View 7 Replies
View Related
Jul 7, 1999
How can one perform upgrade to SQL 7.0 from 6.x without using the upgrade wizard? Is there any unattended upgrade option that one can exercise?
Also, if SQL 7.0 is already installed, can one do a selective upgrade of some SQL 6.5 objects? For instance, can one upgrade only the tables, views and triggers from 6.5 to a 7.0 database?
Any pointers, help, info in this regard would be greatly appreciated!
Rnathan
View 2 Replies
View Related
Feb 25, 2008
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.
View 4 Replies
View Related
Jul 29, 2006
if i upgrade from sql server 2005 expressto sql server 2005 enterprise can i do it ?
am i need to uninstall 2005 express before ?
View 1 Replies
View Related
Dec 29, 2006
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
View 5 Replies
View Related
Dec 19, 2006
Hi,
I'm currently trying to develop an unattended installation of the Client Tools to be distributed to developers workstations.
All is well on 'clean' machines, but the problems arise when an instance of SQL Server Express is already present. The install fails, and the reason isn't clear from the log files.
I know Express installs a couple of the Client Components (like Config Manager), and I believe this is what it blocking me.
Has anyone tried this scenario?
Would I be best to REMOVE the Client_Components first, and then re-install them with SSMS etc.? Or is there a better method?
I have to leave the Express Database instance untouched as I'm not responsible for its installation or maintenance.
Thanks,
Gordon.
View 1 Replies
View Related
Jan 26, 2007
How can I upgrade Sql Express SP1 to SQL Server 2005 Standard ?
View 1 Replies
View Related
Mar 12, 2007
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
View 1 Replies
View Related
Aug 20, 2007
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
View 1 Replies
View Related
Feb 18, 2008
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?
View 2 Replies
View Related
Sep 26, 2007
Hi,
I am trying to upgrade MSDE 2000 to MS SQL Server 2005 Express Edition SP2 (Build 9.00.3042.0) using a silent install.
MSDE on our systems is installed as a standalone product. There is only a single default instance (MSSQLSERVER) running on the system. SQL Authentication mode is being used.
When I try and upgrade MSDE 2000 directly to MS SQL Server 2005 Express Edition SP2, the install fails with an error:
"SQL Server Setup Cannot Upgrade the specified instance by using SQL Server Credential. You must use Windows Authentication credential for the upgrade"
When I try to upgrade the default instance of MSDE to SQL Server 2005 Express Edition SP2 selecting Windows authentication (logging in as a domain/local administrator to the server), the install fails with an error:
"Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user <mydomain><AdminID>"
However, MSDE 2000 upgrade to an earlier version of MS SQL Server 2005 Express Edition (Build 9.00.1399.6) using SA Authentication works successfully without any errors.
So I tried to upgrade our MSDE installation to SQL Server 2005 Express Edition SP2 (Build 9.00.3042.0) as a 2 step process. First by upgrading MSDE to SQL Server 2005 (Build 9.00.1399.6) using SA Authentication which works successfully as mentioned earlier.
However, when I try and upgrade SQL Server 2005 (Build 9.00.1399.6) to SQL Server 2005 SP2 (Build 9.00.3042.0) using SA Authentication, I receive the same error as before:
"SQL Server Setup Cannot Upgrade the specified instance by using SQL Server Credential. You must use Windows Authentication credential for the upgrade"
When I upgrade using Windows Authentication, the setup displays the following error:
"[Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet the requirements of the password filter DLL.. To continue, correct the problem, and then run SQL Server Setup again"
The log file content for the error is:
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------SQL_ERROR (-1) in OdbcStatement::execute_batch
sqlstate=01000, level=0, state=1, native_error=0, msg=[Microsoft][SQL Native Client][SQL Server]Signing sps ...
sqlstate=42000, level=16, state=1, native_error=15119, msg=[Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet the requirements of the password filter DLL.
sqlstate=HY000, level=0, state=0, native_error=0, msg=[Microsoft][SQL Native Client]Unspecified error occurred on SQL Server. Connection may have been terminated by the server.
sqlstate=42000, level=16, state=2, native_error=2745, msg=[Microsoft][SQL Native Client][SQL Server]Process ID 51 has raised user error 50000, severity 20. SQL Server is terminating this process.
sqlstate=HY000, level=20, state=127, native_error=50000, msg=[Microsoft][SQL Native Client][SQL Server]Cannot create ##MS_AgentSigningCertificate## in msdb. INSTMSDB.SQL terminating.
Error Code: 15119
MSI (s) (08!80) [10:56:13:133]: PROPERTY CHANGE: Adding SqlUpgradeMessage property. Its value is 'SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet the requirements of the password filter DLL.. To continue, correct the problem, and then run SQL Server Setup again.'.
SQL Server Setup has encountered the following problem:
Failed to execute the Transact-SQL statement:
/**************************************************************/
/* Sign agent sps and ...
Script file: sqlagent90_msdb_upgrade.sql
The error was: [Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet the requirements of the password filter DLL.. To continue, correct the problem, and then run SQL Server Setup again.
SQL_ERROR (-1) in OdbcHandle::release
sqlstate=HY010, level=-1, state=-1, native_error=0, msg=[Microsoft][ODBC Driver Manager] Function sequence error
SQL_ERROR (-1) in OdbcHandle::release
sqlstate=HY010, level=-1, state=-1, native_error=0, msg=[Microsoft][ODBC Driver Manager] Function sequence error
SQL_ERROR (-1) in OdbcHandle::release
sqlstate=HY010, level=-1, state=-1, native_error=0, msg=[Microsoft][ODBC Driver Manager] Function sequence error
Error Code: 0x80073b0f (15119)
Windows Error Text: Source File Name: libodbc_statement.h
Compiler Timestamp: Wed Jun 14 16:28:15 2006
Function Name: OdbcStatement::execute_batch@sqlagent90_msdb_upgrade.sql@967
Source Line Number: 91
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The registry entries suggest that the version now is 9.00.3042.0. However, I am not sure if the upgrade was successful. I can connect to the database using the old SA user ID and password.
If anyone else has faced similar issues, please let me know the workaround for the same.
Thanks and Regards,
Sahil Girotra
View 3 Replies
View Related
Sep 28, 2007
Hi,
I am planning an upgrade from MSDE to SQL Server 2005 Express Edition SP2 (Build 9.00.3042.0) for our 2000/2K3 Servers. The MSDE installation on our servers is a standalone installation (default instance) and uses Mixed Mode Authentication. When I execute the setup program for upgrade and choose SQL Server Authentication (and enter the corresponding SA user Id password), the setup program displays an error "SQL Server Setup cannot upgrade the specified instance by using SQL Server Credential. You must use Windows Authentication credential for the upgrade". However, when I select Windows Authentication for the upgrade, the setup program displays an error €œ[Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet the requirements of the password filter DLL.. To continue, correct the problem, and then run SQL Server Setup again€? (Error Code 15119).
I even tried changing the Authentication mode from Mixed Mode to Windows Authentication (by changing the LoginMode registry key value to 1) and running the upgrade using Windows Authentication, but I receive the same error.
1) Is the password policy for SQL Server 2005 Express Edition SP2 different from MSDE or SQL Server 2005 Express Edition (Initial Version), since upgrade from MSDE to SQL Server 2005 Express Edition (Initial Version) worked successfully without any issues.
2) When I am using Windows Authentication for the upgrade, the installer does not prompt me for any password. What password is the installer validating against the password filter DLL? Is there a way to find it out? Also, is it possible to find out what was the reason for the password validation to fail?
I would really appreciate if I could get some answers to all the problems I am facing.
Thanks in Advance.
Regards,
Sahil Girotra
View 1 Replies
View Related
Sep 6, 2007
I have a Windows Server 2000/Windows Server 2003 Environments with MSDE installed (default instance) and SecurityMode is SQL. I want to upgrade from MSDE to SQL Server 2005 Express Edition using a silent install since the number of servers is huge.
I downloaded the latest SQL Server 2005 Express Edition SP2 Version 9.0.3042.0 from http://msdn2.microsoft.com/en-us/express/bb410792.aspx
I am having the following problems:
- When I try to upgrade the default instance of MSDE (MSSQLSERVER) to SQL Server 2005 Express Edition SP2 using the above installer and selecting SQL authentication, the install fails with an error "SQL Server Setup Cannot Upgrade the specified instance by using SQL Server Credential. You must use Windows Authentication credential for the upgrade".
- When I try to upgrade the default instance of MSDE (MSSQLSERVER) to SQL Server 2005 Express Edition SP2 using the above installer and selecting Windows authentication, the install fails with an error "Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user <mydomain><AdminID>
I had earlier tested upgrading the MSDE installation to SQL Server 2005 Express Edition Version 9.00.1399.6 downloaded from http://www.microsoft.com/downloads/details.aspx?familyid=220549b5-0b07-4448-8848-dcc397514b41&displaylang=en and the upgrade worked successfully using SQL Authentication (SA User and corresponding password), but for some reason it doesn't work when I use the latest version 9.0.3042.0.
Has anyone else faced similar issues. Any tips on how I can upgrade from MSDE to SQL Server 2005 Express Edition SP2 are welcome.
Thanks in Advance.
Sahil Girotra
View 4 Replies
View Related
Jun 21, 2007
I have a database on one server that is running MSDE and I would like to copy it to another server running SQL Server Express.
The process I followed was to create a backup on the first server.
Copy the backup file to the other sever
Then restore using the backed database file on the new server
Is this the right procedure? Everything I see about migrating in on the same server. I do not want to do it on the same server as we are migrating the application to the new server.
View 4 Replies
View Related
Aug 23, 2007
I tried to upgrade an Express edition 2005 to Standard Edition 2005. I did remember to use the command prompt setup parameter to allow the upgrade but still the option to upgrade is disabled. Can upgrade from express to standard?
View 10 Replies
View Related
Aug 15, 2006
When doing a unattended install of Microsoft SQL Server Express, I have a problem specifing the service to installed to be run under the as local system account.
I'm using: SQLACCOUNT & SQLPASSWORD parameters but it just won't work.
As default SQL Server is installed using the NETWORK SERVICE account, this causes the database to be read-only. What I want is to specifiy in the script that the service should run under the LOCAL SYSTEM account instead. This must also be OS-language independent.
I've tried:
SQLACCOUNT=NT AUTHORITYSYSTEM
SQLACCOUNT=NT AUTHORITYLOCAL SYSTEM
SQLACCOUNT=NT AUTHORITYLOCAL SERVICE
SQLACCOUNT=SYSTEM
SQLACCOUNT=BUILT-INSYSTEM
etc.
and even some different SID as:
S-1-5-18
S-1-5-19
All with no password with the SQLPASSWORD parameter:
SQLPASSWORD=
I still getting the same error while validating the service account.
Is there someone else who knows what I'm doing wrong?
Best regards,
Mattias
View 5 Replies
View Related
Jun 28, 2006
I'm trying to upgrade the Default Instance of MSDE 2000 Release A which is installed with Mixed Mode and strong password to SQL Server 2005 Express in a Windows 2000 Server with SP4. On the Upgrade Logon Information screen, if I select SQL Server Authentication Mode, it will give me this message:
SQL Server Setup Cannot Upgrade the specified instance by using SQL Server Credential. You must use Windows Authentication credential for the upgrade.
Thanks for any help.
View 1 Replies
View Related
Mar 9, 2007
If I search for updates with Microsoft or Windows Update it notifies me to upgrade SQL Server Express to SP2. After the download the installation fails. The reason seems to be that Microsoft Update downloads SP2 with the wrong language:
Summary.txt
**********************************************************************************
Products Detected Language Level Patch Level Platform Edition
Datenbankdienste für Express (SQLEXPRESS) DEU SP1 2005.090.2047.00 x86 EXPRESS
Datenbankdienste für Express (SQLExpress) ENU SP2 x86 EXPRESS
**********************************************************************************
Products Disqualified & Reason
Product Reason
Datenbankdienste für Express (SQLExpress) Für dieses Update ist die Sprache DEU erforderlich (required/me). Bei der Produktinstanz SQLExpress wird die Sprache ENU verwendet. Downloaden (download/me) Sie das Update für ENU.
**********************************************************************************
Summary
One or more products failed to install, see above for details
Exit Code Returned: 1627
Thank you.
View 7 Replies
View Related
Sep 22, 2006
Hey guys -
I am busy testing SQL 2005 Server Unattended installations and have a quick question. Microsoft specifies the following code for command line installation:
Start /wait <CD or DVD Drive>serverssetup.exe /qb INSTANCENAME=<InstanceName> ADDLOCAL=All PIDKEY=<pidkey value with no "-"> SAPWD=<StrongPassword>
SQLACCOUNT=<domainuser>
SQLPASSWORD=<DomainUserPassword>
AGTACCOUNT=<domainuser>
AGTPASSWORD=<DomainUserPassword> SQLBROWSERACCOUNT=<domainuser>
SQLBROWSERPASSWORD=<DomainUserPassword>
Here is a link to the installation pages: Click Here (http://msdn2.microsoft.com/en-us/library/ms144259.aspx)
My question is what are all the different accounts for?
Any help will be appreciated.
Thanks
Reghardt
View 1 Replies
View Related
Sep 10, 2007
Hello,
I have a quick question about automating installation of SQL 2005. This question doesn't relate as much to SQL 2005 as it does setting up a database server.
I know that it's usually standard practice to allow SQL to "lock pages in memory". What I am trying to do is find a command line utility that will allow me to add this step to the SQL install script. Any help is appreciated. Thank you.
View 3 Replies
View Related
May 7, 2008
Hi All,
A client of mine was using SQL Express and soon realised this doesn't meet his needs performance or database size wise. He also realised that SQL Server 2005 Workgroup came free with his R2 version of SBS.
So in essence, I have been trying to find the Microsoft recommended way to upgrade from Express to Workgroup. I have not been able to find a step-by-step guide and to add to my confusion, when I run the work-group installer it tells me to run the installer with a switch which I have gone ahead and done but when selecting components it has all of them defaulted to blanked out.
Surely the process for an in-place upgrade should not be so technical as I am finding it ? To my mind, the natural progression would be to upgrade express to a better capable version of 2005 and should be as easy as pie.
Anyway, I am basically looking for a step-by-step guide on how to upgrade to get it done right the first time as opposed to upgrading and than realised some remenants of Express are still larking about causing trouble.
Regards,
QS
View 3 Replies
View Related
Mar 1, 2007
Hi. I'm trying to get full-text search working on my SQL 2005 Express with Advanced Services and am having problems. I thought that I installed it correctly, and when I look in the services running, I see it SQL Server Fulltext Search(MSSQLSERVER). Also note that I have SQL Server 2005 Standard installed on this same laptop. I don't know if that Full text Search applies to the Standard, Express or both.
What I do see is that if I connect to the database engine named <mylaptop>, I can see the version is 9.0.1399 and I can see the check box to enable full-text indexing in a particular databases properties. When I run SELECT FULLTEXTSERVICEPROPERTY('IsFullTextInstalled'), I get a 1.
However, when I connect to the engine name <mylaptop>SQLExpress, I se the version is 9.0.3042, and I don't see the same check-box to enable full-text indexing. When I run SELECT FULLTEXTSERVICEPROPERTY('IsFullTextInstalled'), I get a 0.
I've never tried this before so I know I'm probably missing something basic. But, I have searched quite a bit and not found my answer. So, I'm looking to you for help.
Thanks in advance.
John.
View 3 Replies
View Related
Jan 8, 2008
Hello,
I am currently using SQL server express for my website. The connection is fairly sluggish and it can take about 30 seconds to log in say. My web host says this is because I am using SQL server express and they recommend upgrading to SQL server 2005.
Has anyone else had similar sluggish connection with SQL server express?
Can I also ask the best way to upgrade an SQL server express database to SQL server 2005?
Thanks for any help
View 3 Replies
View Related
Jan 17, 2008
Hello All, I am trying the following script to upgrade SQL Server 2005 SP1 to SP2. I have an Active Passive cluster configuration. I have default instances of SQL Server. I am using the following script.
start /wait c:1sqlserversp2SQLSERVER2005SP2-KB921896-x86-ENU.exe /allinstances /quiet.
The sql server install fails to run. When I used the above command with just
start /wait c:1sqlserversp2SQLSERVER2005SP2-KB921896-x86-ENU.exe /quiet still the summary.txt file came with authentication success and that is all. I changed the above script and did
start /wait c:1sqlserversp2SQLSERVER2005SP2-KB921896-x86-ENU.exe /instancename=instancename of the cluster
This worked, however the install patched the passive node (DB engine, all the cluster unaware components) but failed to patch the DB engine on the Active node. I had to run the SQL Server sp2 install manually but still it did not patch the DB engine on the primary node
1. Can someone please help me with this issue as I want the unattended install to work. so it installs both active and passive node. I will post the final output and also the ADS script to do this as a bonus if this works.
Here is the summary.txt file.
**********************************************************************************
Processes Locking Files
Process Name Feature Type User Name PID
msftesql Database Services Service 5152
MSSQLSERVER Database Services Service 4412
ResrcMon.exe Database Services Application SHOMSCSService 4688
**********************************************************************************
Product Installation Status
Product : Setup Support Files
Product Version (Previous): 3042
Product Version (Final) :
Status : Not Selected
Log File :
Error Description :
----------------------------------------------------------------------------------
Product : Database Services (MSSQLSERVER)
Product Version (Previous): 2153
Product Version (Final) :
Status : Failure
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log
Error Number : 29506
Error Description : MSP Error: 29506 SQL Server Setup failed to modify security permissions on file D:Microsoft SQL ServerMSSQL.1MSSQLData for user sqlservice. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that exists on the destination drive.
----------------------------------------------------------------------------------
Product : Integration Services
Product Version (Previous): 3042
Product Version (Final) :
Status : Not Selected
Log File :
Error Description :
----------------------------------------------------------------------------------
Product : SQL Server Native Client
Product Version (Previous): 3042
Product Version (Final) :
Status : Not Selected
Log File :
Error Description :
----------------------------------------------------------------------------------
Product : Client Components
Product Version (Previous): 3042
Product Version (Final) :
Status : Not Selected
Log File :
Error Description :
----------------------------------------------------------------------------------
Product : MSXML 6.0 Parser
Product Version (Previous): 1129
Product Version (Final) :
Status : Not Selected
Log File :
Error Description :
----------------------------------------------------------------------------------
Product : SQLXML4
Product Version (Previous): 3042
Product Version (Final) :
Status : Not Selected
Log File :
Error Description :
----------------------------------------------------------------------------------
Product : Backward Compatibility
Product Version (Previous): 2004
Product Version (Final) :
Status : Not Selected
Log File :
Error Description :
----------------------------------------------------------------------------------
Product : Microsoft SQL Server VSS Writer
Product Version (Previous): 3042
Product Version (Final) :
Status : Not Selected
Log File :
Error Description :
----------------------------------------------------------------------------------
**********************************************************************************
Summary
One or more products failed to install, see above for details
Exit Code Returned: 29506
View 1 Replies
View Related
May 23, 2008
Hi,
I'm trying to upgrade my system from SSE 2005 to SS 2005, when I ran Upgrade Advisory it fails with several errors that identified as blocked failure..
Here are some of the warning and errors:
Warning on SQL Server component (Insatance Name SQLEXPRESS) - "SQL server version 09.00.3054 is not supported by this release of Upgrade Advisory"
On the Reporting Services - "Virtual Directory settings do not match the default configuration"
On the Reporting Services - "Other Reporting Services upgrade issues"
On the Reporting Services - "Custom virtual directory settings block edition upgrade"
On the Reporting Services - "Custom extensions are deployed on the report server"
I tried to follow the instructions to Reporting Services Upgrade Issues but it didn't help..
Is it me or someone else run into this same problem? Any KB on this somewhere?
Other question is - can I install both versions on the same system without a problem?
Thanks,
T.
View 1 Replies
View Related
Jan 10, 2008
The scenario I have is as follows:
Our product ships with a bootstrapper that installs SQL Server 2005 silently for our clients - basically it's a pre-req which we load for them if it's not already installed.
The bootstrapper supplies the service account identity parameters for the SQL Server install command line in English. It supplies the local system account (NT AUTHORITYSYSTEM).
The problem occurs when we tried to install the product onto a French version of XP. We got the error message "SQL Server setup could not validate the service accounts. Either the service accounts have not been provided for all the services being installed, or the specified username or password is incorrect. For each service, specify a valid username, password, and domain, or specify a built-in system account."
Having read the page http://msdn2.microsoft.com/en-us/library/ms143504.aspx#Localized_service_names we have discovered that the system account identity has a different name for French (AUTORITE NTSYSTEM) along with some other languages ... but we're not sure how to resolve the problem.
Can anyone out there tell me whether we ...
1) Can get the machine being installed on to tell us the local system account identity so we can substitute it into our command line in the bootstrapper?
2) Have to write a different bootstrapper for each language that names the local system account identity differently?
3) Have overlooked some other solution?
Also, does anyone know how many languages and which they are that give the local system account a name that's different to "NT AUTHORITYSYSTEM"??
Thanks,
Sara
<EDIT>
Sorry, omitted a vital bit of information. The bootstrapper is written in C++.
We know the .NET code to retrieve an NT account given a well known SID. Can we do the same in C++ somehow??
</EDIT>
View 3 Replies
View Related
Jan 16, 2008
I am out of brain cells. I can not figure out how to upgrade instances of sql express to sql 2005 or even add an instance of sql 2005. I have installed/upgraded everything else (SSMS, etc.) to SQL 2005.
I am dazed and confused. I don't even know where to start in explaining what I have tried and done. I have 303 log files going back to 3/27/2007 from various attempts.
Where do I start in figuring this debacle out???
View 7 Replies
View Related
May 25, 2007
I currently have SQL Server Management Studio Express 2005 and would like to upgrade my machine to SQL Developer 2005 as easily as possible. Keeping my databases and such.
Any recommendations on the best way to do this would be greatly appreciated.
thanks!
View 3 Replies
View Related
Oct 13, 2007
Good afternoon,
I have written a .NET app that kicks off an unattended install of SQL Server Express Advanced. After the install, the same app tries to connect to SQL Express adn run a script that creates a database plus a few other things.
However, the problem I am having is that my app cannot connect. I get the error:
"An error has occurrred while establishing a connection to the server. This failure may be casued by the fact that under the default settings SQL Server does not allow remote connections."
However, the unattended install goes great. No problems there. I know this because I can Open SSMS, run queries, created DB's, etc. I also know that it is not the remote connections issue because the unattended install is set to allow remote connections (both names pipes and TCP/IP).
So, why can't i connect? I don't need to reboot after the install do I? Please tell me i don't...and please tell me it is something simple I am overlooking.
Thanks...
View 3 Replies
View Related
