Trouble with KB 970315
in [Server Configuration]
|
Prev: Clustered SQL server 2005 x64 ENT- jobs keep failing after upgradeto SP3 with CU5
Next: SQL 2005 express database monitoring
From: Bob Weiner on 29 Dec 2009 10:52 You are right about calling tech support. I talked to them yesterday and they found an issue that I would never have been able to find on my own. The problem, either triggered by the installation of the hotfix or an event in close proximity, was due to a bug with the SQL 2008 Filestream. Running that service on Win 2003 R2 in cluster mode can lead to a failure of the database engine to fail over. This bug is yet to be resolved but after disabling the filestream in the registery the db engine starting failing over propertly. It is a strange because the second instance still has the filestream enabled and it fails-over fine. I am grateful for the workaround though hope one day for a real fix. Maybe SP2. I probably spoke too harshly regarding my opinion on the use of SQL Server. I work in higher education and not a company and have no right to speak on best practices in that world. Here, I have one SQL server (cluster) and it is used for everything - development, testing (= asking the guy next door to me for a second opinion), and production. I have to trust that it will work as designed. I used to set up non-production environments testing/development but in reality that ideology made more of a mess than the benefit it was supposed to provide. Steen was also right in pointing out that my original question lacked specific error messages. That is a good point that I will try to remember in future posts. "TheSQLGuru" wrote: > Every company I know that puts out beta software for public evaluation > includes at least one statement in the setup process or readme et al that > says do not put this stuff on production systems. And yes, connecting > sharepoint 2010 beta to a production sql server is affecting a production > system in my book. > > I this case it does seem that the patch installation is the original problem > cause. Virtually any installation failure such as this (if a > uninstall/reinstall try doesn't work) is a guaranteed trip to MS support. > You can scan through the megs of log files that are written hunting for a > cause and if you find one then try to figure it out yourself or with the > help of forumites. But by far your best course of action, especially given > that a cluster is involved, is to work your way through the MS support > system. > > -- > Kevin G. Boles > Indicium Resources, Inc. > SQL Server MVP > kgboles a earthlink dt net > > > "Bob Weiner" <bob.weiner(a)community.nospam> wrote in message > news:24FD1B74-0DED-40D9-8DA3-6F51754E60A5(a)microsoft.com... > > The patch is not beta - it is an MS supported hotfix. There is no reason > > to > > think that this would harm the database. > > > > SharePoint 2010 is beta but runs on a separate server and only connects to > > the sql server for the purposes of creating and storing data - which is > > our > > whole reason for owning a sql server. I do not believe that connecting > > software, beta or not, should be able to negatively impact the functioning > > of > > the database engine. If I am wrong on this point, I think it is time to > > change the database server, not the beta software. > > > > So, I guess I don't see how I could have "messed things up beyond repair" > > or > > why it is so obvious that you'd be pretty amazed. I know the word "beta" > > scares a lot of people and as such your comment seems more flippant than > > insightful. > > > > I will admit however, that I am not an SQL MVP so maybe I am > > misunderstanding. Is this MS's position on the subject as well? > > > > > > > > "TheSQLGuru" wrote: > > > >> Boy I sure hope you haven't messed things up beyond repair here. I would > >> be > >> on the phone to MS tech support. > >> > >> Obviously I am pretty amazed that you would even think of installing BETA > >> software anywhere near a production server!!! > >> > >> -- > >> Kevin G. Boles > >> Indicium Resources, Inc. > >> SQL Server MVP > >> kgboles a earthlink dt net > >> > >> > >> "Bob" <Bob(a)discussions.microsoft.com> wrote in message > >> news:C8BA0C81-8F18-4F13-994A-197F17976EEE(a)microsoft.com... > >> > > >> > I have a clustered SQL 2008 SP 1 running on Win2k3 R2 x64 SP2. There > >> > are > >> > two DB instances, the default for SharePoint, vcenter, and some custom > >> > databases and the other for OCS. > >> > > >> > I applied the cumulative update of KB 970315 to one of the nodes so > >> > that I > >> > could use the server for SharePoint 2010 beta 2. Before applying it to > >> > the > >> > second node, I failed over the groups to ensure that they would run. > >> > > >> > The group containing the default instance does not run on the updated > >> > server. It is the SQL Server resource within the group that fails to > >> > start. > >> > > >> > Everything is currently running on node 1 but I cannot install SP 2010 > >> > and > >> > if node 1 fails, I'll lose the production SharePoint services. > >> > > >> > How can I resolve this problem? > >> > > >> > Thank you, bob > >> > > >> > >> > >> . > >> > > > . > |