Headquarters Error

Server 1 Windows Server 2003 SP2 SQL Server 2000 EE SP4 4 GB RAM 160 GB HDD

Server 2 Windows Server 2003 SP2 Headquarters Server 1.3.1011 Headquarters Client 1.3.1011 2 GB Ram 80 GB HDD

The SO database and the Headquarters database are both housed on Server 1. The SO database is 4.4 GB and the Headquarters database is 1.4 GB. I have tried running the Worksheet 401 multiple times and keep getting the error at the same point. I have attached the log file.

Any Help would be greatly appreciated.

Ted Archer snipped-for-privacy@fairvilla.com

Reply to
Ted Archer
Loading thread data ...
1) First check and make sure all of your hard drives have space available on them. 2) SQL Server 2000. are you using the free desktop engine or is this a fully functional version? The free desktop engine will have a 2gig database limit.

the first areas i would check would be available hard drive space, and what limitations the SQL Server will have with your database sizes.

Does this error happen on all 401 worksheets for all locations? or just for one particular store?

Reply to
Andy Miller - R

Andy,

First, let me say thank you for responding to my post. Let me answer your questions in order:

1) My SQL Server has 118 GB free space and my Headquarters Server has 22.3 GB free space. The Store Operations database that I am running the 401 Worksheet against is 4.4 GB. I should have enough free space.

2) I am using SQL Server Enterprise Edition, so there is no 2 GB database limit to worry about.

I have SQL Server set to allow automatic growth of the database and there is no database maximum size limit set, so the only limit is my 118 GB of free disk space.

The error only occurs on one location, the 401 worksheet runs fine on the other two locations I have defined. The one location where the error is occurring is the site I used for creating my master database in Headquarters... go figure !?!

I attached the log, and it looks like data is extracted from all of the SO tables and then the updating to HQ starts and that is when the error occurs.

I am willing to try any and all suggestions to try to get this to work.

Thanks again for your response,

Ted Archer

Reply to
Ted Archer

You will also want to make sure the HQ Client computer has enough disk space. it will write log files and temporary files onto that local hard drive during the 401.

It seems you have already done all the necessary research for the typical space issues.

I don't think I'm going to be able to be much more help than that. You may need to open a case with microsoft. If you have a valid maintenance contract with microsoft you might have incidents available to use up. If you do find the solution, I'd be interested in hearing what you found. Good Luck.

Reply to
Andy Miller - R

I have Headquarters Server and Client running on the same server, it has

22.3 GB free disk space.

I'll open a ticket with Microsoft and then post the response for anyone else who runs into this problem to have a resolution.

Thanks,

Ted Archer

Reply to
Ted Archer

Does anyone know how to resolve the following Headquarters error: Error 7: Not enough storage is available to complete this operation. (Unhandled Error, state = '9')

I received the error while running a Worksheet 401. My environment is the following:

Server 1 Windows Server 2003 SP2 SQL Server 2000 EE SP4 4 GB RAM 160 GB HDD

Server 2 Windows Server 2003 SP2 Headquarters Server 1.3.1011 Headquarters Client 1.3.1011 2 GB Ram 80 GB HDD

The SO database and the Headquarters database are both housed on Server 1. The SO database is 4.4 GB and the Headquarters database is 1.4 GB. I have tried running the Worksheet 401 multiple times and keep getting the error at the same point. I have attached the log file.

Any Help would be greatly appreciated.

Ted Archer snipped-for-privacy@fairvilla.com

Reply to
cptsoft

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\MemoryManagement

NOTE: Make sure to backup your registry by going to File then Export before doing any changes.

This value should be set to zero. If it isn't, try changing the value and see if that helps.

I performed the steps above and the problem was resolved. I'm not sure exactly which step fixed the problem, but I do know it was not step 4 (the value was already set at 0). I hope this helps anyone else who encounters this error in the future.

Ted Archer

snipped-for-privacy@fairvilla.com

Reply to
Ted Archer

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.