I have windows server 2003 service pack 1 and sql server 2005 service
pack 1 - 64 bit. Sometimes it happens in the middle of the night. Sometimes it's in the middle of the day and sometimes it's multiple times in the same day. Usually the server fails over.
We are planning to upgrade the SQL Server in our production environment from SQL Server 2000 to SQL Server 2005. This is a 4 Node cluster environment with 3 Databases on 3 Virtual instances. The main requirement is to achieve this with no/minimal downtime.
Could you please suggest or direct me to any documentation for the best practices used to upgrade such an environment?
We're upgrading a SQL Server 2000 cluster (Active/Passive) running on Windows 2000 Server to a SQL Server 2005 Cluster running on Windows Server 2003. We can't purchase new hardware and we have no spare hardware. We also need to move from Windows 2000 Server to Windows 2003 Server at the same time. We want to keep downtime to a bare minimum.
What we were thinking was the following steps... Anyone try this?
1. Break the link between the servers.
2. Install a fresh copy of windows 2003 server on one side along with SQL Server 2005. While this step is running, the active node would still be live on Windows 2000 Server and SQL Server 2000 serving our customers.
3. Restore a copy of a backup from the active production side to the node we're upgrading and at that point we would bring the active node down, switching the active node to be the newly upgraded server.
4. As a final step, the old active node would now have the link to it broken, we would install a fresh copy of windows 2003 server on it and sql server 2005. At this point we would bring it back into the cluster and the cluster would be complete again.
Need your help and guidence for doing upgrading SQL Server 2000 Cluster to SQL Server 2005 Cluster.
Let me explain my current environment.
1. Currently SQL Server 2000 Cluster environment is running on Windows 2000 Server we need to upgrade this to SQL Server 2005 on Windows 2003 Server. >>> Production environment.
My Plans:
1. On Testing Environment Install SQL Server 2000 cluster on Windows 2003 Server and do a restore of databases from the produciton environment.
2. Upgrade In-Place from SQL Server 2000 Cluster to SQL Server 2005 Cluster.
My doubts
1. Can i install SQL Server 2000 Cluster on Windows 2003 Server. Is it possible or not.
I am trying to install SQL 2005 in a 2-node virtual Windows 2003 cluster. I set the cluster up through Virtual Server 2005 with 2 virtual nodes and one virtual domain. The nodes can connect to each other as well as the physical machine. When I try to install a fresh copy of SQL 2005 on my cluster, I get an error every time. The error stops the installation while checking system configuration after installing prerequisites. The log file entry is as follows:
******************************************* Setup Consistency Check Report for Machine: --SERVERNAME-- ******************************************* 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: Warning Description: IIS is not installed, therefore Report Server feature will be disabled Action: Install IIS in order for Report Server feature to be enabled 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 <Func Name='PerformDetections'> 1 Loaded DLL:C:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlsval.dll Version:2005.90.1399.0 Error: Action "InvokeSqlSetupDllAction" threw an exception during execution. Error information reported during run: Source File Name: datastorecachedpropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: CachedPropertyCollection::findProperty Source Line Number: 130 ---------------------------------------------------------- Failed to find property "ComputerList" {"SqlComputers", "", ""} in cache Source File Name: datastoreclusterinfocollector.cpp Compiler Timestamp: Fri Sep 16 13:20:12 2005 Function Name: ClusterInfoCollector::collectClusterVSInfo Source Line Number: 883 ---------------------------------------------------------- Failed to detect VS info due to datastore exception. Source File Name: datastoreclustergroupsproperties.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: ClusterGroupScope.SharedDisks Source Line Number: 56 ---------------------------------------------------------- Failed to find a cluster group that owned shared disk: J: WinException : 2 Error Code: 0x80070002 (2) Windows Error Text: The system cannot find the file specified. Source File Name: datastoreclustergroupsproperties.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: ClusterGroupScope.SharedDisks Source Line Number: 56
My environment is a 64 bit Windows Server 2012 Standard edition that is running SQL Server 2012 SP1 Standard Edition (64 bit) which has an Active Passive Cluster set up and I unfortunately had no involvement in this cluster build. The person who did is no longer with the company and is not responsive to questions.
This morning this following errors popped up:
Event ID: 1230 - Cluster resource 'Databases' (resource type 'Physical Disk', DLL 'clusres.dll') did not respond to a request in a timely fashion. Cluster health detection will attempt to automatically recover by terminating the Resource Hosting Subsystem (RHS) process running this resource. This may affect other resources hosted in the same RHS process. The resources will then be restarted.
The suspect resource 'Databases' will be marked to run in an isolated RHS process to avoid impacting multiple resources in the event that this resource failure occurs again. Please ensure services, applications, or underlying infrastructure (such as storage or networking) associated with the suspect resource is functioning properly.
Event ID: 1146 - The cluster Resource Hosting Subsystem (RHS) stopped unexpectedly. An attempt will be made to restart it. This is usually associated with recovery of a crashed or deadlocked resource. Please determine which resource and resource DLL is causing the issue and verify it is functioning properly.
When I saw these errors, I brought the "Databases", "Logs", and "Quorom" disks back online and all was well. I then proceeded to check Application and System Logs noticing there where some VMWare/SAN errors that caused the CPU spike resulting in the Cluster errors.
Regarding the questions, why didn't a failover occur and What can I do to mitigate this process are now what I am focusing on. Researching the above errors, I discovered that you could a policy based what happens in a situation like occurred this morning. You can set policies at the Role level, "Server" level, and at the disk level.
The Role Policy seems to be a little less involved, screenshot RoleProperties.png show these. I assume these are defaults. The server name properties are set to the following screenshot, Servername_Properties_Policy.png. This seems to be correct to me, but there is where I am lacking. I think this means that if it fails at this level all associated resources, disks, etc will failover to node 2.Now where I think the issue is, the third screenshot, Database_Properties_Policy.png. There is no policy set to for situation where a disk resource fails. Which I believe is what happened this morning. Some questions:
1. Do I need to set this similar to what is in the ServerName screenshot? 2. What happens if I check the box for "If restart is unsuccessful, fail over all resources in the role"? Will this only fail over this one disk? If so, it doesn't seem like that would be ideal. Would it fail over at the Role level and move over all associated resources?
I am also not sure what time limits I should set for Period restarts, maximum restarts, delay between restarts, etc...
I'm experiencing some frustration with my active/passive SQL cluster not running my .DTSX packages. I am hoping someone can shed some light on what I need to do.
I've created some .DTSX packages with the SQL Server Business Intel Dev Studio. I initially built & tested these packages in a non-SQL cluster environment without any problems. I'm now re-creating them to work on our SQL cluster. If I run the package through the Dev Studio it works great.
The packages basically grab .txt files from one of the shared drives (which is a resource of the sql cluster group) and imports the data into the one of the databases. The database does not have any special settings (right-click -> new database... -> enter name -> click ok).
I've setup a SQL Server Agent Job with 1 step with the following properties. Step name: I Offices Type: SQL Server Integration Services Package Run as: SQL Agent Service Account Package source: File system Package: G:ImportRAGFLOffices.dtsx
When I run the SQL Server Agent Job through MSSQL Server Management Studio (right-click -> start job) I get an error on "Execute job 'RAGFL TestJob'".
These are the 2 messages that show up when I view the history of the SQL Server Agent job.
*********************************************************************************************** Date 9/25/2007 1:16:13 PM Log Job History (RAGFL TestJob)
Step ID 0 Server BADBOYS Job Name RAGFL TestJob Step Name (Job outcome) Duration 00:00:01 Sql Severity 0 Sql Message ID 0 Operator Emailed Operator Net sent Operator Paged Retries Attempted 0
Message The job failed. The Job was invoked by User sa. The last step to run was step 1 (I Offices). ***********************************************************************************************
*********************************************************************************************** Date 9/25/2007 1:16:13 PM Log Job History (RAGFL TestJob)
Step ID 1 Server BADBOYS Job Name RAGFL TestJob Step Name I Offices Duration 00:00:01 Sql Severity 0 Sql Message ID 0 Operator Emailed Operator Net sent Operator Paged Retries Attempted 0
Message Executed as user: THEISLANDAdministrator. The package execution failed. The step failed. ***********************************************************************************************
I am in the process of moving databases from a SQL 2005 Standard version to a 2-node 2014 cluster.All of my 2005 databases back up successfully.They all restore without issue except for one database that has a full text catalog. I get this message
Msg 7610, Level 16, State 1, Line 2 Access is denied to "fileStoragedataMSSQLSERVERFullTextCatalog", or the path is invalid. Msg 3156, Level 16, State 50, Line 2 File 'sysft_FTCatalog' cannot be restored to 'fileStoragedataMSSQLSERVERFullTextCatalog'. Use WITH MOVE to identify a valid location for the file. Msg 3119, Level 16, State 1, Line 2 Problems were identified while planning for the RESTORE statement. Previous messages provide details. Msg 3013, Level 16, State 1, Line 2 RESTORE DATABASE is terminating abnormally.
[code]....
I went as far as giving the folder full access to everyone temporarily and received the same error.
I'm attempting to use RDA to synchronize a pocket pc emulator with SQL Server 2005 database by following tutorial http://msdn2.microsoft.com/en-us/library/aa454892.aspx, which uses AdvWorksMobile database that comes with SQL Server 2005.
When get to testing of "To test application features " ( step 4 of the merge replication setup lab ), I am receiving SQLCe Exception errors.
ORIGINALLY, I was able to deploy an application and view the local database on the emulator, but once I clicked "InitSinc" button, I received an error.
"Failure to connect to SQL Server with provided connection information. SQL Server does not" exist, access is denied because the SQL user is not a valid user on the SQL Server, or the password is incorrect. Found this error listed in Server Agent Errors log http://technet.microsoft.com/en-us/library/ms172357.aspx, but it wasn't very helpful since it doesn't provide any suggestions on fixing the problems.
I am brand new to SQL CE Server , mobile programming and .NET framework in general so please bare with me
All the connections / security settings, etc that were set up were taken from a tutorial so I am not sure what SQLCeServer is complaining about. Reading up on the error on the web didn't help, it all pointed to making sure that the snapshot folder had correct permissions set up. I verified that MACHINENAMEUISR_MACHINENAME guest user had Read rights to the database so I don't think that piece is the problem. Otherwise ,Merge publication has been setup in Microsoft SQL Server Management Studio by following the tutorial.
I am trying to run this sync on my home pc so there should be no issues with any user permissions
I have IIS installed
I did NOT have SQL Server Agent running in management studio at this time
I am trying to run this tutorial on an XP machine, which is my regular home PC so I dont think there are any special networking settings to consider
I am able to hit http://localhost/AdvWorksMobile/sqlcesa30.dll from my pc OK, but when I try to hit it from a cradled emulator ( after replacing "localhost" with "MACHINE_NAME" ), Internet Explorer on the emulator gives me a "Cannot Connect With Current Settings" error message. This part wasn't part of tutorial but decided so not sure if I am supposed to be able to hit it from my emulator..so I am not sure if the fact that I can't hit it is related to the problem. AFTER STARTING SQL SERVER AGENTin Microsoft SQL Server Management Studio, I killed the application, and after relaunching it, it hits "The Specified table does not exist [Vendor]" error. This time it doesn't even launch first - that is I dont even get to pressing "InitSinc" button. Debugger is showing that this error is hit on the following line in AdvWorksMobile.AddWorksDataSetTableAdapters
int returnValue = this.Adapter.Fill(dataTable);
I am not sure why the errors changed on me after starting SQL Server Agent. What can I do to fix this connection problem?
I've just installed SQL 2005 SP2 Rollup 3 Package (Build 3186) on a 2 node X64 W2K3 Cluster. Everything went fine, although after the install, the SQLAgent Services of my instances started to complain about delegation not enabled for the domain account used for the SQLAgent Service.
SPN's were already registered, so I've enabled unconstrained delegation & no errors anymore..
Apparently we're obliged to enable delegation as soon as this hotfix is installed
(maybe due to fix 938086 included in it ?)
To make this setup more secure, we would like to enable constrained delegation. This does not seem to work, as soon as we choose constrained delegation by adding the SPN of the clustername to the domain user account we're running with & restart the sql agent, it fails with the same error as when no delegation was configured:
! [298] SQLServer Error: 22022, CryptUnprotectData() returned error -2146892987, 'The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation.' [SQLSTATE 42000] ! [442] ConnConnectAndSetCryptoForXpstar failed (0).
Summary: With Unconstrained delegation enabled for computer account & user account, everything goes fine. As soon as constrained delegation is chosen, by adding the SPN's to the domain user account of SQL Agent, SQL agent fails to start.
We use a domain account for the SQL Agent. This account has an 2 SPN registered on it
...so got the below information from the cluster log:
000009fc.00000d68::2007/02/13-12:36:53.210 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed 000009fc.00000d68::2007/02/13-12:36:53.226 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746; message = [Microsoft][SQL Native Client]TCP Provider: An existing connection was forcibly closed by the remote host.
000009fc.00000d68::2007/02/13-12:36:53.226 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746; message = [Microsoft][SQL Native Client]Communication link failure 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] OnlineThread: QP is not online. 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed 000009fc.00000d68::2007/02/13-12:36:53.242 ERR SQL Server <SQL Server (ITG)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Native Client]Communication link failure 0000088c.00000af8::
Looked at the system log to see if there are any errors , but could not found any during that time....The last message in the system log was
Event Type: Warning Event Source: Print Event Category: None Event ID: 3 Date: 2/13/2007 Time: 5:03:04 PM User: NT AUTHORITYSYSTEM Computer: xxx Description: Printer ITGHP8N1 on rchprt01 (from R6911497-XP) in session 1 was deleted.
before that there were messages of creating and deleting the printer...and R6911497-XP is my laptop which was not really running during that time...
From some research came to know that this might be because of network issues, but let me know for what errors I need to look for network issues...does the above error in the system log suggests network errors...
We are trying to install SQL Server on a cluster that has 4 nodes, 3 of them running SQL2k. We're getting an error in the setup after it is done with Framework:
Failed to find property "ComputerList" {"SqlComputers", "", ""} in cache ... Source File Name: datastoremachineconfigscopeproperties.cpp Compiler Timestamp: Wed Aug 24 13:40:04 2005 Function Name: SqlInstallConfigScope.InstanceName ....- Error: Could not find an install of type 3 for instance SQL ##
We think it's due to a directory and item in the registry for a server instance we used to run on this server, but no longer due as it was uninstalled and the server moved to this cluster. The directory doesn't show in other nodes in the cluster, but does in the cluster it was moved from. We continue to find that 2nd instance refuses to failover to this server also. We have determined that it€™s only the SQL server which is having issues as we were able to move the disks over. When we start the SQL service it pops back to 2nd instances home server.
I have a two node failover cluster with SQL 2005 installed. I am running Windows Server 2003 x64 Enterprise and SQL 2005 x64 Enterprise. When I try the SP2 upgrade, I basically get an error message saying no passive nodes were succesfully patched. I have tried installing from the active node and the virtual server, same results with both. I have also tried the LMHOSTS file addition that Microsoft recommends, but that didnt solve the problem either. We do have an MSDTC Resource set up, as I have read this may cause problems, but it still doesnt work.
I dont know what to do next, any ideas?
Time: 03/11/2008 09:40:26.456 KB Number: KB921896 Machine: CAROLINA OS Version: Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 2 (Build 3790) Package Language: 1033 (ENU) Package Platform: x64 Package SP Level: 2 Package Version: 3042 Command-line parameters specified: Cluster Installation: Yes Log Location on Passive Nodes: (OAKLAND) C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfix (CAROLINA) C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfix ********************************************************************************** Prerequisites Check & Status SQLSupport: Passed ********************************************************************************** Products Detected Language Level Patch Level Platform Edition Setup Support Files ENU 9.2.3042 x64 Database Services (MSSQLSERVER) ENU RTM 2005.090.1399.00 x64 ENTERPRISE SQL Server Native Client ENU 9.00.3042.00 x64 Client Components ENU RTM 9.00.1399.06 x64 ENTERPRISE MSXML 6.0 Parser ENU 6.10.1200.0 x64 SQLXML4 ENU 9.00.1399.06 x64 Backward Compatibility ENU 8.05.2004 x64 Microsoft SQL Server VSS Writer ENU 9.00.3042.00 x64 ********************************************************************************** Products Disqualified & Reason Product Reason ********************************************************************************** Processes Locking Files Process Name Feature Type User Name PID ********************************************************************************** Product Installation Status Product : Setup Support Files Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : Database Services (MSSQLSERVER) Product Version (Previous): 1399 Product Version (Final) : Status : Failure Log File : Error Number : 11009 Error Description : No passive nodes were successfully patched ---------------------------------------------------------------------------------- ********************************************************************************** Summary No passive nodes were successfully patched Exit Code Returned: 11009 e : Error Description : ---------------------------------------------------------------------------------- ********************************************************************************** Summary No passive nodes were successfully patched Exit Code Returned: 11009
First I am fairly new to SQL Server 2005 Clustering so this is why I was to see if any of you might be able to help me.
Are current setup is as follows:
CRM1 SERVER 2K3 R2 xxx.xxx.xxx.74
CRM2 SERVER 2K3 R2 xxx.xxx.xxx.75
HP MSA1000 xxx.xxx.xxx.75
MSDTC IP xxx.xxx.xxx.77
SQL INSTANCE xxx.xxx.xxx.78
Now are CRM guys are trying to connect to xxx.xxx.xxx.78 for there SQL instance or RDP into this ip address and they can’t…Now the question is should they be able yto logon to the SQL Instance via RDP?
We have sql server 2005 installed locally on 2 servers and want to set up failover clustering. Do we need to uninstall what we have then install as failover cluster? Thanks.
I notice this running the SQL Server Profiler under the application name Report Server. Every time it runs, it reports an error (in the Error field of Profiler). Does anyone know what this is?declare @p1 nvarchar(64)set @p1=NULLexec GetDBVersion @DBVersion=@p1 outputselect @p1
I re-installed the IIS and sql server report services. Then I config the sql server 2005 report.
After that I run the http://servername/reports.
The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is 'Unknown'. The expected version is 'C.0.8.40'. To continue, update the version of the report server database and verify access rights. (rsInvalidReportServerDatabase) Get Online Help
I received this error on upgrade installation from SQL 2000 Standard to SQL 2005 Standard. It doesn't seem to be causing any problems after install but I am currently not using Notification Services in any production capacity.
Errors:
----------------------------- Microsoft SQL Server 2005 Setup ------------------------------
Failed to install and configure assemblies C:Program FilesMicrosoft SQL Server90DTSTasksMicrosoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2147024893 Error message: The system cannot find the path specified. Error description: Could not load file or assembly 'System.EnterpriseServices.Wrapper.dll' or one of its dependencies. The system cannot find the path specified.
------------------------------ Microsoft SQL Server 2005 Setup ------------------------------
Failed to install and configure assemblies C:Program FilesMicrosoft SQL Server90NotificationServices9.0.242Binmicrosoft.sqlserver.notificationservices.dll in the COM+ catalog. Error: -2147024893 Error message: The system cannot find the path specified. Error description: Could not load file or assembly 'System.EnterpriseServices.Wrapper.dll' or one of its dependencies. The system cannot find the path specified.
Any help would be greatly appreciated. Thanks, Keith
Hi. I have installed an SQL 2005 Failover Cluster on a Two Node Active Passive Windows 2003 Cluster.If i am trying to failover from the Active node to the passive Node,The Sql Server,Sql Server Agent and SQL Analysis resources fail,However if i reset the passowrd in the services tab of the above three services on the pasive node,the resources come online. Below is the brief of my setup 1.I have two Active directory domain controllers running Windows 2003 R2 Standard edition with SP2. 2.i have installed a Windows 2003 Two Node Active Passive Cluster as NODE1 and NODE2. 3.The Domain account used to install WIndows 2003 A/P Cluster is Clusteradmin.This account is the member of Administartors on the Domain as well as the Local Admin on NODE1 and NODE2. 4.SQL 2005 with SP2 is installed on both the Nodes as SQL 2005 Failover Cluster.The account used to install SQL 2005 is sqadmin.This account is the member of Administartors on the domain and the member of Local Admins on NODE1 and NODE2. 5.SLQ 2005 has four domain groups for 4 SQL Services.The Services are SQL Server,SQL Server Agent,SLQ Anaylisis Server and Full text Search. 6.Each of these servcie has a seperate service account created for them.All these service accounts areb the members of domain admin and the member of Local Admin on NODE1 and NODE2. 7.Each of these servcies is running under these servcie accounts in the Servcies tab in NODE1 and NODE2. 8.If i fail the resources from NODE1 to NODE2 ,The SQL Server,SQL Server Agent and SQL Anaylisis resources are failing.on going to the service tab of NODE 2 I reset the password for these services,the services come online. 10.The Cluster resources and MSDTC Resources are Failing over successfully.They are coming online successfully. 11,I have a problem with the SQL Server Resources,even if i failback to NODE1 from NODE2,the same resources are failing again.
I have a failed sql cluster setup on Windows 2003 OS cluster. sql will not uninstall on node 1 because it says the group name was not specified in the template.ini file for the cluster. The OS cluster nodes have been evicted from the cluster. The OS cluster is no longer available to provide a group name for.
SQl uninstall process process is failing because of the error mentioned above.
I want to completely , uninstall SQL server from both nodes, clean up Windows Server and install just a default instance of SQL server on just one of the machines, The cluster can wait.
A few months ago, I was trying to install SQL Server 2005 SP2 on a cluster (Active-Active), the Cluster has 3 instances, 2 lives in one node and the other one in the other node. When I try to make the deployment an error message appear, I do not have the error right now but it€™s something like €śCould not connect to the passive node, installation failed€?. The worst part of the error was all instances shut down and I couldn€™t bring on line and I have to reinstall all instances. I need to install SP2 but I€™m a little afraid fail again. Do you know the best way to deploy the SP2 on a cluster? Maybe move all instances in one node before install SP2? Can you help me with your comments. Do you think I have problems with the windows cluster?
I'm building an SQL Server 2005 cluster on a Windows 2003 cluster. Windows 2003 cluster and MSDTC service are all up and running properly. No problems there, but when I try to install SQL Server 2005 as a cluster service, it fails. The installation goes past the stage where it validates both the nodes and doesn't find any issue there, but when it tries to install fiels it fails. It fails on node 2. When I checked the scduled installer job it creates on node2 to install, the job never seems to run and fails. I'm using only one user account to setup windows cluster MSDTC and SQL Server. Now the complications: It is 64 bit Windows 2003 and SQL Server 2005. Also, the node 1 is built to be a domain controller as well.
Our software vendors upgraded their software and our environment - and applications do not interface as they ought. The vendors do not appear to have any further ideas (to those listed below) and at this stage neither do I. It is now a week since the *upgrade* went live. Looking for new suggestions....
Full story (epic) below. Object names have been changed to protect the *innocent*.
Our organisation had 2 applications:-
appBank appHouse
both running on the respective platforms:
Server name svrCAT: Windows Server 2000 sp 4 / SQL Server 2000
Server name svrDOG: Windows Server 2000 sp 4 / SQL Server 2000
Transactions were "posted" from svrDOG to svrCAT via a linked SQL Server, using login dbL1nkLogin.
dbL1nkLogin was made a user of (with relevant table permissions) of the respective databases:
dbForBank dbForHouse
*** At this point all was working ***
Upgrading appBank to appBigBank required SQL Server 2005 (and more diskspace).
A new server was purchased:
Windows Server 2003 R2 sp 2 / SQL Server 2005 (Server name svrHORSE)
A linked server was created from the SQL instance on svrHORSE to svrDOG using login name dbL1nkLogin. dbL1nkLogin was made a user (with relevant table permissions) on database:
dbForBigBank
Attempts to "post" transactions were "posted" from svrDOG to svrHORSE via the linked SQL Server fail with the appBank application generating the following errors:
On first attempt:
************* FILE ERROR ************* Error Code...... 3902- Error Message...The COMMIT TRANSACTION request has no co .rresponding BEGIN TRANSACTION. Table Name......** NOT APPLICABLE ** Description.....** NOT APPLICABLE ** Function....... COMMIT sys991: Program already in use COBOL error at 000444 in sys500 Called from 00076A in sys990ssv Called from 000457 in sys991 Called from 01177D in gls489 Called from 000DFA in gls396 Called from 003961 in gls394 Called from 000258 in glp900 Called from 003DC1 in syp250
On subsequent attempts:
************* FILE ERROR ************* Error Code...... 1206- Error Message...The Microsoft Distributed Transaction Co .ordinator (MS DTC) has cancell Table Name......tblHouseFinancials Description.....DYNAMIC SQL CALL INTERLUDE Function....... UPDATE *FAILED* Processing Job 'WIN/'
* Parameters and controls within the appBank application were verified.
* Password on dbL1nkLogin was reset in the SQL instances on svrHORSE and svrDOG
* Compared the link server settings on svrHORSE to svrCAT:
Security tab: Be made using security context - Remote Logging: dbL1nkLogin / password
Server Options: Collation Compatible checked (on svrHORSE only) Data Access checked RPC checked RPC Out checked
* Made dbL1nkLogin dbo on databases dbForBigBank and dbForHouse. * Changed default database from master to dbForBigBank on svrHORSE * Rebooted svrHORSE and svrDOG (multiple times) * Verified that svrHORSE could ping svrDOG, and vice versa * Using DTCping.exe, Verified that the SQL instance on svrHORSE could ping svrDOG, and vice versa * On svrHORSE, Administrative Tools -> Component Services -> Computers has the following settings for "My Computer" Network DTC Access:
These settings were already set. My understanding of KB329332 suggest they are correct. As I could not establish the configuration date of these settings rebooted the server to ensure they'd taken effect.
* Loaded SQL Server 2000 sp4 on svrDOG (Rebooted afterwards in case services not stopped and started correctly) srvDOG now has MDAC 2.8 sp1 (2.81.1117.6) while srvHORSE has a later version (2.82.3959)- I assume sp2. While they are not the same version, MDAC 2.8 sp2 KB 231943 advises that 2.8 sp2 is not available via the web - so I think it's the best I can do).
* Stopped and manually started MSDTC and SQL Server (via Administrative Tools - Services) in case MSDTC was not being started first.
* KB873160 suggests opening port 135 and adding msdtc.exe as an exception in the Windows Firewall. At present there is no firewall on svrHORSE - which I would assume negates this necessity (at present). In Administration Tools - Services there was a service for the firewall running. Stopping this service has no effect on this issue.
* ( The svrHORSE machine was not created from an ghosted image ).
** None of these things have resolved the issue. **
Hello everyone. I have a problem in accessing my SQL SERVER Express 2005 database.
The error is: Cannot open database "MyDB" requested by the login. The login failed. Login failed for user 'NT AUTHORITYSERVIZIO DI RETE'.
My ConnectionString is: Data Source=(local); User ID=ExtApp; Initial Catalog=MyDB; Trusted_Connection=yes; Connection Timeout=15
In SQL SERVER I have set the Database log in ExtApp with SQL Authentication mode, instead of Windows Auth mode, and even inserted in my database the user associated with this login
The debugger keeps on telling me the same error that occours when I Try to open a connection (please note that the code has no errors because it works in another application, a client app not an asp.net 2.0 web app, so I assume that there are no errors or mistakes in the code).
Please can anyone tell me something about this????
I've been having horrific problems installing and working with SQL Server Express 2005. I installed SSE with the Visual Web Developer tool so I assumed that the instance would synch up; but it didn't (see log contents at end) so I opened up permissions wide open to all users, and even that didn't help. I don't know for sure but I suspect that the problem probably relates to my deleting SQL Server entries from the registry and all directories and files related to it on disk. After going through the process of uninstalling and reinstalling Express 2005 numerous times, I became frustrated and decided to pull out all stops. After reading and following all MSDN instructions and every blog and forum I could possibly locate on the subject, I could never resolve the problem of not reaching my database. I enabled all pipes and TCP/IP, etc. in the Configuration Manager, in both instances I had created; had run all command-line procedures recommended; and used cleanup programs that I could find, before reinstalling. I couldn't even get success in doing a test connection. I did get to a point where my ASP returned the message that it had connected but that the user didn't have permissions. I think I'm destined to working with Access, which is a shame since I have encouraged students in a Web development class I teach to work with the more powerful SQL Server products. They've had success with SQL Server, so I'm setting a bad example. Thanks in advance for help any of you can suggest. Microsoft SQL Server 2005 Setup beginning at Sun Feb 05 23:48:08 2006Process ID : 2036c:6645bd818fccc8ef0bad80e6a12f5bsetup.exe Version: 2005.90.1399.0Running: LoadResourcesAction at: 2006/1/5 23:48:6Complete: LoadResourcesAction at: 2006/1/5 23:48:6, returned trueRunning: ParseBootstrapOptionsAction at: 2006/1/5 23:48:6Loaded DLL:c:6645bd818fccc8ef0bad80e6a12f5bxmlrw.dll Version:2.0.3604.0Complete: ParseBootstrapOptionsAction at: 2006/1/5 23:48:8, returned trueRunning: ValidateWinNTAction at: 2006/1/5 23:48:8Complete: ValidateWinNTAction at: 2006/1/5 23:48:8, returned trueRunning: ValidateMinOSAction at: 2006/1/5 23:48:8Complete: ValidateMinOSAction at: 2006/1/5 23:48:8, returned trueRunning: PerformSCCAction at: 2006/1/5 23:48:8Complete: PerformSCCAction at: 2006/1/5 23:48:8, returned trueRunning: ActivateLoggingAction at: 2006/1/5 23:48:8Complete: ActivateLoggingAction at: 2006/1/5 23:48:8, returned trueRunning: DetectPatchedBootstrapAction at: 2006/1/5 23:48:8Complete: DetectPatchedBootstrapAction at: 2006/1/5 23:48:8, returned trueAction "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions: Condition "EventCondition: __STP_LaunchPatchedBootstrap__2036" returned false.Running: PerformSCCAction2 at: 2006/1/5 23:48:8Loaded DLL:C:WINDOWSsystem32msi.dll Version:3.1.4000.2435Loaded DLL:C:WINDOWSsystem32msi.dll Version:3.1.4000.2435Complete: PerformSCCAction2 at: 2006/1/5 23:48:9, returned trueRunning: PerformDotNetCheck at: 2006/1/5 23:48:9Complete: PerformDotNetCheck at: 2006/1/5 23:48:9, returned trueRunning: ComponentUpdateAction at: 2006/1/5 23:48:9Complete: ComponentUpdateAction at: 2006/1/5 23:48:30, returned trueRunning: DetectLocalBootstrapAction at: 2006/1/5 23:48:30Complete: DetectLocalBootstrapAction at: 2006/1/5 23:48:30, returned trueRunning: LaunchLocalBootstrapAction at: 2006/1/5 23:48:30
I am the DBA for a product development company with an application currently connected to and running fine on SQL Server 2000. I have recently installed our product on 2005 sql server with compatability version of 90 and some folks have begun testing. Apparently, there are a lot of strange things happening and ODBC errors are frequent. The more they move around in the app, the more errors appear. Sometimes, they appear, sometimes they don't. The most common occurence is an error such as, x table is missing the following columns. Then the user does it again and does not receive the error. Another issues is "Application Terminating Due to Severe Database Error" and when we look at the logs our app generates:
08/10/2006 08:57:09 (01000/10054), [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()). SQLColAttributes 08/10/2006 08:57:09 Table x.TS_X is missing the following columns:
The user has database role membership db_data_read and db_data_write access to the database. MDAC version - 2.81.1117 ODBC version - 2000.85.1117
Could this be a permissions issue or possibly more of an ODBC issue? Any thoughts would be greatly appreciated
I am running a SQL Server 2000 enterprise default instance and SQL Server 2005 standard named instances on a machine. I uninstalled the default instance and tried to instance 2005 but was unable to with the error:
'an installation packages for the product Microsoft SQL Server Backward Compatibility cannot be found. Try the installation again using a valid copy of the installation packages sqlserver2005_bc.msi'
I have tried to repair the backward compatibility currently installed and have also tried runing the msi file again but it will not install.
I have also put back 2000 as the default instance. then tried to apply sp1 to the 2005 named instances and i cannot do that either. anyone have any ideas?
I created an SSIS package for a client that does data importing. When I run the pacakge from Visual Studio there is an error window showing all the errors and warnings. A good example of an error is if the import file is in the wrong format.When there is a error or warning can I write the error log to a file OR notify someone of the errors so they can make corrections and rerun the package OR any ideas that the client can find out what went wrong and then make corrections accordingly? Thanks
