We've got a problem with our server in that Windows has totally died - a routine upgrade appears to have gone wrong and the repair function of the Windows installer keeps getting stuck in a loop so I've given up on that front. What I was wondering is:
1. If I install a fresh copy of Windows 2003 R2 over the top of the existing install will that kill MSSQL Sever 2005 and/or Windows Sharepoint Services?
2. If so, is there a simple way to get them back?
3. If I install another copy of Windows on the D: drive is there a recommended way to move the MSSQL databases & Sharepoint to the newer install or a way of pointing the new install at the old databases?
I'm not an admin person (i'm a developer normally) so I haven't got a lot of background in this stuff so any tips, pointers or ideas are welcome. If this is covered somewhere on the MS site I'm happy to read but I'm just getting lost at the moment.
And, yes, I realise that backups are a good thing but the latest backups are not new enough for some items. The backup process has been adjusted accordingly.
I wrote a stored proc that essentially did the following: [truncate tables X, Y, Z]begin tran[lots of inserts to tables X, Y, Z]if @@error <> 0begin rollback tran return -1endcommit tran I'm not sure what happened, but the error message I received was: Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK TRANSACTION statement is missing. Previous count = 1, current count = 2. I was under the impression that if an error occurred, it would never make it to the 'commit tran'. However, I believe that it rolled back the transaction, and then tried to commit. Nonetheless, a deadlock occurred and the database went into recovery. We have traced the recovery process and it made it to Phase 3 of 3 2% and another deadlock occurred DURING THE RECOVERY. We have tried restarting the server (suggested by the trace), but it immediately goes into recovery again. It is VERY URGENT to resolve this TODAY. I would greatly appreciate any and all help. Thanks, Matt
I am writing up a general purpose document regarding Disaster Recovery and Backup and Restore, etc. I have a question that I've been unable to find any definitive answer on, and I was hoping that someone might have an answer.
Here is the scenario and what I have so far, and my question:
Scenario - A simple database, with one MDF and one LDF, each on it's own disk, with no mirroring or filegroups etc.
Disaster - the LOG disk fails.
To simulate the disaster, I shut down SQL Server, and delete the LDF manually.
When I restart SQL Server, the database is marked as suspect. As expected :)
So, now the recovery begins..... I've read that in this case there is no data loss, but I find that hard to believe. Can anyone confirm?
Anyway, how to restore the database to usable status? Here is what I've come up with so far:
1) Do a backup of "the tail of the log." This works even though there is no log. I have no idea why really, but I can't proceed otherwise.
2) Detach the database.
3) Reattach the database. This auto-creates a new log file (albeit not in the location I want, which makes for more work after).
At this point the database appears to be fine. I have not seen any lost data or problems, but of course I'm working on a test database, not with live users hitting it constantly. If the database were under heavy use, I expect that there might indeed be data lost?
Is this the recommended way to recover from a disaster of this type? Or, would it be better to just go back to your last good backups and forget about "up to the minute" recovery in this case? Or is there yet another means?
New user on these forums, so basically, hey, how are yas?
I have a bit of a situation, and have done a search - although not much info has turned up relating to my situation (maybe my search was just useless).
Anyways, basically, I run SQL Server 6.5 on NT4 server. The disks were striped - not RAIDED.
What happened was, the 4th disk died, and we replaced it with a new blank drive.
Now, I am left with two DAT files (log and data) for my database. I cannot remember how large these were created as it was many years ago.
I have no backups.
Reseting the status hasn't worked, also I have tried creating a new DB / Devices (in size similar to those reported in windows), and "moving" the devices to point to the original ones, but no luck: and thus was wondering if anybody had any hint / tips or ideas?
Cluster services gives the high availability needed - that is great.But I have never seen any discussion about what happens when a nodefails - what do you do to get everything back to the active-passivetandem.I imagine there is not much difference in terms of recovery procedurefor either active or passive node. So I'm just going to make up ascenario that we have encountered. The system hard drive (not theshared disk) on primary node fails. Cluster fails over to the passivenode. Following are the problems I have at hand:-After installing windows, I need to install driver and configure thepermission to access the SAN. There is no way I could do it since thesecondary node has exclusive access to the disks.-Imagine I got that working, is there anyway to install SQL so SQLwould know this server used to be the primary node and attach the DBand translog automatically-Finally, there is no proper way to apply SQL 2000 service pack 3a.Originally when the cluster was fully functional, the service pack wasapplied to active node and that automatically upgrades passive node.Now we have a machine without 3a and a machine with 3a alreadyinstalled. See any problem?Consider all of the above as this one big question: What is a properprocedure to restore a cluster when one of the node goes down? Whetherit's the active or passive node.
Assuming all windows servers belonging to the WSFC are on the same subnet, will the AG listener become a single failure point in system if all Application servers connect to the AG through the listener? If the answer is yes, what are the options to resolve this issue?
In case of hardware unrecoverable issue, I have two msdn articles which states different things.
First one claims you remove the node from mscs.
[URL]
Second one claims you should remove it using sql server installation and links to the first link which says you should do it from mscs:
[URL]
Then this third article invalidates the second article. "To remove a node from an existing SQL Server failover cluster, you must run SQL Server Setup on the node that is to be removed from the SQL Server failover cluster instance."
[URL]
It is a hardware faillure where the secondary node is inaccessible.
So what is the proper way to evict a node you cannot access due to a hardware failure?
note: I don't plan on adding back the failed nodes after removing it. i.e. I am interested in the removing part.
SQL 2012. I am working in understanding more the feature <AlwaysOn>. I have already worked with FCI (Failover Cluster Instance) and I would like to understand more about <AlwaysOn>.
Browsing internet/documentation I am getting more knowledge about <AlwaysOn> but a doubt persists:
1) Combination of FCI + AlwaysOn (2 SQL servers for FCI providing cluster instance: SQLClusterSQLReporting + 1 SQL server (at least) for <AlwaysOn>: SQLAOn/SQLReporting)
If the FCI instance is called SQLClusterSQLReporting, all the connections are mapped to this name.
But if the<AlwaysOn> feature is added to the system, in case of failure the name of <SQL Instance AlwaysOn> must be used therefore I am obliged to re-map all my connections to SQLAOn/SQLReporting.
QUESTION: IS it correct?
If yes, I do not understand the usefulness for the <AlwaysON> feature that lead to re-map all the connection.
In my opinion it should be a <MAIN> SQL Instance covering both <FCI> + <AlwaysOn>.
I have a windows 2012 cluster environment that consists of two SQL servers nodes with Quorum disk configured as witness.
Manual failover between nodes is working fine, however the sql instance virtual is not seeing the Quorum disk.
Moreover the Quorum disk has the same number as another cluster storage disk, is that considered a problem?
When I move the SQL instance from a node to anohter, should the Quorum Disk change ownership as well to that destination node ? if it is not changing ownership what would be the problem??
Hi,I have a peculiar problem (or maybe not). I have SQL clients installedon XP boxes. These XP boxes are a member of let us say "XYZ" domain.SQL Server is installed on one of the boxes having Windows 2000 Serverin the same network. The installation has been done on local domainaccount. Since SQl Server has been installed with Windowsauthentication, what happens if the XYZ domain fails. Will it bepossible for all clients to access the database present on SQL Serverin the Win 2K box. I think I have made myself clear upto some extent.Please throw light on how to accomplish the connectivity between SQLclients and server in case of domain failure.Regards,Vinodi
I have a Windows 2008 R2 Always on Cluster with 3 nodes (two in the primary site and one in the DR site).
Primary Site: -Primary Site Server1 -Primary Site Server2
DR Site 1 (to be decommed): -DR Site Server1
Our company is planning on decommissioning the DR site. But before we do this, we want to add a 4th site to the cluster. Migrate the data...and then decommission the original DR Site.
Is it possible to have this configuration:
Primary Site: -Primary Site Server1 -Primary Site Server2
DR Site 1 (to be decommed): -DR Site Server1
DR Site 2 (NEW DR Site): -DR Site Server1
IF this is possible, do I simply add the new DR site to the existing cluster (same steps as adding the first DR node to the cluster when the cluster was originally configured? or are there special steps?
I am using an unattended install script to install the database on the client machine. All the settings look correct. But my application cannot access the db -
Error: Cannot open database requested by the login.
Now when I install SQL Server Express manually, it works fine. I have the service running under local system and enabled user instances is true. I cannot figure out the problem(been working on it for 2 days).
Has anyone else experienced SQL Express resetting to Windows Authentication only instead of mixed mode for logins after a power failure. I only noticed it happen today as we had 2 power outages in the office and it happened both times. If anyone has seen this happen or knows of a fix please let me know.
We have see login failures for windows accounts. Below is the error message.
Description: In our env most logins are windows accounts. Initially we thought it is an UAC issue and we tried to launch the SSMS using "Run as Administrator". However, we are seeing login failures.
Enviroment: Microsoft SQL Server 2014 - 12.0.2402.0 (X64) RTM Enterprise Edition (HyperVisor)
Error Message in Error Log :
2015-08-10 22:36:45.290 Logon Error: 18456, Severity: 14, State: 11. 2015-08-10 22:36:45.290 Logon Login failed for user 'domainloginname'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: 10.xxx.xxx.xxx]
[code]....
We tried dropping this account and re-creating the windows account with same permissions but still result is same. It throws same error message. Login failure message !!!
I have an xp dev machine i use which has sql server 2005. I skipped installin sp1 on sql server and went to sp2 directly. I tried over and over again but getting following errors. Not sure how to fix it.
Product : Database Services (MSSQLSERVER) Product Version (Previous): 1399 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log Error Number : 29528 Error Description : MSP Error: 29528 The setup has encountered an unexpected error while Installing Local Groups. The error is: A member could not be added to or removed from the local group because the member does not exist.
---------------------------------------------------------------------------------- Product : Analysis Services (MSSQLSERVER) Product Version (Previous): 1399 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixOLAP9_Hotfix_KB921896_sqlrun_as.msp.log Error Number : 29528 Error Description : MSP Error: 29528 The setup has encountered an unexpected error while Installing Local Groups. The error is: A member could not be added to or removed from the local group because the member does not exist.
---------------------------------------------------------------------------------- Product : Reporting Services (MSSQLSERVER) Product Version (Previous): 1399 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRS9_Hotfix_KB921896_sqlrun_rs.msp.log Error Number : 29528 Error Description : MSP Error: 29528 The setup has encountered an unexpected error while Installing Local Groups. The error is: A member could not be added to or removed from the local group because the member does not exist.
After going into detailed log file i noticed this account its trying to use,
MSI (s) (A8!54) [17:13:45:891]: PROPERTY CHANGE: Adding SQLBROWSERACCOUNT property. Its value is 'PHXNT1ADMINISTRATOR'.
MSI (s) (A8!54) [17:13:45:907]: PROPERTY CHANGE: Adding AGTACCOUNT property. Its value is 'PHXNT1ADMINISTRATOR'. Restored account SQLBROWSERACCOUNT=PHXNT1ADMINISTRATOR MSI (s) (A8!54) [17:13:45:907]: PROPERTY CHANGE: Adding SQLACCOUNT property. Its value is 'NT AUTHORITYSYSTEM'. Restored account AGTACCOUNT=PHXNT1ADMINISTRATOR
MSI (s) (A8!84) [17:13:48:109]: PROPERTY CHANGE: Adding Rollback_sqlGroupMember.D20239D7_E87C_40C9_9837_E70B8D4882C2 property. Its value is '100Installing Local Groups50000SQLServer2005SQLBrowserUser$PHOENIXDEV2PHXNT1ADMINISTRATOR'.
MSI (s) (A8!84) [17:13:48:343]: PROPERTY CHANGE: Adding Do_sqlGroupMember.D20239D7_E87C_40C9_9837_E70B8D4882C2 property. Its value is '110Installing Local Groups50000SQLServer2005SQLBrowserUser$PHOENIXDEV2PHXNT1ADMINISTRATOR'.
my domain was upgraded from nt to 2003 long time ago from phxnt1 to phxad1 which i dont know why it still try's to use the old account. The old domain is still online would this cause this problem not sure.
I have a very confusing problem that I'm going to attempt to relay concisely:
I have a LAN on which I'm running an Intranet web site built in ASP.Net 2.0 and using SSRS / Sql Server 2005 on the same server.
The name of the box is "warehouse" or "warehouse.mydomain.us." When I ping "warehouse," I get a response from 137.86.166.8, as I should. Likewise, I get a response from 137.86.166.8 when I ping "warehouse.mydomain.us." If I do a "ping -a" on 137.86.166.8, it correctly resolves to "warehouse.mydomain.us." Based on the facts presented in this paragraph, I believe that my DNS is working as expected.
Using IE (6.0.2900.2180.xpsp_sp2_gdr.050301-1519) with "low" security settings, I navigate to http://warehouse.mydomain.us/lex/ (Lex is the name of the app) and it authenticates me to the index page (which calls the SSRS web service to get and display a list of available reports), except that I get the login prompt three times. If I hit F5 (refresh), I get three more login prompts and then I get a 401.1 error. From this point, no matter what I do, I can not see the index page again without closing and restarting IE.
I know that IE only passes credentials to certain sites, so I add my domain (http://warehouse.mydomain.us/) to the Local Intranet list ( Tools->Internet Options->Security->Local Intranet->Advanced) and then I can refresh and see my index page once, but I still get 3 login attempts and then the same thing happens -- I refresh and go through 3 logins and then get a 401.1.
If I now change my address bar to read http://137.86.166.8/lex, I get a single login and it works like a champ. This makes me think that there's a DNS problem, so I open up Mozilla Firefox and wouldn't you know it -- Firefox works like a champ all around -- one single sign-in, it keep credentials between Lex and SSRS, and it appears to use the DNS correctly. However, I can't use Firefox because I can't get any of the SSRS reports to look like they're supposed to in Mozilla-based browsers.
Argh.
I have set my IE securtiy settings to "Low." I have added the primary domain to the Local Intranet list and also to the Trusted Sites list (but you can't do both at the same time). I have even added the internal IP to my "hosts" file.
Does anyone know anything that might be a help to me in getting this figured out?
Other notes of interest:
My machine is an XP machine, but is not on the domain, but I do have a valid domain login that I use and it works in Firefox without problem.
I need to change the authentication mode from 'windows' to mixed, its a 4-node participating in always-on... Will this brake/impact alwayson in any way? I know I have to restart the sql instance.
SQL Server 2005 x64 Developer Edition Log output from the SP2 installation... ------------------------------------------------------------------------------------------------ Product : Database Services (MSSQLSERVER) Product Version (Previous): 2221 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log Error Number : 11032 Error Description : Unable to install Windows Installer MSP file ------------------------------------------------------------------------------------------------
The C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log file is a 5mb file that I can't make much sense out of...here are the first many lines of the file. I'll be glad to provide more information - just let me know what you need to know... Thanks, Dave
=== Verbose logging started: 8/15/2007 20:32:13 Build type: SHIP UNICODE 3.01.4000.4042 Calling process: e:47b31966cf7dcaa4e0fe0fa356ab34dahotfix.exe === MSI (c) (D4:9C) [20:32:13:508]: Resetting cached policy values MSI (c) (D4:9C) [20:32:13:508]: Machine policy value 'Debug' is 0 MSI (c) (D4:9C) [20:32:13:508]: ******* RunEngine: ******* Product: {F14F2E25-99AF-42A9-977C-F6D0352DC59F} ******* Action: ******* CommandLine: ********** MSI (c) (D4:9C) [20:32:13:508]: Client-side and UI is none or basic: Running entire install on the server. MSI (c) (D4:9C) [20:32:13:508]: Grabbed execution mutex. MSI (c) (D4:9C) [20:32:13:508]: Cloaking enabled. MSI (c) (D4:9C) [20:32:13:508]: Attempting to enable all disabled priveleges before calling Install on Server MSI (c) (D4:9C) [20:32:13:508]: Incrementing counter to disable shutdown. Counter after increment: 0 MSI (s) (9C:BC) [20:32:13:539]: Grabbed execution mutex. MSI (s) (9C:FC) [20:32:13:539]: Resetting cached policy values MSI (s) (9C:FC) [20:32:13:539]: Machine policy value 'Debug' is 0 MSI (s) (9C:FC) [20:32:13:539]: ******* RunEngine: ******* Product: {F14F2E25-99AF-42A9-977C-F6D0352DC59F} ******* Action: ******* CommandLine: ********** MSI (s) (9C:FC) [20:32:13:539]: Machine policy value 'DisableUserInstalls' is 0 MSI (s) (9C:FC) [20:32:13:539]: Adding MSIINSTANCEGUID to command line. MSI (s) (9C:FC) [20:32:13:539]: End dialog not enabled MSI (s) (9C:FC) [20:32:13:539]: Original package ==> C:WINDOWSInstaller1f00a5.msi MSI (s) (9C:FC) [20:32:13:539]: Package we're running from ==> C:WINDOWSInstaller1f00a5.msi MSI (s) (9C:FC) [20:32:13:586]: APPCOMPAT: looking for appcompat database entry with ProductCode '{F14F2E25-99AF-42A9-977C-F6D0352DC59F}'. MSI (s) (9C:FC) [20:32:13:586]: APPCOMPAT: no matching ProductCode found in database. MSI (s) (9C:FC) [20:32:13:586]: Detected that this product uses a multiple instance transform. MSI (s) (9C:FC) [20:32:13:586]: MSCOREE not loaded loading copy from system32 MSI (s) (9C:FC) [20:32:13:586]: Applying multiple instance transform 'qlRun01.mst'... MSI (s) (9C:FC) [20:32:13:586]: Looking for storage transform: SqlRun01.mst MSI (s) (9C:FC) [20:32:13:586]: Validating transform 'SqlRun01.mst' with validation bits 0x809 MSI (s) (9C:FC) [20:32:13:586]: Transform 'SqlRun01.mst' is valid. MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2205 2: 3: Patch MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2205 2: 3: PatchPackage MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: _Tables 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: _Columns 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: Media 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: File 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: TRANSFORM: 'PatchPackage' table is missing or empty. No pre-transform fixup necessary. MSI (s) (9C:FC) [20:32:13:586]: TRANSFORM: Applying regular transform to database. MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: _Tables 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: _Columns 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: _Validation 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: File 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: MsiFileHash 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: Signature 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: RegLocator 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: AppSearch 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: CompLocator 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: DrLocator 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: Binary 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: CustomAction 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: Directory 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: Registry 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: Condition 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: CreateFolder 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: _sqlObjectSecurity 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: Icon 3: -2147287038 MSI (s) (9C:FC) [20:32:13:586]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038 ...
We are planning to change all IPs of PRODUCTION Failover Cluster Setup. In my cluster setup ... we have 2 Physical Nodes with windows-2008, Roles are MSDTC and SQL-2008R2.
IP change for:
1. Both Nodes(Physical) 2. MSDTC 3. SQL Server 4. windows Cluster
So Almost... All IPs are going to change.
Im DBA here, I need to take care of SQL cluster and MSDTC. But I haven't performed this activity before.So I'm worrying about Impacts and consequences of this change. steps how should I perform this activity.
I'moving my asp application to a new hosting server.
So when i tried the setup locally with the live DB & application in my test machine... The DB access is denied when application tries to hit the DB.
DB is in seperate machine with SQL Server 2000 & application(ASP) is in Windows server 2003..... Kindly help me with your suggestions....on what went wrong?
We have a requirement to build SQL environment which will give us local high availability and disaster recovery to second site. We have two sites- Site A & Site B. We are planning to have two nodes at Site A and 2 nodes at Site B. All four nodes will be part of same Windows failover cluster. We will build two SQL Cluster, InstanceA will be clustered between the nodes at Site A Server and InstanceB will be clustered between the nodes at Site B, we will enable Always On Between the InstanceA and InstanceB and will be primary owner where data will be written on InstanceA and will be replicated to InstaceB. URL....Now we want we will have instanceC on the Site B and data will be writen from the application available on Site B, will be replicated to the instance on the Site A as replica.
Pages on a full recovery model database corrupted, need to ensure data loss is minimal for restore operation am thinking about restoring the latest full backup.
in the process of migrating a big db from server 1 to server 2, we had to roll back the change. I started with taking a full db backup and restoring it on server 2 with norecovery, and then a couple logs with norecovery, and then the last log with recovery.
Is there some way to continue this chain now, I mean to change the db to norecovery, or other way to restore logs.
I dont want to do a new full backup.
If I try to do a log restore now i get the message:
Msg 3117, Level 16, State 4, Line 1
The log or differential backup cannot be restored because no files are ready to rollforward.
We have 3 replica AG setup. 2 replicas are in sync/automatic failover, the other(DR Server, different subnet) in asynchronous/manual mode…All these replicas were on sql server 2012, Recently we upgraded DR server to 2014. Since then we have a problem, the AG databases in 2014 instance went into ‘Synchronizing/ in recovery’ state…The SQL server error log has message, the recovery couldn’t start for the database ‘XYZ’…We tried to create a new database and add it to AG , it works for fine for other two 2012 replicas, but on 2014 we see the same issue
We have an issue with a 3 node SQL 2012 Always on availability group. Normal operation is node 1 (primary replica) with node 2 and node 3 as secondary replicas.After some patching, SQL wasn't running on node 1 hence the AG flipped over to node 2. This went unnoticed for some time and the transaction log for one of the AG databases became full on node 2 and node 3. (I think this is because it couldn't commit the transactions on node 1 so couldn't truncate it's t-log?) The DB is using synchronous replication btw.So I started SQL on node 1 and flipped the AG back to node 1 (with a data loss warning but I accepted this).Now the issue is that on node 2 and 3, the DB in question is stuck in a "Reverting / In Recovery" State. I've tried various commands such as ALTER DATABASE SET ONLINE, RESTORE DATABASE WITH RECOVERY etc but these fail stating unable to obtain a lock on the DB.
The weird thing is that on node 1 the state of the DB is "synchronised".how to resolve this issue on node 2 and 3? I've left them overnight (in case they were rolling back transactions, the DB is fairly large) but nothing seems to have happened. remove the DB from the AG in node 2 and 3 and add it back in again, ie recreate the replication?
If you are doing a disaster recovery of an entire SQL 2005 cluster, can you just install SQL server and restore the system database to get the configuration?
I am using ODBC to connect SQL Server 2000 + SP4 server runnig on Windows 2003 standard edition Server +SP1. But, sporadically my application server connectivity to DB fails and i receive the following error messages
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite (WrapperWrite()). [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation.) In D:de.cpp 702 Apr 12 2006 20:34:47 [Microsoft][ODBC SQL Server Driver]Communication link failure) In D:de.cpp 702 Apr 12 2006 20:34:47 20071017 08:23:10 TID (00000ff0) Sev (3) Err (0) Msg (Read failure. General SQL error.
Strange thing is that i receive this error only sporadically, Please Please advice !
I am attempting to write a Windows service that watches a database for uploaded files to import. When a new file is found, the corresponding SSIS package is run from the file system with variables passed through. I started development as a Windows app and copied the functionality to a service.
The app runs fine. The service does not. I get a "Failure" each time a package is executed. Everything is identical behind the scenes with the obvious exceptions that OnStart and OnStop handlers are buttons in the app. I added a script task at the beginning of one of the SSIS packages to notify me that it is even running at all. It doesn't even hit that initial task.
Again, the app will run all packages just fine. The data is imported and the results return as "Success."
The following is the code executing the package. Any help is appreciated. I've been banging my head on this one for a few days now. (Is there a tag to format a code sample?)
Dim pkgLocation As String Dim pkg As New Package Dim app As New Application Dim pkgResults As DTSExecResult
