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'm trying to setup database mirroring between 3 servers and the details are as follows:
1. All 3 machines reside in the same domain.
2. Server1 consists of SQL 2005 Ent Edition without SSAS, Server 2 consists of SQL 2005 Ent Ed without SSAS & SSRS, Server 3 consists of SQL 2005 Express Ed.
3. All the 3 machines are having their individual service domain accounts.
4. Server 1 consists of 5 databases which needs to be mirrored to Server 2. I took full backups and tlog backups and restored the full backups in NO Recovery mode on Server 2 and then applied the tlog backups to sync them with Server 1.
5. I created the logins on Server 1 (Server 2 & 3), Server 2 (Server 1 & 3) and Server 3 (Server 1 & 2) and gave "sa" permissions respectively.
6. I kept the first database on Server 1 to full recovery mode, created an endpoint with the default port and granted connection to Server 2 & 3 logins.
7. I created an endpoint on Server 2 with the default port number and granted connection to Server 1 & 3 logins.
8. I created an endpoint on Server 3 with the default port number and granted connection to Server 1 & 2 logins.
9. On Server 2 I'm executing this statement
ALTER DATABASE <dbname>
SET PARTNER = 'TCP://<Server Network Address of Server 1>:<Port No>'
10. On Server 1 I'm executing this statement
ALTER DATABASE <dbname>
SET PARTNER = 'TCP://<Server Network Address of Server 2>:<Port No>'
ALTER DATABASE <dbname>
SET WITNESS = 'TCP://<Server Network Address of Server 3>:<Port No>'
On Step 9 & 10, I'm getting an error message "Msg 1416, Severity 16, State 2 Database <dbname> is not configured for mirroring" in the query window but when I see the error logs individually on Server 1 & 2 I'm seeing "Error: 1443, Severity: 16, State: 2. Database mirroring has been terminated for database 'dbname'. This is an informational message only. No user action is required."
I would appreciate if any one can look into the problem I'm facing. I've googled and could not come up with a solution.
We are having problems getting the two databases to connect with each other for mirroring. We have the following setup:
- Doing Principal and Mirror (no witness)
- Using Management Studio
- Both servers are SQL Server 2005 SP1 Standard Edition
- Same domain account, same user id
- We can telnet to both and connect to both from Stuio.
We were originally getting error 1418, but now we're getting:
"Neither the partner nor the witness server instance for database "tmsng" is available. Reissue the command when at least one of the instances becomes available. (Microsoft SQL Server, Error: 1431)"
2006-11-06 13:01:59.62 spid24s Database mirroring has been terminated for database 'tmsng'. This is an informational message only. No user action is required.
2006-11-06 13:03:32.98 spid17s Database mirroring connection error 4 'An error occurred while receiving data: '64(The specified network name is no longer available.)'.' for 'TCP://MWSM3D02:5022'.
2006-11-06 13:53:18.14 spid73 The Database Mirroring protocol transport has stopped listening for connections.
2006-11-06 13:53:20.15 spid73 Server is listening on [ 'any' <ipv4> 5022].
2006-11-06 13:53:20.15 spid73 The Database Mirroring protocol transport is now listening for connections.
2006-11-06 13:53:29.79 spid73 The Database Mirroring protocol transport has stopped listening for connections.
2006-11-06 13:53:31.79 spid73 Server is listening on [ 'any' <ipv4> 5022].
2006-11-06 13:53:31.79 spid73 The Database Mirroring protocol transport is now listening for connections.
2006-11-06 14:21:43.48 spid24s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '')
2006-11-06 14:47:38.79 spid22s Database mirroring has been terminated for database 'tmsng'. This is an informational message only. No user action is required.
2006-11-06 14:49:23.06 spid22s Database mirroring connection error 4 'An error occurred while receiving data: '64(The specified network name is no longer available.)'.' for 'TCP://MWSM3D02:5022'.
We have a database with AlwaysOn enabled, where the database is getting mirrored using AlwaysOn to a secondary node in a two node cluster. Now we want to set up a DR site for that database in a different data center.
So trying to analyse what technologies. We can use for setting up the DR for that database. Can we use mirroring / replication or what's the best way of setting up DR on that database.
I have a 2 node cluster having 4 cores each wherein having 3 instances of SQL 2008 R2 enterprise comprising of 60 databases, 20 on each instance. I need to setup mirroring for each of the databases to a secondary server having 4 cores and 3 instances.
What i understand is that in this case the mirror server will be providing max of 512 worker threads and the 60 mirror databases would consume 240 threads.
What all needs to be checked for looking into the feasibility of going ahead with a async mirror setup as mentioned above.
I have checked my Production databases, both are went to Disconnected state, both are unable to connect to the application, i checked all the services and its working fine. and restarted the end points on Principal and Mirror, still issue not solved, after restart the witness server End point both the databases are working fine.
I am using SQl Server 2012 Database Mirroring with around 40 gb as mdf and 1 gb as ldf. Now my ldf size increased . How to reduce ldf size while mirror enabled with mirror server and witness server. Can shrink the ldf with mirror enables.
please see my post in the previous thread; http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2606008&SiteID=17&mode=1 We are making our final decission of using either transaction log replicant or a database mirror replicant and which solution would provide the biggest ease of provisioning as well as the fastest turn around in recovery.
"Good Morning Team,
I have a client whom has a 2 node SQL 2005 cluster with over 100 databases, their schema design is that they create a new database for every customer that signs to their services.
The problem I am encountering is that for every new database created in the cluster we like to setup a SQL2005 mirror replicant at a remote site for disaster recovery should the cluster ever fail.
i'm looking at the SQL professionals to help me with 2 questions.
#1 Upon creation of a new database in the cluster is there an easily scripted method that could be used to automatically create the mirror replicant, what about if not being aware of the new databases having been created? since we do not know when the customer creates databases or perhaps a SQL job that could be done based on new databases created that would automatically script the procedure of a database mirror.
#2 understanding the procedures required in a mirror replicant from a cluster primary involving, database backup, database restore to mirror replicant, transaction log backup and then transaction log restore with both points of the restore leaving the mirror replicant in NO RECOVERY mode and lastly creating the connection end points.
has anyone encountered such a situation with a database cluster with a mirror replicant consisting of such a wide span of individual smaller databases and would anyone have suggestions on how to make this highly available with a mirror replicant?
I have SQL 2005 mmirroring sucessfully working in an ASP.NET 2.0 web application. I also have session state being maintained in SQL Server using the built-in functionality in ASP.NET. The problem is, even with "allowCustomSqlDatabase=True" and specifying a failover partner in the DSN, it appears that ASP.NET does not work with the failover partner. It always tries to get the session info from the "data source" server specified in the DSN.
Is there a way to get the session state to fail over to the mirrored server without writing a custom session state provider?
I have a SQL Server 2005 DB server (SRV1) and a mirror DB server (SRV2) without witness server. I saw that there is a "Failover" button on Mirror window of SRV1. When click it servers changes roles.
My question is that: If my mirrored DB server crashs and I can not open windows or if I lost all data on SRV1, how can I failover from only mirror DB (SRV2)?
I hope this is in the right forum, I'm new to MSDN. I'm also not an expert in SQL, so please bear with me as I was unable to find an answer by searching the archives.
We have a single SQL 2005 Standard installation with 30 user CALs on a Server2003R2 box. We have another Server 2003 box in a remote but connected location that we previously used for backup replication. What we'd like to do is use some of the replication features in SQL 2005 to replicate the data over every night to the other box, onto which we would install another copy of SQL 2005. This would not be a server accessed by clients, but simply a "live backup", that in the event of a catastrophic failure, could be manually set up to operate as a SQL server in place of the failed primary server. I don't need any kind of automatic "failover", just the ability to replicate the data over to the other system so I have two SQL Servers that synchronize from one to the other overnight.
I was told that I wouldn't need to buy the user CALs again, that the 30 user cals would translate over if the primary server fails and has to be replaced by the cloned server. But what do I buy for the SQL server itself? A boxed version is a bit pricy and comes with 5 CALs which apparently I wouldn't need. Then I noticed that on softwaremedia.com the open license version, which can be bought a la carte, lists a requirement of buying at least 5 cals or a processor license. What exactly do I need to do this, and how can I get it for the least amount of further spending?
I've tried to replicated exactly what it says in the online documentation. At the end of the post are the SQL statements issued.
1. Enable encrypted outbound connections on the primary server 2. Enable encrypted outbound connections on the mirror server 3. Enable encrypted outbound connections on the witness server 4. Enable encrypted inbound connections on the primary server 5. Enable encrypted inbound connections on the mirror server 6. Enable encrypted inbound connections on the witness server 7. Set mirror''s partner to the primary 8. Set primary''s partner the mirror 9. Set principal€™s witness. Every step run''s normally,but why can''t auto failover.
I used the following Script:
/* -------- 1. ENABLE OUTBOUND CONNECTIONS ON THE PRIMARY -------- */ use master; go DROP USER PrincipalLogin1 DROP LOGIN PrincipalLogin1 DROP USER PrincipalLogin2 DROP LOGIN PrincipalLogin2 GO
Create login PrincipalLogin1 with password='PrincipalLogin' go Create user PrincipalLogin1 from login PrincipalLogin1 go
Grant connect on endpoint::Principal_Endpoint_Mirroring to PrincipalLogin1 go ---stop
create certificate MirrorCertForPartnerPub authorization PrincipalLogin1 from file = 'd:BackupCertMirrorCertForPartner.cer'; go
Create login PrincipalLogin2 with password='PrincipalLogin' go Create user PrincipalLogin2 from login PrincipalLogin2 go
Grant connect on endpoint::Principal_Endpoint_Mirroring to PrincipalLogin2 go create certificate WintnessCertForPartnerPub authorization PrincipalLogin2 from file ='D:BackupCertCertForDBRole.cer' GO
ALTER DATABASE Mirrortest SET PARTNER = 'TCP://10.1.40.158:5022' GO
ALTER DATABASE Mirrortest SET witness = 'TCP://10.10.11.30:7000' GO
select * from sys.certificates
/* -------- 2. ENABLE OUTBOUND CONNECTIONS ON THE MIRROR -------- */ --On Mirror --Remove the database --Connect to either partner. --Issue the following Transact-SQL statement:
ALTER DATABASE Mirrortest SET PARTNER OFF
--Optionally, you can recover the former mirror database. On the server instance that was the mirror server, enter:
--RESTORE DATABASE Mirrortest WITH RECOVERY;
RESTORE DATABASE [Mirrortest] FROM DISK = N'D:BackupCertMirrortest.bak' WITH FILE = 1, NORECOVERY, NOUNLOAD, REPLACE, STATS = 10 GO select * from sys.endpoints
drop endpoint Mirror_Endpoint_Mirroring
select * from sys.certificates
Create certificate MirrorCertForPartner with subject ='this is the certificate for mirror', start_date='06/25/2006'
backup certificate MirrorCertForPartner to file='d:ackupcertMirrorCertForPartner.cer'
CREATE ENDPOINT Mirror_Endpoint_Mirroring STATE=STARTED AS TCP (LISTENER_PORT=5022) FOR DATABASE_MIRRORING ( Authentication=Certificate MirrorCertForPartner ,ROLE=ALL) GO
/* -------- 3. ENABLE OUTBOUND CONNECTIONS ON THE WINTESS -------- */
--On Witness
USE [master] GO
select * from sys.certificates
drop certificate CertForDBRole GO
create master key encryption by password='asdf'
Create certificate CertForDBRole with subject='this is a certificate for pricipal role', start_date='06/25/2006'
backup certificate CertForDBrole to file='c:CertForDBRole.cer'
select * from sys.endpoints
drop endpoint Witness_Endpoint_Mirroring
CREATE ENDPOINT Witness_Endpoint_Mirroring STATE=STARTED AS TCP (LISTENER_PORT=7000) FOR DATABASE_MIRRORING ( Authentication=Certificate CertForDBRole ,ROLE=ALL) GO
/* -------- 4. ENABLE INBOUND CONNECTIONS ON THE PRIMARY -------- */ use master; go DROP USER PrincipalLogin1 DROP LOGIN PrincipalLogin1 DROP USER PrincipalLogin2 DROP LOGIN PrincipalLogin2 GO
Create login PrincipalLogin1 with password='PrincipalLogin' go Create user PrincipalLogin1 from login PrincipalLogin1 go
Grant connect on endpoint::Principal_Endpoint_Mirroring to PrincipalLogin1 go ---stop
create certificate MirrorCertForPartnerPub authorization PrincipalLogin1 from file = 'd:BackupCertMirrorCertForPartner.cer'; go
Create login PrincipalLogin2 with password='PrincipalLogin' go Create user PrincipalLogin2 from login PrincipalLogin2 go
Grant connect on endpoint::Principal_Endpoint_Mirroring to PrincipalLogin2 go create certificate WintnessCertForPartnerPub authorization PrincipalLogin2 from file ='D:BackupCertCertForDBRole.cer' GO
ALTER DATABASE Mirrortest SET PARTNER = 'TCP://10.1.40.158:5022' GO
ALTER DATABASE Mirrortest SET witness = 'TCP://10.10.11.30:7000' GO
select * from sys.certificates
/* -------- 5. ENABLE INBOUND CONNECTIONS ON THE MIRROR -------- */ use master; go DROP USER MirrorLogin1 DROP LOGIN MirrorLogin1 DROP USER MirrorLogin2 DROP LOGIN MirrorLogin2 GO
Create login MirrorLogin1 with password='MirrorLogin' go Create user MirrorLogin1 from login MirrorLogin1 go
Grant connect on endpoint::Mirror_Endpoint_Mirroring to MirrorLogin1 go
--stop create certificate PrincipalCertForPartnerPub authorization MirrorLogin1 from file = 'd:BackupCertPrincipalCertForPartner.cer'; go
Create login MirrorLogin2 with password='MirrorLogin' go Create user MirrorLogin2 from login MirrorLogin2 go create certificate WitnessCertForPartnerPub authorization MirrorLogin2 from file ='D:BackupCertCertForDBRole.cer' GO
Grant connect on endpoint::Mirror_Endpoint_Mirroring to MirrorLogin2 go
ALTER DATABASE Mirrortest SET PARTNER = 'TCP://10.10.116.42:5022' GO
ALTER DATABASE Mirrortest SET WITNESS = 'TCP://w7mis02:5024' GO
/* -------- 6. ENABLE INBOUND CONNECTIONS ON THE WITNESS -------- */
use master; go DROP USER WitnessLogin1 drop login WitnessLogin1 DROP USER WitnessLogin2 drop login WitnessLogin2
Create login WitnessLogin1 with password='WitnessLogi*n@' go create user WitnessLogin1 from login WitnessLogin1 go
create certificate PrincipalCertForPartnerPub authorization WitnessLogin1 from file = 'c:ackupcertPrincipalCertForPartner.cer'; go --*************************************** Create login WitnessLogin2 with password='WitnessLogi*n@' go create user WitnessLogin2 from login WitnessLogin2 go
create certificate MirrorCertForPartnerPub authorization WitnessLogin2 from file = 'c:ackupcertMirrorCertForPartner.cer'; go
Grant connect on endpoint::Witness_Endpoint_Mirroring to WitnessLogin1 go Grant connect on endpoint::Witness_Endpoint_Mirroring to WitnessLogin2 go
After adding the Witness Server to the Mirror session, the Witness Connection state between the Mirror and Witness Connection is Disconnected and the state between Principal and Witness Connection is Connected.
The procedures defined in Books Online was used to setup Database Mirroring...when the Witness server was added to the Mirror session, only the alter database T-SQL statement was executed on the Principal server.
ALTER DATABASE <db_name> SET WITNESS = 'TCP://<servername>:<port>'
After executing the above statement, a few seconds later the state between Principal and Witness Connection changed to Connected and the state between Mirror and Witness Connection remains Disconnected.
The Mirror session is not using Certificates, every server is on the same domain, using the same domain login account, and all servers have SP2 installed running Enterprise Edition.
Any idea's why the state between Mirror and Witness Connection remains Disconnected?
I was trying to test mirroring and now would like to delete the mirror database but it says I need to remove database mirroring first. I deleted the endpoint and cannot figure out how to remove the mirroring. Can someone please help.
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?
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?
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?
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?
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.
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.
I'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.
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.
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.
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
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?
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 ----------------------
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....
I am trying to create a new transactional publication between two Sql 2005 servers. This is my first attempt with replication in 2005, so i have obviously missed something in the setup. Each time i try to create the new puplication i receive the following error.
Any help is greatly appreciated
TITLE: New Publication Wizard ------------------------------
SQL Server could not configure 'DTS-70P40LT2Y0A' as a Distributor.
Hi Room, I am new to SQL reporting 2005 and wanted to setup SQL 2005 reporting on stand along server 2003 box. SQL Server 2005 server and reporting services were installed. Can anyone provide me some hints how to setup the sql 2005 reports.? Any articles or links.? Thanks for the help. TJ
Below is the error message receive when installing SQL 2005 (x64) enterprise edition.
Failed to install and configure assemblies c:Program Files (x86)Microsoft SQL Server90NotificationServices9.0.242Binmicrosoft.sqlserver.notificationservices.dll in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501 Error description: The transaction has aborted
Has someone seen this before? Any pointer is appreciated. Thanks.
