Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

beserver.exe claims memory

Updated: 22 May 2010 | 8 comments
Jürgen Eisenbarth's picture
0 0 Votes
Login to vote

We have installed BE11d on a Windows Server 2003 Std. 64-bit with Service Pack 1. The process "beserver.exe" claims to much memory. We have 8 GByte RAM on this server. The process "beserver.exe" claims 7GByte memory.
Does anybody know this problem?

regards
j�

Comments

Gauri Ketkar's picture
20
Nov
2006
0 Votes 0
Login to vote

Hi,

-- Is this windows R2 Server ?
-- Do you get any Alert in BE ?
-- Check for any relevant Event IDs



Update us on the same ..



Thank you
Gauri

Steve Broomell's picture
20
Nov
2006
0 Votes 0
Login to vote

I don't know what caused it but here is a helpful hint to find out.

1. Bring up the task manager and look at the processes tab while following the following steps.
2. Restart the Backup Exec services (this will show you the base mem usage for BEServer). Mine is around 78megs)
3. Watch BEServer as you perform tasks in Backup Exec

Jürgen Eisenbarth's picture
22
Nov
2006
0 Votes 0
Login to vote

Hi,

it is windows R2 with Service-Pack 1.

We have no alerts in BE.

We have the same problem on a second server with Windows Server Std. R2 64bit and Backup Exec 11d 64bit. The beserver.exe claims to much memory.

We have testet BE11d 32bit on a windows server 2003 R2 32bit. The beserver claims 78MByte memory and remains constant.

Thank you
Juergen Eisenbarth

tejashree Bhate's picture
01
Dec
2006
0 Votes 0
Login to vote

Hello,

You may refer to the following technote to repair the Backup Exec database

(title)How to run a Backup Exec database repair when the original Backup Exec database is found to be inconsistent

http://support.veritas.com/docs/265180

Thanks.

Frederik Muth's picture
25
Jun
2007
0 Votes 0
Login to vote

I have also the same problem, running 2003R2 x64-Server and BE 11d
 
after repairin the database the problem was not resolved!
 
any ideas?
 
thx in advance!!
Frederik Muth's picture
09
Aug
2007
0 Votes 0
Login to vote

Finally, we resolve the problem :womanvery-happy:
 
Check out if the following path exist:

C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files

 

If not, create the tmp-folder and restart the be services!!

Tim Line's picture
06
Nov
2007
0 Votes 0
Login to vote

Hi all, i thought i'd drag this one up again!

We are having a similar problem, i've been through and re-created the folder 'Temporary ASP.NET Files' but the problem still remains. I have also reinstalled the microsoft reporting tool...i'm now at a loss

cheers

Tim Line's picture
06
Nov
2007
0 Votes 0
Login to vote