Exchange 2003 Event logs errors

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Hi all

Hope you can help with this getting these errors in the event log on my Exchange 2003 server and it is stopping the RUS from updating the Global Address List with new users


cheers
Mick

I have a single-server Exchange 2003 enviornment. In the app log of
the server I am getting the following recurring errors:

Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 2037
Date: 10/6/2004
Time: 9:26:46 AM
User: N/A
Computer: MAIL1
Description:
The file version of '\address\FAX\i386\ZFProxy.dll' installed on the
local server is not current. Unable to locate a correct version on any
server in the site.

Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 2027
Date: 10/6/2004
Time: 9:26:46 AM
User: N/A
Computer: MAIL1
Description:
Unable to generate the e-mail address. Unable to load address module
'E:\Program Files\Exchsrvr\address\ FAX\i386\ZFProxy.dll' for address
type 'smtp'. Error 0xc007007e.

Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8231
Date: 10/6/2004
Time: 9:26:46 AM
User: N/A
Computer: MAIL1
Description:
Permanent failure reported by policy group provider for 'CN=Recipient
Policies,CN=NCA,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=********,DC=org':'MAD.EXE',
error=8000ffff. Taking provider offline.


Research led me to MS KB article 286356
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q286356

but here is the problem - the directory E:\program
files\exchsvr\address\FAX\i386\ does not exist on my server. To be
more clear, the path exists up until 'address', but there is no FAX
folder in there. I'm a little confused by what may have caused this.
I appreciate all suggestions.

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

I just checked my Exchange server in VMware and I don't have that directory either. It appears to be something that's added after Exchange.

 

Go to www.eventid.net and search for your eventid numbers from their home page. After you do one search you'll be able to add the Source to your searches too. It's one of the best resources around for researching Event Viewer errors.

 

Hi Guys


been to eventid already and checked the errors and followed the recommended steps

think it is something that was installed on the old 5.5 server and the ADC has copied it over to the 2000 server then when the ADC was removed it was left

Although there was never a problem until upgrading to 2003 thats when the error started

it's looking for the folder and file stated but its not there and i dont have the dll file to replace it with


does anyone have that single dll file ?

rather than having to install it on another pc then copy the file to the replaced directory structure ??

 

tried contacting MS/google for it?

 

Anybody got any more thoughts on this ?

 

Did you delve into this solution as mentioned in the article?

Sounds like a nightmare but that is not unusual

 

tried removing the entries so that RUS doesnt try to load the dll but without success


any more ideas this is a getting desperate now

 

Hi All


Just back to work after being off for a week and while trying to get a solution to this problem i have managed it thank god for Virtual PC

installed a windows 2000 server on virtual pc installed Exchange 5.5 (as this is where the file had been copied from when the old ADC connector had been in place)

installed Zetafax connector for Exchange 5.5 this recreated the folder structure and missing dll file then copied and pasted this onto my usb key and copied onto the Live Exchange server

Clicked rebuild the RUS and then started the system attendant and hey presto the addresses appeared in the default address book


woo hoo all sorted

 

Nice work mojorisin!

I didn't study Exchange as part of my MCSE but I do run it at home. From my limited experience, I already know it can be an absolute bear sometimes. Great when it works but try migrating it and all hell breaks lose.

You did well to sort this, congrats mate!

 

Cheers for the congrats bluerinse always nice when you can get something working again

great to start back to my week that was i can tell you (phew)