jseadrew
asked on
Exchnage Offline Address Book and Global Address List
Hi, I have been tossed into and exchnage environment and don't have much knowledge of it. I have been in IT for 10 years and 6 of those I worked with Lotus Notes. I have a few minor issues with the OAB and the GAL in Exchange.
To explain the sitiuation I am working with Exchnage 2003 on a Windows 2003 server. I have a SBS domian controller that is also riunning Windows 2003 Server that at one time did host exchange. I guess some parts of exchange are still on the SBS and this could be my problem. A company that we are no longer using came out to rebuild the RAID on the SBS, it did not go well and windows had to recover several thosand files before the server came back up. Since then Exchange has not worked right. I used to have a SBS store that was mounted but now and this is the issue the store is not and will not mount. So I have an Exchange server and a SBS server listed in the ESM under servers.
First, users are not getting GAL updates for newly created users. I had to manually delete OAB files from the users laptop and send and recieve to get updates. I am getting this error on the exchange server. "Error updating public folder with free busy information on VM Exchange. Error 0x80004005.
Second, users are getting errors when they send and receive for the OAB. "Task Exchange Serve reported error (0x8004010F) The operation failed. An object could not be found." I have opened ESM and tried to rebuild and set the OAB to the new default but the error persist.
Third users are slowly starting to have problems connecting to exchange while using the VPN. I added the DC and exchange server to the local host file and that seemed to work but I am wonderign if I need to check other places for the cause.
I am pretty sure most of these issues are related so any help would be greatly appreciated. I am new to this site so If I need to break this into three seperate threads I can. Thanks for any help!
To explain the sitiuation I am working with Exchnage 2003 on a Windows 2003 server. I have a SBS domian controller that is also riunning Windows 2003 Server that at one time did host exchange. I guess some parts of exchange are still on the SBS and this could be my problem. A company that we are no longer using came out to rebuild the RAID on the SBS, it did not go well and windows had to recover several thosand files before the server came back up. Since then Exchange has not worked right. I used to have a SBS store that was mounted but now and this is the issue the store is not and will not mount. So I have an Exchange server and a SBS server listed in the ESM under servers.
First, users are not getting GAL updates for newly created users. I had to manually delete OAB files from the users laptop and send and recieve to get updates. I am getting this error on the exchange server. "Error updating public folder with free busy information on VM Exchange. Error 0x80004005.
Second, users are getting errors when they send and receive for the OAB. "Task Exchange Serve reported error (0x8004010F) The operation failed. An object could not be found." I have opened ESM and tried to rebuild and set the OAB to the new default but the error persist.
Third users are slowly starting to have problems connecting to exchange while using the VPN. I added the DC and exchange server to the local host file and that seemed to work but I am wonderign if I need to check other places for the cause.
I am pretty sure most of these issues are related so any help would be greatly appreciated. I am new to this site so If I need to break this into three seperate threads I can. Thanks for any help!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi, I ran the best practices tool on both servers. Basically the SBS really had no errors. The exchange server had several replica errors for the OAB 2 - 3a - 4. I think some data on the RAID was corrupt during the attemted rebuild and has to be rebuilt some way. I'm getting several errors when i try to mount the store on the SBS. If I could get this store to mount I think my problems would go away.
The MAPI call 'OpenMsgStore' failed with the following error:
The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.
The MAPI provider failed.
Microsoft Exchange Server Information Store
ID no: 8004011d-0526-00000000
The MAPI call 'OpenMsgStore' failed with the following error:
The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.
The MAPI provider failed.
Microsoft Exchange Server Information Store
ID no: 8004011d-0526-00000000
There can be lots of reasons for that error. It could be as simple as Outlook installed on the server, which I see so many times. To replicate the system folders you need to get the store mounted. otherwise it is a pain because the system folders have to be recreated.
Simon.
Simon.
ASKER
Thank you very much for your reply!!!