Link to home
Create AccountLog in
Avatar of weebruv
weebruv

asked on

Exchange 2003 error msgs

Hi

I have a client who has a multi server environment consisting of three servers.  I have an issue with the Microsoft Exchange 2003 sp2 server just now.  This server has Windows 2003 sp2 installed and is also a DC within the domain.  
I am getting the following errors in the logs

Event ID 1160
Database resource failure error Out of memory occurred in function JTAB_BASE::EcRetrieveColumnByPtagId while accessing the database "First Storage Group\Mailbox Store (Server_Name)"

Event ID 1159
Database error 0xfffffbbe occurred in function JTAB_BASE::EcConfig while accessing the database "First Storage Group\Mailbox Store (Server_Name)".

My client has Veritas Backup Exec 9.1 installed on the server as well and the backup fails when trying to backup a users mailbox, error This file cannot verify. Database or database element is corrupt.  When this happens the server needs to be rebooted.

I have looked at the errors and the /3GB and /USERVA boot.ini change is not recommended by Microsoft on a server that has AD installed, which the server is.

Does anyone have any ideas?
Avatar of abhaigh
abhaigh
Flag of United Kingdom of Great Britain and Northern Ireland image

run dcpromo and demote the machine if possible to start with

Can you do that ?? I always understood that DCPromo is not supported on an Exchange Server either way. Also 3GB and userva=3030 should not be included in boot.ini on DCs

http://support.microsoft.com/kb/822179
 
looks like I sit corrected on that point - however I did find this

https://www.experts-exchange.com/questions/22998567/Exchange-2003-store-exe-out-of-memory.html

it certainly looks quite relevant to your problem
Avatar of weebruv
weebruv

ASKER

John you are correct demoting the server is not a option also it is not recommended to use the 3Gb switch in the boot.ini file
http://support.microsoft.com/kb/815372
http://support.microsoft.com/kb/815372

Open in new window

Avatar of weebruv

ASKER

Resolved the problem.  It was down to the installation software being ina  location which only allowed Domain Admins access, when this was moved to another location everything worked
ASKER CERTIFIED SOLUTION
Avatar of ee_auto
ee_auto

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer