Tuesday, March 27, 2012
Cluster resource SQL Server (InstanceName) failed to come offline
Recently I added some additional memory to a sever thats part of an active
passive cluster (for a total of 8GB). After which we started receiving an
error message when trying to move the cluster over to the passive server:
Source:ClusSvc
Event ID: 1117
Description: Cluster resouce SQL Server(InstanceName) failed to come offline
I did some searching online but the only thing I could find was a thread on
google news from October 2003 (link included below). I am wondering if
anyone else has also experienced this particular problem and if so how they
may have solved it.
Google Groups Link:
http://groups.google.com/groups?hl=e...3DN%26tab%3Dwg
Thanks!
Brad Baker
Anything in the SQL Error log?
Did you re-configure SQL to use the additional RAM?
--
Mike Epprecht, Microsoft SQL Server MVP
Johannesburg, South Africa
Mobile: +27-82-552-0268
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Brad Baker" <bab5470@.no_sp@.m.rochester.rr..com> wrote in message
news:e78npbWfEHA.3964@.TK2MSFTNGP12.phx.gbl...
> Hi -
>
> Recently I added some additional memory to a sever thats part of an active
> passive cluster (for a total of 8GB). After which we started receiving an
> error message when trying to move the cluster over to the passive server:
>
> Source:ClusSvc
> Event ID: 1117
> Description: Cluster resouce SQL Server(InstanceName) failed to come
offline
>
> I did some searching online but the only thing I could find was a thread
on
> google news from October 2003 (link included below). I am wondering if
> anyone else has also experienced this particular problem and if so how
they
> may have solved it.
>
> Google Groups Link:
>
http://groups.google.com/groups?hl=e...3DN%26tab%3Dwg
>
> Thanks!
> Brad Baker
>
>
>
|||Anything in the SQL Error log?
> Other than the error mentioned in the event viewer I didn't see anything
> really pertinant.
Did you re-configure SQL to use the additional RAM?
> We enabled AWE and also enabled SQL to use 7GB of RAM. The only thing
> that might be noteworthy is that the active server has 8GB of RAM versus
> the passive system which has 4GB of RAM. We've run unbalanced cluster for
> quite some time though and only experienced this problem after adding the
> last 2GB.
Brad
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%23AWVeqWfEHA.4092@.TK2MSFTNGP10.phx.gbl...
> Anything in the SQL Error log?
> Did you re-configure SQL to use the additional RAM?
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Johannesburg, South Africa
> Mobile: +27-82-552-0268
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Brad Baker" <bab5470@.no_sp@.m.rochester.rr..com> wrote in message
> news:e78npbWfEHA.3964@.TK2MSFTNGP12.phx.gbl...
> offline
> on
> they
> http://groups.google.com/groups?hl=e...3DN%26tab%3Dwg
>
|||The error message indicates that the SQL Server recource fail to come offline. Instead of moving the group, try taking the SQL Server resource offline and see the results/errors ? If it goes offline then I would take all
resources in the SQL group offline, move the group to the other node and bring one resource online at a time -- starting with the resources that are not dependent on any resources i.e the disks first followed by sql ip
resoruce, sql network name and then sql server. Also, I will uncheck "restart" property for the resources to troubleshoot this issue (set it back to default after issue is resolved).
NOTE: Since AWE is enabled, max server memory is set to 7GB and passive node has 4GB, when you move the SQL Group to the passive node, SQL server instance will acquire almost all of the available memory
and leave ONLY up to 128MB fo memory free. For more info, please refer to SQL Server BOL topic "Managing AWE Memory".
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
Cluster problem
active/active/active cluster has failed. It cannot proceed beyond the
beginning of the sql2k5 sp2 installation. It fails because it can't install
sqlsupport.msi. It seems to want to put the files in the wrong place.
We can't get the sp to install after a lot of trying and want to 1) fail the
instance the node normally hosts to a partner 2) disconnect the node from
the cluster heartbeat and public networks and 3) run a SQL de-install of the
problematic instance on the disconnected node to clear off SQL and then
reinstall it, bringing it up to SQL2K5 SP2 4) reconnect the node to the
network and 5) fail the instance on the partner node back.
I don't think this will work because during the de-install the add/remove
routine will ask to remove code from san drives it can't find because
they're no longer accessible to it, since it has been disconnected from the
network and SAN. I think a manual removal may be all that can work.
After the node has been reconnected, and SQL installation commenced I will
be asked to create a new instance, a local or clustered instance, neither of
which I want. Can I avoid this by running SQL Setup on the reconnected node
and asking to manage a virtual instance instead of installing a fresh one?
Will I need, at some point, to evict the disconnected node from the cluster?
I know on a previous occasion, I couldn't get the node, once evicted, to
rejoin. Once it's out, it's out for good, isn't it?
"Robert Hindla" <rhindla@.panix.com> wrote in message
news:C38733A0.1BA20%rhindla@.panix.com...
> An installation of sql2k5 sp2 to one node of a three node
> active/active/active cluster has failed. It cannot proceed beyond the
> beginning of the sql2k5 sp2 installation. It fails because it can't
> install
> sqlsupport.msi. It seems to want to put the files in the wrong place.
Are you installing the first instance or the second instance?
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp
The next ClusterHelp classes are:
Jan 18 - 31 in Denver
Mar 10- 13 in Denver
|||The virtual SQL instance I'm proposing to de-install and then re-configure
using the setup program in 'manage' mode (instead of 'setup' mode) is one of
two named instances. It isn't the default instance.
The default instance functions satisfactorily, but only after a lot of
backing and filling, such as returning the native client to RTM level and
then re-running the installation of the client tools.
On 12/17/07 1:25 PM, in article
351AA24D-A3AA-4812-9682-F36BAFB1BC14@.microsoft.com, "Russ Kaufmann [MVP]"
<russ@.clusterhelp.com> wrote:
> "Robert Hindla" <rhindla@.panix.com> wrote in message
> news:C38733A0.1BA20%rhindla@.panix.com...
> Are you installing the first instance or the second instance?
|||"Robert Hindla" <rhindla@.panix.com> wrote in message
news:C38DA216.1BACB%rhindla@.panix.com...
> The virtual SQL instance I'm proposing to de-install and then re-configure
> using the setup program in 'manage' mode (instead of 'setup' mode) is one
> of
> two named instances. It isn't the default instance.
> The default instance functions satisfactorily, but only after a lot of
> backing and filling, such as returning the native client to RTM level and
> then re-running the installation of the client tools.
So, it sounds to me like things are seriously hosed (to use a highly
technical term) with your cluster. I would consider a complete rebuild over
the holidays if it were me.
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp
The next ClusterHelp classes are:
Jan 18 - 31 in Denver
Mar 10- 13 in Denver
Sunday, March 25, 2012
Cluster Installation Failure
A SQL 2005 Failover Clustering installation (from the RTM disks) failed on
Database Services. Please see messages below. Windows cluster server name
is COMDEVDB01 (Windows 2003), primary node = COMDEVCLU01, secondary node =
COMDEVCLU02. SQL cluster virtual name = COMDEVSQLCLU, named instance =
COMDEVPROD. I installed from COMDEVCLU01. Should I install from COMDEVDB01
while COMDEVCLU01 is the active node (i.e., I will be on COMDEVCLU01)?
Earlier install failed on SQLBrowser errors and rolled back. Before the
cluster install two non-clustered SQL 2005 named instances had been installed
on COMDEVCLU01 and SP2 had been applied (both current versions = 3152).
After the SQLBrowser failure I installed a non-clustered SQL 2005 named
instance on COMDEVCLU02 with Database Services and Integration Services (also
version 3152). After that, the cluster install on COMDEVCLU01 failed with
these errors but did not rollback.
Should I try to install SP2 for the SQL cluster from COMDEVCLU01?
Can I "complete" this installation (save it) or will I have to uninstall and
re-install?
Should I uninstall all SQL Server instances on COMDEVCLU01 and install the
clustered instance first?
summary.txt message:
Machine : COMDEVCLU01
Product : Microsoft SQL Server 2005
Product Version : 9.00.1399.06
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0006_COMDEVCLU01_SQL.l og
Last Action : ComponentUpgrade
Error String : The setup has encountered an error while Upgrading
Components. The error: -2147019873
Error message: The group or resource is not in the correct state to perform
the requested operation.
Error Number : 29550
SQLSetup0006_COMDEVCLU01_SQL.log message:
MSI (s) (AC:14) [15:52:23:016]: Product: Microsoft SQL Server 2005 - Update
'Hotfix 3024 for SQL Server Database Services 2005 ENU (KB000000)' could not
be installed. Error code 1603.
MichaelA_CCGA
Michael:
I will be posting a similar question to yours entitled "Failed SQL Cluster
Advice." That hopefully will get answered as well.
In the meantime you mentioned RTM Disks. Are these CDs and did your install
fail when you put in Disk 2 "Tools" This is my issue and I have googled to
find that this is a known issue and the resolution is copy both disks to a
common path.
Was this your issue as well?
Thanks, emagidson
"MichaelA_CCGA" wrote:
> Thanks in advance for any help.
> A SQL 2005 Failover Clustering installation (from the RTM disks) failed on
> Database Services. Please see messages below. Windows cluster server name
> is COMDEVDB01 (Windows 2003), primary node = COMDEVCLU01, secondary node =
> COMDEVCLU02. SQL cluster virtual name = COMDEVSQLCLU, named instance =
> COMDEVPROD. I installed from COMDEVCLU01. Should I install from COMDEVDB01
> while COMDEVCLU01 is the active node (i.e., I will be on COMDEVCLU01)?
> Earlier install failed on SQLBrowser errors and rolled back. Before the
> cluster install two non-clustered SQL 2005 named instances had been installed
> on COMDEVCLU01 and SP2 had been applied (both current versions = 3152).
> After the SQLBrowser failure I installed a non-clustered SQL 2005 named
> instance on COMDEVCLU02 with Database Services and Integration Services (also
> version 3152). After that, the cluster install on COMDEVCLU01 failed with
> these errors but did not rollback.
> Should I try to install SP2 for the SQL cluster from COMDEVCLU01?
> Can I "complete" this installation (save it) or will I have to uninstall and
> re-install?
> Should I uninstall all SQL Server instances on COMDEVCLU01 and install the
> clustered instance first?
> summary.txt message:
> ----
> Machine : COMDEVCLU01
> Product : Microsoft SQL Server 2005
> Product Version : 9.00.1399.06
> Install : Failed
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0006_COMDEVCLU01_SQL.l og
> Last Action : ComponentUpgrade
> Error String : The setup has encountered an error while Upgrading
> Components. The error: -2147019873
> Error message: The group or resource is not in the correct state to perform
> the requested operation.
> Error Number : 29550
> ----
> SQLSetup0006_COMDEVCLU01_SQL.log message:
> ----
> MSI (s) (AC:14) [15:52:23:016]: Product: Microsoft SQL Server 2005 - Update
> 'Hotfix 3024 for SQL Server Database Services 2005 ENU (KB000000)' could not
> be installed. Error code 1603.
> --
> MichaelA_CCGA
|||Sorry I dropped out of the discussion but I wanted to post the question
before I took a few days off and I'm just now catching up. I have printed
your exchange with Geoff and I will review that in more detail.
I did not have the "2nd CD" problem but the information about uninstalling
may prove very useful.
Thanks again, and I'll check back in tomorrow or Thursday.
MichaelA_CCGA
"EMagidson" wrote:
[vbcol=seagreen]
> Michael:
> I will be posting a similar question to yours entitled "Failed SQL Cluster
> Advice." That hopefully will get answered as well.
> In the meantime you mentioned RTM Disks. Are these CDs and did your install
> fail when you put in Disk 2 "Tools" This is my issue and I have googled to
> find that this is a known issue and the resolution is copy both disks to a
> common path.
> Was this your issue as well?
> Thanks, emagidson
> "MichaelA_CCGA" wrote:
Thursday, March 22, 2012
Cluster install failing
on the remote machine failed, check the task scheduler log. The log on the
remote machine says "Unable to start task...Access is denied". Any idea how
to get around this?
Environment is DL585, Windows 2003 x64 sp1, SQL 2005 x64 Dev Edition
I also need to mention that I have Act as part of the operating system and
log on as a service rights on both nodes.
"Brad" wrote:
> When installing SQL 2005 on a 2 node cluster, the install fails saying setup
> on the remote machine failed, check the task scheduler log. The log on the
> remote machine says "Unable to start task...Access is denied". Any idea how
> to get around this?
> Environment is DL585, Windows 2003 x64 sp1, SQL 2005 x64 Dev Edition
|||You have to install using a domain account that is a member of the local
administrators group on each server.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Brad" <Brad@.discussions.microsoft.com> wrote in message
news:AA1196F9-0113-4844-B2C4-1BEABCAE97F3@.microsoft.com...[vbcol=seagreen]
>I also need to mention that I have Act as part of the operating system and
> log on as a service rights on both nodes.
> "Brad" wrote:
|||Permissions. The account that you are using to install the failover cluster
instance must be a member of the local admin group on each machine. (The
service accounts related to SQL Server do NOT need to be.)
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Brad" <Brad@.discussions.microsoft.com> wrote in message
news:F9ED4AEF-08EF-40CD-845E-E86794714C8A@.microsoft.com...
> When installing SQL 2005 on a 2 node cluster, the install fails saying
> setup
> on the remote machine failed, check the task scheduler log. The log on
> the
> remote machine says "Unable to start task...Access is denied". Any idea
> how
> to get around this?
> Environment is DL585, Windows 2003 x64 sp1, SQL 2005 x64 Dev Edition
|||Yes, thank you. The domain account I am using is already a member of the
admin group on both nodes. The error still persists.
"Geoff N. Hiten" wrote:
> You have to install using a domain account that is a member of the local
> administrators group on each server.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Brad" <Brad@.discussions.microsoft.com> wrote in message
> news:AA1196F9-0113-4844-B2C4-1BEABCAE97F3@.microsoft.com...
>
>
|||I didn't provide that information up front but the account is a member of the
admin group on both boxes.
"Michael Hotek" wrote:
> Permissions. The account that you are using to install the failover cluster
> instance must be a member of the local admin group on each machine. (The
> service accounts related to SQL Server do NOT need to be.)
> --
> Mike
> http://www.solidqualitylearning.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
> "Brad" <Brad@.discussions.microsoft.com> wrote in message
> news:F9ED4AEF-08EF-40CD-845E-E86794714C8A@.microsoft.com...
>
>
|||Hi,
But is it the LOCAL ADMIN ACCOUNT not domain admin account?
Nik Marshall-Blank MCSD/MCDBA
Linz, Austria
"Brad" <Brad@.discussions.microsoft.com> wrote in message
news:56372080-3701-40DA-8CF1-9B002BDC2E11@.microsoft.com...[vbcol=seagreen]
> Yes, thank you. The domain account I am using is already a member of the
> admin group on both nodes. The error still persists.
> "Geoff N. Hiten" wrote:
|||Yes, it is in the local admin group on both machines.
"Nik Marshall-Blank" wrote:
> Hi,
> But is it the LOCAL ADMIN ACCOUNT not domain admin account?
> --
> Nik Marshall-Blank MCSD/MCDBA
> Linz, Austria
> "Brad" <Brad@.discussions.microsoft.com> wrote in message
> news:56372080-3701-40DA-8CF1-9B002BDC2E11@.microsoft.com...
>
>
|||Make sure the task scheduler service is enabled and running on all nodes.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Brad" <Brad@.discussions.microsoft.com> wrote in message
news:DC6D365B-B9E9-4A59-947C-0A947C91826B@.microsoft.com...[vbcol=seagreen]
> Yes, it is in the local admin group on both machines.
> "Nik Marshall-Blank" wrote:
|||Did you ever get a resolution on this ? I am having the exact same
problem.
I have checked all the obvious problems, like permissions, task
scheduler service running, etc.
I am going to call Microsoft Support tomorrow if I can't figure this
out.
Brad wrote:[vbcol=seagreen]
> I didn't provide that information up front but the account is a member of the
> admin group on both boxes.
> "Michael Hotek" wrote:
sqlsql
Cluster File Share failed
Enterprise Edition with SP3A. The cluster is set up as a
Active/Active cluster.
What would cause the Cluster File Share resource to fail?
I have a file share directory set up so that if my server
fails over the file share directory 'shot_p' will be
recognized on the failover server.
Event Viewer Error:
Cluster File Share resource 'shot_p' has failed a status
check. The error code is 64.
Thanks,
Mike
Sounds like your network name resource failed...
C:\>net helpmsg 64
The specified network name is no longer available.
C:\>
Regards,
John
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:21aef01c45afe$75b27840$a401280a@.phx.gbl...
> I have a Windows 2000 Advanced Server with SQL Server 2000
> Enterprise Edition with SP3A. The cluster is set up as a
> Active/Active cluster.
> What would cause the Cluster File Share resource to fail?
> I have a file share directory set up so that if my server
> fails over the file share directory 'shot_p' will be
> recognized on the failover server.
> Event Viewer Error:
> Cluster File Share resource 'shot_p' has failed a status
> check. The error code is 64.
> Thanks,
> Mike
Cluster Failover
getting the following error:
Does anyone have any ideas'
Many Thanks
Event Type: Error
Event Source: ClusSvc
Event Category: Startup/Shutdown
Event ID: 1234
Date: 06/09/2006
Time: 09:09:18
User: N/A
Computer: NXNHPSQLSRV1
Description:
The Cluster service account does not have the following required user
rights:
Act as part of the operating system
These user rights were granted to the Cluster service account during
cluster setup and must not be removed.
User Action
Assign these rights to the Cluster service account. One way to do this
is to use Local Security Settings (Secpol.msc). Another way is to edit
the Group Policy object that is associated with the Cluster service
account's user object in Active Directory.
If you have already assigned these rights to the Cluster service
account, and the user rights appear to be removed, a Group Policy
object might be removing the rights. Check with your domain
administrator to find out if this is happening.Hi
Have you checked the rights? I assume it is a domain account that you are
using for the cluster service account?
John
<Joe.Mobley@.nationalexpress.com> wrote in message
news:1157531034.223893.106160@.b28g2000cwb.googlegroups.com...
> Each morning I find that 1 of my servers has failed across and I'm
> getting the following error:
> Does anyone have any ideas'
> Many Thanks
> Event Type: Error
> Event Source: ClusSvc
> Event Category: Startup/Shutdown
> Event ID: 1234
> Date: 06/09/2006
> Time: 09:09:18
> User: N/A
> Computer: NXNHPSQLSRV1
> Description:
> The Cluster service account does not have the following required user
> rights:
> Act as part of the operating system
> These user rights were granted to the Cluster service account during
> cluster setup and must not be removed.
> User Action
> Assign these rights to the Cluster service account. One way to do this
> is to use Local Security Settings (Secpol.msc). Another way is to edit
> the Group Policy object that is associated with the Cluster service
> account's user object in Active Directory.
> If you have already assigned these rights to the Cluster service
> account, and the user rights appear to be removed, a Group Policy
> object might be removing the rights. Check with your domain
> administrator to find out if this is happening.
>|||It's probably time to work with your server admin folks to see what else are
being modified. Nobody should be revoking privileges like this from service
accounts. Whether it's modified systematically via some group policy or
manually by someone mucking around, you've got a potentially big problem.
Linchi
"Joe.Mobley@.nationalexpress.com" wrote:
> Each morning I find that 1 of my servers has failed across and I'm
> getting the following error:
> Does anyone have any ideas'
> Many Thanks
> Event Type: Error
> Event Source: ClusSvc
> Event Category: Startup/Shutdown
> Event ID: 1234
> Date: 06/09/2006
> Time: 09:09:18
> User: N/A
> Computer: NXNHPSQLSRV1
> Description:
> The Cluster service account does not have the following required user
> rights:
> Act as part of the operating system
> These user rights were granted to the Cluster service account during
> cluster setup and must not be removed.
> User Action
> Assign these rights to the Cluster service account. One way to do this
> is to use Local Security Settings (Secpol.msc). Another way is to edit
> the Group Policy object that is associated with the Cluster service
> account's user object in Active Directory.
> If you have already assigned these rights to the Cluster service
> account, and the user rights appear to be removed, a Group Policy
> object might be removing the rights. Check with your domain
> administrator to find out if this is happening.
>|||Sounds like a GP issue -removing rights from the cluster service account.
Check with the Domain admins about providing a static profile to the cluster
service account.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
<Joe.Mobley@.nationalexpress.com> wrote in message
news:1157531034.223893.106160@.b28g2000cwb.googlegroups.com...
> Each morning I find that 1 of my servers has failed across and I'm
> getting the following error:
> Does anyone have any ideas'
> Many Thanks
> Event Type: Error
> Event Source: ClusSvc
> Event Category: Startup/Shutdown
> Event ID: 1234
> Date: 06/09/2006
> Time: 09:09:18
> User: N/A
> Computer: NXNHPSQLSRV1
> Description:
> The Cluster service account does not have the following required user
> rights:
> Act as part of the operating system
> These user rights were granted to the Cluster service account during
> cluster setup and must not be removed.
> User Action
> Assign these rights to the Cluster service account. One way to do this
> is to use Local Security Settings (Secpol.msc). Another way is to edit
> the Group Policy object that is associated with the Cluster service
> account's user object in Active Directory.
> If you have already assigned these rights to the Cluster service
> account, and the user rights appear to be removed, a Group Policy
> object might be removing the rights. Check with your domain
> administrator to find out if this is happening.
>
Cluster Failover
getting the following error:
Does anyone have any ideas'
Many Thanks
Event Type: Error
Event Source: ClusSvc
Event Category: Startup/Shutdown
Event ID: 1234
Date: 06/09/2006
Time: 09:09:18
User: N/A
Computer: NXNHPSQLSRV1
Description:
The Cluster service account does not have the following required user
rights:
Act as part of the operating system
These user rights were granted to the Cluster service account during
cluster setup and must not be removed.
User Action
Assign these rights to the Cluster service account. One way to do this
is to use Local Security Settings (Secpol.msc). Another way is to edit
the Group Policy object that is associated with the Cluster service
account's user object in Active Directory.
If you have already assigned these rights to the Cluster service
account, and the user rights appear to be removed, a Group Policy
object might be removing the rights. Check with your domain
administrator to find out if this is happening.Hi
Have you checked the rights? I assume it is a domain account that you are
using for the cluster service account?
John
<Joe.Mobley@.nationalexpress.com> wrote in message
news:1157531034.223893.106160@.b28g2000cwb.googlegroups.com...
> Each morning I find that 1 of my servers has failed across and I'm
> getting the following error:
> Does anyone have any ideas'
> Many Thanks
> Event Type: Error
> Event Source: ClusSvc
> Event Category: Startup/Shutdown
> Event ID: 1234
> Date: 06/09/2006
> Time: 09:09:18
> User: N/A
> Computer: NXNHPSQLSRV1
> Description:
> The Cluster service account does not have the following required user
> rights:
> Act as part of the operating system
> These user rights were granted to the Cluster service account during
> cluster setup and must not be removed.
> User Action
> Assign these rights to the Cluster service account. One way to do this
> is to use Local Security Settings (Secpol.msc). Another way is to edit
> the Group Policy object that is associated with the Cluster service
> account's user object in Active Directory.
> If you have already assigned these rights to the Cluster service
> account, and the user rights appear to be removed, a Group Policy
> object might be removing the rights. Check with your domain
> administrator to find out if this is happening.
>|||It's probably time to work with your server admin folks to see what else are
being modified. Nobody should be revoking privileges like this from service
accounts. Whether it's modified systematically via some group policy or
manually by someone mucking around, you've got a potentially big problem.
Linchi
"Joe.Mobley@.nationalexpress.com" wrote:
> Each morning I find that 1 of my servers has failed across and I'm
> getting the following error:
> Does anyone have any ideas'
> Many Thanks
> Event Type: Error
> Event Source: ClusSvc
> Event Category: Startup/Shutdown
> Event ID: 1234
> Date: 06/09/2006
> Time: 09:09:18
> User: N/A
> Computer: NXNHPSQLSRV1
> Description:
> The Cluster service account does not have the following required user
> rights:
> Act as part of the operating system
> These user rights were granted to the Cluster service account during
> cluster setup and must not be removed.
> User Action
> Assign these rights to the Cluster service account. One way to do this
> is to use Local Security Settings (Secpol.msc). Another way is to edit
> the Group Policy object that is associated with the Cluster service
> account's user object in Active Directory.
> If you have already assigned these rights to the Cluster service
> account, and the user rights appear to be removed, a Group Policy
> object might be removing the rights. Check with your domain
> administrator to find out if this is happening.
>|||Sounds like a GP issue -removing rights from the cluster service account.
Check with the Domain admins about providing a static profile to the cluster
service account.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
<Joe.Mobley@.nationalexpress.com> wrote in message
news:1157531034.223893.106160@.b28g2000cwb.googlegroups.com...
> Each morning I find that 1 of my servers has failed across and I'm
> getting the following error:
> Does anyone have any ideas'
> Many Thanks
> Event Type: Error
> Event Source: ClusSvc
> Event Category: Startup/Shutdown
> Event ID: 1234
> Date: 06/09/2006
> Time: 09:09:18
> User: N/A
> Computer: NXNHPSQLSRV1
> Description:
> The Cluster service account does not have the following required user
> rights:
> Act as part of the operating system
> These user rights were granted to the Cluster service account during
> cluster setup and must not be removed.
> User Action
> Assign these rights to the Cluster service account. One way to do this
> is to use Local Security Settings (Secpol.msc). Another way is to edit
> the Group Policy object that is associated with the Cluster service
> account's user object in Active Directory.
> If you have already assigned these rights to the Cluster service
> account, and the user rights appear to be removed, a Group Policy
> object might be removing the rights. Check with your domain
> administrator to find out if this is happening.
>
Sunday, March 11, 2012
CLR Stored Procedure "Failed to get permission to execute"
This is variant/continuation of a problem I've discussed on the
sqlserver.programming group (Thanks to Erland for a lot of help over there).
I thought it might benefit me to raise the issue here as well.
In a nutshell:
I have a C# stored procedure (called SProc, in cs.dll, but "imported" as
"csfn") that uses PInvoke to access a function in a C++ dll (called
cpp.dll). The function is __declspec(dllexport)'d. If the C++ dll is
UNMANAGED this now seems to work OK. (Thank again to Erland helping me get
this far). Now, if I add some managed code to the C++ dll (leaving the
unmanaged entry point unchanged, but now compiling with /clr) I get a
"Failed to get permisssion to execute" message as below.
I've tried all the obvious (to me anyway) ways of adding the appropriate
permissions. I've used the "Trust Assembly" node of the .Net 2.0
Configuration tool to give "Full Trust" to both cs.dll AND cpp.dll but it
still fails. I've confirmed that I can call the C++ dll from a c# EXE from
the command line, and that works OK.
I'd really appreciate any help.
/john
Error text follows.
Msg 6522, Level 16, State 1, Procedure csfn, Line 0
A .NET Framework error occurred during execution of user defined routine or
aggregate 'csfn':
System.IO.FileLoadException: Could not load file or assembly 'cpp,
Version=11.0.1.0, Culture=neutral, PublicKeyToken=eb5ebc232de94dcf' or one
of its dependencies. Failed to grant permission to execute. (Exception from
HRESULT: 0x80131418) --> System.Security.Policy.PolicyException: Execution
permission cannot be acquired.
System.Security.Policy.PolicyException:
at System.Security.SecurityManager.ResolvePolicy(Evidence evidence,
PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset,
PermissionSet& denied, Boolean checkExecutionPermission)
at System.Security.SecurityManager.ResolvePolicy(Evidence evidence,
PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset,
PermissionSet& denied, Int32& securitySpecialFlags, Boolean
checkExecutionPermission)
System.IO.FileLoadException:
at DotNetFun.SqlServer.SProc.CPPTest()
at DotNetFun.SqlServer.SProc.CPPTest()
at DotNetFun.SqlServer.SProc.PrintMessage(String Message)
.Hello Eric,
The consensus is (I think), that you can use pInvoke to call an
unmanaged DLL from a managed stored procedure. However, it looks like
calling a MIXED (ie managed and unmanaged) DLL is not going to work. You can
look at the thread I started on the sqlserver.programming group for more
information.
It seems that mixed and/or managed DLLs need to be added to SQL with
CREATE ASSEMBLY, and this fails on a mixed dll, even if set it as UNSAFE.
I'd like to establish if that is expected to work, but I suspect it is
failing for good reason.
/john
"Eric" wrote in message news:200762618736eric_hackett@.kindermorg
an.com...
> Did you find any satisfaction for this? I have a nearly identical problem.
> Using a third party dll, wrapping it with my own dll, and then writing CLR
> stored proc to use wrapped function. Other functions in the stored proc
> dll work. Only the ones that need external resources are choking.
> Please reply here if you get this working.
> EggHeadCafe.com - .NET Developer Portal of Choice
> http://www.eggheadcafe.com
Thursday, March 8, 2012
CLR initialization failed with hresult 0x80131022
I guess this may not strictly be a CLR integration question, because what I'm actually doing is using sp_OACreate in a T-SQL batch to call a COM object written in C#. Not as nice as using full CLR integration, but unfortunately the T-SQL must run without error on a SQL 2000 server before it is upgraded to 2005, and I preferred this option to using reams of dynamic SQL.
The first call to sp_OACreate fails with hRes 0x80131022. MSSQLServer also logs the following error to the app event log:
"Failed to initialize the Common Language Runtime (CLR) v2.0.50727 with HRESULT 0x80131022. You may fix the problem and try again later."
Please can anyone suggest why this is happening? I've tried repairing the .NET framework (v2) installation, and reinstalled SQL Server Express. I've double checked both CLR integration and OLE Automation are allowed in the Surface Area config tool for SQL Express. I've tried running SQL Express using both LocalSystem and the administrator account on the machine. I've even checked there is plenty of free memory (including virtual memory). Nothing has helped though.
Thanks in advance for any help or suggestions you can provide,
Rob
Trying to load the CLR from SP_OA procedures is not supported and we block it in 2005, as described in the following kb: http://support.microsoft.com/kb/322884
It looks like you'll need to use different wrapper code on 2000 and 2005 to create your clr-based routines.
|||Thanks for the response, but I notice the article clearly states it applies to 7.0 and 2000 only, not 2005 as you've suggested in your answer? Assuming CLR can be loaded when calling sp_OA procs on a 2005 installation, let me explain my question a bit more clearly...
Due to the lack of SQL Server Agent on an Express installation, my (pseudo) T-SQL code is structured as thus:
if @.@.version <= 8.x
sp_start_job 'SQL 2000 Job'
else
sp_OACreate 'JobReplacement.ForSQLExpress'
This way, when running on SQL 2000, the T-SQL follows the first branch, starting a SQL job. As soon as the DB engine has been upgraded, the T-SQL follows the alternative path, using the sp_OA procedures to call onto a C# coded COM object (which basically does the same things the job did on SQL 2000). Thus the T-SQL is effectively version neutral, and allows the engine to be upgraded at an arbitrary time without any further changes to the T-SQL code.
Therefore, as you can see, the sp_OA procedures are only called when running on SQL 2005 (Express). If you are telling me (contrary to what is stated in the KB article) that this is not possible under 2005, I will indeed re-think my approach. Otherwise, perhaps someone can help me further?
Thanks again,
Rob
|||The KB doesn't obviously state the Sql Server 2005 limitation as its primary purpose is to state that using SP_OA to load the clr on Sql 2000 or earlier is unsupported. The relevent section to 2005 is in this line:
"Later versions of SQL Server will host Common Language Runtime (CLR) and will support procedures, functions, triggers, types, and aggregates that are written in CLR langauges. In these later versions, you cannot load CLR by using extended stored proceduress or sp_OA stored procedures."
So the KB article does not officially apply to SQL Server 2005 because while using SP_OA to load the CLR was unsupported in SQL Server 2000, it is impossible in SQL Server 2005.
My suggestion would be to use the built-in clr integration support on SQL Server 2005, however the only way to do this in a T-SQL neutral fashion would be with a lot of dynamic sql to enable clr, create assembly, create procedure, etc.|||Ok, thanks for your help.CLR initialization failed with hresult 0x80131022
I guess this may not strictly be a CLR integration question, because what I'm actually doing is using sp_OACreate in a T-SQL batch to call a COM object written in C#. Not as nice as using full CLR integration, but unfortunately the T-SQL must run without error on a SQL 2000 server before it is upgraded to 2005, and I preferred this option to using reams of dynamic SQL.
The first call to sp_OACreate fails with hRes 0x80131022. MSSQLServer also logs the following error to the app event log:
"Failed to initialize the Common Language Runtime (CLR) v2.0.50727 with HRESULT 0x80131022. You may fix the problem and try again later."
Please can anyone suggest why this is happening? I've tried repairing the .NET framework (v2) installation, and reinstalled SQL Server Express. I've double checked both CLR integration and OLE Automation are allowed in the Surface Area config tool for SQL Express. I've tried running SQL Express using both LocalSystem and the administrator account on the machine. I've even checked there is plenty of free memory (including virtual memory). Nothing has helped though.
Thanks in advance for any help or suggestions you can provide,
Rob
Trying to load the CLR from SP_OA procedures is not supported and we block it in 2005, as described in the following kb: http://support.microsoft.com/kb/322884
It looks like you'll need to use different wrapper code on 2000 and 2005 to create your clr-based routines.
|||Thanks for the response, but I notice the article clearly states it applies to 7.0 and 2000 only, not 2005 as you've suggested in your answer? Assuming CLR can be loaded when calling sp_OA procs on a 2005 installation, let me explain my question a bit more clearly...
Due to the lack of SQL Server Agent on an Express installation, my (pseudo) T-SQL code is structured as thus:
if @.@.version <= 8.x
sp_start_job 'SQL 2000 Job'
else
sp_OACreate 'JobReplacement.ForSQLExpress'
This way, when running on SQL 2000, the T-SQL follows the first branch, starting a SQL job. As soon as the DB engine has been upgraded, the T-SQL follows the alternative path, using the sp_OA procedures to call onto a C# coded COM object (which basically does the same things the job did on SQL 2000). Thus the T-SQL is effectively version neutral, and allows the engine to be upgraded at an arbitrary time without any further changes to the T-SQL code.
Therefore, as you can see, the sp_OA procedures are only called when running on SQL 2005 (Express). If you are telling me (contrary to what is stated in the KB article) that this is not possible under 2005, I will indeed re-think my approach. Otherwise, perhaps someone can help me further?
Thanks again,
Rob
|||The KB doesn't obviously state the Sql Server 2005 limitation as its primary purpose is to state that using SP_OA to load the clr on Sql 2000 or earlier is unsupported. The relevent section to 2005 is in this line:
"Later versions of SQL Server will host Common Language Runtime (CLR) and will support procedures, functions, triggers, types, and aggregates that are written in CLR langauges. In these later versions, you cannot load CLR by using extended stored proceduress or sp_OA stored procedures."
So the KB article does not officially apply to SQL Server 2005 because while using SP_OA to load the CLR was unsupported in SQL Server 2000, it is impossible in SQL Server 2005.
My suggestion would be to use the built-in clr integration support on SQL Server 2005, however the only way to do this in a T-SQL neutral fashion would be with a lot of dynamic sql to enable clr, create assembly, create procedure, etc.|||Ok, thanks for your help.Saturday, February 25, 2012
close all existing connections and processes to a database
Dear all
I created this trigger on a table that i think failed while execution. I tried to modify it and run it again but it seems that i cant do that. If i try and delete the database i also cant - saying that it is still in use. But i am not using it and ther are no other users connected to it. I think the trigger has probably hit a loop and that is holding the link.
To close that i know that a solution would be to restart the SQL server instance but that would be a bit hard since the SQL server where my test database resides is a production server and has few other databases that are important and few users use them.
Is there any way through a SQL statement that there can be forced a delete? Or force close all the connections? Or force close all the processes without actually restarting the SQL server instance.
I have tried all options that were offered on some other forums like forcing it to a single user but even that operation can not be performed saying that the database is still in use.
Thank you so much for all your help and time.
Sincerely
Dan
You could cycle through the SPID's in master.dbo.sysprocess and KILL off any SPID's using the test database_id.
And then you have learned why you 'should' not 'play' on a production server. Create yourself a local server for experiementation and testing. Get an 'old', decommissioned desktop and convert it to a test server. There is no excuse for mucking up a production server.
Tuesday, February 14, 2012
Client EM produce OS "failed login errors"
we've got a SQL2000SP3a on a 2 active-active node clusters of W2K3,
this cluster in using AD.
I've found that whenever I use Enterprise Manager on my local computer
to register the above instance, it will constantly produce "Failed
login for <Domain>\<DomainUser>" errors in the Windows Security Log of
the database server machine. There's no failed login in the SQL error
log and I can work normally with the Enterprise Manager. The OS failed
logins error are gone once I un-register the instance from my
Enterprise Manager.
Does anyone know or met with this before?"New MSSQL DBA" <boscong88@.gmail.com> wrote in message
news:1120635376.062877.121860@.z14g2000cwz.googlegr oups.com...
> hi all, have anyone else met with the following problem.
> we've got a SQL2000SP3a on a 2 active-active node clusters of W2K3,
> this cluster in using AD.
> I've found that whenever I use Enterprise Manager on my local computer
> to register the above instance, it will constantly produce "Failed
> login for <Domain>\<DomainUser>" errors in the Windows Security Log of
> the database server machine. There's no failed login in the SQL error
> log and I can work normally with the Enterprise Manager. The OS failed
> logins error are gone once I un-register the instance from my
> Enterprise Manager.
> Does anyone know or met with this before?
I don't really know, but as a complete guess, EM is trying to connect to the
operating system to get information about the MSSQL service state, and your
Windows account doesn't have those permissions. If this isn't helpful, you
might consider posting the full error details from the log.
Simon