[chef] RE: RE: RE: RE: Issues with SQL Server 2008 R2 Recipe

["Vinayak, Gaurav" < >]

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:
 
 
Sent: 06 June 2014 21:23
To: Vinayak, Gaurav; 

 
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:
 
Sent: Friday, June 6, 2014 2:30 AM
To: 

 ;
 

 
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:
 
Sent: 05 June 2014 23:11
To: 

 ;
 

 
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 
<
 >
Sent: Thursday, June 5, 2014 8:56 AM
To: 

 
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:
 
Sent: Thursday, June 5, 2014 12:04 AM
To: 

 
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