I have a SQL 2k5 log shipping setup and all copy jobs as well as restore jobs are running properly but the LS_Alert job that the wizard auto creates fails every two minutes has anyone experienced this before. After going through the wizard it creates a LS_Alert job and schedules it every two minutes and it fails constantly.
Thanks!
kdubb
We have log shipping for databases from production to back office (BO) environments for users to run reports. In preparation for moving a back office environment to a different server, we want to setup an addition log shipping environment, let’s call it BO2, same as the BO. One of the challenges we had was the amount of time it would take to get the full backup from production to BO2 due to the size of the database. It would take days just to transfer the full backup.
Solution:Let’s just say the database being logged shipped is DB123. Instead of using the full backup of DB123 from production, we use the mdf and ldf of DB123 from current log shipped database on the BO to setup the additional log shipping on BO2.
Steps:1.Setup the directory structure for the undo file (tuf) on the BO2 server same as the BO server.
Note: The undo can be moved to different drive after the log shipping is setup.
2.Stop SQL services on the BO server.
3.Copy the undo file (tuf), mdf, and ldf files of the log shipped database, DB123, from server BO to server BO2.
Note: Keep these files as main copies because they will be used multiple times. Do NOT copy files to where you’ll put the new database files.
4.After the files are copied, start SQL services on BO.
5.On the BO2 server, create an empty database DB123 with database name, file_id, logical names, physical names exactly the same as the ones on the BO server.
Note: Make the size of mdf and ldf small so it doesn’t take long to create the database.
6.Stop SQL Services on the BO2 server.
7.Overwrite the new mdf and ldf files of the empty database DB123 with the mdf and ldf files that were copied over from BO.
8.Start SQL services on BO2.
Note: If the file_id, logical names and physical names are not matching up, the database will be in suspect mode.
9.Do a backup of DB123 with COPY_ONLY.
10.Drop DB123 on BO2 after backup is complete.
11.Use the full backup from previous step to setup log shipping of DB123 on BO2.
Note: Below was the LiteSpeed syntax that was used
exec master.dbo.xp_restore_database @database = N'DB123' ,
@filename = N'F:SQL BackupsDB123_FULL.slsfull',
@filenumber = 1,@with = N'STATS = 10',
@with = N'STANDBY = N''C: MSSQLDataROLLBACK_UNDO_DB123.trn''',
@affinity = 0,@logging = 0
12.Stop SQL services on BO2.
13.Again, overwrite the mdf, ldf and undo file (tuf) of DB123 on server BO2 with mdf, ldf, and undo file (tuf) from BO.
14.Start SQL services on BO2.
15.Replay transaction log from PRD
Note: You can change the location of the undo file by copy the current undo file to the new location and point to new location in “STANDBY” parameter. DO NOT do cut and paste of undo file but do copy and paste.
It works on Microsoft SQL Server 2008 R2 (SP2) - 10.50.4033.0 (X64) . I have not tried it on SQL Server 2012 yet.
In steps that stop/start SQL services, you can bring the database offline/online.
In a way, this is doing detach/attach a log shipped database.
I have a SQL 2k5 log shipping setup and all copy jobs as well as restore jobs are running properly but the LS_Alert job that the wizard auto creates fails every two minutes has anyone experienced this before. After going through the wizard it creates a LS_Alert job and schedules it every two minutes and it fails constantly.
Thanks!
kdubb
I have a SQL 2k5 log shipping setup and all copy jobs as well as restore jobs are running properly but the LS_Alert job that the wizard auto creates fails every two minutes has anyone experienced this before. After going through the wizard it creates a LS_Alert job and schedules it every two minutes and it fails constantly.
Thanks!
kdubb
Whats new for SQL Server 2005 SP2 states:-
"The sqllogship application is now supported."
Can anybody confirm that log shipping is not supported in SQL Server 2005 SP1?
Thanks
Hi everyone,
How/when should transaction logs be truncated without breaking Log Shipping?. I'm trying to deal with the scenario of my tlogs increasing their size as I configure log shipping to 5 min. -frequency backups.
Many thanks
Question: I have Log Shipping setup and i am wanting to verify it will do what we need. That is when a table is changed in our production enviroment that change is replicated into our other server. IE I rename a field in a table or create a new table... You know change the structure... How do I replicate that stuff to my other servers?
View 6 Replies View RelatedWe have an environment where 3 SQL 2000 servers exist; one production servers and two standby servers that receive logs via log shipping. Everything works fine and it is stable. My client wants to get a new 64 bit server and run SQL 2005 64 bit version for the production box. Can we still do log shipping with the two remaining SQL 2000 boxes or do they all have to be on the same version and bit version?
Thanks
Bill
Hello, I would like to know if anyone here has any information on how to change the default version of SQL Server 2005 Express which ships with Visual Studio 2005 to the new SQL 2005 Express SERVICE PACK 1?
I see a file under disc:vswcuSSESQLEXPR.exe I am wondering if changing that file with the new one from Microsoft Download Center will do it...
There's another file under that folder named sqlexpr32.exe I am wondering what it's for?
Thanks in advance.
Hello, I would like to know if anyone here has any information on how to change the default version of SQL Server 2005 Express which ships with Visual Studio 2005 to the new SQL 2005 Express SERVICE PACK 1?
I see a file under disc:vswcuSSESQLEXPR.exe I am wondering if changing that file with the new one from Microsoft Download Center will do it...
There's another file under that folder named sqlexpr32.exe I am wondering what it's for?
Thanks in advance.
I am having trouble finding any documentation on how linked servers are set-up under SQL 2005 for log-shipping and replication. Under SQL 2000, the only linked servers "visible" were ones that were user-defined. Under SQL 2005, it seems when you set-up log-shipping or replication, you get these new linked servers which are automatically defined. I would like to understand them and in particular, how security is maintained. We recently had a production issue where after some problem with a server which resulted in having to restart SQL Server, and shrink msdb, log-shipping started to fail authentication when trying to run alert jobs. Only after rebooting the server, and also the log-ship target server, and waiting 9 hours, did the authentication correct itself. I would like to know how it resolved itself and what took so long?
View 3 Replies View RelatedHello,
We have log-shipping set up between a source and 3 destination SS 2000 databases. Two of the destination servers actually perform their log restores across the network from the other secondary server. This allows us to only copy the files once from a remote location. All three servers stay caught up within 15 minutes of each other.
Recently, I added a fourth server to this that has SS 2005 SP2 (X64). I wrote a stored procedure that restores log backups from the same single location as the maintenance plan jobs. The problem that I'm experiencing is that this fourth server is not keeping up with the other three. It seems to take longer to restore the same log backups. The destination servers are all on the same domain. This fourth server was previously part of the same maintenance plan configuration as the others prior to rebuilding it for SS 2005 SP2 (X64). During that time, it stayed caught up with the other servers. There is another database on the new server that I am log-shipping to in the same manner and it stays caught up, though, for the most part, the log backups are smaller. There is a file on the fourth server with a ckp extension for the database in question that doesn't seem to exist for the other databases on this server and the other servers.
Any information on this behavior would be appreciated.
I have set up log shipping between two servers with a third serving as a monitoring server. Recently the monitoring for the eight databases that I am log shipping began to indicate that everything was failing. Upon further inventigation of the log_shipping_monitor_history_detail tables on the prinary and secondary everthing appears to working properly but I have been unable to resyncronize the monitoring. I have attempted to use the stored procedure sp_refresh_log_shipping_monitor to no avail, it does not appear to do anything with respect to the data in the dbo.log_shipping_primary_databases and log_shipping_monitor_primary tables on the primary server or the log_shipping_monitor_secondary and dbo.log_shipping_secondary_databases tables on the secondary. I have also manually updated the records in these tables in an attempt to syncronize but after the next sucessful backup, copy and restore this monitoring data is not updating. Does anyone have any ideas as to what I am doing wrong or how I might rectify this situation.
View 3 Replies View RelatedHi
Im planning to setup sqlserver 2005 log shipping between two servers.The size of the database is around 50GB and we are taking transaction log backup and shipping at 30mins interval.
Suppose if the backup job couldnt take the transaction log backup with in the specified interval ie 30mins,then how does the copy and restore job works. Will it give an error saying tht the transaction log could nt be copied and restored ???
How to deal with this kind of situations where the backup is taking more time than the threshold time limit and ur copy,restore fails. Is there a way to handle this kind of situation in logshipping Sqlserver 2005.
and how does it affect the Secondary database. ??
Please help me out !!
Thnkx in advance
Regards
Arvind L
I am getting the following error " The specified servername does not exist" when I run the Log Shipping procedure. There is only a Primary server running Win Server 2003 withe Service pack 2 and SQL Server 2005 with service pack 2 and one secondary server runnung Win Server 2003 R2 with service pack 2 and SQL Server 2005 with service pack 2. All permission setting look ok . Can anyone help
View 4 Replies View RelatedHello, I would like to know if anyone here has any information on how to change the default version of SQL Server 2005 Express which ships with Visual Studio 2005 to the new SQL 2005 Express SERVICE PACK 1?
I see a file under disc:vswcuSSESQLEXPR.exe I am wondering if changing that file with the new one from Microsoft Download Center will do it...
There's another file under that folder named sqlexpr32.exe I am wondering what it's for?
Thanks in advance.
Hi
I could not able to find Forums in regards to 'Log Shipping' thats why posting this question in here. Appriciate if someone can provide me answers depends on their experience.
Can we switch database recovery model when log shipping is turned on ?
We want to switch from Full Recovery to Bulk Logged Recovery to make sure Bulk Insert operations during the after hours load process will have some performance gain.
Is there any possibility of loosing data ?
Thanks
I have installed SQL Server 2005 and setup a cluster and log shipping. I decided to perform a planned failover and realized that there are no sp_change_primary_role and sp_change_secondary_role stored procedures. I checked on both the SQL Server 2005 installations and could not find them.
My question is :
"Is it safe to get these stored procedures from a SQL Server 2000 database and run them on the SQL Server 2005 database ??"
"Has anyone come across such missing stored procedures in SQL Server 2005 and know the reason why it is so (so that I can avoid it in the future if it due to a faulty installation) ?"
Cheers
NEVILLE GEORGE
Hello,
I would like to know if anyone has a recommended method for having backups to tape while running log shipping. For example, is it possible to copy the transaction log backups used for log shipping to tape and apply them to a Full Database Restore from a 3rd Party Backup tool such as Veritas?
My goal is to be able to do a point-in-time restore from tape and still be able to use SQL Server 2005 Log Shipping.
Thanks,
Erik
Afternoon,
I have a few Log Shipped DBs that are working great.
Currently they are set to fire off every 15 minutes 24/7.
My question is this ... I need to get FULL backups of the source DBs in order to restore them on certain Dev boxes.
If I were to execute the full backup on one of these Log Shipped DBs ... how would it affect the log shipping process?
Is there a special method to accomplish this?
As a side note, what would be some concerns/issues if in being able to create the FULL backups and not interupt log shipping, I were to create the backup using a 3rd party tool like Quest LiteSpeed?
I sure wish we were on Enterprise, then I could create a mirror and then snapshot off it to create my backups BUT ... that is not the case as we stand today.
Thanks
Hi,
I 'm sure I am missing something obvious, hopefully someone could point it out. After a failover log shipping, I want to fail back to my inital Primary server database; however, my database is marked as loading. How can I mark it as normal?
I did the failover as follow:
I did a failover log shipping from the 2 server Sv1 (Primary) and Sv2 (Secondary) by doing the following
1) Stop the primary database by using sp_change_primary_role (Sv1)
2) Change the 2nd server to primary server by running sp_change_secondary_role (Sv2)
3) Change the monitor role by running sp-change_monitor_role (Sv2)
4) Resolve the log ins - (Sv2)
5) Now I want to fail back - I copy the TRN files to Sv1 - use SQL Ent to restore the database at point in time. The task is done; however, the database is still mark as loading. I could not use sp_dboption.
I appreciate any suggestion.
Thanks in advance
I recently installed SQL 2005. During the setup, I didn't get the option that makes me add the licensing module I'm using. I don't want to be slapped in the wrist by microsoft. After setup, how can I check the licensing used?
James
Im about to upgrade all our SQL 2000 Servers to 2005
In your setups do you install the anlaysis services, reporting services on separate servers rather than all on the same server.
Currently we have separate servers for web IIS and was wondering if to install on three different servers
I am trying get a database setup in my new install of VS 2005. I have a project on one PC where I just have VS2005 installed and i am able create a website, go to the APP_DATA folder and add a database. On another PC I have VS 2005 installed and then I installed SQL server 2005. Now I fail to connect to ??? when I try and enter the sercuity page of webconfig or try to add a database when I open the APP_DATA folder. There have been many things done on this PC between the install of the two mentioned packages and trying this database creation. However, I feel that something related to the install of SQL Server 2005 after VS 2005 has done something unexpected. Or, I need to manage something between the SQL Express version that got loaded with VS 2005 and the subsequent install of SQL Server. I just don't know what to look for at this point.
View 1 Replies View RelatedI'm a Network Administrator that has to do everything from desktop to server, to routing, and DBA so I need a bit of advice. Stretched thin for time and knowledge in the SQL area and trying to do the best I can.
I currently have a MS SQL 2000 database that is 60GB in size for MS Dynamics 8.0 and one that is 2GB that I want to move to a new server.
I've setup and tested it and it all works, now I'm looking for some Best Practices information for best performance. Currently doing about 3,000 transactions a day.
Server is HP ML350-G5 2 Xeon Dual Core 2.0GHz CPUs w/16GB RAM w/external drive bays running 72GB 15K SAS drives with SMART ARRAY P800.
OS is Windows Server 2003 Enterprise w/SP2 - MS SQL 2005 Standard
I have the following drive configurations setup.
C:(RAID1+0)OS - SQL 2005
D:(RAID1+0)Dynamics Application Shared dictionary files for clients
G:(RAID0)BACKUPS (see note below about TEMPDB) I also have a 25GB swap file on this drive maybe better to put in on the D: volume if I put TEMPDB here
H:(RAID1+0)LOGS (2 user db logs and the tempdb log)
I:(RAID1+0)DATA (2 user db - [model, msdb, master]
Recently found that my G: drive (RAID0) only has space for 2 backups (poor space planning on my part) before I need to move the files. Normally I backup the DB with BackupExec 10.1d just fine in about 2 hours over the wire at night since no one is in the DB at night.
Was wondering if putting my TEMPDB there on (RAID0) would be advisable or not. In SQL 2005 it gets rebuilt each time SQL is restarted so it would seem that ensuring it's on a RAID1 or RAID1+0 might not be as necessary as say the DATA files.
Then if I really wanted to I could actually do backups on the I:DATA drive at night and then use TAPE to back that up, and use an automated script to move them off to offline storage once the TAPE backup is done.
For the [model, msdb, master] should they need to be on the I:DATA drive or just leave them on C:OS ? Not sure how much they're actually used.
Also doing some brief testing the Microsoft Dynamics was much slower on the new Server than it was on the original. Odd to me since the new Server is like a McLaren F1 racing a Ford Pinto. The old server is running a single P4 CPU and 6GB RAM
I've set MS SQL 2005 to use 12GB of RAM on the new server so as to leave 4GB for other Server tasks.
I ran the Maintenance Wizard and had it do checks and defrag and index rebuild etc... so not really sure why the speed would be noticeably slower. One thing I did notice is that once a screen query was ran then the next time it was a bit faster but overall I was expecting to see the screens fly by on this new hardware and SQL 2005 but it doesn't really do that.
I've read some of the white papers etc for tuning, but wow I just don't have unlimited hours to do all this analysis, there seem to be hundreds of pages to read on that type of stuff.
Thanks in advance for the advice.
Hello I have installed Visual Web Developer 2005 Express, as well as Visual studio 2005 Standard edtion. I installed SQL 2005 express edition after installing Visual Web developer 2005 Express Edition! at least I thought I did. I most recently tried to install the SP1 of SQL 2005 express edi... and I seem to have gotten a failure to install message with (sa) in the message(I remember it from the first install but it had gone away on 2nd attempt). I have a two part question (1 Does VWD 2005 Express Edition have SQL 2005 Express Edi... included within it can this be causing the failure and, (2 how can I resolve this problem.
Thank You,
DKB
OK we currently have a single SQL 2000 Server for our DW with a DR SQL 2000 Server. We are wanting to create a setup where we have a Failover Cluster of SQL 2005 here at the main office with a DR SQL 2005 system at our DR site. My question is... How would you all do the failover and stuff? How many servers would I need and what would be the job/role for each server. Some things to take note we are implimenting a SAN in our network and we are also implimenting a Virtual Server system on our network. To my understanding you do not really wish to run SQL Servers on a Virtual machine if possible. So I am already planning on making the SQL Servers Physical systems. We are also planning on putting the DB's on the SAN and have the SAN replicate all the data to DR. So... How would you all invision things to be setup? Is there any good documentation I can read about this type of setup. Thank you in advance for all the advice you can provide.
Thanks,
Billy S.
So, here's my problem..
I've been working on getting SQL 2k5 installed for a few days now. It's been the single most trying installation I've ever attempted. Absolutely riddled with problems.. I've had to do integrate SP2 and XP and reinstall my OS... I've literally lost 15-20 hours of my life to this.
So here's my newest problem.
I've new to the techie world so try and make sense of this. Thanks.
Error: Action "InvokeSqlSetupDllAction" threw an exception during execution.
Unable to load setup helper module : 87
Message displayed to user
Failed to load SqlSpars.dll
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_DSLPTP05_.NET Framework 2.0.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0008.cab" Error Code : 2
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_DSLPTP05_.NET Framework 2.0 LangPack.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0008.cab" Error Code : 2
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_DSLPTP05_.NET Framework Upgrade Advisor.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0008.cab" Error Code : 2
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_DSLPTP05_.NET Framework Upgrade Advisor LangPack.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0008.cab" Error Code : 2
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_DSLPTP05_.NET Framework Windows Installer.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0008.cab" Error Code : 2
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_DSLPTP05_.NET Framework Windows Installer LangPack.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0008.cab" Error Code : 2
Running: UploadDrWatsonLogAction at: 2006/4/29 16:4:46
Message pump returning: 87
Dears,
i have a problem when i setup workstation componant in sql 2005 it fail when the setup remove the backup file in the end of setup and give me this
if anyone no what id the problem solve it to me
thanks
... Dear All,
I am trying to install the professional edition of SQL Server 2005 on a new PC with xp pro. I have tried several times with several options but the installation is stalled with the error message that "The drop location is missing file(s) that allow setup to determine how a multi instance product should be installed. Setup cannot continue, please repair the drop and try again."
Does anyone know what the probelm is and how to fix this?
Thanks!
I'm trying to setup a SQL 2005 SP2 Mirror in between two mashines with no witness server.
I have successfully established the following:
1. Backup The Database on Principal Server: OK!
2. Copy the backup over to the mirror server: OK!
3. Restore the Database on Mirror Server: OK!
4. Establish Endpoint on Principal Server: Encyrption Disabled OK! TCP - PORT 5022
4.1 Test Script: Checks fine (values match)
SELECT e.name, e.protocol_desc, e.type_desc, e.role_desc, e.state_desc,
t.port, e.is_encryption_enabled, e.encryption_algorithm_desc,
e.connection_auth_desc
FROM sys.database_mirroring_endpoints e JOIN sys.tcp_endpoints t
ON e.endpoint_id = t.endpoint_id
5. Establish Endpoint on Mirror Server: Encyrption Disabled OK! TCP - PORT 5022
5.1 Test Script: Checks fine (values match) (same script as above)
6. Specify Principal server from Mirror server: OK! Connecting with IP
7. Specify Mirror server from Principal server: OK! Connecting with IP
8. View Mirror Information:
8.1 Test Script: Shows everything in NULL
SELECT mirroring_state_desc, mirroring_partner_name, mirroring_witness_name, mirroring_witness_state_desc, mirroring_role_desc, mirroring_safety_level_desc
FROM sys.database_mirroring
Mirror endpoints are still in red even though they initialized correctly.
Mirror monitor shows no mirrors are up.
SQL Logs shows: The Database Mirroring protocal transport is now listening for connections.
Any help would be appreciated.
I have downloaded SQL server 2005 dev edition from Microsoft download using MSDN licence. I selected SQL Server Studio, Integration Services, Reporting Services and Notification Services to install.
Native client, Backward Compatibility, Setup Support files, VSS writer, online help are getting install but MSXML, SQL Server Studio, Integration Services, Reporting Services and Notification Services are failed. Same setup is running fine in other system.
Error : SQLSetup0013_BTG356299_Core.log
----------------------
Microsoft SQL Server 2005 Setup beginning at Tue Jan 08 14:02:14 2008
Process ID : 2196
C:SoftMSDNSQL 2005 DevSQL Server x86Toolssetup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2008/0/8 14:2:14
Complete: LoadResourcesAction at: 2008/0/8 14:2:14, returned true
Running: ParseBootstrapOptionsAction at: 2008/0/8 14:2:14
Loaded DLL:C:SoftMSDNSQL 2005 DevSQL Server x86Toolsxmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2008/0/8 14:2:14, returned true
Running: ValidateWinNTAction at: 2008/0/8 14:2:14
Complete: ValidateWinNTAction at: 2008/0/8 14:2:14, returned true
Running: ValidateMinOSAction at: 2008/0/8 14:2:14
Complete: ValidateMinOSAction at: 2008/0/8 14:2:14, returned true
Running: PerformSCCAction at: 2008/0/8 14:2:14
Complete: PerformSCCAction at: 2008/0/8 14:2:14, returned true
Running: ActivateLoggingAction at: 2008/0/8 14:2:14
Complete: ActivateLoggingAction at: 2008/0/8 14:2:14, returned true
Running: DetectPatchedBootstrapAction at: 2008/0/8 14:2:14
Complete: DetectPatchedBootstrapAction at: 2008/0/8 14:2:14, returned true
Running: LaunchPatchedBootstrapAction at: 2008/0/8 14:2:14
Error: Action "LaunchPatchedBootstrapAction" threw an exception during execution. Error information reported during run:
"c:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe" finished and returned: 1602
Aborting queue processing as nested installer has completed
Message pump returning: 1602
----------------------
*******************************************
Setup Consistency Check Report for Machine: BTG356299
*******************************************
Article: WMI Service Requirement, Result: CheckPassed
Article: MSXML Requirement, Result: CheckPassed
Article: Operating System Minimum Level Requirement, Result: CheckPassed
Article: Operating System Service Pack Level Requirement, Result: CheckPassed
Article: SQL Compatibility With Operating System, Result: CheckPassed
Article: Minimum Hardware Requirement, Result: CheckPassed
Article: IIS Feature Requirement, Result: CheckPassed
Article: Pending Reboot Requirement, Result: CheckPassed
Article: Performance Monitor Counter Requirement, Result: CheckPassed
Article: Default Installation Path Permission Requirement, Result: CheckPassed
Article: Internet Explorer Requirement, Result: CheckPassed
Article: Check COM+ Catalogue, Result: CheckPassed
Article: ASP.Net Registration Requirement, Result: CheckPassed
Article: Minimum MDAC Version Requirement, Result: CheckPassed
Article: Edition Upgrade Check, Result: Warning
Description: There can be a product on higher SP level. Action: If you are attempting to upgrade an existing instance of Microsoft SQL Server to another Edition by installing the RTM version of the new Edition, you need to pass "SKUUPGRADE=1" to setup.exe on the command line.
<Func Name='PerformDetections'>
0
<EndFunc Name='PerformDetections' Return='0' GetLastError='0'>
<Func Name='DisplaySCCWizard'>
CSetupBootstrapWizard returned 1
<EndFunc Name='DisplaySCCWizard' Return='0' GetLastError='183'>
Loaded DLL:c:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlsval.dll Version:2005.90.3042.0
<EndFunc Name='DwLaunchMsiExec' Return='1602' GetLastError='0'>
Complete: InvokeSqlSetupDllAction at: 2008/0/8 14:4:23, returned false
Error: Action "InvokeSqlSetupDllAction" failed during execution.
Action "AnalyzeInstallStage" will be skipped due to the following restrictions:
Condition "Action: InvokeSqlSetupDllAction has finished and passed." returned false.
Action "PrepareForChainingStage" will be skipped due to the following restrictions:
Condition "Action: InvokeSqlSetupDllAction has finished and passed." returned false.
Action "SequenceChainingActionsStage" will be skipped due to the following restrictions:
Condition "Action: InvokeSqlSetupDllAction has finished and passed." returned false.
Action "InstallChainedPackagesStage" will be skipped due to the following restrictions:
Condition "Action: InvokeSqlSetupDllAction has finished and passed." returned false.
Error: Action "ExposeVistaClusteredResources" failed during execution. Error information reported during run:
Action: "ExposeVistaClusteredResources" will be marked as failed due to the following condition:
Condition "The Clustered SQL Server instance that hosts is installed." returned false.
Running: ReportChainingResults at: 2008/0/8 14:4:23
Error: Action "ReportChainingResults" threw an exception during execution.
DwLaunchMsiExec() returned : 1602
Error Code: 0x80070642 (1602)
Windows Error Text: User cancelled installation.
Source File Name: sqlchainingsqlchainingactions.cpp
Compiler Timestamp: Thu Nov 16 20:31:57 2006
Function Name: sqls::ReportChainingResults:erform
Source Line Number: 3416
Source File Name: datastorecachedpropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:27:59 2006
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "watsonFailedActionErrorCode" {"SetupStateScope", "", ""} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:28:01 2006
Function Name: SetupStateScope.watsonFailedActionErrorCode
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupStateScope"
Failed to create CAB file due to datastore exception
Source File Name: datastorecachedpropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:27:59 2006
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "watsonFailedActionErrorCode" {"SetupStateScope", "", ""} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:28:01 2006
Function Name: SetupStateScope.watsonFailedActionErrorCode
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupStateScope"
Message pump returning: 1602
----------------------
Please help,
I just recently installed SQL Server 2005. I have a question about "SQL Server Management Studio".
I want my machine to act as the db server, so I can learn the basics of SQL Server 2005. Once I open
"SQL Server Management Studio" and attempt to connect to a database engine, I get the following error
Cannot connect to database engine....
I don't see any services running in the windows services console, I used to
work with SQL Server v7 awhile back and I remember within the left frame of "SQL Server Management Studio"
window, in the Registered Servers frame that the "Database Engine" icon usually had a green right arrow in it
when it was running correctly. Right now I have this "Database Engine" icon but there is a white circle with
no right green arrow signifying that it is running....
Thanks in advance for your help,
Wes