Issues with SQL Server 2008 R2 Recipe


#1

Guys,

I am using the latest version of SQL Server Cookbook i.e. 2.2 on the chef
community & the chef-client version is 11.12.4.

Issue:

Even after successful execution of the recipe & i don’t get to see the SQL
Server Installed on the target box whereas IIS got installed flawlessly.

I am using the knife windows plugin for bootstrapping.

Target Box OS - Win 2008 R2 64-Bit.

Anybody faced similar issue or can advise what’s wrong here?

Regards,
Gaurav Vinayak


#2

Gaurav, do you have a log from the Chef run? That would point to clues.
One issue I’ve seen with sql server is that it uses a lot of memory (it
will basically allocate as much memory as physical ram on your system for
performance reasons), and since knife-windows is executing over winrm, you
can run afoul of WinRM’s memory restrictions. You could try setting
maxmemorypershellmb to something huge, say larger than physical ram on the
system.

Thanks.

-Adam

-----Original Message-----
From: Vinayak [mailto:gaurav.vinayak@netapp.com]
Sent: Thursday, June 5, 2014 12:04 AM
To: chef@lists.opscode.com
Subject: [chef] Issues with SQL Server 2008 R2 Recipe

Guys,

I am using the latest version of SQL Server Cookbook i.e. 2.2 on the chef
community & the chef-client version is 11.12.4.

Issue:

Even after successful execution of the recipe & i don’t get to see the SQL
Server Installed on the target box whereas IIS got installed flawlessly.

I am using the knife windows plugin for bootstrapping.

Target Box OS - Win 2008 R2 64-Bit.

Anybody faced similar issue or can advise what’s wrong here?

Regards,
Gaurav Vinayak


#3

Thanks for responding Adam!

Please find attached the logs for chef client run & also the winrm configuration parameter.

Regards,
Gaurav


From: Adam Edwards adamed@getchef.com
Sent: Thursday, June 5, 2014 8:56 AM
To: chef@lists.opscode.com
Subject: [chef] RE: Issues with SQL Server 2008 R2 Recipe

Gaurav, do you have a log from the Chef run? That would point to clues.
One issue I’ve seen with sql server is that it uses a lot of memory (it
will basically allocate as much memory as physical ram on your system for
performance reasons), and since knife-windows is executing over winrm, you
can run afoul of WinRM’s memory restrictions. You could try setting
maxmemorypershellmb to something huge, say larger than physical ram on the
system.

Thanks.

-Adam

-----Original Message-----
From: Vinayak [mailto:gaurav.vinayak@netapp.com]
Sent: Thursday, June 5, 2014 12:04 AM
To: chef@lists.opscode.com
Subject: [chef] Issues with SQL Server 2008 R2 Recipe

Guys,

I am using the latest version of SQL Server Cookbook i.e. 2.2 on the chef
community & the chef-client version is 11.12.4.

Issue:

Even after successful execution of the recipe & i don’t get to see the SQL
Server Installed on the target box whereas IIS got installed flawlessly.

I am using the knife windows plugin for bootstrapping.

Target Box OS - Win 2008 R2 64-Bit.

Anybody faced similar issue or can advise what’s wrong here?

Regards,
Gaurav Vinayak


#4

One thing that I have noticed is that that the recipe is unable to create the required SQL Server Service on the target machine.

I can see the SQL server package there though.

Thanks & Regards,

Gaurav Vinayak
IT Strategic Innovation Services
NetApp, Inc.
it.netapp.com
cloud.it.netapp.com
office: 91 120 244 5144 ext 4503
mobile: 408-355-6052, 91-99104-33692
Gaurav.Vinayak@netapp.com

nCloud FAQ
nCloud User Manual

-----Original Message-----
From: Vinayak, Gaurav [mailto:Gaurav.Vinayak@netapp.com]
Sent: 05 June 2014 23:11
To: chef@lists.opscode.com; adamed@getchef.com
Subject: [chef] RE: RE: Issues with SQL Server 2008 R2 Recipe

