Program too big to fit into memory

[AJZnSD]

Hey Guys,

I am running vmware ESX 2.5, I have created two virtual 2003 servers via a template.

Both VM’s have the same resources allocated dual 3.4 xeon and one gb of ram. I was successful at installing SQL 2k on the first box.

When I try to kick off the installation on the second server I get a dos window that pops up briefly with the following error “Program too big to fit into memory”.

The installation never starts this error pops up before the splash screen.

Can anyone shed some light on this or point me in the right direction?

Thanks,
AJZ

 

[Cstorms]

I know you said template but do you have enough RAM allocated to that VM, maybe its set to low? Shot in the dark. Good luck.

 

[WhoKilledKenny]

Describe your ESX environment... total RAM, Total CPU, Number of ESX hosts. Is it an ESX Cluster resource?

 

[w33mhz]

it sounds like to me you need to allocate more memory to that machine and I would also check your reg size as well sometimes that will mess with you and you will need to bump it up. I recommend if you are just starting the ESX host out, reinstall with ESX 3.0.1 your life will be easier.

 

[AJZnSD]

It is a ESX 2.5.2 cluster with 5 physical servers running dual 3.4 Xeon’s and 8 GB of ram. The ESX server that is hosting the VM I am working with is far from maxed total CPU utilization hasn’t exceeded 50% memory has not exceeded 60% of the total resources. I have also vmotioned the VM from one esx box to another with the same results. As far as the ram I bumped it up to 2 GB without success.

Thanks,
AJZ

 

[WhoKilledKenny]

The reason you are creating two SQL VMs? By chance are you trying to build an MS Cluster? Sorry I'm a little lost at "When I try to kick off the installation on the second server." Installation of on OS or SQL?

 

[AJZnSD]

Sorry for the confusion….. We are running vmware I created two virtual machines (VM) from a 2k3 template.

One machine is going to be the SQL DB, which installed without a problem.

The second VM needs to have MS SQL Network Utilities installed on it.

The problem described above is the error I get when I attempted to launch autorun or setupsql.exe.

AJZ

 

[w33mhz]

Whoops my bad 2k3 doesn't have the reg size feature like Win2k does. How are you installing SQL? from an actual CD or an ISO? Or did you copy the install on to the machine. Sometimes if any of the installation files are corupt it you could recieve such a message. What is the size of you page file, have you tried to increase that as well. What is the actual memory usage on the machine (via windows not Virtual Center). It doesn't sound like an issue with the VMWare side.

 

[AJZnSD]

I was trying to install from an ISO image. I gave up and created a new template.

Once I deployed the new template I was able install the application from the original ISO.

My only guess is the template became corrupted after the first image was deployed.

Thanks for the input guys,
AJZ

 

[WhoKilledKenny]

Did you copy the ISO file from a windows box to the ESX server using WinSCP3 Utilily? If so, go to the VMFS volume where the ISO is located. You may see a strange extention on the file, like SQL.iso.xxx. Just do a move command on ESX to fix the file extention - #mv SQL.iso.xxx SQL.iso