On November 18th 2011, I upgraded the memory on a SEP server 12.1.XXXX. Prior to this upgrade the server was running perfectly fine. Absolutely no problems whatsoever. This SEP installation was a "clean install" on a Windows 20008R2 server that is the Premium add-on to SBS 2011 Standard. It had been running for MONTHS perfectly fine! Need to make that clear. The original config of the server was 12GB in a HP DL360 G7. I had purchase 24GB of HP memory as per spec and added it to the server based on HP's memory upgrade procedures. The server was now running 36GB of memory. The initial memory modules were 2GB and the added modules were 4GB.
I performed the upgrade at 4:30am in the morning. As per my normal procedure for the next few days after an upgrade I look over the server and make sure that all services provided by the server run fine. Unfortunately 3 days later I noticed that the client computers at this location were not updating the anti virus definitions. I then noticed that the hard drive had lost a considerable amount of hard drive space and found that the SQLA0000.tmp file in the temp directory was 180 GB.
Further investigation proved unequivocally that this file was created at 4:30am on the same morning that I installed the extra memory. Since that time the file had grown to the 180 GB. All other issues as mentioned in other articles were the same a) processor stays constant at 18% used by dbsrv11.exe which is the SQL ANYWHERE server (which I believe has a db size limitation)
Taking out the memory and returning the server back to 12GB based solved the issue. This is not a real resolve as I need the extra memory. Now I have to make that dreaded call to Symantec only to get the run around as they probably will not have a fix.
Hopefully this can shed some light on the issue for Symantec so they can solve this issue.
TigerBytes how much memory do have in these servers?