Thanks for responding Adam!

Please find attached the logs for chef client run & also the winrm configuration parameter.

Regards,
Gaurav


From: Adam Edwards adamed@getchef.com
Sent: Thursday, June 5, 2014 8:56 AM
To: chef@lists.opscode.com
Subject: [chef] RE: Issues with SQL Server 2008 R2 Recipe

Gaurav, do you have a log from the Chef run? That would point to clues.
One issue I’ve seen with sql server is that it uses a lot of memory (it will basically allocate as much memory as physical ram on your system for performance reasons), and since knife-windows is executing over winrm, you can run afoul of WinRM’s memory restrictions. You could try setting maxmemorypershellmb to something huge, say larger than physical ram on the system.

Thanks.

-Adam

-----Original Message-----
From: Vinayak [mailto:gaurav.vinayak@netapp.com]
Sent: Thursday, June 5, 2014 12:04 AM
To: chef@lists.opscode.com
Subject: [chef] Issues with SQL Server 2008 R2 Recipe

Guys,

I am using the latest version of SQL Server Cookbook i.e. 2.2 on the chef community & the chef-client version is 11.12.4.

Issue:

Even after successful execution of the recipe & i don’t get to see the SQL Server Installed on the target box whereas IIS got installed flawlessly.

I am using the knife windows plugin for bootstrapping.

Target Box OS - Win 2008 R2 64-Bit.

Anybody faced similar issue or can advise what’s wrong here?

Regards,
Gaurav Vinayak


#5

So two things:

  1. You should try setting MaxMemoryPerShellMb to something really big,
    e.g. 32G
  2. Do you have PowerShell 3.0 on the system? You might be hitting this
    issue: https://tickets.opscode.com/browse/CHEF-4971, which can be fixed
    with a patch from Microsoft. The issue there is that the
    MaxMemoryPerShellMb memory limitation override is ignored, causing
    memory-intensive applications like sql server to fail, particularly at
    times like service start. I believe upgrading to PowerShell 4.0 or later
    might also fix it.

-Adam

-----Original Message-----
From: Vinayak, Gaurav [mailto:Gaurav.Vinayak@netapp.com]
Sent: Friday, June 6, 2014 2:30 AM
To: chef@lists.opscode.com; adamed@getchef.com
Subject: RE: [chef] RE: RE: Issues with SQL Server 2008 R2 Recipe

One thing that I have noticed is that that the recipe is unable to create
the required SQL Server Service on the target machine.

I can see the SQL server package there though.

Thanks & Regards,

Gaurav Vinayak
IT Strategic Innovation Services
NetApp, Inc.
it.netapp.com
cloud.it.netapp.com
office: 91 120 244 5144 ext 4503
mobile: 408-355-6052, 91-99104-33692
Gaurav.Vinayak@netapp.com

nCloud FAQ
nCloud User Manual

-----Original Message-----
From: Vinayak, Gaurav [mailto:Gaurav.Vinayak@netapp.com]
Sent: 05 June 2014 23:11
To: chef@lists.opscode.com; adamed@getchef.com
Subject: [chef] RE: RE: Issues with SQL Server 2008 R2 Recipe

Thanks for responding Adam!

Please find attached the logs for chef client run & also the winrm
configuration parameter.

Regards,
Gaurav


From: Adam Edwards adamed@getchef.com
Sent: Thursday, June 5, 2014 8:56 AM
To: chef@lists.opscode.com
Subject: [chef] RE: Issues with SQL Server 2008 R2 Recipe

Gaurav, do you have a log from the Chef run? That would point to clues.
One issue I’ve seen with sql server is that it uses a lot of memory (it
will basically allocate as much memory as physical ram on your system for
performance reasons), and since knife-windows is executing over winrm, you
can run afoul of WinRM’s memory restrictions. You could try setting
maxmemorypershellmb to something huge, say larger than physical ram on the
system.

Thanks.

-Adam

-----Original Message-----
From: Vinayak [mailto:gaurav.vinayak@netapp.com]
Sent: Thursday, June 5, 2014 12:04 AM
To: chef@lists.opscode.com
Subject: [chef] Issues with SQL Server 2008 R2 Recipe

Guys,

I am using the latest version of SQL Server Cookbook i.e. 2.2 on the chef
community & the chef-client version is 11.12.4.

Issue:

Even after successful execution of the recipe & i don’t get to see the SQL
Server Installed on the target box whereas IIS got installed flawlessly.

I am using the knife windows plugin for bootstrapping.

Target Box OS - Win 2008 R2 64-Bit.

Anybody faced similar issue or can advise what’s wrong here?

Regards,
Gaurav Vinayak


#6

Hi Adam,

Thanks for responding back. I’ll work on the solution provided & will let you know the output.

FYI,
I was able to install the SQL Server by manually calling the chef-client on the target box.

Regards,
Gaurav Vinayak

-----Original Message-----
From: Adam Edwards [mailto:adamed@getchef.com]
Sent: 06 June 2014 21:23
To: Vinayak, Gaurav; chef@lists.opscode.com
Subject: [chef] RE: RE: RE: Issues with SQL Server 2008 R2 Recipe

So two things:

  1. You should try setting MaxMemoryPerShellMb to something really big, e.g. 32G 2. Do you have PowerShell 3.0 on the system? You might be hitting this
    issue: https://tickets.opscode.com/browse/CHEF-4971, which can be fixed with a patch from Microsoft. The issue there is that the MaxMemoryPerShellMb memory limitation override is ignored, causing memory-intensive applications like sql server to fail, particularly at times like service start. I believe upgrading to PowerShell 4.0 or later might also fix it.

-Adam

-----Original Message-----
From: Vinayak, Gaurav [mailto:Gaurav.Vinayak@netapp.com]
Sent: Friday, June 6, 2014 2:30 AM
To: chef@lists.opscode.com; adamed@getchef.com
Subject: RE: [chef] RE: RE: Issues with SQL Server 2008 R2 Recipe

One thing that I have noticed is that that the recipe is unable to create the required SQL Server Service on the target machine.

I can see the SQL server package there though.

Thanks & Regards,

Gaurav Vinayak

-----Original Message-----
From: Vinayak, Gaurav [mailto:Gaurav.Vinayak@netapp.com]
Sent: 05 June 2014 23:11
To: chef@lists.opscode.com; adamed@getchef.com
Subject: [chef] RE: RE: Issues with SQL Server 2008 R2 Recipe

Thanks for responding Adam!

Please find attached the logs for chef client run & also the winrm configuration parameter.

Regards,
Gaurav


From: Adam Edwards adamed@getchef.com
Sent: Thursday, June 5, 2014 8:56 AM
To: chef@lists.opscode.com
Subject: [chef] RE: Issues with SQL Server 2008 R2 Recipe

Gaurav, do you have a log from the Chef run? That would point to clues.
One issue I’ve seen with sql server is that it uses a lot of memory (it will basically allocate as much memory as physical ram on your system for performance reasons), and since knife-windows is executing over winrm, you can run afoul of WinRM’s memory restrictions. You could try setting maxmemorypershellmb to something huge, say larger than physical ram on the system.

Thanks.

-Adam

-----Original Message-----
From: Vinayak [mailto:gaurav.vinayak@netapp.com]
Sent: Thursday, June 5, 2014 12:04 AM
To: chef@lists.opscode.com
Subject: [chef] Issues with SQL Server 2008 R2 Recipe

Guys,

I am using the latest version of SQL Server Cookbook i.e. 2.2 on the chef community & the chef-client version is 11.12.4.

Issue:

Even after successful execution of the recipe & i don’t get to see the SQL Server Installed on the target box whereas IIS got installed flawlessly.

I am using the knife windows plugin for bootstrapping.

Target Box OS - Win 2008 R2 64-Bit.

Anybody faced similar issue or can advise what’s wrong here?

Regards,
Gaurav Vinayak


#7

Yes, it’s often the case that the manual Chef run works outside of WinRM,
but things don’t work with WinRM due to the issues I highlighted, so that at
least is consistent.

-----Original Message-----
From: Vinayak, Gaurav [mailto:Gaurav.Vinayak@netapp.com]
Sent: Tuesday, June 10, 2014 8:36 AM
To: adamed@getchef.com; chef@lists.opscode.com
Subject: RE: [chef] RE: RE: RE: Issues with SQL Server 2008 R2 Recipe

Hi Adam,

Thanks for responding back. I’ll work on the solution provided & will let
you know the output.

FYI,
I was able to install the SQL Server by manually calling the chef-client on
the target box.

Regards,
Gaurav Vinayak

-----Original Message-----
From: Adam Edwards [mailto:adamed@getchef.com]
Sent: 06 June 2014 21:23
To: Vinayak, Gaurav; chef@lists.opscode.com
Subject: [chef] RE: RE: RE: Issues with SQL Server 2008 R2 Recipe

So two things:

  1. You should try setting MaxMemoryPerShellMb to something really big, e.g.
    32G 2. Do you have PowerShell 3.0 on the system? You might be hitting this
    issue: https://tickets.opscode.com/browse/CHEF-4971, which can be fixed with
    a patch from Microsoft. The issue there is that the MaxMemoryPerShellMb
    memory limitation override is ignored, causing memory-intensive applications
    like sql server to fail, particularly at times like service start. I believe
    upgrading to PowerShell 4.0 or later might also fix it.

-Adam

-----Original Message-----
From: Vinayak, Gaurav [mailto:Gaurav.Vinayak@netapp.com]
Sent: Friday, June 6, 2014 2:30 AM
To: chef@lists.opscode.com; adamed@getchef.com
Subject: RE: [chef] RE: RE: Issues with SQL Server 2008 R2 Recipe

One thing that I have noticed is that that the recipe is unable to create
the required SQL Server Service on the target machine.

I can see the SQL server package there though.

Thanks & Regards,

Gaurav Vinayak

-----Original Message-----
From: Vinayak, Gaurav [mailto:Gaurav.Vinayak@netapp.com]
Sent: 05 June 2014 23:11
To: chef@lists.opscode.com; adamed@getchef.com
Subject: [chef] RE: RE: Issues with SQL Server 2008 R2 Recipe

Thanks for responding Adam!

Please find attached the logs for chef client run & also the winrm
configuration parameter.

Regards,
Gaurav


From: Adam Edwards adamed@getchef.com
Sent: Thursday, June 5, 2014 8:56 AM
To: chef@lists.opscode.com
Subject: [chef] RE: Issues with SQL Server 2008 R2 Recipe

Gaurav, do you have a log from the Chef run? That would point to clues.
One issue I’ve seen with sql server is that it uses a lot of memory (it will
basically allocate as much memory as physical ram on your system for
performance reasons), and since knife-windows is executing over winrm, you
can run afoul of WinRM’s memory restrictions. You could try setting
maxmemorypershellmb to something huge, say larger than physical ram on the
system.

Thanks.

-Adam

-----Original Message-----
From: Vinayak [mailto:gaurav.vinayak@netapp.com]
Sent: Thursday, June 5, 2014 12:04 AM
To: chef@lists.opscode.com
Subject: [chef] Issues with SQL Server 2008 R2 Recipe

Guys,

I am using the latest version of SQL Server Cookbook i.e. 2.2 on the chef
community & the chef-client version is 11.12.4.

Issue:

Even after successful execution of the recipe & i don’t get to see the SQL
Server Installed on the target box whereas IIS got installed flawlessly.

I am using the knife windows plugin for bootstrapping.

Target Box OS - Win 2008 R2 64-Bit.

Anybody faced similar issue or can advise what’s wrong here?

Regards,
Gaurav Vinayak